IRC log for #brlcad on 20130417

00:00.32starseekerwonders if there's a way to automatically message first timers on the channel about sticking around...
00:00.53starseeker``Erik: did Notify get clogged up again?
00:11.49Notify03BRL-CAD:carlmoore * 55164 brlcad/trunk/src/librt/db_io.c: fix warning about expecting long unsigned int
00:12.00Notify03BRL-CAD:carlmoore * 55165 brlcad/trunk/src/conv/comgeom/cvt.c: add version number when printing out requirements per verbose mode
00:13.05Notify03BRL-CAD:carlmoore * 55166 brlcad/trunk/src/conv/conv-vg2g.c: make reference to prompts that may be needed
00:13.47Notify03BRL-CAD:starseeker * 55167 brlcad/trunk/src/other/poly2tri/poly2tri/common/shapes.h: MSVC didn't define __FLT_EPSILON__ - use FLT_EPSILON instead
00:14.07Notify03BRL-CAD Wiki:Phoenix * 4997 /wiki/User:Phoenix/GSoc2013/Proposal: /* Calculating surface-surface intersection curves */
00:14.09Notify03BRL-CAD Wiki:Phoenix * 4998 /wiki/User:Phoenix/GSoc2013/Proposal: /* Calculating surface-surface intersection curves */
00:14.11Notify03BRL-CAD Wiki:Phoenix * 4999 /wiki/User:Phoenix/GSoc2013/Proposal: /* Calculating surface-surface intersection curves */
00:14.13Notify03BRL-CAD Wiki:Phoenix * 5000 /wiki/User:Phoenix/GSoc2013/Proposal: /* Split the surfaces and generate new trimmed sub-surfaces using intersection curves */
00:14.15Notify03BRL-CAD Wiki:Phoenix * 5001 /wiki/User:Phoenix/GSoc2013/Proposal: /* Calculating surface-surface intersection curves */
00:14.17Notify03BRL-CAD Wiki:Starseeker * 5002 /wiki/Google_Summer_of_Code/Project_Ideas: /* Mentors */ Update mentor list
00:14.19Notify03BRL-CAD Wiki:Starseeker * 5003 /wiki/Google_Summer_of_Code/Project_Ideas: /* Other Tool Projects */ Remove clone tool until we have a proper project definition
00:14.21Notify03BRL-CAD Wiki:Starseeker * 5004 /wiki/Google_Summer_of_Code/Project_Ideas: /* Project Categories */ tweaks
00:14.23Notify03BRL-CAD Wiki:Phoenix * 5005 /wiki/User:Phoenix/GSoc2013/Proposal: /* Split the surfaces and generate new trimmed sub-surfaces using intersection curves */
00:14.25Notify03BRL-CAD Wiki:Starseeker * 0 /wiki/Vector_output_from_raytracing:
00:14.27Notify03BRL-CAD Wiki:Starseeker * 5009 /wiki/Google_Summer_of_Code/Project_Ideas: /* Project Categories */ shuffle some tasks around
00:14.29``Erikanother fruity email gumming up the parser :/
00:14.29Notify03BRL-CAD Wiki:Phoenix * 5010 /wiki/User:Phoenix/GSoc2013/Proposal: /* Split the surfaces and generate new trimmed sub-surfaces using intersection curves */
00:14.31Notify03BRL-CAD Wiki:Phoenix * 5011 /wiki/User:Phoenix/GSoc2013/Proposal:
00:14.33Notify03BRL-CAD Wiki:Phoenix * 5012 /wiki/User:Phoenix/GSoc2013/Proposal: /* Computation of the new solid model */
00:14.35Notify03BRL-CAD Wiki:Phoenix * 5013 /wiki/User:Phoenix/GSoc2013/Proposal: /* Calculating surface-surface intersection curves */
00:14.37Notify03BRL-CAD Wiki:Phoenix * 5014 /wiki/User:Phoenix/GSoc2013/Proposal: /* Split the surfaces and generate new trimmed sub-surfaces using intersection curves */
00:14.39Notify03BRL-CAD Wiki:Phoenix * 5015 /wiki/User:Phoenix/GSoc2013/Proposal: /* Computation of the new solid model */
00:14.41Notify03BRL-CAD Wiki:Phoenix * 5016 /wiki/User:Phoenix/GSoc2013/Proposal: /* Other ideas */
00:14.42starseeker``Erik: heh - thanks :-)
00:14.43Notify03BRL-CAD Wiki:Phoenix * 5017 /wiki/User:Phoenix/GSoc2013/Proposal: /* Deliverables */
00:14.45Notify03BRL-CAD Wiki:Phoenix * 5018 /wiki/User:Phoenix/GSoc2013/Proposal: /* Why me */
00:14.47Notify03BRL-CAD Wiki:Phoenix * 5019 /wiki/User:Phoenix/GSoc2013/Proposal: /* Links */
00:14.49Notify03BRL-CAD Wiki:Phoenix * 5020 /wiki/User:Phoenix/GSoc2013/Proposal: /* Links */
00:14.51Notify03BRL-CAD Wiki:Phoenix * 5021 /wiki/User:Phoenix/GSoc2013/Proposal: /* Links */
00:14.53Notify03BRL-CAD Wiki:Phoenix * 5022 /wiki/User:Phoenix/GSoc2013/Proposal: /* Computation of the new solid model */
00:14.55Notify03BRL-CAD Wiki:Phoenix * 5023 /wiki/User:Phoenix/GSoc2013/Proposal: /* Computation of the new solid model */
00:14.57Notify03BRL-CAD Wiki:Phoenix * 5024 /wiki/User:Phoenix/GSoc2013/Proposal: /* Development schedule */
00:14.59Notify03BRL-CAD Wiki:Phoenix * 5025 /wiki/User:Phoenix/GSoc2013/Proposal: /* Development schedule */
00:15.01Notify03BRL-CAD Wiki:Phoenix * 5026 /wiki/User:Phoenix/GSoc2013/Proposal: /* Development schedule */
00:15.03Notify03BRL-CAD Wiki:Phoenix * 5027 /wiki/User:Phoenix/GSoc2013/Proposal: /* Development schedule */
00:15.05Notify03BRL-CAD Wiki:Phoenix * 5028 /wiki/User:Phoenix/GSoc2013/Proposal: /* Development schedule */
00:15.07Notify03BRL-CAD Wiki:Phoenix * 5029 /wiki/User:Phoenix/GSoc2013/Proposal: /* Time availability */
00:15.09Notify03BRL-CAD Wiki:Phoenix * 5030 /wiki/User:Phoenix/GSoc2013/Proposal: /* Why BRL-CAD */
00:15.11Notify03BRL-CAD Wiki:Phoenix * 5031 /wiki/User:Phoenix/GSoc2013/Proposal: /* Why me */
00:15.13Notify03BRL-CAD Wiki:Phoenix * 5032 /wiki/User:Phoenix/GSoc2013/Proposal: /* Development schedule */
00:15.15Notify03BRL-CAD Wiki:Starseeker * 5033 /wiki/NURBS_Intersections: Clarify that the project links don't have source code we can use, just research papers.
05:08.17*** join/#brlcad caen23_ (~cezar@92.81.161.99)
08:23.57*** join/#brlcad hsrai (~hsrai@202.164.53.116)
10:16.08*** join/#brlcad hsrai (~hsrai@202.164.53.116)
10:44.53*** join/#brlcad aks001 (uid10889@gateway/web/irccloud.com/x-ybbwnqxokpliteog)
11:08.34*** join/#brlcad Abhishek91 (~Abhishek9@122.166.157.182)
11:14.42Abhishek91Hi everyone. Are there any GSOC mentors online currently ?
11:46.03*** join/#brlcad vladbogo (~vlad@188.25.239.23)
12:56.20*** join/#brlcad caen23 (~cezar@92.81.178.46)
13:39.45*** join/#brlcad brlcad (~sean@66-118-151-70.static.sagonet.net)
13:39.47*** join/#brlcad maths22 (~gcimaths@66-118-151-70.static.sagonet.net)
14:11.01*** join/#brlcad maths22 (~gcimaths@66-118-151-70.static.sagonet.net)
14:11.46*** join/#brlcad brlcad (~sean@66-118-151-70.static.sagonet.net)
14:13.22*** join/#brlcad n_reed (~molto_cre@66-118-151-70.static.sagonet.net)
14:40.58brlcadAbhishek91: you're welcome to discuss you proposal here openly any time
14:41.12brlcadresponses may be immediate or hours later, but someone responds when we can
14:42.44Abhishek91thats perfect ! i just wanted to ask about the website development project listed in the ideas page
14:43.14Abhishek91i have good experience in developing websites/tools in django
14:43.19brlcadI was just responding to your e-mail
14:43.44brlcadfirst up, what's the name of our org? :)
14:44.11Abhishek91brl-cad ? :P
14:44.33brlcadthat's better than your intro email :)
14:45.47Abhishek91haha my bad :)
14:47.06Abhishek91i guess its because of my habbit of writing blr .. a short-form for where i live :p .. bangalore
14:47.10*** join/#brlcad Notify (~notify@66-118-151-70.static.sagonet.net)
14:47.35brlcadunderstandable
14:49.15Abhishek91i see that your requirement says that you need a long term contributor :) i'm willing to put in time into managing the website after the duration of the summer of code as well !
14:50.55brlcadyeah, we don't just want a site developed
14:50.59brlcadthat's nearly useless by itself
14:51.19brlcadit needs to be polished, integrated, understood, communicated, maintained, ...
14:53.40brlcadAbhishek91: I just replied so you can follow up there or here to discuss
14:56.13Abhishek91sure i understand ! is there anything i could do to get started from a web developer's perspective.. to further understand what is required of me ?
14:58.16brlcadyes, lots of reading
14:58.19brlcadsee last year's work
14:58.56brlcadalso, download and compile brl-cad optimized, run the benchmark, become familiar with everything in the output log
14:59.07Abhishek91i got the mail :) thank you so much
14:59.22Abhishek91sure ! will do that tonight !
15:00.00brlcadthe more you know and understand, the more detail you'll be able to put into a proposal
15:00.39brlcadjust, like I mention in the e-mail, make sure you account time for LOTS of discussions, following our coding guidelines, and integrating your work
15:01.17brlcada good patch might be to make some useful enhancement or modification to his existing code (after you get it up and running) so you can demonstrate a working understanding
15:01.39vladbogohello
15:01.52Abhishek91sounds good !
15:02.04vladbogoi am interested in the New Cross-Platform 3D Display Manager project
15:02.11brlcadhi vladbogo, welcome
15:02.19vladbogothanks:)
15:02.39brlcadvladbogo: sounds great -- that's a tough one so you have a lot of homework ;)
15:02.46vladbogoi received your mail and started to read the documentation about the display tools
15:03.27vladbogoyou warned me about that in the mail but the project seems really interesting to me so I am willing to invest a lot of time
15:04.15brlcadthat's great because it'll probably require a lot of time ;)
15:04.45vladbogoi started by reading the manpages for the tools indicated and managed to make a brief idea about how things work
15:04.49brlcadit's a challenge not because of qt/ogre/whatever, but because you're going to have to understand the existing code in order to extend it
15:05.08brlcadunderstanding the difference between a framebuffer and a display manager, for example
15:05.51brlcada low-level way you can see a DM in action, run "mged -c" and it'll prompt you for which DM to run
15:06.06brlcadnu == NULL or no display manager
15:06.26brlcadX or ogl obviously refer to different ones ;)
15:07.03vladbogothanks
15:07.06brlcadportions of their source are in src/libdm but also in src/mged/dm* (unfortunatley, that's something to clean up and eliminate)
15:07.26vladbogoi looked there
15:07.57vladbogoand to be honest it seemed quite overwhelming
15:08.12brlcadwhich crash course intro: mged -c test.g then "make sph sph" .. you just make a sphere, wireframe displays in the DM, run "rt" and a framebuffer window should pop up with a rendering
15:08.29brlcadyes
15:08.35brlcaddon't be overwhelmed :)
15:08.39brlcadask questions
15:08.48vladbogobut what i understood is that the tk framework is used
15:08.49brlcadwe're here to help answer questions and explain things
15:09.02vladbogothanks a lot
15:09.26brlcadtk framework is used if you run mged without the -c or if you run the "gui" command
15:09.54brlcadtk framework is otherwise not used
15:10.14brlcadthere was an effort a few years ago to create a tk DM, but that work is incomplete (src/libdm/dm-tk.c
15:10.23vladbogoand also it isn't clear if qt/ogre should be integrated in tk?
15:17.33brlcadif it's qt/ogre, it should not involve tk
15:18.20brlcadit could be qt/ogre or tk/ogre or pure tk/ogl or pure qt/ogl
15:18.52brlcaddon't want to unnecessarily involve technologies where they provide no benefit
15:19.12vladbogothanks
15:20.04vladbogoi think that now the most important part is to study the code
15:21.19vladbogowhich to you think it would be better making a patch or trying to get to know as many information about what is done and where rather than concentrating on a particular part?
15:25.04brlcad"yes"
15:25.21brlcadyou have to balance those
15:25.27brlcadno patch == no proof
15:25.33brlcadno research == no useful patch
15:25.52vladbogook i understood
15:26.16vladbogoi haven't been clear enough but you answered my question
15:26.23brlcadsomething you could work on might be to create a debug DM that actually works
15:26.44brlcadcompletely non-graphical, a DM that just prints/logs calls
15:27.29vladbogoand another question
15:28.04brlcadi.e., that'd be a good patch that would also help you understand the code
15:28.20brlcadso you'd have a better idea of what you'd need to do and describe in your proposal
15:28.50brlcadthe DM interface is basically a set of callback functions that get defined
15:29.10brlcadso you'd be stubbing in a bunch of empty functions first, just to get it to show up as a mged -c option
15:29.29brlcadthen make it print something useful instead of empty functions
15:30.25vladbogothat seems interesting
15:31.12vladbogois there any place where i could get some more information about this?
15:31.22brlcadhere?
15:31.31vladbogo:)
15:31.42brlcadcan start by following one of the existing DM interfaces, like DM_OGL or DM_TK
15:32.07vladbogothanks
15:32.10brlcadsearching for one of those will pull up all the places you'd probably need to edit to add your new debug interface
15:32.40brlcadand you'd add your DM_TEXT or DM_DEBUG similarly
15:32.59brlcadlikes DM_TXT
15:35.13vladbogothen i will start working and put questions on the way
15:35.25vladbogothank you very much for your help
15:35.36brlcadagain, don't get frustrated or overwhelmed
15:35.50vladbogo:)
15:36.00brlcadit's a LOT of code, you're not expected to just jump in and starting creating a better interface than AutoCAD
15:36.01vladbogohope so
15:36.14brlcadthat's next week
15:37.39vladbogothanks again
16:54.46*** join/#brlcad Ch3ck (~Ch3ck@41.205.14.251)
16:54.59Ch3ckHi I
16:55.55Ch3ckwish to work implement a pull routine for performing the opposite of the matrix push on geometry
16:56.12Ch3ckbut i don't have a reference to where the matrix is defined in the src
17:00.13brlcadhello Ch3ck
17:00.52brlcadCh3ck: our matrix type is defined in include/vmath.h
17:01.25brlcadsee include/bn.h and src/libbn for all sorts of matrix math code
17:01.31brlcadsrc/libged/push.c for push
17:03.12Ch3ckok thanks very much
17:03.41Ch3cki ws also thinking on working on the implementing a simplification of the CSG tree
17:03.58Ch3cktogether with its manipulating routines..
17:04.17Ch3cki also wish to know where its defined in the src
17:06.49Ch3ckthanks for the help on the matrix implementation..
17:13.56brlcadCSG tree is much more complicated, it lives and can exist in several forms
17:14.12brlcadmost of those forms are defined in include/raytrace.h though
17:17.34Ch3ckok thanks for the assistance
17:19.58Notify03BRL-CAD:erikgreenwald * 55168 (brlcad/trunk/src/libged/simulate/simphysics.cpp brlcad/trunk/src/libged/simulate/simulate.c): add missing semicolons
17:20.33Notify03BRL-CAD:erikgreenwald * 55169 brlcad/trunk/src/libged/simulate/simrt.c: add missing * from xrayp pointer declaration?
17:21.50Ch3ckhey what lets say i have an idea on how to implement the unpush operation on the matrix
17:22.20Ch3ckdo i need to submit a small src patch on the idea ?? when submitting my proposal??
17:25.25Notify03BRL-CAD:bob1961 * 55170 brlcad/trunk/src/librt/primitives/arb8/arb8.c: This fixes a bug in rt_arb_centroid() (.e.g, "*cent[0] = x_avg;" becomes "(*cent)[0] = x_avg;", notice that [] binds tighter than *).
17:40.39Ch3ckHi @brlcad to increase my chances of being selected should i submit some code  like sample code on how i want to implement the unpush operation??
17:40.50Ch3cki'll appreciate the guidance..
18:03.25*** join/#brlcad botton (~willie@router.isis.poly.edu)
18:03.26*** part/#brlcad botton (~willie@router.isis.poly.edu)
18:10.53brlcadCh3ck: you should submit a patch, but it doesn't have to be on the idea your proposing
18:11.21brlcadit certainly helps if it's related so that you can become familiarized with code that you'll be working with
18:11.52brlcadbut the patch is predominantly just intending to demonstrate competency
18:11.59brlcadbeing relevant to your proposal is just a bonus
18:13.15Ch3ckok
18:13.20Ch3ckthanks for the help
18:13.29Ch3ckwell i'll try to fix some bugs..
18:14.07brlcada good unpush patch might be to stub in an empty function in all the right places so that when you run "unpush" it prints a message
18:14.16brlcador some other libged fix/cleanup
18:22.28*** join/#brlcad ncsaba (~ncsaba@p5498139B.dip.t-dialin.net)
18:22.52ncsabaHi there
18:23.59ncsabaI would need some advice on calculating the centroid of a torus segment :-)
18:24.54ncsabain theory it would work by solving some integrals - but my integrations skills are veeery rusty
18:51.21Notify03BRL-CAD:brlcad * 55171 brlcad/trunk/include/bu.h: unlikely to have HUGE_VALF and not HUGE_VAL so go with the bigger infinity first
18:54.03Notify03BRL-CAD:brlcad * 55172 brlcad/trunk/include/bu.h: similarly, try maxdouble before float. this will probably warrant some TLC to get single precision clean again.
18:55.06brlcadhi ncsaba
19:00.10*** join/#brlcad caen23_ (~cezar@92.81.182.107)
19:01.59brlcadncsaba: this may help: http://www.eng.auburn.edu/~marghitu/MECH2110/staticsC3.pdf
19:02.04Notify03BRL-CAD:starseeker * 55173 brlcad/trunk/src/other/poly2tri/CMakeLists.txt: That macro came from the stepcode cmake logic, which isn't guaranteed to be available.
19:02.49brlcadfor non-elliptical torii, solving the centroid of the circle segments will give you the torus centroid
19:03.43brlcadand I think Couter + Cinner (where each is a vector to the outer and inner circle centroid respectively) will give you the centroid
19:04.32brlcadwhere C is {4r/3pi, 4r/3pi}
19:10.23Notify03BRL-CAD:starseeker * 55174 brlcad/trunk/src/other/CMakeLists.txt: libvds and poly2tri are needed by the core library set.
19:12.22brlcadnotes it's high time that someone add a src/other/README that documents all of the places and ways each of our external dependencies are used
19:13.10brlcadit's getting to be a lot, begging for a table of contents
19:15.05Notify03BRL-CAD:brlcad * 55175 brlcad/trunk/TODO: someone should write up what all those do
19:16.10*** join/#brlcad someta (73f88294@gateway/web/freenode/ip.115.248.130.148)
19:20.46*** part/#brlcad someta (73f88294@gateway/web/freenode/ip.115.248.130.148)
19:25.18Notify03BRL-CAD:carlmoore * 55176 brlcad/trunk/src/proc-db/csgbrep.cpp: add DEFAULT_FILENAME to warn user that the file is indeed to be output, and also add 'arguments ignored' if any arguments are detected
19:25.26Notify03BRL-CAD Wiki:Madhavan 12 * 0 /wiki/User:Madhavan_12:
19:30.42ncsababrlcad: I think I will finally manage to solve the integrals...
19:31.40ncsabaBTW, I have the surface done - once I finish the centroid I will post the next patch
19:43.21*** join/#brlcad ncsaba (~ncsaba@p5498139B.dip.t-dialin.net)
19:54.28*** join/#brlcad brlcad (~sean@66-118-151-70.static.sagonet.net)
19:55.09*** join/#brlcad starseeker (~starseeke@66-118-151-70.static.sagonet.net)
19:55.09*** join/#brlcad n_reed (~molto_cre@66-118-151-70.static.sagonet.net)
19:55.18*** join/#brlcad maths22 (~gcimaths@66-118-151-70.static.sagonet.net)
20:14.59*** join/#brlcad Notify (~notify@66-118-151-70.static.sagonet.net)
20:45.03starseekermakes a note to mention the paper "Determining intersection curves between surfaces of two solids" in conjunction with the SSI discussion, since it does at least talk about finding the initial starting point for a marching intersection approach (if that's needed)
20:47.35*** join/#brlcad Ch3ck (~Ch3ck@41.205.14.251)
21:01.58Notify03BRL-CAD:starseeker * 55177 (brlcad/trunk/TODO brlcad/trunk/src/other/CMakeLists.txt brlcad/trunk/src/other/Makefile.am): Add beginnings of a README for src/other
22:44.20*** join/#brlcad Ch3ck (~Ch3ck@41.205.13.161)

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