01:01.10 | yukonbob | brlcad: re: gsoc -- we need to have a front-and-center permalink to the GSOC wiki on the main website... |
01:01.39 | yukonbob | re: mentoring -- I'd consider helping however I can... |
01:09.55 | *** join/#brlcad BigAToo (n=BigAToo@pool-96-230-124-61.sbndin.btas.verizon.net) |
01:22.25 | brlcad | yukonbob: was planning on adding a news item if we get accepted, but yeah, it would be nice to have a better more visible link |
01:27.41 | yukonbob | nods... |
01:29.06 | yukonbob | brlcad: I'm -=happy=- to help however I can, if you (or anybody else) thinks I can assist. |
01:31.37 | yukonbob | my sched is pretty booked, but, as I said, if I can help, let me know how. |
01:31.51 | yukonbob | (re: booked -- full time work :P ) |
01:36.24 | yukonbob | starseeker: fwiw, I don't think the wheel should have the 'schematics' in the background 'bleed-through' it; ie: turn the transparency in the wheel assembly off. (on my $0.02). |
01:36.28 | yukonbob | *only my |
01:41.55 | starseeker | brlcad: sure, one sec |
01:42.35 | starseeker | yukonbob: there are a few ways to do it - I was going for the "fade" from design to reality |
01:42.52 | yukonbob | starseeker: hi :) |
01:42.56 | starseeker | howdy :-) |
01:43.13 | yukonbob | I see the fade from wireframe -> "reality", and I like it. |
01:43.32 | starseeker | let me get the core images up for brlcad quick |
01:43.33 | yukonbob | what I'm talking about is the subtle "schematics" in the background showing through the "real" rim |
01:43.51 | starseeker | you mean the moko schematics? |
01:44.05 | yukonbob | I guess so :) |
01:44.16 | brlcad | yukonbob: I'm sure you can assist (e.g., could be a backup mentor again, could work on that visible link) |
01:44.30 | brlcad | could also work on the ideas page |
01:44.40 | yukonbob | hey brlcad : |
01:44.43 | yukonbob | :) |
01:44.50 | brlcad | that needs to be separated into two categories -- high priority and secondary (or something similar) |
01:44.54 | brlcad | hi :) |
01:45.33 | brlcad | also could use some more items, few refactoring code cleanup tasks would be good |
01:46.01 | yukonbob | would toss "convert bwish to a "standard wish/tlcsh loadable module" |
01:46.04 | yukonbob | into that list. |
01:46.22 | yukonbob | *wish/tclsh |
01:46.36 | brlcad | sure, go for it |
01:49.17 | starseeker | brlcad: here you go: http://bzflag.bz/~starseeker/gsoc/ |
01:50.13 | starseeker | let me know if you want the non-transparent version of the tire |
02:03.57 | yukonbob | will add to bwish to wiki list tonight, and look at organizing whole list...; am now in transit. |
02:08.15 | brlcad | starseeker: could use a bigger tire |
02:08.27 | brlcad | yukonbob: cool, thx |
02:09.08 | brlcad | we have to have the list finalized by noon (EDT) |
02:09.23 | brlcad | that's when they'll review our app |
02:12.18 | dreeves | brlcad looking at extrude.c in librt in the rt_extrude_shot function it doesn't appear to ever free the memory for the normals that are allocated in the FindRoots function... |
02:17.14 | brlcad | dreeves: not surprising, that's a bit of code that is rarely ever used |
02:17.28 | brlcad | it shouldn't be allocating memory at all |
02:17.44 | brlcad | calling a malloc in the middle of a ray shot is very bad |
02:17.46 | dreeves | Yeah that is what I was looking into just to get my feet wet |
02:17.59 | brlcad | there's a todo entry to make it work without alloc |
02:18.05 | dreeves | I saw that on your list of things todo |
02:18.10 | brlcad | ah, cool |
02:19.52 | brlcad | if anything, it could batch them or preallocate during prep, but it really would be best to avoid allocation altogether to compute the roots |
02:20.32 | brlcad | and even better still to get an arbitrary degree curve polynomial root solver into libbn |
02:20.54 | brlcad | there is a polynomial solver in libbn, but is compile-time wired to a given max degree |
02:22.00 | dreeves | I was thinking in the prep function |
02:22.44 | dreeves | I'm thinking about it but seems like an arbitrary degree curve is what is standing in the way of getting rid of the alloc's |
02:24.16 | dreeves | obviously but I'm sure we once we know the degree of the curve we can pre allocate the memory but the problem is management of that memory that is what I'm working on right now |
02:24.52 | dreeves | I will go check out libbn |
02:28.56 | brlcad | starseeker: never mind, took care of it |
02:29.30 | brlcad | dreeves: yeah |
02:32.42 | brlcad | also, the solver in libbn probably isn't the right type or have the right stability conditions -- would take a bit of testing to verify its use |
02:38.10 | dreeves | Yeah I assume you are talking about the root solvers in poly.c so yeah those seem to be specialized cases of root finders not somuch I can adjust the max degree then recompile...I was going to experiment with the test case of the sketch to just call to that root finder vs the one findroots just to see the impact on performance but that's ok I think I can work with the find roots |
02:38.27 | starseeker | brlcad: just resize, or re-render? |
02:38.42 | brlcad | starseeker: never mind :) |
02:38.59 | brlcad | can you repost your last version? |
02:44.29 | starseeker | of the poster? uh, one sec... |
02:45.17 | brlcad | yeah |
02:46.43 | starseeker | http://bzflag.bz/~starseeker/gsoc/poster2a.png |
02:46.49 | starseeker | that one? |
02:48.44 | brlcad | yep, thanks |
02:57.28 | *** join/#brlcad Axman6 (n=Axman6@pdpc/supporter/student/Axman6) |
03:34.55 | brlcad | how about this? http://brlcad.org/~sean/tmp/brlcad_gsoc2009_poster.png |
03:47.06 | *** join/#brlcad madant_ (n=madant@117.196.129.20) |
03:56.04 | louipc | looks rustic |
04:11.54 | starseeker | brlcad: font's a bit hard to read, but looks good |
04:13.25 | brlcad | starseeker: which one? |
04:14.03 | starseeker | the "Interested in 3D CAD Software?" one |
04:15.01 | starseeker | but obviously my design chops are minimal - I would have cheerfully used the previous fonts ;-) |
04:16.06 | starseeker | I don't know how workable it is, but would it be possible to have an orange "fill color" in the brlcad.org/wiki/gsoc link, to match the logo next to it? |
04:18.20 | brlcad | nah, that's good feedback |
04:18.33 | brlcad | had the same inclination, but always good to hear it from others to confirm |
04:18.50 | brlcad | that's the point of getting a critique :) |
04:19.31 | starseeker | critiquing artwork probably comes under the "net negative producer" you studied in that management class, as a rule ;-) |
04:19.41 | brlcad | heh |
04:20.04 | starseeker | 's thought was that an "engineering" app should strive for a crisp, clean look... |
04:20.23 | starseeker | unfortuantely that's waaaay to easy to make into "default and boring" |
04:28.28 | brlcad | true, would normally go for that, but then the logo becomes even more distracting |
04:28.56 | brlcad | easier to follow that style than fight it given it's so distinct |
04:31.50 | *** join/#brlcad ashishrai (i=d2d43dfb@gateway/web/ajax/mibbit.com/x-ae59e4bdb9e611b6) |
04:40.40 | starseeker | fight the good fight! ;-) |
04:47.50 | brlcad | http://brlcad.org/~sean/tmp/brlcad_gsoc2009_poster2.png |
05:01.12 | starseeker | yeah, that works better :-) |
05:02.27 | starseeker | What do you think about the Google Summer of Code 2009... paragraph? does it need a non-white fill? I'm not sure, just asking |
05:21.15 | brlcad | hm, http://brlcad.org/~sean/tmp/brlcad_gsoc2009_poster3.png |
05:23.49 | starseeker | yeah, I like that |
05:23.54 | starseeker | that one gets my vote :-) |
05:25.12 | starseeker | brlcad: should the color bar fade ins be parallel to the tire fade in, or should the light sides be on the right? |
05:25.38 | starseeker | is wondering if the left side looks "washed out" if all the fading is on that side |
05:25.56 | starseeker | would mean the logo would be on the left though... |
05:25.58 | starseeker | hmm |
05:26.09 | brlcad | it washes out if there's too much transparency |
05:26.23 | brlcad | and it's unbalanced if it's just solid |
05:30.34 | dreeves | I got rid of the memory allocation from the root find but it only increased the speed by 30% is that what you would expect? or more increase? |
05:30.56 | starseeker | yeah, I think you've got it brlcad |
05:31.01 | starseeker | nice job |
05:37.36 | brlcad | dreeves: I would expect a fair bit more, but depends on how many bezier's are in the sketch |
05:37.56 | dreeves | just 1 |
05:38.12 | dreeves | It's the sketch you attached to the tracker |
05:41.00 | yukonbob | re: solid block in gsoc poster vs. fading block (and text fill-colour): too bad it's unbalanced... that block ("balance of poster" vs. text readability) is at odds with itself... |
05:41.14 | dreeves | I just focused on the root finder because I clocked it and it was taking about 93% of the overall time to raytrace |
05:41.58 | yukonbob | brlcad: do you have an example of the solid block, for comparison's sake? |
05:42.39 | yukonbob | if they're both (top and bottom) solid, does the poster look "out of balance"? |
05:44.13 | brlcad | dreeves: 93% sounds about right .. that's why I'd expect more than 30% if it drops to near zero |
05:47.04 | dreeves | ok drilled down into some of the funcs called from findRoots and noticed they are allocing mem to |
05:47.10 | dreeves | will work on those |
05:53.31 | brlcad | mallocs show up as a real hot spot on the profiler if they occur during any *_shot() evaluation (even once per ray) |
06:07.21 | brlcad | http://brlcad.org/~sean/tmp/brlcad_gsoc2009_poster4.png |
06:13.52 | yukonbob | brlcad: that looks better, imo. Here's what else I'd consider: Make the wheel assembly -not- transparent in any way; no 'bleeding' of the schematic through the wheel; the wheel simply fades across itself from wireframe to raytraced. The mask for the wheel is 100% (ie: solid) for everything that describes the wheel, but nothing that's blank. The bottom layer is the OpenMoko schematic, the middle layer are the bars&text (solid, or at least |
06:15.23 | yukonbob | The net effect would be the wheel covers everything, the bars are more solid (making the text more readable), and the openmoko gfx is showing in all other areas. |
06:15.53 | yukonbob | the mask for the wheel could be the image of the wheel itself, with some hand edits around the wireframe section on the left. |
06:17.02 | yukonbob | The mask would be a completely solid blob... (ie: the holes in the rim would show white, not openmoko gfx). |
06:19.19 | yukonbob | in fact... I think I'd adjust the mask for the wireframe to move the visibility left -- it looks like some of the wireframe hits the text in the top bar |
06:20.49 | yukonbob | would install GIMP if he wasn't in middle of re-building world |
06:20.59 | yukonbob | what's the due-date for this poster? |
06:23.13 | *** join/#brlcad dtidrow (n=Don@c-68-62-76-34.hsd1.mi.comcast.net) |
06:24.55 | brlcad | it's not worth spending a whole lot more time on, frankly |
06:25.03 | yukonbob | hehe |
06:25.04 | yukonbob | :) |
06:25.07 | brlcad | but technically, it's not "due" .. just good marketing |
06:25.13 | brlcad | after acceptance |
06:28.06 | yukonbob | is GIMP project? |
06:28.24 | brlcad | photoshop |
06:28.37 | yukonbob | ah |
06:28.51 | yukonbob | <-- not a photoshop person |
06:39.01 | brlcad | http://brlcad.org/~sean/tmp/brlcad_gsoc2009_poster5.png |
06:39.11 | brlcad | some of those ideas |
06:40.43 | brlcad | not quite as big a fan of the solid bars, though, fairly plain |
06:41.20 | brlcad | probably would work with a really light gradient, but I think it's at a good enough point for this year |
06:41.40 | brlcad | need to focus on the ideas list |
06:46.44 | yukonbob | I think you're right re: solid bars --- I like gradient in bottom bar of poster4, though... |
06:47.03 | yukonbob | keeps text more readable than other gradients. |
06:50.02 | yukonbob | Zzzzz |
06:52.08 | brlcad | agrees |
06:52.21 | brlcad | v4 it is |
06:59.20 | *** join/#brlcad Ralith (n=ralith@216.162.199.202) |
07:25.10 | CIA-40 | BRL-CAD: 03brlcad * r34041 10/brlcad/trunk/src/tclscripts/rtwizard/lib/ (MGEDpage.itk PictureTypeBase.itcl): |
07:25.10 | CIA-40 | BRL-CAD: implement support to actually utilize the perspective mode setting (apparently |
07:25.10 | CIA-40 | BRL-CAD: it was never wired up). this makes it work though there is still some quirk |
07:25.10 | CIA-40 | BRL-CAD: where you sometimes need to display one of the other render 'steps' so that it |
07:25.10 | CIA-40 | BRL-CAD: finds the setting. |
07:27.29 | CIA-40 | BRL-CAD: 03brlcad * r34042 10/brlcad/trunk/NEWS: |
07:27.29 | CIA-40 | BRL-CAD: implement support to actually utilize the perspective mode setting (apparently |
07:27.29 | CIA-40 | BRL-CAD: it was never wired up). this makes it work though there still flimsy (need the |
07:27.29 | CIA-40 | BRL-CAD: main view). this was noticed and requested by a few folks on and off the cad |
07:27.29 | CIA-40 | BRL-CAD: team (gillich and various analysts iirc). |
07:30.45 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1252 10/wiki/GSOC: Redirecting to [[Google Summer of Code]] |
07:31.00 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1253 10/wiki/Gsoc: Redirecting to [[Google Summer of Code]] |
07:31.27 | *** join/#brlcad madant_ (n=madant@117.196.130.93) |
07:37.49 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r0 10/wiki/Special:Log/upload: uploaded "[[Image:Brlcad gsoc2009 flyer.png]]": BRL-CAD GSoC 2009 Flyer |
07:40.32 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1255 10/wiki/Google_Summer_of_Code/2008: add the 2008 flyer to give it some identity |
07:40.58 | *** join/#brlcad Kamran (n=qadir010@58-27-157-151.wateen.net) |
07:41.06 | Kamran | hi all |
07:42.01 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1256 10/wiki/Google_Summer_of_Code/2009: add the 2009 flyer |
07:42.10 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1257 10/wiki/Google_Summer_of_Code: update to the 2009 flyer |
07:44.37 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1258 10/wiki/Google_Summer_of_Code/Flyers: start a gallery |
07:46.41 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1259 10/wiki/Google_Summer_of_Code: link to the flyers page |
07:46.50 | brlcad | howdy Kamran |
07:50.56 | Kamran | i want to work on Web-based solid geometry model repository |
07:53.20 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1260 10/wiki/Google_Summer_of_Code/Project_Ideas: organize into high-priority and other |
07:53.21 | brlcad | what can you tell me about that task? |
07:53.39 | brlcad | (that are you ideas for it, I know what's on the ideas page) |
07:56.18 | Kamran | we can save the geomatries in xml formats |
07:56.38 | Kamran | and then publish that xml in repository for sharing |
07:59.30 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1261 10/wiki/Google_Summer_of_Code/Project_Ideas: link to the design movie for the gui task |
08:00.50 | brlcad | Kamran: hm, the problem there would be that we have a format already -- introducing xml on the backend would provide very little gain and be rather cumbersome to accomplish efficiently |
08:01.31 | brlcad | this can't be just some generic model repository, it needs to relate to our tools and formats for engineering and solid modeling purposes |
08:02.27 | brlcad | e.g. if xml was going to be on the backend, i'd think STEP-XML would make a better choice than anything we'd come up with in a summer for compatibility, but that is a beast in itself (and you could probably spend all summer writing a converter) |
08:03.43 | Kamran | so how a student can achieve it using Drupal or Mediawiki? |
08:04.16 | Kamran | i think if converter is implmented that would be, it will be achieved? |
08:06.03 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1262 10/wiki/Google_Summer_of_Code/Project_Ideas: /* Web-based solid geometry model repository */ add some notes as this tends to be a hot topic |
08:06.19 | brlcad | Kamran: no te entiendo |
08:07.08 | brlcad | drupal/mediawiki just provide a plugin framework from which to work in, with the point being that it's not a fully custom system that someone has to wade through later |
08:07.50 | brlcad | there are other options like a rails project, possibly ajax, or some other framework .. just not completely/mostly home-grown |
08:08.53 | brlcad | as for the converter, my point was that we have a compact and efficient .g file format as well as a couple dozen importers and exporters -- ideally, models could be automatically stored and converted between the various supported formats |
08:10.07 | Kamran | if i have to work on this web-based repository, i have to patach the repository or not? |
08:12.41 | brlcad | patch the repository? |
08:12.43 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1263 10/wiki/Google_Summer_of_Code/Project_Ideas: /* Additional Projects */ all is not lost. |
08:13.02 | brlcad | you're making a repository .. it's a matter of what goes into the repository and how you store things |
08:13.03 | Kamran | yes |
08:13.13 | *** join/#brlcad _sushi_ (n=_sushi_@84-72-93-63.dclient.hispeed.ch) |
08:18.45 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1264 10/wiki/Google_Summer_of_Code/Project_Ideas: add difficulties |
08:19.59 | brlcad | Kamran: brl-cad is a collection of more than 400 tools, to suggest a model repository, your proposal should reference which tools you will be using and how -- I'd suggest checking out the source code and reading HACKING and src/README for starters (there's a section on the various dirs) |
08:20.34 | Kamran | thanks |
08:34.09 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1265 10/wiki/Google_Summer_of_Code/Project_Ideas: add a bug-fix task and annotate the 2008 projects |
08:34.33 | brlcad | np |
08:48.52 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1266 10/wiki/Google_Summer_of_Code/Project_Ideas: merge mged and archer |
08:54.33 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1267 10/wiki/Google_Summer_of_Code/Project_Ideas: /* CSG evaluation of Boundary Representations */ boole and esolid |
08:58.30 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1268 10/wiki/Google_Summer_of_Code/Project_Ideas: /* Geometry database (i.e. ".g" file format) enhancements */ |
08:59.37 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1269 10/wiki/Google_Summer_of_Code/Project_Ideas: swap |
09:09.11 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1270 10/wiki/Google_Summer_of_Code/Project_Ideas: implict to explicit brep support |
09:21.42 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1271 10/wiki/Google_Summer_of_Code/Project_Ideas: fixed precision project |
10:03.42 | *** join/#brlcad Axman6 (n=Axman6@pdpc/supporter/student/Axman6) |
10:26.37 | madant_ | brlcad: nice fonts ;) |
10:28.22 | madant_ | starseeker: :) I like the poster |
10:54.41 | CIA-40 | BRL-CAD: 03Homovulgaris 07http://brlcad.org * r1272 10/wiki/Google_Summer_of_Code/Project_Ideas: /* Constraints and Parametrics */ Short Introduction added |
11:22.21 | *** join/#brlcad Kamran (n=qadir010@58-27-157-151.wateen.net) |
11:39.42 | *** join/#brlcad archivist (n=archivis@host81-149-119-172.in-addr.btopenworld.com) |
12:49.51 | *** join/#brlcad BigAToo (n=BigAToo@pool-96-230-124-61.sbndin.btas.verizon.net) |
13:02.46 | starseeker | madant_: thanks :-) |
13:03.03 | starseeker | brlcad pulled it together |
13:03.19 | starseeker | just took some screenshots and blended 'em |
13:16.49 | *** join/#brlcad ashishrai (i=d2d43dfb@gateway/web/ajax/mibbit.com/x-346e276e35b4e6eb) |
13:42.22 | *** join/#brlcad BigAToo (n=BigAToo@pool-96-230-124-61.sbndin.btas.verizon.net) |
14:39.18 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1273 10/wiki/Google_Summer_of_Code/Project_Ideas: AquaTk MGED |
14:41.00 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1274 10/wiki/Google_Summer_of_Code/Project_Ideas: /* Additional Projects */ |
14:49.31 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1275 10/wiki/Google_Summer_of_Code/Project_Ideas: add initial mentor list |
14:50.01 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1276 10/wiki/Google_Summer_of_Code/Project_Ideas: /* Mentors */ |
14:52.45 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1277 10/wiki/Google_Summer_of_Code/Project_Ideas: /* High Priority Projects */ |
14:54.47 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1278 10/wiki/Google_Summer_of_Code/Project_Ideas: move mentors to the end |
14:55.57 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1279 10/wiki/Google_Summer_of_Code/Project_Ideas: don't link to contact page, requires login |
14:57.54 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1280 10/wiki/Google_Summer_of_Code/2009: /* Getting started */ don't be redundant |
14:59.23 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1281 10/wiki/Google_Summer_of_Code/2009: /* Getting started */ |
15:00.49 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1282 10/wiki/Google_Summer_of_Code/2009: /* Getting started */ reword |
15:03.42 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1283 10/wiki/Google_Summer_of_Code: /* Previous years BRL-CAD has participated */ |
15:09.16 | CIA-40 | BRL-CAD: 03Sean 07http://brlcad.org * r1284 10/wiki/Google_Summer_of_Code: link both posters |
15:56.38 | *** join/#brlcad dreeves2 (n=c752f348@bz.bzflag.bz) |
16:02.03 | *** join/#brlcad cad33 (n=c752f348@bz.bzflag.bz) |
16:16.26 | starseeker | brlcad: any idea when they'll announce the projects chosen? |
16:17.47 | d-lo | 18th I thought.... |
16:20.14 | ashishrai | hey !! where are the project ideas for BRL-CAD - can u please give the specific link :) |
16:20.21 | ashishrai | for GSoC |
16:20.57 | starseeker | http://brlcad.org/wiki/Google_Summer_of_Code |
16:21.16 | starseeker | http://brlcad.org/wiki/Google_Summer_of_Code/Project_Ideas |
16:21.36 | ashishrai | starseeker: thanks :) |
16:21.39 | starseeker | remember though, selected orgs aren't known yet |
16:22.07 | ashishrai | brlcad will be :) |
16:22.21 | brlcad | ashishrai: it's not guaranteed |
16:22.41 | brlcad | probably 80/20 chances |
16:23.02 | ashishrai | i just hope so |
16:23.04 | ashishrai | :) |
17:01.02 | *** join/#brlcad samrose (n=samrose@c-24-11-214-181.hsd1.mi.comcast.net) |
17:01.13 | *** join/#brlcad madant_ (n=madant@117.196.151.151) |
17:07.11 | tedcx | How do we get rid of jaggies in the renderings? |
17:07.44 | starseeker | uh... higher resolution render? |
17:07.57 | starseeker | depends on whether it's a geometry issue |
17:09.46 | brlcad | tedcx: you can either turn on jittering (e.g. -j8) or increase your render size and scale down (recommended) or both (for best quality) |
17:13.12 | tedcx | is jittering "dithering"? |
17:15.28 | brlcad | nope |
17:15.55 | brlcad | normally when you render an image, rays are fired in the exact center of a given pixel |
17:16.10 | brlcad | jittering has it fire randomly within the pixel to avoid aliasing artifacts |
17:17.49 | brlcad | -j8 means fire 8 random rays and it then picks the most consistent result (doesn't average/smooth the values still for various reasons) |
17:18.26 | brlcad | thinks there needs to be a jitter-style option that does averaging |
17:21.08 | CIA-40 | BRL-CAD: 03brlcad * r34043 10/brlcad/trunk/TODO: implement a jitter-style averaging option for rt |
17:25.48 | tedcx | and are the "framebuffers" just that or does the "ogl" really write ogl to whatever graphics card you happen to have? |
17:31.57 | starseeker | glares as rt enters some kind of colorview loop |
17:37.06 | brlcad | tedcx: the framebuffer type is a framebuffer communications layer detail, just what protocol it talks to the framebuffer with |
17:37.27 | brlcad | all the framebuffers are raster contexts, the display managers are 3D contexts |
17:38.22 | brlcad | so the ogl framebuffer does end up making OpenGL calls to on an OpenGL context, but that doesn't mean it's 3D data that you can spin around (because it's a framebuffer, i.e., a raster image display) |
17:44.49 | brlcad | nice quote.. "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." |
17:44.53 | brlcad | from Kernigan |
17:45.09 | d-lo | lol |
17:45.10 | brlcad | or this one, Einstein: "Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." |
17:47.13 | brlcad | hah, fantastic... "The end is the same for everybody. We're all worm food." |
17:48.04 | archivist | was Kernigan responsible for the index entry for recursion in the C book |
17:48.47 | archivist | which of course points to the index page |
17:48.47 | ``Erik | recursion: see recursion. ? |
17:49.35 | archivist | index at back og the second edition |
17:49.52 | brlcad | this must be cool quote day |
17:49.55 | brlcad | "If you need to cut, there's no tool as good as a sharp knife. If you need to turn a screw, a sharp knife probably isn't the right tool. If you have a guy who's a sharp knife, and you're using him to turn screws, maybe the problem isn't him. Maybe the problem is you." |
17:50.39 | ``Erik | cool, where's that from? |
17:51.25 | louipc | that is a good one |
17:51.31 | brlcad | random /. user quote |
18:03.01 | starseeker | hmm - "imperfection is the greatness of man" |
18:03.20 | starseeker | not sure if it makes sense, but it sounds deep |
18:13.52 | *** join/#brlcad madant (n=madant@117.196.133.81) |
18:30.35 | bjorkintosh | ayn rand will strongly disagree. |
18:32.40 | CIA-40 | BRL-CAD: 03bob1961 * r34044 10/brlcad/trunk/src/libged/gqa.c: Added code to free rtip. |
18:51.49 | *** join/#brlcad Ralith (n=ralith@216.162.199.202) |
20:05.57 | *** join/#brlcad BigAToo (n=BigAToo@pool-96-230-124-61.sbndin.btas.verizon.net) |
21:22.38 | starseeker | is mildly bemused by the slashdot discussion of quirky programmers |
21:29.32 | *** join/#brlcad PrezKennedy (i=Matthew@whitecalf.net) |
21:41.21 | CIA-40 | BRL-CAD: 03starseeker * r34045 10/brlcad/trunk/src/other/step/README: Add a few notes on the current state of the STEP libraries. Since things are now passing distcheck, pass the baton over to the 'make functionality fixes and develop new functionality' folk. |
21:48.24 | *** join/#brlcad cad63 (n=c752f348@bz.bzflag.bz) |
22:58.40 | bjorkintosh | there's another type besides the quirky? |
23:14.11 | CIA-40 | BRL-CAD: 03brlcad * r34046 10/brlcad/trunk/NEWS: bob fixed a tiny memory leak in gqa making it free the rtip |
23:33.18 | brlcad | starseeker: you did more than just take screenshots and blend them -- set up the whole framework for the design |
23:33.22 | brlcad | thanks |
23:34.10 | brlcad | i just did the typesetting |