IRC log for #brlcad on 20080523

00:07.35*** part/#brlcad prasad_ (n=psilva@static-70-108-244-218.res.east.verizon.net)
01:05.04brlcadyay, indy time
02:07.01*** join/#brlcad cad38 (n=7dec2c31@bz.bzflag.bz)
02:09.35cad38hey
02:37.29*** join/#brlcad thing0 (n=ric@123.208.220.214)
03:21.52*** join/#brlcad SWPadnos_ (n=Me@dsl107.esjtvtli.sover.net)
03:52.53PrezKennedybrlcad, how was indiana jones... I'm guessing that's what you went to see...
04:56.07*** join/#brlcad Elperion (n=Bary@p54875D7E.dip.t-dialin.net)
05:00.19learnerPrezKennedy: yup
05:00.50learnerand guess who went .. someone you know that hasn't been to a theater in years! :)
05:01.57learnerit was pretty good, it's in the same spirit as the others .. there were a few scenes that were pretty cheezy/contrived, but overall I liked it
05:02.07learnernot as good as 1 or 3, but probably better than 2
06:08.48*** join/#brlcad dtidrow_ (n=dtidrow@c-69-255-182-248.hsd1.va.comcast.net)
06:14.53brlcaduh oh
07:42.43*** join/#brlcad thing0 (n=ric@123.208.220.224)
07:45.09brlcadrecovers from the full disks
07:48.24*** join/#brlcad clock_ (n=clock@zux221-122-143.adsl.green.ch)
08:57.48*** join/#brlcad Axman6 (n=Axman6@pdpc/supporter/student/Axman6)
09:46.40*** join/#brlcad elite01 (n=elite01@dslb-088-071-045-035.pools.arcor-ip.net)
10:01.58*** join/#brlcad louipc (n=louipc@76-10-146-181.dsl.teksavvy.com)
10:46.31*** join/#brlcad thing0 (n=ric@58.171.211.214)
12:56.23*** join/#brlcad homovulgaris (i=homovulg@gateway/tor/x-f9fbdc8ea75192f0)
12:56.44homovulgarishi all :)
12:57.09homovulgarishey Sean, u there :) ?
12:57.36homovulgarisi was planning on writing the tests for the polynomial coefficient change i had done.
12:57.59homovulgariswhat all should the test check ? 1. the limits of the root solver ? 2. comparison between pre and post patch results ? and 3. using an external solver like gsl ?
13:18.51PrezKennedypart 2 was godawful
13:19.24homovulgaris:) ?
13:20.29homovulgarishas anybody tried out opencascade ..
13:21.08homovulgaristrying to get salome running on debian unstable
13:49.41brlcadhowdy homovulgaris -- those all sound like reasonable things to test
13:50.37brlcadprobably in order of 2, 1, 3
13:51.31brlcadas well as a macro-level test, running the benchmark to make sure the results are correct (make benchmark or 'benchmark' after install)
14:05.02*** join/#brlcad docelic (n=docelic@78.134.194.21)
14:07.03pooliobrlcad: AH DISKS FULL. Oh, good work :P
14:12.00homovulgarisok ;) on it..
14:20.46brlcadpoolio: yeah, it happens every few months if left unattended
14:21.11brlcadthe machine generates *massive* amounts of log data across all services given how busy it is and what it's used for
14:22.01brlcadwhere massive is several GB/month (of text)
14:23.02brlcadwhich is all neatly compressed and managed, but still accummulates slowly .. and coupled with general multiuser system tendancy to fill to the available resources ... :)
14:23.33brlcadalas reason to get back to work on the system migration where the new servers have a lot more disk
14:23.59brlcadit does encourage/enforce me regularly cleaning up the filesystem though, so not too bad :)
14:43.13``Erikso migrate already, beeyotch :D
14:44.05``ErikI wonder if it'd be useful to do piecewise migration, like move named responsibility to th enew one, then mebbe db stuff to the new one, then mail to the new one, then web to the new one... over the course of a couple weeks or something
14:44.20``Erikinstead of one big switch
15:03.18brlcadyeah, thought about that some
15:04.08brlcadi think it's just more a matter "doing it", whether piecewise or in whole
15:09.43*** join/#brlcad docelic_ (n=docelic@78.134.193.62)
15:16.09PrezKennedyhomovulgaris, i meant part 2 of indiana jones... ;)
15:16.50PrezKennedybrlcad, so my mom actually went? she never goes to the movies
15:21.07brlcadyep
15:21.26brlcadhad a good time too, I think
15:21.46brlcadsaid she was probably good for another 5 years now
15:25.10clock_brlcad: by telling your mom is alive you are giving some partial information about your age, don't you see that as a problem?
15:26.01louipcmy mom's mom is still alive
15:28.07pooliobrlcad: true true, my filesystem is getting messy these days
15:33.48*** join/#brlcad andrecastelo_ (n=chatzill@189.71.79.175)
15:37.44brlcadclock_: actually wasn't saying anything about my mother, but yes she is still alive and no I don't see that as a problem at all (I'm quite thrilled my parents are alive, tyvm)
17:12.31pooliobrlcad: so I think I've got working sphere and cylinder. That's not to say I understand Brep at all, I just know how to write a few lines of code ;)
17:15.16pooliobrlcad: Also, how is the C++ going to factor in with the existing C librt code?
17:52.34``Eriknotes that human lifespan runs from 0 years to in excess of 120 years, and humans are physically capable of breeding as young as ~12, so a fact like ones mother being alive does *NOT* say terribly much about ones age O.o
18:09.04*** join/#brlcad cad27 (n=d90aac02@bz.bzflag.bz)
18:31.13brlcadpoolio: i'm (mentally) working that out now, ideally/necessarily they should be separate compilation units, yet we want them grouped together
18:31.48brlcadso I think I need to do some restructuring, move each primitive into its own subdir
18:32.24``Erikopposed to simple wrapper in src/librt++/ ?
18:32.25brlcadand then break them up .. then your routine is just the g_obj_brep.cpp file
18:33.07brlcad``Erik: he's not making an OO interface, he's implementing a single C routine for each primitive
18:33.13brlcadbut the back-end guts to the routine use C++
18:33.18brlcadvia openNURBS
18:33.37brlcadso it's really still part of librt, just implementation detail
18:33.41brlcadnot a layer on top
18:34.05``Erikah
18:34.30brlcadso instead of turning each primitive into a cpp file, I'm thinking to just break them up
18:34.55brlcadhad that in mind for a long while actually, as a way to organize the bits already there (e.g. the 30+ nurbs files, to 30+ nmg files, etc)
19:18.05*** join/#brlcad thing0 (n=ric@123.208.50.203)
19:54.30pooliobrlcad: cool cool
20:13.13*** join/#brlcad Elperion (n=Bary@p5487677C.dip.t-dialin.net)
20:57.29``Erikwhat? seize the carp?
21:29.38CIA-21BRL-CAD: 03brlcad * r31174 10/brlcad/trunk/ (NEWS src/rt/opt.c src/rt/rtcheck.1 src/rt/viewcheck.c): (log message trimmed)
21:29.38CIA-21BRL-CAD: bob added this option way back in 2005 ( 15 Aug 2005 21:43:07 to be exact ) but
21:29.38CIA-21BRL-CAD: it was never documented. this option makes rtcheck write the plot file data in
21:29.38CIA-21BRL-CAD: text format instead of the default binary format. binary should probably not be
21:29.41CIA-21BRL-CAD: the default, so presumably this was a first step towards that direction; at
21:29.43CIA-21BRL-CAD: least it lets you get text instead of binary so you can avoid the tty warning
21:29.45CIA-21BRL-CAD: about binary output. reduce globals by one, the code is updated to reuse the
22:04.13starseeker_``Erik:  That's not how I fish for carp...
22:06.37starseeker_uses pole and bait rather than seizing with hands...
22:06.41*** join/#brlcad elite01_ (n=elite01@dslb-088-071-035-057.pools.arcor-ip.net)
22:08.06``Erikyeah, you're a wuss
22:08.06``Erik:D
22:09.24*** join/#brlcad elite01__ (n=elite01@dslb-088-071-036-002.pools.arcor-ip.net)
22:44.58*** join/#brlcad quentusrex (n=quentusr@c-71-197-244-228.hsd1.or.comcast.net)
22:48.19CIA-21BRL-CAD: 03brlcad * r31175 10/brlcad/trunk/TODO: it really just causes too much confusion. z-clipping should be off by default.
23:22.36``Erikhttp://www.explosm.net/comics/1286/
23:28.28starseeker_brlcad:  What was that trick you used yesterday to capture the nirt command used by mged?
23:28.45starseeker_or dump it to a file rather
23:30.52*** join/#brlcad clock_ (n=clock@217-162-110-88.dclient.hispeed.ch)
23:35.25brlcadnirt > some_file
23:35.49brlcadooh
23:35.54brlcadsaveview
23:36.34brlcadsaves the view .. view scripts just happen to also be render scripts (since they have all the necessary view information)
23:37.27brlcadnotes that nirt only needs a -o option to be compatible with the saveview script interface .. someone(tm) should add that

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