IRC log for #brlcad on 20140512

00:51.45 *** join/#brlcad starseeker (~starseeke@66-118-151-70.static.sagonet.net)
01:17.36 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
01:45.57 *** join/#brlcad Zhao_Anqing (clouddrift@210.32.165.124)
01:49.02 *** join/#brlcad maths22_ (~maths22@66-118-151-70.static.sagonet.net)
01:50.51 *** join/#brlcad _zxq9_ (~ceverett@FL9-125-199-207-150.okn.mesh.ad.jp)
03:30.10 brlcad mihaineacsu_: how goes the proposal?
04:19.34 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
04:34.01 *** join/#brlcad hcurtis (b82d4651@gateway/web/freenode/ip.184.45.70.81)
04:42.01 *** join/#brlcad teepee (~teepee@gateway/tor-sasl/teepee)
06:33.27 *** join/#brlcad d_rossberg (~rossberg@66-118-151-70.static.sagonet.net)
06:52.00 *** join/#brlcad oana_ (~elf11@p5.eregie.pub.ro)
08:14.23 *** join/#brlcad Zhao_Anqing (clouddrift@210.32.163.34)
08:19.21 d_rossberg Zhao_Anqing: as a short response: your patch looks ok now
08:20.43 *** join/#brlcad _zxq9_ (~ceverett@125.199.207.150)
08:21.02 *** join/#brlcad zxq9 (~ceverett@FL9-125-199-207-150.okn.mesh.ad.jp)
08:36.14 Zhao_Anqing d_rossberg:Ok. Thank you. So next step, I should submit another patch now?
08:46.03 mihaineacsu_ brlcad: last week a had a few questions. they're still unanswered
09:00.15 *** join/#brlcad pandrei (~pandrei@188.25.163.247)
09:29.59 d_rossberg Zhao_Anqing: this would be fine, maybe for another nmg feature where a test during it's reorganization would make sense?
09:48.00 Zhao_Anqing d_rossberg: how about unit test for nmg_copy?
09:48.34 Zhao_Anqing the routines nmg_construct_XXX(..)
09:49.08 Zhao_Anqing and model * nmg_clone_model(const struct model * original)
10:09.28 *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51)
10:20.23 d_rossberg nmg_construct_~() are static functions not visible outside the nmg_copy.c source file
10:21.04 d_rossberg but a test for nmg_clone_model() would be nice
10:26.30 Zhao_Anqing OK. I will write unit test for nmg_clone_model()
10:26.33 Zhao_Anqing ^-^
10:29.28 d_rossberg i'm curious how you'll test it :)
10:37.34 *** join/#brlcad mihaineacsu (~mihaineac@92.81.148.11)
10:55.01 *** join/#brlcad teepee (~teepee@gateway/tor-sasl/teepee)
11:55.15 *** join/#brlcad devinder (~chatzilla@202.164.53.117)
13:02.03 *** join/#brlcad vladbogo (~vlad@86.127.153.104)
13:13.18 Notify 03BRL-CAD:starseeker * 60574 brlcad/trunk/src/gtools/gdiff2.cpp: I may be wrong, but I think I put more bu_ptbls into the diff3 struct than are actually needed.
13:27.29 *** join/#brlcad ries (~ries@190.9.171.121)
13:38.58 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
13:50.43 *** join/#brlcad mihaineacsu (~mihaineac@92.81.148.11)
14:07.04 *** join/#brlcad talia__ (~talia@user3-212-216.wireless.utoronto.ca)
14:11.03 talia__ Hi everyone! I have a question regarding the analysis library project, I was reading the documentation, and it seemed to me tthat gqa and rtweight/area/check have a big functionality overlap, I'm wondering if the major difference between these two are gqa has the ability to model more complicated models, when rt* is mainly for simpler models but allowing assymetic view and user-specific raytracing number and angels?
14:13.02 *** join/#brlcad vladbogo (~vlad@86.127.153.104)
15:09.59 starseeker talia__: there is a lot of overlap
15:10.39 starseeker talia__: gqa overall has more abilities, but it doens't have rtcheck and friends' ability to shoot a grid of rays off of the xyz axis vectors
15:11.19 starseeker so yes, pretty much exactly what you said, except the complexity of the model is independent of the tools
15:11.54 starseeker gqa and rt* tools can both work on pretty much any model, with the differences in technique you've outlined
15:13.30 starseeker so ultimately, what we'd like to do is get the ability to fire "patterns" of rays in the librt API, have libanalyze use that ability and do the analytical book-keeping/calculating necessary to find various physical and geometric properties, and have the tools be simply human interfaces to the underlying library capabilties
15:16.15 talia__ hmmm...would that be (mostly) modifying gqa so it could accept physical and geometric properties outlined in different rays?
15:18.19 talia__ sorry I am still a little confused...would there be any advantage of gqa over rt* tools? interms of the functional overlapping like volume and weight calculation?
15:25.31 Notify 03BRL-CAD:starseeker * 60575 brlcad/trunk/src/gtools/gdiff2.cpp: A few more steps toward 3-way merge. Untested. Need to decide how aggressive to get about merging objects - right now, not trying.
15:30.33 talia__ Hi Sean, ru still there? I just have one more question regarding the proposal, so I saw that the functionalities should be reviewed and a possible API should be proposed, would there be any other pseudo-code or things you would be expecting to see on it?(excluding the ones listed in the templates..)
15:34.03 Notify 03BRL-CAD:starseeker * 60576 brlcad/trunk/src/gtools/gdiff2.cpp: Categorize functions.
15:42.09 Notify 03BRL-CAD:starseeker * 60577 brlcad/trunk/src/gtools/gdiff2.cpp: Init properly...
15:42.59 Notify 03BRL-CAD:starseeker * 60578 brlcad/trunk/src/gtools/gdiff2.cpp: Don't forget the BU_PUT
16:04.51 Notify 03BRL-CAD:carlmoore * 60579 brlcad/trunk/src/gtools/gdiff2.cpp: fix spellings
16:18.06 *** join/#brlcad FreezingCold (~FreezingC@135.0.41.14)
16:30.46 *** join/#brlcad ries (~ries@190.9.171.121)
16:43.44 brlcad talia__: hang around long enough and you'll always get a reply ;)
16:44.29 brlcad mihaineacsu: which questions? I don't see any unanswered in my backlogs
16:48.52 mihaineacsu brlcad: where can I find the existing work on the material database project. I did find Albert Coder's patches, but I can't find the actual location of those files mentioned there.
16:50.10 brlcad mihaineacsu: daniel responded to that
16:50.24 brlcad he mentioned looking at the mailing list discussion, there was a url there
16:50.41 mihaineacsu I did check them
16:50.47 mihaineacsu ok, I'll look again
16:51.28 brlcad looks
16:54.58 *** join/#brlcad teepee (~teepee@gateway/tor-sasl/teepee)
17:00.10 brlcad mihaineacsu: try searching on "materials database brlcad-devel tar.gz"
17:02.38 Notify 03BRL-CAD:starseeker * 60580 brlcad/trunk/src/gtools/gdiff2.cpp: Use the state container instead of passing so many parameters...
17:08.30 brlcad find it?
17:10.26 mihaineacsu brlcad: yes! Thank you!
17:14.11 oana_ brlcad, hello
17:26.47 brlcad hello oana_ how goes it?
17:27.03 brlcad writing any interesting code lately?
17:27.57 oana_ good thanks, getting ready to graduate, nothing on a large scale actually : ) how are things around here?
17:42.04 Notify 03BRL-CAD:starseeker * 60581 brlcad/trunk/src/gtools/gdiff2.cpp: start adding the ability to see what diff3 is actually doing.
17:45.21 Notify 03BRL-CAD:starseeker * 60582 brlcad/trunk/src/gtools/gdiff2.cpp: report conflicts by default
17:49.26 *** join/#brlcad FreezingCold (~FreezingC@135.0.41.14)
17:51.23 *** join/#brlcad hcurtis (b82d3382@gateway/web/freenode/ip.184.45.51.130)
18:00.54 brlcad oana_: roller coaster with lots of different projects going on, but going well
18:01.05 brlcad just about to start another gsoc and socis summer
18:02.13 oana_ brlcad, that's great : D
18:06.01 brlcad oana_: working with any open source projects of late?
18:07.52 oana_ brlcad, no, I contributed a little last summer to gerbil, wrote a module and such but nothing major
18:08.37 *** join/#brlcad javampire (~ncsaba@p4FF70DB1.dip0.t-ipconnect.de)
18:18.22 Notify 03BRL-CAD:starseeker * 60583 brlcad/trunk/src/gtools/gdiff2.cpp: reorganize a bit
18:37.23 Notify 03BRL-CAD:starseeker * 60584 brlcad/trunk/src/gtools/gdiff2.cpp: Will need the diff3 container type for more than just conflicts
18:39.57 *** join/#brlcad cwstirk (~charlie@c-71-56-216-45.hsd1.co.comcast.net)
18:44.24 *** join/#brlcad kesha (~kesha@14.139.122.114)
18:53.08 *** join/#brlcad javampire (~ncsaba@p4FF70DB1.dip0.t-ipconnect.de)
19:15.27 *** join/#brlcad mihaineacsu (~mihaineac@92.81.148.11)
19:17.28 *** join/#brlcad ries (~ries@190.9.171.121)
19:52.05 Notify 03BRL-CAD:starseeker * 60585 brlcad/trunk/src/gtools/gdiff2.cpp: Refactor directory object comparision logic to avoid duplication.
19:59.18 Notify 03BRL-CAD:starseeker * 60586 brlcad/trunk/src/gtools/gdiff2.cpp: Work on reusing the same results container and info from the original diffs
20:14.28 Notify 03BRL-CAD:starseeker * 60587 brlcad/trunk/src/gtools/gdiff2.cpp: If we're going to dig down into the attributes for merging, we'll need some sort of 'hold the final product' container...
20:33.55 Notify 03BRL-CAD:n_reed * 60588 brlcad/trunk/src/libbrep/boolean.cpp: remove duplicate check
20:34.13 brlcad oana_: gerbil? what's that?
20:49.23 mihaineacsu brlcad: I believe it's this one http://gerbilvis.org/
21:07.11 *** join/#brlcad hcurtis (b82d3382@gateway/web/freenode/ip.184.45.51.130)
21:21.32 brlcad nods
21:28.46 Notify 03BRL-CAD:carlmoore * 60589 brlcad/trunk/src/nirt/nirt.c: was able to change my MANPATH and get manpage for nirt; here, I explain -E
21:40.26 *** join/#brlcad FreezingCold (~FreezingC@135.0.41.14)
23:32.16 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)

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