IRC log for #brlcad on 20140603

00:16.16 *** join/#brlcad hcurtis (b82d1ab1@gateway/web/freenode/ip.184.45.26.177)
00:21.27 hcurtis brlcad: Checking in
01:44.07 hcurtis I've tried to research this myself, but I could not find a clear answer. The page http://brlcad.org/wiki/Compiling says I should type "svn up brlcad-svn-trunk" to update the source code in the brlcad-svn-trunk directory in my VM. It then says in order to check out source code I should type "svn checkout svn://svn.code.sf.net/p/brlcad/code/brlcad/trunk brlcad" and "cd brlcad."
01:45.05 hcurtis However, since the source code I just updated is in my brlcad-svn-trunk directory, should I type "svn checkout svn://svn.code.sf.net/p/brlcad/code/brlcad/trunk brlcad-svn-trunk" instead?
02:00.34 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
02:05.46 brlcad hcurtis: you usually only checkout from svn once, and you update that checkout many many times
02:06.06 hcurtis Ohhhhh
02:06.12 hcurtis lol
02:06.21 brlcad the VM already has the sources checked out, so the instructions are saying that you only need to update those sources
02:06.49 brlcad so you can just cd brlcad-svn-trunk and run "svn update" for example
02:08.11 hcurtis I was doing it backward because that was the order those commands are in in http://brlcad.org/wiki/Compiling.
02:08.58 brlcad that is the order
02:09.16 brlcad but as the instructions make emphatic ... "WE ALREADY DID THIS FOR YOU"
02:09.27 brlcad so instead of checkout, you update
02:10.32 brlcad we didn't want everyone downloading the VM to have to do a checkout .. it takes a long time
02:10.50 brlcad but inevitably, the checkout in the VM will quickly get out of date and need to be updated
02:15.09 hcurtis The words "WE ALREADY DID THIS FOR YOU" are in the section called "Download BRL-CAD." As a result, I thought they were saying they'd already downloaded the code for me. My research told me that downloading != checking out, so I thought checking out the code was a separate step.
02:16.21 hcurtis I'm not denying I messed up. I'm just telling you how I got there.
02:17.04 Notify 03BRL-CAD:brlcad * 61074 brlcad/trunk/HACKING: fix dir typo
02:18.28 brlcad nods, you're not the first
02:19.31 brlcad if you have a suggestion to tighten up the instructions more clearly (disambiguating, not just adding more info), all ears
02:20.47 brlcad it's a fine line between explaining how to compile using tools we rely on and explaining how those tools work (which is outside the scope of that page, they have their own docs)
02:21.36 brlcad conceptually, checking out source is downloading them, but so is updating sources too
02:27.26 hcurtis brlcad: Another reason I didn't realize my method was incorrect was that the VM never complained (yet it complains often about other things). But then my reading over the weekend led me to think, wait a second, what I'm doing can't be right.
02:32.17 hcurtis I understand why you check out code---so that you can have a working copy of individual files you want to make changes to. However, I don't really understand why devs need to actually install BRL-CAD. Is it so that they can see immediately the effect that their changes have on the software?
02:37.22 brlcad you don't need to actually install
02:37.30 brlcad 99% of the time at least
02:38.05 brlcad there is a very slim category of issues that only occur from an installation location, though, so those instructions are complete
02:38.34 hcurtis Ok
02:46.23 Notify 03BRL-CAD:brlcad * 61075 brlcad/branches/RELEASE/NEWS: ugh, wrong year went unnoticed
02:47.51 hcurtis brlcad: One of the guides that came with the VM disk image says "If you want to override the current installation (not recommended until you are comfortable and successful with the build process), take the next step after completing all the above successfully" and then lists some commands. Why would a dev want to override the VM installation?
02:50.09 Notify 03BRL-CAD:brlcad * 61076 (brlcad/branches/STABLE/NEWS Property Changed: and 3 others): get the year right, merge c61075 from RELEASE
02:54.06 Notify 03BRL-CAD:brlcad * 61077 (brlcad/tags/rel-7-24-2/NEWS Property Changed: and 3 others): merge c61075 from RELEASE to get correct year into the NEWS file
03:34.03 *** join/#brlcad teepee (~teepee@gateway/tor-sasl/teepee)
04:20.26 *** join/#brlcad Notify (~notify@66-118-151-70.static.sagonet.net)
04:20.40 *** join/#brlcad brlcad (~sean@66-118-151-70.static.sagonet.net)
04:23.21 *** join/#brlcad starseeker (~starseeke@66-118-151-70.static.sagonet.net)
04:23.22 *** join/#brlcad Ch3ck (~Ch3ck@66-118-151-70.static.sagonet.net)
04:23.44 *** join/#brlcad maths22 (~maths22@66-118-151-70.static.sagonet.net)
04:23.44 *** join/#brlcad Ch3ck_ (~Ch3ck@66-118-151-70.static.sagonet.net)
04:23.58 *** join/#brlcad ejno (~ejno@unaffiliated/kazaik)
04:24.17 *** join/#brlcad n_reed (~molto_cre@66-118-151-70.static.sagonet.net)
04:27.37 *** join/#brlcad devinder (~chatzilla@202.164.53.117)
04:46.28 *** join/#brlcad devinder (~chatzilla@202.164.53.117)
04:50.46 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
04:58.14 *** join/#brlcad ejno (~ejno@unaffiliated/kazaik)
05:03.52 *** join/#brlcad ejno_ (~ejno@unaffiliated/kazaik)
05:12.17 *** join/#brlcad Ch3ck (~Ch3ck@66-118-151-70.static.sagonet.net)
05:14.19 *** join/#brlcad maths22 (~maths22@66-118-151-70.static.sagonet.net)
05:14.33 *** join/#brlcad n_reed (~molto_cre@66-118-151-70.static.sagonet.net)
05:14.34 *** join/#brlcad starseeker (~starseeke@66-118-151-70.static.sagonet.net)
05:14.43 *** join/#brlcad ejno_ (~ejno@unaffiliated/kazaik)
05:14.44 *** join/#brlcad Notify (~notify@66-118-151-70.static.sagonet.net)
05:15.11 *** join/#brlcad Ch3ck_ (~Ch3ck@66-118-151-70.static.sagonet.net)
05:17.18 *** join/#brlcad Ch3ck__ (~Ch3ck@66-118-151-70.static.sagonet.net)
05:22.37 *** join/#brlcad maths22 (~maths22@66-118-151-70.static.sagonet.net)
05:22.37 *** join/#brlcad Ch3ck__ (~Ch3ck@66-118-151-70.static.sagonet.net)
05:22.48 *** join/#brlcad Ch3ck___ (~Ch3ck@66-118-151-70.static.sagonet.net)
05:28.01 hcurtis brlcad: Thank you for answering the questions I had earlier.
05:39.26 *** join/#brlcad Zhao_Anqing (~clouddrif@183.157.160.11)
05:50.00 *** join/#brlcad Zhao_Anqing (clouddrift@222.205.111.198)
06:26.42 *** join/#brlcad oana_ (~oana@188.209.97.130)
06:49.15 Notify 03BRL-CAD Wiki:Pulkit Mittal * 7191 /wiki/User:Pulkit_Mittal/GSOC2014/logs: /* Development Logs */
07:02.12 *** join/#brlcad Ch3ck (~Ch3ck@66-118-151-70.static.sagonet.net)
07:02.13 *** join/#brlcad maths22_ (~maths22@66-118-151-70.static.sagonet.net)
07:02.13 *** join/#brlcad tofu_ (~sean@66-118-151-70.static.sagonet.net)
07:02.14 *** join/#brlcad n_reed_ (~molto_cre@66-118-151-70.static.sagonet.net)
07:02.19 *** join/#brlcad ejno_ (~ejno@unaffiliated/kazaik)
07:11.20 *** join/#brlcad Ch3ck_ (~Ch3ck@66-118-151-70.static.sagonet.net)
07:11.24 *** join/#brlcad maths22 (~maths22@66-118-151-70.static.sagonet.net)
07:11.25 *** join/#brlcad brlcad (~sean@66-118-151-70.static.sagonet.net)
07:11.27 *** join/#brlcad n_reed (~molto_cre@66-118-151-70.static.sagonet.net)
07:12.02 *** join/#brlcad Notify (~notify@66-118-151-70.static.sagonet.net)
08:34.01 *** join/#brlcad Zhao_Anqing (clouddrift@222.205.109.23)
08:36.50 *** join/#brlcad Zhao_Anqing (clouddrift@210.32.187.221)
08:40.29 *** join/#brlcad KimK (~Kim__@ip68-102-30-143.ks.ok.cox.net)
09:05.56 *** join/#brlcad Zhao_Anqing (~clouddrif@183.157.160.27)
09:19.18 *** join/#brlcad vladbogo (~vlad@195.216.218.10)
09:19.59 *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51)
09:50.51 *** join/#brlcad KimK (~Kim__@ip68-102-30-143.ks.ok.cox.net)
11:02.51 *** join/#brlcad raj12lnm (31cd6b50@gateway/web/freenode/ip.49.205.107.80)
11:25.55 *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51)
11:37.05 raj12lnm brlcad : Submitted the patch.
12:06.10 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
12:26.37 *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51)
12:34.06 *** join/#brlcad ries (~ries@190.9.171.121)
12:43.47 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
12:51.19 *** join/#brlcad d_rossberg (~rossberg@66-118-151-70.static.sagonet.net)
13:21.51 *** join/#brlcad teepee (~teepee@gateway/tor-sasl/teepee)
13:43.16 *** join/#brlcad vladbogo (~vlad@195.216.218.10)
13:45.53 Notify 03BRL-CAD:carlmoore * 61078 brlcad/trunk/doc/docbook/system/man1/en/g-x3d.xml: oops, forgot to change that -u to -P
13:49.43 Notify 03BRL-CAD:starseeker * 61079 brlcad/trunk/doc/docbook/system/man1/en/gdiff2.xml: start reworking gdiff2 man page.
13:51.24 Notify 03BRL-CAD:starseeker * 61080 brlcad/trunk/src/conv/step/step-g/OpenNurbsInterfaces.cpp: Turn the new pullback on by default - it's both faster and better.
14:13.23 Notify 03BRL-CAD:starseeker * 61081 (brlcad/trunk/include/brep.h brlcad/trunk/src/conv/step/step-g/OpenNurbsInterfaces.cpp brlcad/trunk/src/libbrep/PullbackCurve.cpp): Go ahead and remove the old pullback method - svn history has it if we need it for some reason.
14:26.36 *** join/#brlcad talia (~talia@user3-212-216.wireless.utoronto.ca)
14:44.06 *** join/#brlcad oana_ (~elf11@p5.eregie.pub.ro)
15:11.28 *** join/#brlcad ishwerdas (~ishwerdas@117.199.98.204)
15:16.17 *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51)
15:24.59 Notify 03BRL-CAD:starseeker * 61082 brlcad/trunk/src/librt/CMakeLists.txt: librt will need libbrep's includes as well.
15:34.15 raj12lnm hi brlcad:
15:53.36 *** join/#brlcad cwstirk (~charlie@c-24-9-78-79.hsd1.co.comcast.net)
16:06.26 Notify 03BRL-CAD:n_reed * 61083 brlcad/trunk/src/librt/primitives/brep/brep.cpp: address unused argc warning
16:06.53 Notify 03BRL-CAD:starseeker * 61084 (brlcad/trunk/src/libbrep/CMakeLists.txt brlcad/trunk/src/librt/CMakeLists.txt): Turn the fitting code back on - uses interpolation routines, so makes a decent simple test framework for figuring out what the TNT routines are up to.
16:26.57 *** join/#brlcad pandrei (~pandrei@188.25.160.25)
16:28.23 Notify 03BRL-CAD:starseeker * 61085 (brlcad/trunk/src/conv/step/CMakeLists.txt brlcad/trunk/src/libbrep/CMakeLists.txt and 4 others): Surprisingly, once the new pullback routine is turned on by default, it looks like we are no longer using TNT anywhere.
16:49.00 *** part/#brlcad ishwerdas (~ishwerdas@117.199.98.204)
17:10.12 *** join/#brlcad impulse (~impulse@TOROON4828W-LP140-02-2925027964.dsl.bell.ca)
17:56.14 Notify 03BRL-CAD:carlmoore * 61086 (brlcad/trunk/doc/docbook/system/mann/en/gastank.xml brlcad/trunk/src/shapes/gastank.c): in gastank and its man page, specify mm in 2 places; in man page, switch a period and right parenthesis
17:58.54 *** join/#brlcad ries_ (~ries@190.9.171.121)
18:11.36 *** join/#brlcad ries_ (~ries@190.9.171.121)
18:21.14 *** join/#brlcad albertcoder (~albertcod@117.225.206.150)
18:23.13 Notify 03BRL-CAD Wiki:Albertcoder * 7192 /wiki/User:Albertcoder/GSoC2014/logs: /* Development Period */
18:38.55 ``Erik noms his quinoa tabbouleh O.o
18:55.03 raj12lnm ``Erik what is the difference between float (*vert)[5]
18:55.10 raj12lnm and float *vert[5]
18:55.11 raj12lnm ?
19:01.09 ankesh11 raj12lnm: float (*vert)[5] means vert is a pointer to an array of floats.
19:01.30 ankesh11 float *vert[5] just means vert is an array of float pointers
19:01.56 raj12lnm ankesh11 : do you have acess to brlcad main repository ?
19:02.07 raj12lnm i mean do have it downloaded ?
19:02.13 ankesh11 Yes
19:02.28 raj12lnm ankesh11 : can you go to include/wdb.h
19:02.39 raj12lnm and also srs/libwdd/metball.c
19:02.47 raj12lnm c/srs/src
19:03.05 raj12lnm sorry for the type src/libwdb/metball.c
19:03.29 raj12lnm ankesh11 : Did you open those files ?
19:04.14 ankesh11 strange, I don't have metball.c. This is an older version though
19:05.40 raj12lnm sorry
19:05.49 raj12lnm src/libwdb/wdb.c
19:06.14 ankesh11 Okay, yes
19:06.28 raj12lnm now do you see an error in there ?
19:06.51 raj12lnm shoudn't the definition be fastf_t (*vert)[5]
19:09.07 raj12lnm wonders if ankesh11 is still there !~
19:09.33 ``Erik (*vert)[5] would mean vert is an array with a length of 5, each node being a pointer to floats... so that'd be wrong, since it should be a dynamic length array of pointers, each to an array of 5 floats...
19:10.44 ``Erik a good quick modification (like patch to get commit access sized) would be to make a metaball point struct with the point_t and two floats, so it'd be an array of those structs...
19:11.56 raj12lnm ``Erik : First I would want to know if the current is currect
19:12.05 raj12lnm suspects that it is a bug!
19:12.29 ``Erik conceptually, there is an arbitrarily sized set of these metaball control points, each control point is a physical location (vert[0], vert[1], vert[2]), a "field strength" value and a "goo" value
19:12.47 ``Erik I think the current form is correct...
19:12.57 raj12lnm yeah. That is well noted``Erik
19:13.11 raj12lnm but the concern is if the current is correct ?
19:13.28 raj12lnm shouldnt that be fastf_t (*verts)[5]
19:13.35 ``Erik it's been used in production with some large sets (thousands) without walking past a boundary and triggering a segfault
19:13.49 ``Erik no, it shouldn't be (*verts)[5]
19:13.58 raj12lnm why do you say that ?
19:14.30 ``Erik because it's not 5 arrays of floats, it's an array of float vert[5]'s...
19:14.43 raj12lnm alright I get your point
19:15.23 ``Erik you can always try to make the change and run something to see... (there's a procdb to make metaballs, then crank it through rt... I suspect if you change it, you'll get segfaults or pagefaults)
19:15.45 raj12lnm ``
19:15.51 raj12lnm Erik
19:15.56 raj12lnm can u see this patch https://sourceforge.net/p/brlcad/patches/278/
19:16.00 raj12lnm and commit it ?
19:16.18 raj12lnm i had a discussion with brlcad about it yesterday and he asked me to submit the patch
19:17.26 ``Erik I don't see any benefit to it and it removes constraints that the compiler could be using for optimization or possibly even bounds safety O.o
19:19.01 *** join/#brlcad luca79 (~luca@host137-11-dynamic.0-87-r.retail.telecomitalia.it)
19:20.36 ``Erik I'd rather let brlcad make that call since he's a little more in the mix on it, y'know?
19:21.00 *** join/#brlcad albertcoder (~albertcod@117.234.230.53)
19:21.49 *** join/#brlcad gagan (~gagan@124.253.224.219)
19:22.26 ``Erik personally, I think the patch is about equivalent to removing a 'const' *shrug* :)
19:23.09 ankesh11 brlcad: I have ported the scripts to Flot. Here's what a plot looks like: http://i.imgur.com/KFQrLdp.png
19:24.31 ankesh11 The other graphs don't yield much details due to lack of data. Would be really helpful if you can send the archived logs.
19:28.47 raj12lnm ``Erik , brlcad : as per http://unixwiz.net/techtips/reading-cdecl.html I still think it should be
19:28.57 raj12lnm fastf_t (*verts)[5]
19:29.26 raj12lnm because verts is a pointer to array of 5 fastf_t
19:30.05 raj12lnm and not verts is a 5 array of pointer to float which is eq. to fastf_t *verts[5]
19:34.20 raj12lnm ankesh11 : Did you see my point ?
19:35.27 ankesh11 raj12lnm: I did, I am not familiar with the core repository, my comments could mislead you.
19:36.09 raj12lnm alright ankesh11. But I believe it is just a matter of declaration in a widely used programming language (C) ;)
19:36.48 raj12lnm as per the article we go right first and then to left and take into account the pointers
19:36.58 raj12lnm and paranthesis
19:37.33 ankesh11 Yes, and I maintain float (*vert)[5] means vert is a pointer to an array of floats.
19:39.27 ankesh11 and not "an array with a length of 5, each node being a pointer to floats" as ``Erik had pointed out.
19:41.27 *** join/#brlcad vladbogo (~vlad@188.27.64.224)
19:41.52 raj12lnm ankesh11 : but the article suggests otherwise
19:47.32 ankesh11 raj12lnm: You missed something. I agreed to your point.
19:48.27 raj12lnm so you mean if allocate memory correctly then fastf_t (*verts)[5] can point to [[1,2,3,4,5],[0,1,2,3,4]] ?
19:48.37 Notify 03BRL-CAD Wiki:Vladbogolin * 7193 /wiki/User:Vladbogolin/GSoC2014/Logs: /* Week 3 */
19:50.18 raj12lnm where fastf_t is defined as double !
19:50.30 ankesh11 raj12lnm: Yes.
19:50.31 raj12lnm (I am sure you know this ;) )
19:51.19 raj12lnm ``Erik : I am still not sure. Can you just give a rethought
19:53.47 Notify 03BRL-CAD:carlmoore * 61087 brlcad/trunk/doc/docbook/system/mann/en/gastank.xml: oops, -h had to to be changed to -H, because -h is used now for help
19:55.41 Notify 03BRL-CAD Wiki:Ankeshanand * 7194 /wiki/User:Ankeshanand/GSoC14/logs: /* Update logs for 3rd June */
20:00.28 ``Erik I'll dig in a bit more when I have time, it's been a bit since I've done any C at all, much less non-obvious C, so I may be off :) changing it to a struct would eliminate any confusion and make things more readable all around, I'd think...
20:01.37 Notify 03BRL-CAD:vladbogo * 61088 (brlcad/trunk/src/libfb/CMakeLists.txt brlcad/trunk/src/libfb/fb_generic.c): Implemented the open function and added the framebuffer to fb_generic.
20:07.45 albertcoder vladbogo, Can I have your github account link please?
20:10.39 albertcoder vladbogo, ping
20:11.17 Notify 03BRL-CAD:starseeker * 61089 brlcad/trunk/src/libbu/tests/bu_date-time.c: time is a problem as a variable name - change it.
20:12.20 vladbogo albertcoder: this is my github account link https://github.com/vladbogo but for brlcad I use sourceforge https://sourceforge.net/u/vladbogo/profile/
20:13.20 albertcoder thanks a lot vladbogo :)
20:13.35 vladbogo you're welcome :)
20:14.05 pandrei hello :)
20:17.05 Notify 03BRL-CAD:carlmoore * 61090 (brlcad/trunk/doc/docbook/system/man1/en/gencolor.xml brlcad/trunk/src/util/gencolor.c): minor cosmetic changes to gencolor and its man page
20:24.04 raj12lnm ``Erik should i wait for brlcad for the final word on it ? the only reason I will not want to change it to a struct for now because this is a publicly exposed api. And if we make a suttle change in it I am not sure about the consequences
20:24.58 raj12lnm Also on the similar lines the mk_pipe has a similar point issue. (so if struct changes is called for i think we must uniformally change it)
20:25.36 raj12lnm ``Erik : I think since brlcad is not here currently, Do you think writting on the list will be a good idea ?
20:25.46 Notify 03BRL-CAD:starseeker * 61091 (brlcad/trunk/include/bu.h brlcad/trunk/src/fbed/char.c and 6 others): Fix bu.h to include all of the headers in the bu/ subdirectory, and rework vfont naming conventions so everything builds.
21:10.00 *** join/#brlcad starseek1r (~starseeke@66-118-151-70.static.sagonet.net)
21:50.09 Notify 03BRL-CAD:carlmoore * 61092 brlcad/trunk/doc/docbook/system/man1/en/gif-fb.xml: start fixing gif-fb manpage by trying to provide proper highlighting for command name in DESCRIPTION part
22:02.33 *** join/#brlcad KimK (~Kim__@ip68-102-30-143.ks.ok.cox.net)
22:17.43 *** join/#brlcad clock (~clock@84-72-11-5.dclient.hispeed.ch)
22:22.03 *** join/#brlcad cwstirk (~charlie@c-107-2-138-189.hsd1.co.comcast.net)
22:28.34 Notify 03BRL-CAD Wiki:Krajkreddy * 7195 /wiki/User:Krajkreddy/GSOC14/summary: /* Week2 */
22:31.59 raj12lnm alright people
22:32.05 raj12lnm signingoff
22:32.18 raj12lnm please see the patches :)
23:20.28 *** join/#brlcad starseeker (~starseeke@66-118-151-70.static.sagonet.net)
23:20.28 *** join/#brlcad tofu_ (~sean@66-118-151-70.static.sagonet.net)
23:32.00 *** join/#brlcad hcurtis (b82d1ab1@gateway/web/freenode/ip.184.45.26.177)
23:50.34 hcurtis Last week when I was working on using BRL-CAD functions like bu_malloc to run my dynamic allocation program, I did not build BRL-CAD beforehand. I chose not to because on my system it takes hours and because the dynamic allocation task doesn't involve my changing any BRL-CAD source code. Was that a mistake? In other words, should I build BRL-CAD before I try to use BRL-CAD functions to run my dynamic allocation program?

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