IRC log for #brlcad on 20150820

00:49.49Notify03BRL-CAD Wiki:Bhollister * 9429 /wiki/User:Bhollister/DevLogAug2015: /* Wed, August 19, 2015 */
02:06.42Notify03BRL-CAD Wiki:Konrado DJ * 9430 /wiki/User:Konrado_DJ/GSoc2015/logs: /* 20 AUGUST 2015 */
02:44.23*** join/#brlcad kintel (~kintel@unaffiliated/kintel)
02:53.36Notify03BRL-CAD:starseeker * 66044 brlcad/trunk/misc/CMakeLists.txt: list doxygen files as ignored if we don't have doxygen installed.
02:55.41Notify03BRL-CAD:starseeker * 66045 brlcad/trunk/src/librt/CMakeLists.txt: List bot_shot.cl in cmakefiles list.
03:12.54*** join/#brlcad konrado (~konro@41.205.22.22)
04:05.40*** join/#brlcad shaina (~shaina@59.91.95.250)
05:37.11brlcadvasc__: yes, we had 5 in attendance (including hpg)
05:37.34vasc__oh?
05:37.39brlcadhas only missed 3 or 4 siggraphs since 1998
05:37.51vasc__it's a cool place
05:41.26brlcadif you were at hpg in 2009, it's quite possible that we met
05:42.18brlcadnew orleans was pretty awesome
05:45.36vasc__i was at hpg most of the time
05:46.18vasc__i hanged around with illyan georgiev and javor
05:46.33vasc__i was only presenting some poster
05:46.54vasc__i also talked with marcos fajardo a lot
05:47.28vasc__dunno if he even remembers me by now
05:47.31*** join/#brlcad gurwinder (~chatzilla@202.164.53.117)
05:48.10vasc__there's a lot of issues here...
05:48.13vasc__in the bot
05:48.53vasc__i usually read the st_specific pointer and get my fix there to send to the gpu
05:49.01vasc__but there are sooo many different formats
05:49.06vasc__and none is actually convenient
05:49.11vasc__i'll prolly have to sink deeper
05:49.16brlcadnot surprised, you haven't really had time to work on anything in depth
05:49.46brlcadby formats, what do you mean?
05:49.53brlcaddifferent object types?
05:49.59brlcador different BoT types?
05:50.46gurwinderbrlcad: I'm working on documentation. What are the things required to be submitted by me for POV-Ray exporter?
05:51.04brlcadgurwinder: erm, a complete status? :)
05:51.39vasc__bot types
05:51.55vasc__there's at least three of them it seems or four
05:51.59brlcadsee existing docs for the other converters for examples, but you will likely need to get into more detail since yours is incomplete and the incomplete pieces need to be itemized/explained
05:52.11vasc__it also has these void pointers
05:52.18vasc__and then i don't know what's inside. it's like fishing
05:52.30brlcadtwo that matter most
05:52.41brlcadvolume mode (solid) and plate mode (non-solid)
05:53.02vasc__yeah but the internal storage varies a lot
05:53.24gurwinderbrlcad: ok, I have to explain that what is required for them? I think I should be in future scope? Right?/
05:54.04vasc__i need to at least put some checks so it doesn't try to build bots it should try to build
05:54.28vasc__doing it correct will take more time. not in this timeline .
05:54.31vasc__the work timeline
05:54.38brlcadfor both types, you probably only need to be concerned with faces and verticies unless you really want to get into the detilas
05:54.50vasc__yeah i was trying to get that
05:54.55vasc__but they are stored in that format
05:55.00vasc__for doing badouel
05:55.15brlcadwithout boolean weaving, the different types don't matter so much, just need the tris and find a hit
05:55.23vasc__that's what i'm doing
05:57.35brlcadwhat void pointers were you referring to?  the only one I'm aware of is the opaque one adrt uses for it's accel structure
05:57.44brlcadthe data in rt_bot_internal is all typed
06:02.50gurwinderbrlcad: I found http://brlcad.org/wiki/Doxygen should I follow this or I have to make separate documentation.
06:02.53gurwinder?
06:04.11vasc__i'm trying to read st_spec
06:06.18brlcadgurwinder: doxygen is for commenting code -- you can and should comment your code where it will help to explain things, but that is not user documentation
08:25.49*** join/#brlcad infobot (ibot@69-58-76-73.ut.vivintwireless.net)
08:25.49*** topic/#brlcad is BRL-CAD || http://brlcad.org || logs: http://ibot.rikers.org/%23brlcad/ || Congrats to all GCI 2014 winners Peter & Marc! || Congratulations to our 12 GSoC students! || Don't ask if someone is here, just ask your questions and wait for a response. ;-)
10:01.53starseekerblinks - getting an error on pcbsd for release build - undefined reference to encode_morton3
10:04.11*** join/#brlcad konrado (~konro@41.205.22.49)
10:16.23Notify03BRL-CAD:starseeker * 66047 brlcad/trunk/src/librt/cut.c: The inline on encode_morton3 seems to cause problems with clang on PCBSD 10 when doing a release build...
10:39.38Notify03BRL-CAD:starseeker * 66048 (brlcad/trunk/misc/CMake/LEMON_Util.cmake brlcad/trunk/misc/CMake/PERPLEX_Util.cmake and 6 others): Go with PATH instead of DIRECTORY, since we aren't yet requiring CMake > 2.8.11
10:53.59starseekerscowls - xml build is busted on Haiku
10:56.25starseeker*and* the tcl build
11:56.26starseekerand libbu
11:56.30starseekergrumble
12:01.11*** join/#brlcad d_rossberg (~rossberg@66-118-151-70.static.sagonet.net)
12:13.31d_rossbergdracarys983: why do you want to add the _unused_ variables to current_state?
12:14.25d_rossbergshouldn't be the unused ones removed and the used be added to current_state?
12:35.51Notify03BRL-CAD:carlmoore * 66049 brlcad/trunk/src/librt/cut.c: remove trailing white space
12:39.33*** join/#brlcad ries (~ries@D979C47E.cm-3-2d.dynamic.ziggo.nl)
13:04.31*** join/#brlcad shaina (~shaina@117.199.84.229)
13:30.26*** join/#brlcad sofat (~androirc@202.164.45.212)
13:34.38brlcadstarseeker: undefined reference from what file?
13:35.17brlcadI don't see encode_morton3 being used anywhere, static inline may be better
13:50.14*** join/#brlcad kintel (~kintel@unaffiliated/kintel)
13:52.01brlcadstarseeker: give that a go on pcbsd
13:52.02Notify03BRL-CAD:brlcad * 66050 brlcad/trunk/src/librt/cut.c: try making the duo static inline. suspect the inline cmake test needs adjustment.
14:41.17*** join/#brlcad sofat (~androirc@202.164.45.200)
14:47.14*** join/#brlcad smile (~smile@202.164.45.212)
14:49.41sofat``Erik, Hello
14:49.57sofatI need your help regarding permissions please reply me
15:13.47*** join/#brlcad vasc (~vasc@bl13-115-211.dsl.telepac.pt)
15:23.02*** join/#brlcad ries (~ries@D979C47E.cm-3-2d.dynamic.ziggo.nl)
15:25.10*** join/#brlcad gurwinder (~chatzilla@117.212.48.236)
15:49.17*** join/#brlcad kintel (~kintel@unaffiliated/kintel)
16:11.55Notify03BRL-CAD:vasco_costa * 66051 (brlcad/branches/opencl/include/rt/primitives/bot.h brlcad/branches/opencl/src/librt/primitives/bot/bot.c and 2 others): process ocl triangle data on prep. solves a lot of headaches.
16:21.50*** join/#brlcad sofat (~smile@202.164.45.212)
16:34.56*** join/#brlcad dracarys983 (dracarys98@nat/iiit/x-sgtbhjewnqumxwqa)
16:43.57*** join/#brlcad smile (~smile@202.164.45.212)
16:47.32*** join/#brlcad ries (~ries@D979C47E.cm-3-2d.dynamic.ziggo.nl)
16:51.18Notify03BRL-CAD:vasco_costa * 66052 brlcad/branches/opencl/src/librt/cut.c: if bvh treelet nodes are too small and sah fails just cut along the middle of the list.
16:52.23Straguswonders how traversal cost heuristics could fail
16:52.37*** join/#brlcad sofat_ (~androirc@202.164.45.212)
17:01.39*** join/#brlcad Izakey (~Izakey@41.205.22.25)
17:09.12Notify03BRL-CAD:vasco_costa * 66053 (brlcad/branches/opencl/include/rt/space_partition.h brlcad/branches/opencl/src/librt/cut.c brlcad/branches/opencl/src/librt/primitives/bot/bot.c): remove some redundant message.
17:16.24*** join/#brlcad sofat (~smile@202.164.45.208)
17:37.53Notify03BRL-CAD:carlmoore * 66054 brlcad/trunk/src/conv/iges/extrudcon.c: set ellipse = 1 at INITIALIZATION
17:41.03*** join/#brlcad sofat_ (~androirc@202.164.45.212)
17:43.48Notify03BRL-CAD:vasco_costa * 66055 (brlcad/branches/opencl/include/rt/primitives/bot.h brlcad/branches/opencl/src/librt/primitives/bot/bot.c brlcad/branches/opencl/src/librt/primitives/bot/bot_shot.cl): handle clockwise oriented triangles.
17:57.54*** part/#brlcad Ch3ck_ (~Ch3ck@154.70.110.205)
18:01.02*** join/#brlcad ries (~ries@D979C47E.cm-3-2d.dynamic.ziggo.nl)
18:14.22sofatstarseeker, i have submitted two patches please accept it. ticket no 411,413
18:46.02*** join/#brlcad sofat (~smile@202.164.45.212)
19:19.53*** join/#brlcad ih8sum3r (~ih8sum3r@122.173.234.156)
19:25.59*** join/#brlcad smile_ (~smile@202.164.45.212)
19:43.28*** join/#brlcad bhollister (~brad@2601:647:cb01:9750:71b5:2c08:31db:9bd8)
19:52.01Notify03BRL-CAD:dhoward * 66056 (brlcad/trunk/src/other/PoissonRecon/CMakeLists.txt brlcad/trunk/src/other/PoissonRecon/Src/Array.h and 11 others): * Broke SPR.h/cpp into multiple functions as to make it a more suitable API fora library and in the hopes to replace code inside the PoissonRecon.cpp Execute functionto use a common code base.* Added an 'inline' keywaird to many of the functions in the '.inl' files to fix
19:52.03Notifysomemultiple definitions compile errors.* PoissonRecon_new.cpp is my 1st attempt to replace the code in the Execute functionwith a call to functions to do the processing. I could not get the code to compilewhen including 'SPR.h' so I copied some of the code in the 'SPR.h/cpp' in here andwas going to get back to the compile issues later.
19:52.05Notify...
19:56.21Notify03BRL-CAD:starseeker * 66057 (brlcad/trunk/src/libanalyze/raydiff.c brlcad/trunk/src/librt/primitives/brep/brep.cpp brlcad/trunk/src/librt/primitives/tgc/tgc.c): Enable parallel prep for raydiff - have to comment out some bu_logging in librt though, or we get Tk_FreeGC segfaults stemming from gui_output.c in src/mged/cmd.c:42
20:19.03Notify03BRL-CAD:starseeker * 66058 (brlcad/trunk/src/libanalyze/raydiff.c brlcad/trunk/src/librt/primitives/brep/brep.cpp brlcad/trunk/src/librt/primitives/tgc/tgc.c): Disable parallel prep for raydiff - still getting problems.
20:22.49Notify03BRL-CAD:starseeker * 66059 (brlcad/trunk/src/libanalyze/analyze_private.h brlcad/trunk/src/libanalyze/find_subtracted_shapes.cpp brlcad/trunk/src/libged/shape_recognition.cpp): Make a first stab at using entry/exit offsets in addition to gaps.
20:33.22*** join/#brlcad sofat (~smile@202.164.45.212)
20:43.53*** join/#brlcad sofat (~smile@202.164.45.212)
20:48.48Notify03BRL-CAD Wiki:Konrado DJ * 9433 /wiki/User:Konrado_DJ/GSoc2015/logs: /* 20 AUGUST 2015 */
20:50.16*** join/#brlcad KimK (~Kim__@ip68-102-188-176.ks.ok.cox.net)
20:55.45Notify03BRL-CAD:vasco_costa * 66060 (brlcad/branches/opencl/include/rt/primitives/bot.h brlcad/branches/opencl/src/librt/primitives/bot/bot.c brlcad/branches/opencl/src/librt/primitives/bot/bot_shot.cl): add support for triangle normals (untested).
20:58.15vascwell i think i fixed all the bugs in the triangles i could find
20:58.18vascexcept the normals
20:58.24vascthose sometimes are ok sometimes aren't
20:58.31vascits probably coz of the modes
20:59.24Notify03BRL-CAD:vasco_costa * 66061 (brlcad/branches/opencl/misc/CMake/LEMON_Util.cmake brlcad/branches/opencl/misc/CMake/PERPLEX_Util.cmake and 26 others): merge from trunk.
21:10.11*** join/#brlcad ries (~ries@D979C47E.cm-3-2d.dynamic.ziggo.nl)
21:10.55vascokay
21:11.01Notify03BRL-CAD:vasco_costa * 66062 (brlcad/trunk/include/rt/primitives/bot.h brlcad/trunk/include/rt/shoot.h and 12 others): fix bugs in ocl bot triangle data parsing. add ocl gamma correction and haze. fix a bug in hlbvh construction in certain edge cases were the primitive bounding boxes are empty. experimental ocl bot triangle normal support. phong shading lighting model.
21:11.05vascmost of the major crash bugs seem to be solved now
21:11.16vascthe normals can sometimes look screwed up in the bot
21:11.19vascbut otherwise its ok
21:11.54vascused to be you never knew when you would get a crash with loading a bot
21:35.33brlcadcool!
21:39.58ih8sum3rbrlcad: Are you free can we talk?
21:41.11kanzureask your question
21:41.59Notify03BRL-CAD Wiki:Vasco.costa * 9434 /wiki/User:Vasco.costa/GSoC15/logs: /* Development Status */
21:42.31ih8sum3rI'm facing problem while making vagrant up on server. Error : "http://paste.ubuntu.com/12137973/". I have tested things locally in virtualbox. I think we have VMware that is why I got this error. I am right?
21:43.33Notify03BRL-CAD Wiki:Vasco.costa * 9435 /wiki/User:Vasco.costa/GSoC15/logs: /* Development Status */
21:44.00ih8sum3rShould I run vagrant up provider command on server and test it?
21:44.57Notify03BRL-CAD Wiki:Vasco.costa * 9436 /wiki/User:Vasco.costa/GSoC15/logs: /* Development Status */
21:45.57Notify03BRL-CAD Wiki:Vasco.costa * 9437 /wiki/User:Vasco.costa/GSoC15/logs: /* Week 13 : 17 Aug-23 Aug */
21:57.17vascis the any way to make rt only do firsts hit tracing without csg? so i can do comparative testing
22:05.57Notify03BRL-CAD:carlmoore * 66063 brlcad/trunk/src/librt/screened_poisson.cpp: fix spelling although this is dead code
22:18.46brlcadih8sum3r: that error is not because of vmware vs virtualbox
22:18.56brlcadit says right there in the message that those are both viable providers
22:19.11brlcadand that the problem is no provider was found
22:20.30ih8sum3rso for that do we need to install anything like virtualbox?
22:22.03ih8sum3rbrlcad: My ssh stopped again, Somehow day before yesterday Erik solved it but now I'm facing the same.
22:23.07brlcadvasc: the default is to stop on the first hit, but I don't think there's a way to skip boolean evaluation
22:24.24brlcadih8sum3r: virtualbox or vmware or hyper-v must be installed for vagrant to work ... as the message says, it requires a "provider"
22:25.15brlcadi'm not sure why you're using vagrant, though -- it's not strictly necessary
22:26.37brlcadvirtualbox-ose is installed on our server
22:27.11ih8sum3rIt's the easy way to up virtual machine direct from command line. Instead of running so many command to make it up and destroy we need two commands. Vagrant up to load machine and vagrant destroy to shut it down.
22:31.10brlcadwell it's only easier when it works and you're not stuck misunderstanding the very first error message :)
22:33.44ih8sum3rYah you right. Actually on ubuntu it worked within a matter of minutes so I think I have to choose this to make it up. But now that error :-/.
22:34.53brlcadyou should be following a tutorial like this one: https://www.howtoforge.com/vboxheadless-running-virtual-machines-with-virtualbox-4.2-on-a-headless-ubuntu-12.10-server
22:35.19brlcadassuming you install virtualbox correctly, you start from step 3.1 to create you VM
22:35.53brlcadthen simply run VBoxHeadless to start it
22:36.25vasci guess i can always hit it with the nerf bat later
22:36.29ih8sum3rI haven't checked this one. Let me go through it.
22:36.45vasci just wanted to get a grasp for the speed difference when i do some benchmarking
22:37.04brlcadih8sum3r: if you have a .ovf, you can just import the config
22:37.04ih8sum3rdefinitely make it up.
22:37.34ih8sum3rYah I have .ova file of ubuntu and it's about 860MB I think.
22:37.53brlcadih8sum3r: an ova is not an ovf
22:38.10vascand i also need to use some of your tools to convert csg to triangle meshes
22:38.17vascof implicits
22:38.40vascbut we can do that later
22:39.03brlcadmost of the exporters will convert as will the facetize command in mged
22:39.17brlcadthe robustness of that conversion is highly dependent on the model
22:39.22brlcadand tolerance settings
22:39.35brlcadblack magic and dragons abound
22:40.01brlcad90% should convert without issue
22:40.07brlcadwith default settings
22:41.09ih8sum3rOkay understand what's the difference between both the files. Okay let me work on tutorial you provide me and little experiment with .ovf. Will report you when done.
22:41.21brlcadih8sum3r: you may be able to import an ova, but you'll have to read the docs on the vboxmanage command
22:41.38vasci just want to convince people why to use csg and implicits instead of triangles or whatever
22:41.49vascand when
22:41.52vascand when not to
22:41.55brlcadhttp://www.virtualbox.org/manual/ch08.html
22:42.29brlcadvasc: that's a very complex topic in itself
22:42.56brlcadmany variables, some subjective unless the reader can quantify their sensitivity requirements (most cannot)
22:43.58vasci have my own views. more compact format. more accurate results.
22:43.58brlcadif you take a single sphere, for example, and simply try to match pixel-for-pixel, it'll require approximately 1M triangles at 512x512 resolution
22:44.05vascexactly
22:44.15vascbut then someone will ask: i seldom want to display only spheres
22:44.19vasci want real models here
22:44.29vascso that's when you get the CAD stuff out
22:44.38brlcadthey seldom need pixel-matching results too, though
22:45.11brlcadthey may be happy with the 100 triangle approximation that is wildly inaccurate and incurs a 10% mass loss
22:45.49brlcadusually, it's somewhere in between based on other extrinsic factors
22:46.18ih8sum3rbrlcad: Can I get a commit access for OGV branch? If possible.
22:46.20brlcadthis is literally one of our primary domains of study
22:47.55brlcadall I'm suggesting is that you can't convince without dictating some metric (like volume/mass loss or matching pixels at some resolution)
22:48.28brlcadnot that convincing is our business, maybe your mission ;)
22:48.49brlcadI'd rather lay the facts out and have a quality slider that lets them explore the impact
22:49.56brlcadih8sum3r: have you discussed with those that have been merging your work?  
22:50.10brlcadI don't really need to be in the loop there
22:51.02ih8sum3rNot yet, but the thing is like this branches that had merged before produce so many merge conflicts.
22:51.32ih8sum3rI spend approximately 1.5 weeks to solve each and every thing to back it to normal state.
22:52.01ih8sum3rbut now shubham send PR and in that PR again approximately same merge conflicts as far as I can see
22:52.33brlcadvasc: in CAD it's far more expensive to create the model in the first place ... and repair it every time it undergoes a format or file conversion -- most want the CAD system to work with the data they have as faithfully as possible without incurring a lossy transform
22:52.36ih8sum3rso if that PR accept and merged all my hard-work in vain again.
22:52.47ih8sum3rs / accept/ accpeted
22:52.52brlcadthis is exactly why we focus on being an agnostic hybrid system
22:53.27brlcadih8sum3r: you should be discussing that with shubham
22:53.46brlcadif there's a different merge strategy he should be using, or perhaps a different branching strategy you need to be using
22:53.57brlcadsomewhere there is a failure in communication or coordination
22:54.14vasci had a lot of issues
22:54.20vascuntil i read this page
22:54.38vaschttp://svnbook.red-bean.com/en/1.7/svn.branchmerge.basicmerging.html
22:54.51brlcadvasc: they're on the git repo
22:55.07vasco
22:55.09vasch
22:55.24vascwell my advice is always run update all the time
22:55.25brlcadso yeah, it's kind of funny... someone is doing something wrong ;)
22:55.47vascand talk to each other to avoid writing in the exact same places
22:56.07brlcadthat is true for any repo, sync / up / pull frequently ;)
22:56.35ih8sum3rbrlcad: Right now in GSoC2015-merged branch everything is perfect works perfectly. But if that PR merged with it black magic will happen :D.
22:56.37vascthe earlier you run update usually the less costly the merge is
22:56.47ih8sum3rI told him to pull my work and make changes.
22:56.47vascand you should commit often too
22:56.59ih8sum3rSeems he's quite busy in college stuff
22:57.01brlcadih8sum3r: just because everything is fine on your branch doesn't mean the branch is fine
22:57.37brlcadyou could have branched off the wrong point and need to rebase, you could have rebased incorrectly at some point, the merger could be merging off a bad PR, ...
22:58.09``Erik"works for me" *punches out and heads out on vacation* :D *duck*
22:58.34brlcaddid you manually examine your PR to make sure all the commits and changes it's proposing are correct?
22:59.29``Erikdid sofats permission stuff get sorted out?
22:59.34``Erikbrlcad: how was siggraph?
22:59.36brlcadif so, you should be able to check out master and try to merge your PR, see if you get conflicts
23:00.10ih8sum3rOkay let me check it.
23:00.11brlcad``Erik: I don't know what you're talking about and fantastic
23:00.34brlcadlots of cool things, may try to summarize to the list
23:01.08brlcadgsoc ends tomorrow, though, which will mean a busy busy day :)
23:03.37brlcadonly downside was ton roosendaal gave me his cold on the last day, finally starting to get over it
23:05.23brlcadthat's what I get for trying to collaborate with those dirty blender folks
23:05.42brlcadjust kidding, they're good peoples :)
23:17.55vascnow i get why the normals are screwed.
23:18.00vascthe triangles aren't oriented ccws
23:18.36vascbot supports triangles in ccw, cw and UNORDERED order
23:18.39vascgreat uh?
23:18.58*** join/#brlcad merzo (~merzo@202-41-133-95.pool.ukrtel.net)
23:19.45vascthat blender guy seemed interesting when i saw him
23:19.50vascquite active chap
23:32.40vascso
23:59.22*** join/#brlcad kintel (~kintel@unaffiliated/kintel)
23:59.49Notify03BRL-CAD:vasco_costa * 66064 (brlcad/branches/opencl/src/librt/primitives/bot/bot.c brlcad/branches/opencl/src/librt/primitives/bot/bot_shot.cl): handle in ocl UNORIENTED, CW, and CCW triangles so the normals look ok.

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