IRC log for #brlcad on 20080607

00:04.36 *** join/#brlcad thing0 (n=ric@124-169-237-118.dyn.iinet.net.au)
00:29.49 *** join/#brlcad thing1 (n=ric@203-59-26-22.perm.iinet.net.au)
00:30.39 *** join/#brlcad DaytonaJohn (n=jra@c-68-55-36-65.hsd1.md.comcast.net)
00:36.13 *** join/#brlcad IriX64 (n=mariodot@bas2-sudbury98-1177725958.dsl.bell.ca)
00:53.37 *** join/#brlcad Twingy (n=justin@74.92.144.217)
01:40.46 *** join/#brlcad kolnstyle_ (n=kolnstyl@adsl-71-145-187-60.dsl.austtx.sbcglobal.net)
01:41.14 kolnstyle_ about how much time it would take to rotate by 45 degrees and scale by a factor of 2 a 500x500px image while using biquintic interpolation?
01:41.21 kolnstyle_ a rough estimate is fine
01:41.25 *** join/#brlcad andrecastelo_ (n=chatzill@189.71.9.76)
02:02.49 andrecastelo hey brlcad - is it ok to use bu_bomb() in the center point calculations, in the case of an empty list?
02:04.11 yukonbob afternoon, cadheads
02:19.11 starseeker 's eyebrows go up as he reads the RBGui readme file - so far they only have windows build logic?? ugh
02:22.56 andrecastelo good evening yukonbob
02:24.37 starseeker is beginning to understand properly why brlcad thought there weren't any really great options...
02:37.53 andrecastelo how can i initialize a bu_list will null? head->l = BU_LIST_NULL; ???
02:56.44 brlcad andrecastelo: center point calculations?
02:57.21 andrecastelo brlcad: yep, i'm BUnitizing the rtarea patch
02:57.39 brlcad bu_bomb should be used for exceptional failures -- usually either code that really should *never* be reached, or situations where continuing very well may put users data at risk (e.g. detected corruption)
02:58.11 andrecastelo hm ok then.. the function returns zero if any trouble arises
02:58.32 andrecastelo but my problem right now is initializing the point lits
02:58.36 andrecastelo s/lits/lists
02:58.45 brlcad if there's no way to reasonably continue the application, but it's not critical, you could call bu_exit
02:59.07 brlcad bu_bomb would be cases where you might actually want a stack trace to know just how the f*ck you got to that point in the code
02:59.54 andrecastelo you're right, that won't be needed here.. and i think even in the mlt stuff it won't be that serious
03:00.58 andrecastelo i'll paste you my problem, just a sec
03:02.46 andrecastelo here - http://rafb.net/p/Nmgo0C33.html
03:03.13 andrecastelo my doubt is - how do i set up a bu_list?
03:04.21 andrecastelo i've made the appropriate changes in other sections, where the list is iterated through and stuff and also used vector macros to handle points (is that ok?)
03:06.42 brlcad of course, using existing libraries is always a good thing
03:08.26 brlcad andrecastelo: did you read the header block for bu_list in include/bu.h ?
03:09.05 andrecastelo yes, i even implemented a bu_list type in a separate program, just to test and become familiar with the list
03:10.35 brlcad that's good
03:11.47 andrecastelo what am i missing?
03:16.06 *** join/#brlcad archivist (n=archivis@host81-149-119-172.in-addr.btopenworld.com)
03:25.57 CIA-21 BRL-CAD: 03brlcad * r31337 10/brlcad/trunk/include/bu.h: include a simple example of one way to use a bu_list
03:27.16 brlcad andrecastelo: that line is a problem because you're trying to set a structure type to an integer scalar type
03:28.16 andrecastelo yeah, i know, i was trying to find a way to initialize the lists involving BU_LIST_NULL (because later on i use BU_LIST_UNINITIALIZED to check if it's ready)
03:28.17 brlcad you wouldn't try to do this for example: struct area foo = 0; ... you'd only do that with a pointer, struct area *foo = 0;
03:28.56 brlcad see the example I just added to bu.h, see if that helps
03:30.12 andrecastelo hm ok, will do
03:30.26 andrecastelo is the point list structure correct?
03:30.28 brlcad to use BU_LIST_NULL, you'd actually normally do something like set your hit_points = BU_LIST_NULL
03:30.39 brlcad until you allocate it of course
03:31.04 brlcad sure, looks fine
03:34.36 andrecastelo thanks, will check
03:35.42 starseeker Hmm - http://ogre4j.sourceforge.net/
03:35.49 starseeker That could be useful
03:36.24 brlcad heh
03:36.40 starseeker if a certain project ever reaches such a stage...
03:38.19 brlcad possibly
03:38.29 brlcad so you doing anything more with oed/
03:38.45 brlcad the html dump that is
03:38.52 brlcad or just playing around
03:38.59 starseeker Just playing around, so far
03:39.03 brlcad k
03:39.05 starseeker testing the xhtml output
03:39.43 starseeker indicently, how do I spot the friggin unicode character if it only shows up when served from bz?
03:39.47 brlcad who was it that was trying to import the infobox wikipedia template ?
03:40.15 brlcad would be good if someone figured out what needs to happen for that to work, would be really useful for documentation
03:43.16 starseeker googles infobox...
03:43.22 brlcad you can see the unicode character in emacs
03:43.34 brlcad (as ?? in text mode or c2a0 in hexl-mode)
03:43.45 brlcad it's a no-break space character
03:45.57 starseeker should actually figure out how to get xsltproc not to generate it...
03:47.02 brlcad some insight, http://ask.metafilter.com/71246/What-the-Â
03:47.57 brlcad but yeah, better at the xsltproc phase probably, if there's a setting to output ISO 8859-1 instead of UTF-8
03:48.23 pacman87 brlcad: the infobox wiki template was me
03:50.57 andrecastelo brlcad: here, http://rafb.net/p/hWwqDq60.html (i'll delete the comments i added, though)
03:51.42 brlcad andrecastelo: does it work? :)
03:52.34 andrecastelo yep, it does, but only for the presented areas
03:56.06 starseeker brlcad: Looks like the way to do it is to correct the XSL stylesheet and use a custom one...
03:57.21 andrecastelo also, can i take struct point_list to an include/ header?? i'll need it in viewmlt.c.. though it's not that big deal
03:57.22 starseeker or perhaps I can fake it out with a fragment...
03:59.55 *** join/#brlcad dtidrow_ (n=dtidrow@c-69-255-182-248.hsd1.va.comcast.net)
04:00.30 brlcad andrecastelo: possibly
04:10.22 *** join/#brlcad kolnstyle (n=kolnstyl@adsl-71-145-187-60.dsl.austtx.sbcglobal.net)
04:11.59 CIA-21 BRL-CAD: 03brlcad * r31338 10/brlcad/trunk/include/bu.h: commentify cleanup the bu_list section
04:18.14 *** part/#brlcad thing1 (n=ric@203-59-26-22.perm.iinet.net.au)
04:23.03 starseeker brlcad: Is bz somehow forcing things to be ISO 8859-1? I'm really confused that if I load the file locally in firefox it works and the same page on bz doesn't...
04:27.41 starseeker growls at xsl and realizes setting this up isn't so simple...
04:27.50 starseeker ok, bedtime...
04:28.43 brlcad andrecastelo: it looks like there's already a linked list point structure, but it may be obsolete/unused
04:29.15 brlcad er, never mind .. not unused
04:37.48 brlcad andrecastelo: there's an rt_pt_node structure that's a simple forward linked list of point_t
04:38.43 brlcad so it'd be interested to update that structure to use bu_list instead of it's custom implementation and see what kind of impact it'd make if any on performance
04:38.55 brlcad s/interested/interesting/
04:39.56 brlcad otherwise .. both mlrt and rtarea are in the same location so your structure could be in a private header instead of something in include/
04:42.52 andrecastelo i see, i see.. the structure is in a header in include/ ?
04:43.05 brlcad yeah
04:43.23 brlcad it looks like it's basically a light-weight linked list for primitive construction
04:43.48 brlcad from the look of the primitives, it might even predate the structure
04:49.01 andrecastelo ok, i'll take a look in a while :D
04:56.04 *** join/#brlcad vedge (i=vedge@205.205.224.5)
05:01.39 *** join/#brlcad thing0 (n=ric@124-169-237-118.dyn.iinet.net.au)
06:20.07 *** join/#brlcad vedge (i=vedge@205.205.224.5)
06:28.00 *** join/#brlcad clock_ (n=clock@217-162-111-45.dclient.hispeed.ch)
06:43.00 *** join/#brlcad vedge (n=vedge@ftp.lamouvee.org)
07:41.30 *** join/#brlcad vedge (i=vedge@205.205.224.5)
09:10.17 *** join/#brlcad Elperion (n=Bary@p548768E1.dip.t-dialin.net)
09:17.44 *** join/#brlcad LeRuCh (n=ca546ac4@bz.bzflag.bz)
09:19.38 LeRuCh 05 Afternoon people!
09:20.17 *** join/#brlcad shadow4u (n=7a34444c@bz.bzflag.bz)
09:49.44 *** join/#brlcad elite01 (n=elite01@dslb-088-071-033-031.pools.arcor-ip.net)
09:50.43 *** join/#brlcad LeRuCh (n=ca546ac4@bz.bzflag.bz)
10:15.39 *** part/#brlcad LeRuCh (n=ca546ac4@bz.bzflag.bz)
10:56.57 *** join/#brlcad Elperion (n=Bary@p548768E1.dip.t-dialin.net)
12:59.21 *** join/#brlcad thing0 (n=ric@124-169-70-67.dyn.iinet.net.au)
13:03.20 *** join/#brlcad docelic_ (n=docelic@78.134.197.114)
13:19.52 brlcad finds a handful of remaining hyp issues to resolve
13:34.08 brlcad pacman87: woo hoo, looking great ... http://brlcad.org/tmp/hyp.png
13:34.34 brlcad a few things I've noticed though .. it's really hard to line up the parameters with that c parameter
13:35.29 *** join/#brlcad thing0 (n=ric@58.171.234.251)
13:35.30 brlcad I'd really like to define the height and base ellipse and have those stick .. then the c parameter just be how much to pinch
13:35.59 brlcad since the common case is likely going to be attaching it to rcc and tgc
13:36.22 brlcad I had to do my own newtonian iterative search to find the right c to get this to line up: http://brlcad.org/tmp/hyp_pinch.png
13:37.23 brlcad and I don't know how feasible it is, but it'd be really cool if it could be done without the discontinuity
13:38.22 brlcad the other two things I noticed are that the center point should be the center of the base for consistency (see the tgc as an example), not the center of the primitve (l command should list top center point too (see tgc))
13:38.52 brlcad also, the uv mapping seems off on the scaling -- you can see here: http://brlcad.org/tmp/hyp_pinch_checker.png
13:40.23 brlcad tgc has the right number of vertical sections for that scaling (10), hyp also seems to be starting from a different angle
13:41.34 brlcad after that, that just leaves the make, mirror, and gui additions and I think it'll be done! .. very cool work :-)
13:41.45 brlcad prepares an announcement
13:41.53 brlcad also packs for his flight
13:43.55 *** join/#brlcad thing1 (n=ric@203-59-111-161.dyn.iinet.net.au)
14:19.43 *** join/#brlcad thing0 (n=ric@203-59-101-160.dyn.iinet.net.au)
14:48.46 *** join/#brlcad andrecastelo_ (n=chatzill@189.71.9.76)
15:08.08 *** join/#brlcad thing1 (n=ric@203-59-26-22.perm.iinet.net.au)
15:32.02 *** join/#brlcad thing0 (n=ric@203-59-101-160.dyn.iinet.net.au)
15:41.50 *** join/#brlcad thing2 (n=ric@124-169-115-200.dyn.iinet.net.au)
15:43.57 *** join/#brlcad dtidrow_ (n=dtidrow@c-69-255-182-248.hsd1.va.comcast.net)
15:50.02 *** join/#brlcad thing3 (n=ric@203-59-26-22.perm.iinet.net.au)
16:15.49 *** join/#brlcad clock_ (n=clock@77-56-92-159.dclient.hispeed.ch)
16:40.03 *** join/#brlcad elite01 (n=elite01@dslb-088-071-033-031.pools.arcor-ip.net)
16:42.11 andrecastelo_ good morning all
16:42.18 andrecastelo_ have a good flight, brlcad :)
16:43.27 dtidrow brlcad: where are you headed?
17:43.43 andrecastelo brlcad: i've found rt_pt_node and the files that use it, so I will update everything to handle rt_pt_node with bu_lists
17:49.18 yukonbob hello, cadheads
17:49.50 andrecastelo hey hi yukonbob
17:59.41 andrecastelo http://rafb.net/p/vif2oc76.html
18:01.37 *** join/#brlcad thing0 (n=ric@124-169-115-200.dyn.iinet.net.au)
18:09.55 *** join/#brlcad andrecastelo_ (n=chatzill@189.71.35.172)
18:29.32 *** join/#brlcad andrecastelo__ (n=chatzill@189.71.35.172)
18:32.24 *** join/#brlcad clock_ (n=clock@77-56-90-201.dclient.hispeed.ch)
19:00.55 brlcad andrecastelo: still in route
19:01.14 brlcad dtidrow: was up in NY, now heading back to baltimore
19:01.40 brlcad andrecastelo: when you do that -- set up some profile tests so you can compare before and after
19:01.52 brlcad I don't suspect it'sll be any worse, but it's worth a simple sanity check
19:02.25 andrecastelo i see.. i'm correcting a little bug here in rtarea and will commit it, is that a problem?
19:03.16 andrecastelo the rt_pt_node update to bu_list will affect rpc.c, ehy.c, epa.c, eto.c and rhc.c, so i need to change those as well
19:03.46 andrecastelo are those primitives?
19:05.09 brlcad andrecastelo: fixing bugs is *never* a problem ;)
19:05.21 brlcad those are all primitives you listed
19:05.39 andrecastelo heheh, i mean commiting with the struct point_list, instead of rt_pt_node
19:05.43 pacman87 brlcad: is it possible to have two (or more) ways to give parameters to a primitive?
19:05.56 pacman87 ie, give the user the option of what data to input?
19:05.58 brlcad right parabolic cylinder, elliptical hyperboloid, elliptical paraboloid, etc
19:06.37 brlcad pacman87: not via the 'in' command
19:07.17 brlcad it's pretty linear in letting the user specify parameters in one way consistently
19:07.24 pacman87 andrecastelo: the *.c files you mentioned are
19:08.14 brlcad the "make" command provides a different way to input data in a way, creates a default that fills the current view
19:08.20 andrecastelo brlcad: i've taken a look at those files and the sections that use the structure, and made a few alterations, just a sec and i'll paste
19:08.33 brlcad then you can provide whatever editing options on the edit menu
19:09.11 brlcad that's the most common you'll find if there are other edit parameters (like increasing a length when length wasn't a creation parameter
19:11.01 brlcad andrecastelo: if you test them to work, go ahead and commit the changes -- I can (and do) just as easily review the commit e-mails
19:11.22 andrecastelo ok ok, i'll commit rtarea, it's ready
19:11.24 brlcad if there's a problem, I'd ask you to revert .. that's where small commits helps for reviewing
19:11.44 brlcad rtarea amounts to trying some test cases
19:11.48 pacman87 here's the changes i think you want, correct me if i missed anything:
19:11.48 pacman87 move vertex to center of bottom; change height to measure base to base; ellipse axes specify base dimensions; scale factor determines pinch
19:11.50 brlcad boards his flight, waves
19:12.13 poolio brlcad: have a good flight :)
19:12.20 poolio it's super hot here, don't die :(
19:13.47 andrecastelo hehe
19:13.54 andrecastelo have a good flight, cya later
19:15.38 CIA-21 BRL-CAD: 03andrecastelo * r31339 10/brlcad/trunk/src/rt/viewarea.c:
19:15.38 CIA-21 BRL-CAD: Added calculation of the presented area center. Added structure point_list, a
19:15.38 CIA-21 BRL-CAD: bu_list that holds points, and struct area got two lists - exp_points and
19:15.38 CIA-21 BRL-CAD: hit_points. The calculation of the center point is the same for both, but the
19:15.38 CIA-21 BRL-CAD: gathering of the points is different and this commit takes care of the
19:15.41 CIA-21 BRL-CAD: hit_points assembling.
19:17.29 CIA-21 BRL-CAD: 03andrecastelo * r31340 10/brlcad/trunk/src/rt/viewarea.c: Added more comments in the area_center() function, as it was a bit unclear as what the for() was doing.
19:42.42 *** join/#brlcad elite01 (n=elite01@dslb-088-071-033-031.pools.arcor-ip.net) [NETSPLIT VICTIM]
19:42.42 *** join/#brlcad dtidrow (n=dtidrow@c-69-255-182-248.hsd1.va.comcast.net) [NETSPLIT VICTIM]
19:42.42 *** join/#brlcad pacman87 (n=timothy@71.170.63.120) [NETSPLIT VICTIM]
19:48.15 *** join/#brlcad elite01 (n=elite01@dslb-088-071-033-031.pools.arcor-ip.net) [NETSPLIT VICTIM]
19:48.15 *** join/#brlcad dtidrow (n=dtidrow@c-69-255-182-248.hsd1.va.comcast.net) [NETSPLIT VICTIM]
19:48.15 *** join/#brlcad pacman87 (n=timothy@71.170.63.120) [NETSPLIT VICTIM]
19:53.56 *** join/#brlcad elite01 (n=elite01@dslb-088-071-033-031.pools.arcor-ip.net) [NETSPLIT VICTIM]
19:53.56 *** join/#brlcad dtidrow (n=dtidrow@c-69-255-182-248.hsd1.va.comcast.net) [NETSPLIT VICTIM]
19:55.06 *** join/#brlcad pacman87 (n=timothy@71.170.63.120) [NETSPLIT VICTIM]
20:00.09 *** join/#brlcad elite01 (n=elite01@dslb-088-071-033-031.pools.arcor-ip.net) [NETSPLIT VICTIM]
20:00.09 *** join/#brlcad dtidrow (n=dtidrow@c-69-255-182-248.hsd1.va.comcast.net) [NETSPLIT VICTIM]
20:07.40 *** join/#brlcad elite01 (n=elite01@dslb-088-071-033-031.pools.arcor-ip.net) [NETSPLIT VICTIM]
20:07.40 *** join/#brlcad dtidrow (n=dtidrow@c-69-255-182-248.hsd1.va.comcast.net) [NETSPLIT VICTIM]
20:19.31 *** join/#brlcad elite01 (n=elite01@dslb-088-071-033-031.pools.arcor-ip.net) [NETSPLIT VICTIM]
20:19.31 *** join/#brlcad dtidrow (n=dtidrow@c-69-255-182-248.hsd1.va.comcast.net) [NETSPLIT VICTIM]
20:21.02 *** join/#brlcad elite01 (n=elite01@dslb-088-071-033-031.pools.arcor-ip.net) [NETSPLIT VICTIM]
20:21.02 *** join/#brlcad dtidrow (n=dtidrow@c-69-255-182-248.hsd1.va.comcast.net) [NETSPLIT VICTIM]
20:23.24 *** join/#brlcad elite01 (n=elite01@dslb-088-071-033-031.pools.arcor-ip.net) [NETSPLIT VICTIM]
20:23.24 *** join/#brlcad dtidrow (n=dtidrow@c-69-255-182-248.hsd1.va.comcast.net) [NETSPLIT VICTIM]
20:48.27 *** join/#brlcad elite01 (n=elite01@dslb-088-071-033-031.pools.arcor-ip.net) [NETSPLIT VICTIM]
20:48.27 *** join/#brlcad dtidrow (n=dtidrow@c-69-255-182-248.hsd1.va.comcast.net) [NETSPLIT VICTIM]
20:58.11 *** join/#brlcad pacman87 (n=timothy@71.170.63.120) [NETSPLIT VICTIM]
21:08.58 *** join/#brlcad elite01 (n=elite01@dslb-088-071-033-031.pools.arcor-ip.net) [NETSPLIT VICTIM]
21:08.58 *** join/#brlcad dtidrow (n=dtidrow@c-69-255-182-248.hsd1.va.comcast.net) [NETSPLIT VICTIM]
22:09.34 yukonbob .
23:35.27 yukonbob build error for interested people: http://www.pastebin.ca/1041645
23:35.51 yukonbob ^--- bu_bomb issues w/ latest svn

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