IRC log for #brlcad on 20140506

01:37.20 *** join/#brlcad Zhao_Anqing (clouddrift@222.205.109.192)
02:01.39 *** join/#brlcad ries (~ries@190.9.171.121)
02:48.54 *** join/#brlcad Zhao_Anqing (~clouddrif@123.157.213.169)
03:35.40 *** join/#brlcad teepee (~teepee@gateway/tor-sasl/teepee)
03:38.10 *** join/#brlcad cstirk (~charlie@c-71-56-216-45.hsd1.co.comcast.net)
03:42.19 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
03:49.45 Notify 03BRL-CAD:brlcad * 60497 brlcad/trunk/src/libbrep/PullbackCurve.cpp: make sure distance is initialized before we use it
03:55.44 *** join/#brlcad Zhao_Anqing (~clouddrif@123.157.213.148)
04:12.04 Zhao_Anqing brlcad: hi, er..I hope to make a patch to get the commit access. but the task related to my GSOC task is too hard to make a *SMALL* patch. So, could you give me some suggestion about the recommanded patch? Thank you.
05:08.46 brlcad Zhao_Anqing: patches to gain commit access can be for nearly *anything*
05:08.54 brlcad you're probably overthinking what you need to do
05:09.22 brlcad demonstrating you understand our coding indentation is probably the hardest aspect (which daniel commented on your existing patch not conforming)
05:10.37 brlcad check the TODO file or BUGS file or a previous GCI task or creating a unit test are great too
05:11.16 brlcad you could create a unit test for all of the nmg mk functions, for example
05:11.48 brlcad see src/libbu/tests or src/libbn/tests or src/librt/tests for some examples of varying quality and complexity
05:11.54 brlcad start very simple
05:13.07 Zhao_Anqing Ok. I see. Let me try to write a unit test. Thank you very much.
05:17.20 Zhao_Anqing I am trapped in this problem(make a satisfying patch) for days. Now maybe I know how to do it.
05:17.26 Zhao_Anqing @_@
05:25.22 *** join/#brlcad ishwerdas (~ishwerdas@117.220.148.203)
05:49.58 *** join/#brlcad ishwerdas (~ishwerdas@117.214.203.207)
05:54.50 *** join/#brlcad teepee (~teepee@gateway/tor-sasl/teepee)
05:56.54 *** join/#brlcad ishwerdas (~ishwerdas@117.214.203.207)
07:41.41 *** join/#brlcad luca79 (~luca@net-37-116-120-78.cust.vodafonedsl.it)
08:25.52 *** join/#brlcad ries (~ries@190.9.171.121)
08:57.57 *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51)
09:06.39 *** join/#brlcad d_rossberg (~rossberg@66-118-151-70.static.sagonet.net)
09:08.49 *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51)
09:35.29 *** join/#brlcad richa (uid11933@gateway/web/irccloud.com/x-sinnfdvfcrhclkxt)
11:06.03 *** join/#brlcad vladbogo (~vlad@109.166.130.98)
11:37.35 *** join/#brlcad Zhao_Anqing (~clouddrif@123.157.213.207)
11:43.43 ``Erik Zhao_Anqing: the right balance for how long to try before asking for help can be tricky to learn... if you're completely stuck for a full day with no progress, that might mean it's time to ask. No progress for several days is too long :) how is your unit test patch coming?
11:46.57 *** join/#brlcad caen23_ (~caen23@109.97.108.82)
11:48.21 Zhao_Anqing I am sorry for that, and prepare for it now. but is it necessary for me to write a unit test for nmg_mk? the struct model and nmgregion is no use any longer according to my proposal.
11:51.38 *** join/#brlcad KimK (~Kim__@ip68-102-30-143.ks.ok.cox.net)
11:59.18 d_rossberg Zhao_Anqing: you should write a working test for now and adapt it with your progress
12:00.36 d_rossberg so the test represents the actual state of the nmg creation routines
12:02.06 Zhao_Anqing so I can write a test for function: nmg_mm, nmg_mmr, nmg_mrsv and so on..
12:06.34 Zhao_Anqing to check, after calling these function, whether l.magic is right, pointer refer to the right object..is that right?
12:13.14 *** join/#brlcad ries (~ries@190.9.171.121)
12:37.04 d_rossberg something like this
12:42.51 *** join/#brlcad luca79 (~luca@net-37-116-120-78.cust.vodafonedsl.it)
12:45.17 Zhao_Anqing OK. Thank you. Let me try it.
12:49.10 *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51)
12:59.44 Notify 03BRL-CAD:brlcad * 60498 brlcad/trunk/src/libbu/parallel.c: looks like parallel_interface() can go away entirely because CreateThread()'s callback does indeed take an arg (and the cast was wrong). looks like it's been the API for a long time, so should be the right way.
13:04.26 Notify 03BRL-CAD:brlcad * 60499 brlcad/trunk/src/libbu/parallel.c: doesn't need to be the address
13:16.36 *** join/#brlcad luca79 (~luca@net-37-116-120-78.cust.vodafonedsl.it)
13:17.13 Notify 03BRL-CAD:brlcad * 60500 brlcad/trunk/src/libbu/parallel.c: no longer need the parallel_arg and parallel_func globals now that the non-arg parallel interface is gone.
13:18.58 brlcad Zhao_Anqing: if it takes you more than a day, make the test even smaller ... ;)
13:20.44 Zhao_Anqing That's OK. I will submit it in hours before I go to bed today.
13:28.28 *** join/#brlcad teepee (~teepee@gateway/tor-sasl/teepee)
13:53.07 *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51)
13:57.27 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
14:06.52 *** join/#brlcad hcurtis (b82d1923@gateway/web/freenode/ip.184.45.25.35)
14:21.57 *** join/#brlcad mihaineacsu (~mihaineac@p16.eregie.pub.ro)
14:55.12 brlcad Zhao_Anqing: no need to rush or stress, it's more important that this be a discussion as you learn our conventions
14:55.56 brlcad that's why these tasks really can be VERY small, just a few lines of code that do something useful and demonstrate your understanding
15:00.53 Zhao_Anqing OK. That's really kind of you. Yes, I am trying to integrate into this lovely community. Maybe I am a bit nervous/impatient when I mistake some basic rules, others' mind or something else.
15:09.20 brlcad ``Erik: do you know that all sites (https) direct to elfga?
15:09.41 brlcad hugs Zhao_Anqing
15:11.54 brlcad it's not easy living in someone else's house .. that's why we want it to become your home too, and why it's helpful to have basic discussions and move you in a little bit a timebbbb
15:12.26 brlcad there are almost certainly some chores that you might not be used to ;)
15:13.43 mihaineacsu found himself saying "awwww"
15:13.50 brlcad Zhao_Anqing: did you understand daniel's reply to your patch?
15:18.31 *** join/#brlcad mihaineacsu (~mihaineac@p16.eregie.pub.ro)
15:22.22 brlcad mihaineacsu: welcome back .. any progress on a proposal?
15:23.37 brlcad mihaineacsu: what coding experience do you have?
15:23.45 brlcad tell us some more about yourself ;)
15:24.46 mihaineacsu brlcad: Haven't got to it, I have to prepare to make a scientific presentation at my faculty (I don't know what the english equivalent is) about my undergraduate thesis - my mentor is quite excited about it and insisted I present it there.
15:25.30 mihaineacsu brlcad: but I'll get started by tommorow
15:28.14 mihaineacsu brlcad: I'm in my final of undergraduate studies, I've coding in C/C++ the first 3 years, low level stuff mostly. After that I had to opportunity to work at romanian startup where I learned stuff I had no experience with such web developement (mostly backend stuff for them) - and I found it quite fun, I love learning new stuff
15:29.13 mihaineacsu and this past year I focused more on web developement, I found there was a whole new side I had no idea about, so I just followed hackernews and tried every new technology stack I read about there
15:31.11 ``Erik brlcad: afaik, the only ssl cert on the machine is for elfga.com, so I didn't bother trying to set up the others and they get caught by the wildcard...
15:31.12 mihaineacsu I try to make the most of everything I do, for eg: I might have a boring class at school, but I go through it because you never now how it's help further on.
15:39.51 brlcad mihaineacsu: find it curious that you'd be attracted by the materials database project when your c/c++ skills are considerably more "valuable" ;)
15:40.04 brlcad nothing at all wrong with that if that is where your interest lies
15:42.16 mihaineacsu brlcad: Is there any project you would suggest?
15:42.39 brlcad ``Erik: that's what's curious, I saw no wildcard that should make it match (https://www.brlcad.org for example)
15:43.00 brlcad just the IP entry, but then it has servername set
15:43.19 brlcad mihaineacsu: depends on so many factors ;)
15:43.52 brlcad but dominated by your interests, so if that's the most interesting, there's nothing wrong with that
15:43.56 brlcad like I said, just surprising
15:45.58 brlcad what's your web dev background?
15:46.08 Zhao_Anqing brlcad: I am checking the HACKING file now. I don't understand the first point's meaning.
15:46.10 brlcad i mean in terms of technologies and languages
15:47.19 brlcad Zhao_Anqing: it says the first line in your patch is wrong, he meant the first line in test_nmg_mk.c
15:47.38 mihaineacsu I'm pretty torn apart by so many different things, it took me a while to choose my thesis subject. I finally went with "Real time multplayer games in webgl" - I'm writing it in C++ and using emscripten and asm.js to convert to js. Authoritive server side is in Node.js...the stack is pretty huge but I'm sure things will work out.
15:48.31 Zhao_Anqing I see, it should be T E S T _ N M G _ M K . C, not T E S T _ N M G _ M K . C P P. Am I right?
15:48.36 brlcad Zhao_Anqing: bingo
15:48.46 Zhao_Anqing Aha~
15:50.12 brlcad Zhao_Anqing: you'll find a lot of our rules are about consistency and code quality .. you can't have a 1M-line codebase with even the littlest mistakes going ignored or the project would eventually implode
15:51.07 mihaineacsu brlcad: Python and Javascript. Mostly Python...as platforms I've tried anything from tornado, django, to meteor.js or node.js. I have a php class at school, I'm not a big fan of it, but I'm learning how it works, it's really easy to pickup (and how really easy it is to screw up - security wise)
15:51.23 brlcad which is why we talk about making patches that are "perfect" .. not because we want it to be difficult but because it really becomes necessary in the (very) long-term (decades)
15:52.08 brlcad and if it seems "perfect" today, then it just might survive (because code is never "perfect" over time)
15:52.39 brlcad mihaineacsu: very interesting thesis
15:52.40 mihaineacsu brlcad: at the startup I've worked I also got to learn and work with continous integration, functional testings (such as selenium) and other tools
15:54.17 brlcad so then maybe the materials database really is a strong fit for you
15:55.02 mihaineacsu brlcad: is it a priority for you guys?
15:55.13 brlcad and you'd have the potential to tie in the front-end website to backend c/c++ changes that might make it even better
15:55.26 brlcad (see the "Material and Shader Objects" task)
15:56.01 brlcad priorities are somewhat irrelevant .. it's what is *interesting* to you and a strong fit for your skills
15:56.17 mihaineacsu awesome
15:56.32 Zhao_Anqing brlcad: Ok. Now I totally understand your considerate heart as well as great vision on demanding a patch..
15:56.46 brlcad mihaineacsu: this spells out our "big picture" priorities: http://brlcad.org/BRL-CAD_Priorities.png
15:57.01 brlcad but as you can see.. those are VERY broad categories
15:57.26 mihaineacsu wow
15:57.52 brlcad material infrastructure loosely fits under modeling interface and geometry services
15:59.06 mihaineacsu I'll better get to work then :D
16:00.13 ankesh11 brlcad: Where does the Benchmark project fit in? As in what would be it's application/ use-case and how would foster BRL-CAD's development?
16:01.10 brlcad mihaineacsu: I'd think it'd be incredibly helpful to have a website interace where users can load and download material information, and have that information be seamlessly integrated with our modeling (archer) and analysis (gqa) tools
16:01.43 mihaineacsu awesome :D
16:01.55 mihaineacsu brlcad: I'll prepare a list of questions tommorrow, I want to make sure I get everything right.
16:02.00 brlcad that requires both web work and c/c++ work
16:03.34 brlcad ankesh11: car analogy: the benchmark project is kind of like a car navigation system
16:04.09 brlcad it isn't strictly necessary, but it can be very interesting and incredibly helpful
16:05.50 brlcad the benchmark suite is applicable to most domains (unlike CAD), so it's useable by and exposeable to a FAR wider audience
16:06.00 brlcad the benchmark is also built on top of our most important library (our geometry ray tracing library)
16:06.43 brlcad so any improvements to or development of the benchmark become potential improvements to our library
16:07.56 brlcad but most importantly, it lets us know how fast a given piece of hardware or compiler or memory or other technology will run BRL-CAD, which is useful information for our devs and users alike
16:09.01 Notify 03BRL-CAD:brlcad * 60501 brlcad/branches/RELEASE/src/libbu/affinity.c: merge r60458 into RELEASE from trunk, pulling the blatant 1-char affinity bug fix
16:09.08 Notify 03BRL-CAD:brlcad * 60502 brlcad/trunk/NEWS: with prodding from mike busse, fixed the cpu affinity locking bug. turns out it was a simple modulo vs bitwise-and 1-char typo.
16:10.59 ankesh11 brlcad: Which brings me to another question, can the benchmark results be used as an independent measure of performance across systems? I already saw an old paper using our benchmarks to do comparison, just want to reaffirm this
16:13.23 brlcad ankesh11: absolutely, that's one of the points ;)
16:13.48 ankesh11 brlcad: That's great! :)
16:14.04 brlcad the compilations have to be "equivalent" of course, but you can compare architectures, operating systems, memory changes, compilers, etc
16:14.09 *** join/#brlcad caen23 (~caen23@109.97.108.82)
16:15.03 brlcad hi caen23
16:17.58 ankesh11 Right, and are we starting the database project from scratch or are there archives that need to be populated first?
16:29.14 *** join/#brlcad hcurtis (b82d34eb@gateway/web/freenode/ip.184.45.52.235)
16:37.57 *** join/#brlcad Swarog (~Swarog@87-207-34-29.dynamic.chello.pl)
16:39.28 brlcad ankesh11: we have some starter data, but you can probably start with "pure elements" too
16:39.42 brlcad periodic table style purity
16:43.51 ankesh11 brlcad: Right. I will start with the parsed logs from my system.
16:48.30 Notify 03BRL-CAD:brlcad * 60503 brlcad/trunk/src/tclscripts/helplib.tcl: document the comb command's options in the tcl usage
16:50.34 Notify 03BRL-CAD:brlcad * 60504 brlcad/trunk/src/libged/comb.c: use standard 'or' usage notation
16:51.17 Notify 03BRL-CAD:brlcad * 60505 brlcad/trunk/src/tclscripts/helplib.tcl: missing -l option too
16:59.28 *** join/#brlcad derric (~sol-syste@unaffiliated/sol-system-three)
17:00.46 derric Hi, I have a 2d drawing in dxf format and would like to calculate a moment of ineria for it. I understand that BRL-CAD can import the drawing and calculate the moment. Could somebody walk me though that process?
17:29.56 *** join/#brlcad Anaphaxeton (~george@ppp005054109224.access.hol.gr)
17:49.01 *** join/#brlcad Guest26388 (~george@ppp005054109224.access.hol.gr)
18:20.41 *** join/#brlcad LordOfBikes (~armin@dslb-178-010-189-034.pools.arcor-ip.net)
18:23.57 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
18:26.39 *** join/#brlcad ries_ (~ries@190.9.171.121)
20:08.09 *** join/#brlcad cwstirk (~charlie@c-71-56-216-45.hsd1.co.comcast.net)
21:13.55 Notify 03BRL-CAD:starseeker * 60506 (brlcad/branches/RELEASE/NEWS brlcad/branches/RELEASE/src/tclscripts/rtwizard/lib/Wizard.itk and 3 others): It looks like the default initial rtwizard window size wasn't quite large enough for the contents, which resulted in the buttons being compressed (apparently they are first in the 'we have to make something smaller' list). Use an iniital size large enough to avoid widget
21:13.58 Notify compression - change is due to user request. (fix merged from trunk r60273).
21:16.59 Notify 03BRL-CAD:starseeker * 60507 (brlcad/branches/RELEASE/NEWS brlcad/branches/RELEASE/src/tclscripts/rtwizard/lib/MGEDpage.itk and 3 others): Add a dialog allowing the user to manually set the view center to rtwizard's View menu (user requested feature, merged from trunk r60274).
21:22.38 Notify 03BRL-CAD:starseeker * 60508 (brlcad/branches/RELEASE/NEWS brlcad/branches/RELEASE/doc/docbook/system/man1/en/rtwizard.xml and 4 others): Added a -s option for rtwizard that mimics the one rt provides - sets the image to a square size of n pixels. (trunk r60278)
21:25.06 Notify 03BRL-CAD:starseeker * 60509 (brlcad/branches/RELEASE/doc/docbook/system/man1/en/rtwizard.xml Property Changed: and 2 others): pull doc fix from r60332
21:26.09 Notify 03BRL-CAD:starseeker * 60510 brlcad/trunk/NEWS: eyemodel issue turned out not to be an rtwizard bug
21:30.27 Notify 03BRL-CAD:starseeker * 60511 (brlcad/branches/RELEASE/NEWS brlcad/branches/RELEASE/src/libged/wdb_obj.c and 3 others): Need to make sure we restore the bu_log redirects after running bu_cmd on wdb_newcmds - otherwise, we lose bu_log output at MGED command prompt (seen when using reid, for example - trunk r60425)
21:32.11 Notify 03BRL-CAD:starseeker * 60512 (brlcad/branches/RELEASE/NEWS brlcad/branches/RELEASE/src/libged/inside.c and 3 others): Fix ellipsoid routine for the inside command. (trunk r60426)
21:34.51 Notify 03BRL-CAD:starseeker * 60513 (brlcad/branches/RELEASE/NEWS brlcad/branches/RELEASE/src/libged/rcodes.c and 3 others): Make rcodes command messages a little more informative (trunk r60427)
21:37.14 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
21:44.07 *** join/#brlcad caen23 (~caen23@109.97.108.82)
21:47.16 Notify 03BRL-CAD:starseeker * 60514 brlcad/branches/RELEASE/src/libfb/tcl.c: include string.h for strlen
21:51.34 Notify 03BRL-CAD:starseeker * 60515 (brlcad/branches/RELEASE/src/other/libpng/ANNOUNCE brlcad/branches/RELEASE/src/other/libpng/CHANGES and 113 others): Upgrade libpng to 1.6.10 (CVE-2014-0333)
21:53.57 Notify 03BRL-CAD:starseeker * 60516 brlcad/branches/RELEASE/src/conv/g-dot.c: g-dot is complaining about brlcad_ident being unused, so go ahead and use it for something.
22:02.04 *** join/#brlcad caen23 (~caen23@109.97.108.82)
22:27.50 *** join/#brlcad caen23 (~caen23@109.97.108.82)
22:32.35 brlcad starseeker: careful doing work on RELEASE ... pulling merges from trunk is kosher, but doing work on branch without pushing to trunk is going to get them out of sync (or possibly conflict) the next time a full merge is tried
22:33.53 brlcad not to mention NEWS item headaches.. ;)
22:50.22 brlcad starseeker: my bad, I see you did merge! I somehow missed the mergeinfo block in the patch and was comparing against a checkout that wasn't up to date
22:50.43 brlcad I think it's just trunk NEWS that is wrong
22:52.17 Notify 03BRL-CAD:brlcad * 60517 brlcad/trunk/NEWS: combine the news update for cliff's update to 1.6.10 with the previous 1.6.3 entry that erik did
22:52.31 brlcad is confused why he got conflicts trying to remerge that revision
22:54.51 Notify 03BRL-CAD:brlcad * 60518 brlcad/branches/RELEASE/NEWS: merge r60517 from trunk to branch, noting the libpng upgrade (fixing CVE 2014-0333)
23:18.41 *** join/#brlcad Anaphaxeton (~george@ppp005054109224.access.hol.gr)
23:29.04 *** join/#brlcad caen23 (~caen23@109.97.108.82)
23:46.26 starseeker brlcad: 60516 might cause a problem
23:46.58 starseeker but I don't know that it's needed in trunk?
23:48.06 *** join/#brlcad FreezingCold (~FreezingC@135.0.41.14)
23:48.43 *** join/#brlcad hcurtis (b82d18e7@gateway/web/freenode/ip.184.45.24.231)

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