IRC log for #brlcad on 20130903

00:00.42 *** join/#brlcad FLOSSrookie (~brian@107-200-34-111.lightspeed.tulsok.sbcglobal.net)
01:13.34 *** join/#brlcad Notify (~notify@66-118-151-70.static.sagonet.net)
01:28.48 *** join/#brlcad FLOSSrookie (~brian@107-200-34-111.lightspeed.tulsok.sbcglobal.net)
02:51.59 brlcad it has been a crazy busy day
02:52.16 brlcad zero_level: I have a little time to discuss, but not too long
02:53.44 FLOSSrookie Will my brlcad usage suffer if I do not learn Tcl?
02:56.37 brlcad FLOSSrookie: not really
02:57.14 brlcad I know of several power users that never learned Tcl
02:57.54 FLOSSrookie brlcad: Just how do the programmers use Tcl in brlcad? Are core components written in it or just c and c++ for features?
03:00.03 brlcad Ch3ck_: I'd be inclined to believe octave's output as well, but not when writing a unit test -- you need provable values, not subjectively believable ones
03:00.34 FLOSSrookie brlcad: But if I ever did learn enough about programming I think brlcad would be a great thing to contribute to. If I ever (in my dreams probably) became proficient enough to contribute would Tcl be necessary then or really just c and c++?
03:01.20 brlcad Ch3ck_: you need to find some inputs that clearly demonstrate that either bn_poly_sub is wrong, or that octave is (provably) right for a given specific equation where the two results differ
03:02.35 brlcad Ch3ck_: I suggest devising a more simply polynomial (by hand), do the subtraction (by hand), and look at what bn and octave produce as their outputs, see if they differ from your hand-written result significantly
03:03.45 brlcad zero_level: lots of great questions in the paste -- great discussion pending
03:04.15 brlcad FLOSSrookie: almost the entire GUI is in Tcl/Tk
03:05.34 brlcad if you're interested in contributing, Tcl would not really be necessary, nor C++ -- you won't get very far (in BRL-CAD) without C though
03:06.12 brlcad that said, there are some great simply tutorials on the web on how to create geometry using a scripting language (like shell script, perl, and python, iirc)
03:25.43 *** join/#brlcad FLOSSrookie (~brian@107-200-34-111.lightspeed.tulsok.sbcglobal.net)
03:27.02 FLOSSrookie I am sorry. My Internet connection from AT&T is junk. It might go down again very soon. Sometimes it goes down for an hour, two hours, or all day or all week.
03:27.02 FLOSSrookie So, I will paste my questions from before:
03:27.02 FLOSSrookie brlcad: Just how do the programmers use Tcl in brlcad? Are core components written in it or just c and c++ for features?
03:27.02 FLOSSrookie brlcad: But if I ever did learn enough about programming I think brlcad would be a great thing to contribute to. If I ever (in my dreams probably) became proficient enough to contribute would Tcl be necessary then or really just c and c++?
03:35.31 FLOSSrookie Anyone?
04:08.22 *** join/#brlcad FLOSSrookie (~brian@107-200-34-111.lightspeed.tulsok.sbcglobal.net)
05:25.44 *** join/#brlcad kesha__ (~kesha@14.139.122.114)
05:31.21 *** join/#brlcad FLOSSrookie (~brian@107-200-34-111.lightspeed.tulsok.sbcglobal.net)
05:38.56 Notify 03BRL-CAD:phoenixyjll * 57401 brlcad/trunk/src/libbrep/intersect.cpp: Don't return NULL if split failed. Just duplicate that curve.
06:53.10 *** join/#brlcad caen23 (~caen23@92.81.216.3)
06:54.29 *** join/#brlcad FLOSSrookie (~brian@107-200-34-111.lightspeed.tulsok.sbcglobal.net)
06:59.45 Notify 03BRL-CAD Wiki:KeshaSShah * 0 /wiki/File:Layers.jpg:
07:11.36 Notify 03BRL-CAD Wiki:KeshaSShah * 0 /wiki/File:ScreenshotForLayers.png:
07:16.16 Notify 03BRL-CAD Wiki:KeshaSShah * 6082 /wiki/User:KeshaSShah/GSoC13/Reports: /* Week 12 */
07:38.55 zero_level brlcad : can we have at 1830hrs GMT ?
07:39.05 zero_level or now ?
07:42.09 kesha__ 00:00 IST !! :D
07:46.12 Ch3ck_ brlcad: thats what i'm doing now ;). Also I have finished with the pull _interface(synopsis, documentation and regression tests). I have uploaded the patch to sf. Awaiting your approval ;)
07:48.17 Ch3ck_ working on unit test now..
07:52.55 Notify 03BRL-CAD:phoenixyjll * 57402 (brlcad/trunk/include/brep.h brlcad/trunk/src/libbrep/boolean.cpp brlcad/trunk/src/libbrep/intersect.cpp): It seems that the original implementation didn't reuse surface trees and curve trees actually. The NULL pointers passed in doesn't have any effects. And only call build_curve_root() and build_surface_root() if the tree passed in is NULL.
08:11.41 Notify 03BRL-CAD:phoenixyjll * 57403 (brlcad/trunk/include/brep.h brlcad/trunk/src/libbrep/boolean.cpp): Initialize the root node.
08:14.54 *** join/#brlcad FLOSSrookie (~brian@107-200-34-111.lightspeed.tulsok.sbcglobal.net)
08:27.09 Ch3ck_ brlcad: fixed the problem. The error was on my part. The bn_poly_sub() routine works fine
08:27.25 Ch3ck_ brlcad: uploaded patch which fixes problem
08:32.14 Ch3ck_ https://sourceforge.net/p/brlcad/patches/224/
08:46.28 Notify 03BRL-CAD Wiki:NyahCh3ck20 * 6083 /wiki/User:NyahCh3ck20/GSoc2013/Coding_Repor: /* Sept 02 - Sept 08 */
09:16.19 Notify 03BRL-CAD Wiki:Phoenix * 6084 /wiki/User:Phoenix/GSoc2013/Reports: /* Week 12 */
10:54.49 FLOSSrookie Just how do the programmers use Tcl in brlcad? Are core components written in it or just c and c++ for features?
11:04.15 *** join/#brlcad kesha__ (~kesha@14.139.122.114)
11:06.27 *** join/#brlcad vladbogo (~vlad@188.25.239.225)
11:20.12 Ch3ck_ well tcl is what brings it all together
11:20.23 Ch3ck_ the core components are mostly in c and C++
11:20.37 Ch3ck_ while tcl serves as the interface between them
11:23.16 FLOSSrookie Ch3ck_: So, the most important then is C and C++ in brlcad? I just want to know because I am selecting a small group of languages to learn and if I ever become proficient enough I would like to add functionality to brlcad.
11:24.07 FLOSSrookie I do now want to multiply languages past necessity. I only want what is most important and if I can get away with not learning one it makes room for another.
11:24.15 FLOSSrookie I do not want ^
11:30.13 Ch3ck_ well C/C++ is very ok and especially C which is at the core of BRL-CAD
11:30.51 Ch3ck_ learning that is ok and you'll be able to contribute greatly. tcl is a scripting language will not be hard to pick up once you're great in c/c++ ;)
11:31.15 Ch3ck_ gives FLOSSrookie some encouragement to learn how to code ;)
11:32.39 FLOSSrookie Ch3ck_: How many languages are too many? Five? Six? Seven?
11:38.06 Ch3ck_ I don't understand what you mean
11:39.02 FLOSSrookie Being new I do not want to overdo it and end up hating programming. Should I just pick five languages or less or more?
11:39.16 Ch3ck_ ahhh
11:39.21 Ch3ck_ start with one at a time
11:39.29 Ch3ck_ it all depends on the direction you want to take
11:39.33 Ch3ck_ programming is very broad
11:39.43 Ch3ck_ since you want to work on BRL-CAD
11:39.50 Ch3ck_ start with C
11:39.53 Ch3ck_ then C++
11:39.57 Ch3ck_ you're good to go
11:40.01 Ch3ck_ or C
11:40.05 Ch3ck_ and you're good to go
11:40.50 FLOSSrookie Ch3ck_: Okay, well thanks :)
11:41.09 Ch3ck_ its ok
11:41.22 Ch3ck_ no matter which you choose make sure you master it well ;)
11:41.33 Ch3ck_ and you're good to go ;)
11:41.40 ``Erik FLOSSrookie: do you do any scripting?
11:43.11 FLOSSrookie ``Erik: Well, I did try and do some Tcl before but not much was done. Some bash for linux admin.
11:44.09 ``Erik ok, how about this for an analogy, TCL is used as the 'bash' in BRL-CAD and C is what the kernel for BRL-CAD is written in, that work? :D
11:44.31 FLOSSrookie Sure!
12:02.04 ``Erik (also; learning 1 programming language is hard, learning 2 is a little tricky, after 3 they get pretty easy... once you're competent in the 4 paradigms, any language is easy)
12:03.55 *** join/#brlcad d_rossberg (~rossberg@66-118-151-70.static.sagonet.net)
12:38.09 Ch3ck_ yeah
12:46.49 *** join/#brlcad mpictor_ (~mpictor_@2600:1015:b106:47ca:0:1a:e3ac:b601)
12:57.24 zero_level kesha : thanks for pointing that out.
12:57.39 zero_level Actually I thought I wld be free around that time.
12:57.49 zero_level But anyways got free early.
13:23.19 *** join/#brlcad kesha (~kesha@14.139.122.114)
13:37.34 *** join/#brlcad Ch3ck_ (~Ch3ck@195.24.220.16)
14:07.39 *** join/#brlcad kesha_ (~kesha@14.139.122.114)
14:08.26 *** join/#brlcad mpictor_ (~mpictor_@2600:1015:b106:47ca:0:1a:e3ac:b601)
15:33.36 *** join/#brlcad FLOSSrookie (~brian@107-200-34-111.lightspeed.tulsok.sbcglobal.net)
15:41.25 starseeker getting a crash with libicv in the regressions - bu_malloc error triggered at src/libicv/encoding.c:53
15:41.56 starseeker CMAKE_BUILD_TYPE is Release - not sure if that is making a difference yet
15:49.04 zero_level starseeker : looking at the matter.
15:49.18 zero_level can you paste the error somewhere ?
16:46.12 *** join/#brlcad caen23 (~caen23@92.85.94.187)
16:47.39 *** join/#brlcad kimzzzz (~AndChat31@1.38.26.91)
16:53.09 *** join/#brlcad zero_level (~mohit@66-118-151-70.static.sagonet.net)
17:06.02 *** join/#brlcad FLOSSrookie (~brian@107-200-34-111.lightspeed.tulsok.sbcglobal.net)
17:24.23 Ch3ck_ starseeker: fixed the error with bn_poly_sub() could apply the patch please?
17:24.33 Notify 03BRL-CAD Wiki:KeshaSShah * 6085 /wiki/User:KeshaSShah/GSoC13/Reports: /* Week 12 */
17:26.36 zero_level pokes at the Notify
17:26.56 Notify 03BRL-CAD:mohitdaga * 57404 (brlcad/trunk/regress/asc2dsp.sh brlcad/trunk/src/libicv/bw.c brlcad/trunk/src/libicv/pix.c): Ensure that image with zero size (that is no data) is not read. And null is passed if such a condition ever prevail. This is needed due to the latest improvement in icv_read where we have facility to read images of any size without specifying the size.
17:27.18 zero_level starseeker : after r57404 this error must be solved.
17:27.22 zero_level Please check.
17:27.23 zero_level thanks.
17:34.10 *** join/#brlcad FLOSSrookie (~brian@107-200-34-111.lightspeed.tulsok.sbcglobal.net)
17:40.55 Notify 03BRL-CAD:mohitdaga * 57405 brlcad/trunk/regress/asc2dsp.sh: We might not need this strict flag. Thanks to the latest improvements in the icv_read. (brlcad, Erik, starseeker I see something fishy with the image in asc2dsp.sh. Please have a look.)
17:45.33 ``Erik zero_level: please don't put requests like that in the commit line, irc or email is preferred (commit message should be the what/why to help people understand your commit)
18:16.28 zero_level ``Erik : ok.
18:18.14 zero_level ``Erik :I will take care in future. Do you see the point ? I am not sure why we would like to pass a zero size image to that utility. That to when we are regressing.
18:18.41 zero_level c/to/too
18:29.41 Notify 03BRL-CAD Wiki:Harman052 * 6086 /wiki/User:Harman052/GSoc2013/Logs:
19:00.21 *** join/#brlcad caen23_ (~caen23@92.83.167.88)
19:20.31 starseeker scowls - looks like the librt internal tree doesn't have the necessary information to translate node names into directory pointers on the fly
19:21.29 starseeker brlcad: can we tack on the necessary pointers somewhere without breaking compabibility?
19:22.21 starseeker compatibility rather
19:28.55 *** join/#brlcad kimzzzz (~AndChat31@1.38.26.91)
20:03.16 *** join/#brlcad mpictor__ (~mpictor_@2601:d:b280:3d4:f87a:3a31:70c6:a66d)
20:23.44 Notify 03BRL-CAD:starseeker * 57406 brlcad/trunk/src/conv/step/g-step/ON_Brep.cpp: Make a stab at adding support for Rational curves
20:26.58 Notify 03BRL-CAD:starseeker * 57407 brlcad/trunk/src/conv/step/g-step/ON_Brep.cpp: set curve degree
21:13.29 Notify 03BRL-CAD Wiki:Vladbogolin * 6087 /wiki/User:Vladbogolin/GSoC2013/Logs: /* Week 12 */
21:16.47 *** join/#brlcad caen23 (~caen23@92.83.167.88)
21:16.48 Ch3ck_ running 2 bed
21:31.11 *** join/#brlcad mpictor (~mark@2601:d:b280:3d4:d63d:7eff:fe2d:2505)
22:05.25 Notify 03BRL-CAD:tbrowder2 * 57408 brlcad/trunk/doc/docbook/system/man3/en/CMakeLists.txt: add man page for popt(3) option processing library

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