IRC log for #brlcad on 20090930

00:16.36 CIA-28 BRL-CAD: 03brlcad * r36091 10/brlcad/trunk/src/librt/primitives/bot/g_bot_include.c:
00:16.36 CIA-28 BRL-CAD: expand the zero-thickness loop and make it use the application-specified
00:16.36 CIA-28 BRL-CAD: distance tolerance instead of hard-coded magic values. this should tighten the
00:16.36 CIA-28 BRL-CAD: bounding box while still keeping the bot visible for space partitioning.
00:23.17 CIA-28 BRL-CAD: 03brlcad * r36092 10/brlcad/trunk/src/librt/primitives/bot/g_bot_include.c: style ws indent comment consistency cleanup
00:24.44 CIA-28 BRL-CAD: 03brlcad * r36093 10/brlcad/trunk/src/librt/primitives/bot/g_bot_include.c: accidental double-line
00:25.51 CIA-28 BRL-CAD: 03brlcad * r36094 10/brlcad/trunk/src/librt/primitives/bspline/bspline.c: apply the same non-zero thickness test that BoT uses so that we don't miss planar spline surfaces during space partition traversal.
00:33.25 CIA-28 BRL-CAD: 03brlcad * r36095 10/brlcad/trunk/src/librt/primitives/bspline/bspline.c: no need to have the zero-length test inside the surface loop. just do a sanity test after visiting all surfaces.
00:33.30 brlcad starseeker: on that note .. any specific reason brep bounding boxes are expanded 1mm instead of tol->dist in brep_prep()?
00:33.33 brlcad fg
00:35.53 starseeker brlcad: not sure offhand
00:49.53 brlcad remember that .bz is possibly going down in as early as 10 minutes from now (or any time now really)
00:50.21 brlcad so you might want to have a local irc client handy since screens will all get shut down
00:51.40 starseeker doesn't have home internet yet anyhow
00:52.50 starseeker is not at all sure if the amount of data in a dsp makes sense to represent as a NURBS surface
00:54.10 brlcad if you want to visualize it via opengl, it does
00:54.26 brlcad remember that's one piece of what those routines are for
00:55.11 starseeker might be better to just tesselate it and use the bots
00:55.41 starseeker I'm not even sure we can hand a surface like this
00:58.36 starseeker er handle even
00:59.03 *** join/#brlcad BigAToo (n=BigAToo@pool-96-230-124-33.sbndin.btas.verizon.net)
01:01.01 CIA-28 BRL-CAD: 03brlcad * r36096 10/brlcad/trunk/src/librt/primitives/brep/brep.cpp: tighten up the bounding box check considerably from 1mm to the distance tolerance. history indicates this was arbitrarily 0.02mm then 1.0mm during testing. this is actually still not quite as tight as the other prims.
01:01.37 brlcad will see if that busts things soon enough..
01:01.48 brlcad shouldn't though, unless there are other bad assumptions at play
01:01.48 starseeker brlcad: It may have been expanded for a reason...
01:02.42 starseeker brlcad: was it causing problems with the old NURBS -> new NURBS conversion?
01:02.42 brlcad speculation, wasn't documented in comments or commit -- hinted at it just being part of testing bb in commit message
01:03.14 starseeker nods - yeah, a lot of that stuff was and still is a tad fuzzy
01:03.16 brlcad either way, should find out rather trivially and can document it if it needs to be something else
01:03.53 brlcad should at least be a comment if there's going to be a magic number that isn't using the tolerance system, otherwise it's just asking for obscure cascading bugs down the road
01:04.04 starseeker Keith and I both intend to go back over the whole kit and kaboddle thoroughly once the sprint is done
01:04.56 starseeker suggests brlcad not look too hard if magic numbers bother him - there are a fair few that will need to be delt with
01:05.07 brlcad oh, I know
01:05.33 starseeker bty, congrats on the release tagging!
01:05.38 starseeker well done
01:05.44 brlcad that one was just blatent and screws with the space partitioning
01:06.02 brlcad st_min/max aren't used during shot(), they're used higher up during SP traversal
01:06.24 brlcad if it's not right, then GetBBox() is wrong
01:07.27 brlcad we can't get that far off schedule between releases -- makes for way too much work
01:08.56 brlcad and it really shouldn't be a one-man job every month, doesn't serve the project regardless of ongoing activity as issues back up and bugs get more costly and release even more intense
01:09.43 starseeker apologizes
01:10.38 brlcad not harping on anyone in particular -- should be everyone pressing for it and helping push it each end of month
01:11.57 brlcad sad to say it, but feeling is our quality is "down" due to bugs introduced that simply aren't on anyone's radar .. feels like a class ".0" release unfortunately
01:12.30 starseeker nods
01:12.41 brlcad *classic
01:13.22 starseeker will try not to move again for a few months ;-)
01:15.48 brlcad there are several active folks that could have helped things along.. :)
01:16.05 brlcad most distressing is *FOUR* releases were missed :/
01:16.19 starseeker ow
01:16.36 brlcad we had four in row right on time
01:16.51 brlcad then four missed, now (hopefully) back on schedule
01:18.32 starseeker Did we introduce the stability issues, or is that the OSX 10.5 stuff?
01:18.45 brlcad read my clock wrong, still 1.5 hours till 11pm
01:18.56 brlcad it's not just osx
01:20.03 brlcad it's several things in general -- tcl changes, rt changes, mged command changes .. just bug creep
01:20.03 brlcad regression tests being ignored
01:20.03 brlcad several are failing
01:21.31 starseeker winces
01:21.39 brlcad happens naturally, just has to be kept in check -- can't just keep heaping in new code and code changes for months on end without keeping things clean along the way
01:23.04 brlcad almost let a bug slip in with my mged argv parsing change from the weekend that I just caught on monday
01:23.20 brlcad that would have been bad :)
01:24.00 starseeker heh
01:24.05 starseeker just a bit
01:28.27 brlcad if I had my druthers and unlimited time/budget, I'd halt all new work so we can focus on just bugs for at least three months solid to fix and refactor anything and everything we know of and can easily expose through automation, across the entire codebase
01:28.55 starseeker nods
01:29.20 starseeker too bad about the time/budget bit :-(
01:30.17 brlcad the payoff from that would escalate our usability and code maintainability faster than anything else by removing *all* potential crashes, failed input processing, 32/64-bit conversions, bad assumptions, bad docs, etc
01:30.30 starseeker yep
01:30.45 starseeker agrees, just not sure how to /who to make the case to
01:31.14 brlcad couldn't be made for that length of time unless we make it some massive community effort
01:31.40 brlcad and then you have to attract bug fixers and get them up to speed
01:31.59 brlcad we had a gsocer like that for bz this year .. was fantastic .. fixed dozens of really hard bugs
01:34.48 starseeker sweeet
01:44.34 *** join/#brlcad cpc26 (n=cpc26@72.170.156.242)
01:52.29 yukonbob reads scrollback with interest...
01:55.08 *** join/#brlcad learner (n=sean@c-68-48-70-217.hsd1.md.comcast.net)
02:00.43 brlcad thinks he may need to add a plate mode to breps
02:09.23 brlcad starseeker: you ever looked into stay's trimming code?
02:09.48 brlcad thinking to kill it if you have, if there's no value to be derived any more
02:11.37 starseeker can't say I have, really - I didn't know there was working trimming code
02:11.49 brlcad never implied it was working or not
02:12.03 brlcad code is code
02:12.22 starseeker I'd go ahead - it's in the revision history if we need it, and on the whole our trimming seems to be in decent shape now
02:13.23 brlcad nobody will need to look at it as a matter of need, it wasn't used
02:13.43 brlcad it would be to see if there's some aspect to what he's doing that is actually useful that could improve what we're doing
02:14.19 starseeker I suppose I could take a look, but it might not be for a while
02:14.29 brlcad not very complex code, might be worth all of five min to review it
02:14.59 starseeker what file is it in?
02:15.02 brlcad looks like that was the only code to actually start to use nurbs nmg structure
02:15.22 brlcad src/librt/primitives/bspline/nurb_trim.c
02:15.38 starseeker looks
02:18.18 starseeker hmm, he's breaking up the curves into bezier sub-curves
02:18.20 starseeker I think
02:18.33 starseeker quadrant based reasoning...
02:18.53 brlcad wouldn't be surprising, that was the approach for surface decomposition, turning nurbs into bspline patches
02:19.37 brlcad hm.. more coffee or quick nap
02:19.50 brlcad gets coffee
02:20.25 starseeker yeah, that's not what we're doing now (at least practically) so I don't think we need it - I don't think we have a working openNURBS routine for the bspline patch thing, and we aren't doing that anyhow
02:23.09 CIA-28 BRL-CAD: 03starseeker * r36097 10/brlcad/trunk/src/librt/primitives/dsp/dsp_brep.cpp: Ugly, ugly, ugly. Wireframe looks halfway reasonable but hardly raytraces at all. Performance is horrible.
02:28.13 starseeker grinds teeth
02:29.06 starseeker now what.. do per-cell surfaces? ugh. what's a reasonable breakdown I wonder...
02:29.54 starseeker this thing might be the super-density control point case that we need to add to the surface tree build logic checking... even then though I doubt it would help much
02:45.41 starseeker exit
02:45.45 starseeker whoops
02:48.08 yukonbob fail
02:58.11 CIA-28 BRL-CAD: 03brlcad * r36098 10/brlcad/trunk/include/nurb.h: make the header safe to include with c++ files as-is with a little wrapping love.
02:58.47 CIA-28 BRL-CAD: 03brlcad * r36099 10/brlcad/trunk/ (4 files in 3 dirs): initial stub in for old nurbs to new nurbs conversion. right now it just stubs a bounding sphere in place while some more thought is put into how to support the old structureless nurbs as freestanding surfaces.
03:16.10 poolio starseeker: how goes brep? :)
03:19.25 learner he has most of the primitives working now
03:19.38 learner pretty cool
03:21.01 poolio awesome!
03:21.43 learner just a couple of the more complex ones remaining (like dsp (terrain), sketches, revolve, pipes, etc)
03:31.38 poolio ruh roh, looks like bzflag is about to go down. see y'all on the other side
03:41.45 *** join/#brlcad BigAToo (n=BigAToo@pool-96-230-124-56.sbndin.btas.verizon.net)
03:46.46 learner poolio: yeah, supposedly any minute (for the past 45)
03:48.10 learner yeah, I just saw the console messages .. here it goes
03:56.59 learner dns is updated, just waiting for the physical swap now
04:00.40 CIA-28 BRL-CAD: 03brlcad * r36100 10/brlcad/trunk/src/librt/primitives/brep/brep.cpp: brep_build_bvh doesn't use the rt_brep_internal
04:20.01 learner cmon sago
04:22.25 *** join/#brlcad brlcad (n=sean@63.246.136.16)
04:22.35 brlcad woot
05:03.18 *** join/#brlcad cpc26 (n=cpc26@72.170.156.242)
05:56.55 *** join/#brlcad Axman6 (n=Axman6@pdpc/supporter/student/Axman6)
06:24.08 CIA-28 BRL-CAD: 03brlcad * r36101 10/brlcad/trunk/ (5 files in 3 dirs): rename bspline.c to bspline.cpp in preparation for new nurbs integration/conversion.
06:26.26 CIA-28 BRL-CAD: 03brlcad * r36102 10/brlcad/trunk/src/librt/primitives/bspline/bspline.cpp: initial conversion for ray-tracing purposes, add a compile-time switch to convert prep() to use brep prep() with stashage into the nurb_internal.
06:27.47 CIA-28 BRL-CAD: 03brlcad * r36103 10/brlcad/trunk/src/librt/primitives/bspline/bspline.cpp: reflect filename change
06:28.44 brlcad not too shabby for one day. tagged release, orchestrated server migration, fixed nurbs bb partitioning, and stubbed out prep.
06:29.11 brlcad goes to get cookies
06:32.32 CIA-28 BRL-CAD: 03brlcad * r36104 10/brlcad/trunk/include/rtgeom.h: consider stashing the ON_Brep in here, not ideal though
08:02.54 *** join/#brlcad _clock_ (n=_sushi_@80-218-244-105.dclient.hispeed.ch)
08:25.41 *** join/#brlcad KingofCSU (n=king@118.249.212.228)
08:28.52 KingofCSU Hello there I can not make a cone anyone can tell me how to make a cone I mean not the trc the cone with top R is 0
08:33.06 KingofCSU Hello How to make a cone by BRL-CAD? I had tried the solid trc , but i can not make the radius of top to 0, the Error is "all dimensions must be greater than zero! then how can I make a cone ?
08:33.44 _clock_ KingofCSU: make some small number as the top radius
08:33.59 _clock_ like 0.0000000000000000000000001
08:34.16 KingofCSU It is the only way?
08:34.22 _clock_ as far as I know yes
08:34.59 KingofCSU thank you, I will try it .
08:35.01 _clock_ KingofCSU: put the smallest number representable in floating point there. I wonder if the engine is going to collapse from that :)
08:35.44 KingofCSU I think 0.1 is ok
08:35.51 _clock_ KingofCSU: or, by binary search, find the smallest number the program accepts without producing the "all dimensions must be greater than zero!" message :)
08:36.32 KingofCSU 0.1 is enough to do such a cone
08:36.33 _clock_ wht are you modelling?
08:36.58 KingofCSU something simple I borrowed a book of CAD. and try to make the samples .
08:38.03 KingofCSU the book is about auto CAD . I try to make the examples by BRL-CAD.
08:38.46 KingofCSU Do you have any other idea to practice the BRL-CAD?
08:38.48 _clock_ oh autocad was initial release 1982
08:38.54 _clock_ and BRL-CAD 1984 according to Wikipedia
08:39.05 _clock_ What a shame for BRL-CAD!
08:39.10 _clock_ And I thought it was 1979
08:39.57 _clock_ aha! But Autocad was initially 2D only!
08:39.58 KingofCSU Whatever. How do you improve your kill of BRL-CAD?
08:40.24 KingofCSU I dont think so . autocad can do 3D too
08:40.26 _clock_ KingofCSU: I want to model something and then struggle to model it
08:40.40 _clock_ through all the badly documented functions :)
08:41.52 KingofCSU it is hard to put the things the the right place in BRL-CAD. it can not catch some point like middle or end
08:42.15 _clock_ Yes I find this useless unless for technological design
08:42.28 _clock_ I always type the coordinates in numerically in the matrix editor
08:42.54 KingofCSU you have to calculate the point
08:43.15 _clock_ I don't have to calculate any point
08:43.16 _clock_ Mostly
08:43.21 KingofCSU still now I can not understand the matrix editor
08:43.39 _clock_ If I need some complex shape I design it in QCAD let it print the coordinates and then type them in
08:44.04 _clock_ KingofCSU: I don't even remember the command to invoke it anymore :)
08:44.25 KingofCSU Oh that is a good idea , to do something in QCAD then ....
08:44.30 _clock_ there is red sed and ted
08:44.58 _clock_ some of them have horrible complicated parameters like you have to type in exactly the directory tree
08:45.04 _clock_ some don't work in some situations
08:45.14 _clock_ and all do basically the same IIRC
08:45.14 KingofCSU I can find anything about the red and ted,
08:45.21 _clock_ I find BRL-CAD very confusing to use :)
08:46.06 KingofCSU I can not find any documents about the red and ted .
08:46.12 _clock_ Sometimes it doesn't 'like' some geometry and is 210x slower in rendering
08:46.25 _clock_ For which some good soul wrote me some exceptional feature to solve exactly my situation
08:46.39 _clock_ However this help doesn't fit into my system of scripts and won't work for other situations of course
08:46.59 _clock_ KingofCSU: I am not surprised, I couldn't find them either
08:47.34 KingofCSU sometimes i find it is hard to use the pix-png tool .
08:48.05 KingofCSU _clock_: then How do you learn the red and ted?
08:48.06 _clock_ KingofCSU: I can't find any reference manual on teh net
08:48.19 KingofCSU same to you
08:48.19 _clock_ KingofCSU: I don't remember how I learned them, but I already forgot it anyway :)
08:48.34 KingofCSU :-D
08:49.04 _clock_ Oh here is some reference on the Wiki
08:49.06 _clock_ http://brlcad.org/wiki/MGED_Commands
08:49.10 _clock_ But:
08:49.15 KingofCSU there are only four BRL-CAD Tutorial Series to reference
08:49.43 _clock_ 1) how should a user determine from "I want to know about red" whether he should search in Documentation or Wiki? Anyway, isn't Wiki a documentation too so shouldn't it be under the Documentation chapter?
08:50.00 _clock_ 2) Is the Wiki official or unofficial documentation? How much can we trust what is written there?
08:50.16 KingofCSU I see. but I am a Chinese. It is hard to understand the English in so special way
08:51.06 KingofCSU the English in a specialized field or subject is hard to learn
08:52.33 KingofCSU just finishing the 4 BRL-CAD Tutorial Series is not enough to model complex things.
08:53.02 _clock_ Basically red is for combinations
08:53.07 _clock_ and sed+ted is for primitives
08:53.28 _clock_ And the BRL-CAD web is slow.
08:53.37 KingofCSU :)
11:37.32 brlcad which further reinforces the need for better organized/searchable/integrated documentation
11:46.25 *** join/#brlcad d-lo (n=claymore@63.246.136.16)
11:46.52 d-lo mornin!
12:01.08 brlcad mernin
12:01.35 brlcad woot, RDNS is fixed
12:02.10 Yoshi47 morning
12:02.35 Yoshi47 Remote Distraction NURBS System
12:06.24 brlcad yeah has been a distraction .. reverse DNS ;)
12:14.46 *** join/#brlcad KingofCSU (n=king@118.249.212.228)
12:24.37 *** join/#brlcad Axman6 (n=Axman6@pdpc/supporter/student/Axman6)
12:25.07 Yoshi47 oh that stuff, haven't even touch the reverse stuff, cause i don't think i need it
12:26.34 brlcad having reverse dns on servers with a fixed ip can be pretty useful
12:26.57 brlcad many tools do reverse lookups to validate origination
12:27.46 brlcad e.g., irc ..
12:37.41 CIA-28 BRL-CAD: 03brlcad * r36105 10/brlcad/trunk/src/librt/primitives/bspline/bspline.cpp: where to pick up
12:45.40 CIA-28 BRL-CAD: 03brlcad * r36106 10/brlcad/trunk/src/proc-db/spltest.c: make the surface non-planar for testing now that planar is fixed
12:52.51 CIA-28 BRL-CAD: 03brlcad * r36107 10/brlcad/trunk/src/libfb/ (if_X24.c if_ogl.c):
12:52.51 CIA-28 BRL-CAD: consistency. if you're going to cast to unsigned long long pointers, then scan
12:52.51 CIA-28 BRL-CAD: that. and do the same for X24 else obscure bugs are introduced.
12:52.51 CIA-28 BRL-CAD: *_open_existing really is a hack that needs to be refactored away/into the libfb
12:52.51 CIA-28 BRL-CAD: callback table better.
13:31.23 ``Erik now just to migrate services *cough*
13:39.35 *** join/#brlcad parigaudi (n=quassel@217.91.127.94)
13:44.55 brlcad yep
14:11.44 *** join/#brlcad BigAToo (n=BigAToo@pool-96-230-124-56.sbndin.btas.verizon.net)
14:16.56 *** join/#brlcad starseeker (n=starseek@63.246.136.16)
14:17.31 starseeker returns
14:20.32 d-lo *dun dun dunnnnnnnn*
14:21.54 d-lo thinks it is mildly amusing that someone in Sri Lanka got their GSoc Tshirt before someone in PA. :)
14:26.15 *** join/#brlcad mafm (n=mafm@2.Red-83-63-197.staticIP.rima-tde.net)
14:34.43 ``Erik got his a while ago
14:35.20 ``Erik like, 2 days after they said they were sending them out (actually saw the fedex tracking # before the email about them sending them out O.O)
14:36.08 ``Erik mebbe you live in an area that they didn't believe to be accessable or inhabited? they had to procure pontoons for the cessna? :D
14:42.11 d-lo ohh! ``Erik made a funny!
14:42.35 ``Erik (do I get a doggie biscuit? do I? do I? do I? huh? huh? do I?)
14:45.34 d-lo Nope, but you can have 179 mins off work today. Just tell'em Dave Said so.
14:47.06 d-lo Nice: Texting while driving in MD will get you a $500 fine. Finalyl, some sense.
14:52.52 Yoshi47 soon to be in Ontario too! even if on phone! or any device that isn't dash mounted
14:53.05 Yoshi47 going to have to find a nice BT headset
14:53.22 Yoshi47 maybe one that can work with my notebook too!
15:57.26 CIA-28 BRL-CAD: 03starseeker * r36108 10/brlcad/trunk/src/librt/primitives/dsp/dsp_brep.cpp: More dsp tweaking - still doesn't raytrace.
16:04.40 CIA-28 BRL-CAD: 03starseeker * r36109 10/brlcad/trunk/src/librt/primitives/dsp/dsp_brep.cpp: Hmm - flip bottom face. Raytrace now at least gives something.
16:28.26 *** join/#brlcad poolio (n=poolio@BZ.BZFLAG.BZ)
16:29.16 *** join/#brlcad SWPadnos (n=Me@dsl107.esjtvtli.sover.net)
16:35.21 CIA-28 BRL-CAD: 03starseeker * r36110 10/brlcad/trunk/src/librt/primitives/dsp/dsp_brep.cpp: Change a couple more face flips - apparently getting a raytrace now, but prep and raytrace times are both still very long.
17:10.04 *** join/#brlcad parigaudi (n=quassel@217.91.127.94)
17:58.37 CIA-28 BRL-CAD: 03bob1961 * r36111 10/brlcad/trunk/src/tclscripts/archer/ (Archer.tcl ArcherCore.tcl): A few minor tweaks.
18:17.02 ``Erik holy owwow, SOMEONE's about to get a major beatdown http://chicago.craigslist.org/chc/sad/1399709773.html
18:44.03 *** join/#brlcad BigAToo1 (n=BigAToo@96.230.124.102)
18:45.01 d-lo ``Erik: lol, that is awesome.
19:02.24 *** join/#brlcad samrose (n=samrose@c-24-11-185-57.hsd1.mi.comcast.net)
20:22.19 CIA-28 BRL-CAD: 03brlcad * r36112 10/brlcad/trunk/src/librt/primitives/bspline/bspline.cpp: implement more breep conversion support callbackage
20:25.25 CIA-28 BRL-CAD: 03brlcad * r36113 10/brlcad/trunk/src/librt/primitives/bspline/bspline.cpp: reorder to remove the forward declarations on implementation-specific helper functions.
20:31.13 CIA-28 BRL-CAD: 03brlcad * r36114 10/brlcad/trunk/src/librt/primitives/bspline/bspline.cpp: plot needs a brep db internal
20:33.10 starseeker ``Erik: yeah, that's some of the best lawyer bait I've seen for a while
20:35.23 CIA-28 BRL-CAD: 03brlcad * r36115 10/brlcad/trunk/src/librt/primitives/bspline/bspline.cpp: pass the new brep db internal, not the old bspline one
20:45.55 *** join/#brlcad BigAToo (n=BigAToo@pool-96-230-124-102.sbndin.btas.verizon.net)
21:25.47 CIA-28 BRL-CAD: 03brlcad * r36116 10/brlcad/trunk/src/librt/primitives/bspline/bspline.cpp: display both the old and new wireframes for now
21:51.50 CIA-28 BRL-CAD: 03brlcad * r36117 10/brlcad/trunk/TODO: mged needs to better deal with kicking off an editor. really need to kick off our own terminal and invoke whatever editor from there.
22:14.45 brlcad hm, a new .deb for ubuntu.. http://tecnicoslinux.com.ar/
22:16.03 brlcad nice if someone could test it out to see if it's worth hosting up
22:18.02 brlcad and for those that can't read spanish, the link in there is http://www.tecnicoslinux.com.ar/livecd/brlcad_7.10_i386.deb
22:34.11 louipc sounds old
22:44.40 brlcad 7.10 is old, but I think the .deb is new :)
22:45.03 brlcad certainly newer than the last .deb posted (7.8.4)
22:46.47 CIA-28 BRL-CAD: 03brlcad * r36118 10/brlcad/trunk/src/librt/primitives/bspline/nurb_brep.cpp: accumulate the bounding volume across the whole model
23:07.44 ``Erik is the misc/debian unusable? I lost access to debian quite a while back :(
23:07.55 brlcad should be usable
23:08.04 brlcad more someone actually compiling the deb
23:09.13 ``Erik and probably no 'customer' we could use as leverage to get a debian machine at the office
23:09.52 brlcad I have access to a couple someone, but that really should be done by someone in the community (imnsho)
23:10.02 brlcad s/someone/somewhere/
23:11.00 ``Erik *shrug* I wasn't all that sad when I deleted my debian partition to make more space for fbsd
23:11.03 ``Erik :)
23:11.47 ``Erik (actually, I still have a debian machine... has, um, 120mhz cyrix processor with a dead fan, 48m ram, and I think a 1.6g hdd
23:11.50 ``Erik )
23:12.50 brlcad I'd rather see us hit every monthly source release with solid docs, stable tools, clean builds, then focus on community infrastructure (website, wiki, forums, docs)
23:13.01 brlcad if we're doing that, the community support will follow
23:13.07 ``Erik spoze
23:13.24 ``Erik I think I need to cook up some test cases for metaballs, there suddenly seem to be a slew of issues cropping up :/
23:13.33 ``Erik stupid ray marching crap
23:14.17 ``Erik check this one out, I got a "test geometry"
23:14.28 brlcad that procdb I hijacked is great for testing :)
23:14.32 ``Erik 33 individual metaballs, each containing exactly one control point, unioned together
23:14.41 ``Erik <-- doesn't think they ... get it
23:15.03 brlcad I gave a snippet that showed how to merge them with code
23:15.15 ``Erik ah, in the last hour or two?
23:15.25 brlcad no, couple months bad
23:15.28 brlcad back
23:15.30 ``Erik oh heh
23:15.42 brlcad I suspect it's because they don't like how they merge weight-wise -- non-intuitiv
23:15.49 ``Erik I did some c&p/vim/c&p today and got a nice generated mb with no issues
23:16.01 ``Erik the blob method is far better for what they want
23:16.03 brlcad they want the weight/power/whatever to be a distance
23:16.06 brlcad then blend
23:16.13 ``Erik effectively what blob does
23:16.27 ``Erik iso is the 'weird' one :/
23:17.15 ``Erik if'n I woulda seen these earlier, I would've seen about preparing materials to steal 10 minutes of this upcoming release meeting in the library
23:23.22 ``Erik overclocks his stove O.o
23:41.37 *** join/#brlcad Ralith (n=ralith@69.90.49.189)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.