IRC log for #brlcad on 20130723

04:12.38 Notify 03BRL-CAD:phoenixyjll * 56182 brlcad/trunk/src/libbrep/intersect.cpp: Deal with closed domains for the overlap curve segments.
04:39.12 Notify 03BRL-CAD:phoenixyjll * 56183 brlcad/trunk/src/libbrep/intersect.cpp: The return value should be number of events appended to the array, not the number of elements in that array.
04:57.47 Notify 03BRL-CAD:phoenixyjll * 56184 brlcad/trunk/src/libbrep/intersect.cpp: Normalize the curves for ssx_overlap, and don't use dynamic memory allocation for the ON_SSX_EVENTs.
05:31.48 Notify 03BRL-CAD:phoenixyjll * 56185 brlcad/trunk/src/libbrep/intersect.cpp: Some clean up, and add comments to document the new features of SSI.
05:42.50 Notify 03BRL-CAD:phoenixyjll * 56186 brlcad/trunk/src/libbrep/intersect.cpp: Free the memory, and fix a wrong return value.
06:03.12 Notify 03BRL-CAD:phoenixyjll * 56187 brlcad/trunk/src/libbrep/intersect.cpp: remove trailing ws.
06:22.27 *** join/#brlcad kesha__ (~kesha@14.139.122.114)
06:26.38 *** join/#brlcad kesha__ (~kesha@14.139.122.114)
06:41.18 *** join/#brlcad kesha__ (~kesha@14.139.122.114)
06:50.50 *** join/#brlcad kesha_ (~kesha@14.139.122.114)
06:56.21 *** join/#brlcad kesha_ (~kesha@14.139.122.114)
07:00.44 *** join/#brlcad kesha_ (~kesha@14.139.122.114)
07:07.06 Notify 03BRL-CAD Wiki:KeshaSShah * 5736 /wiki/User:KeshaSShah/GSoC13/Reports: /* Week 6 */
07:20.10 Notify 03BRL-CAD Wiki:Phoenix * 0 /wiki/File:Partial_overlap.png:
07:20.58 Notify 03BRL-CAD Wiki:Phoenix * 0 /wiki/File:Completely_overlap.png:
07:23.40 Notify 03BRL-CAD Wiki:Phoenix * 5739 /wiki/User:Phoenix/GSoc2013/Reports: /* Test Results */
07:25.14 Notify 03BRL-CAD Wiki:Phoenix * 5740 /wiki/User:Phoenix/GSoc2013/Reports: /* Test Results */
07:28.49 Notify 03BRL-CAD Wiki:Phoenix * 5741 /wiki/User:Phoenix/GSoc2013/Reports: /* Week 6 */
09:30.29 *** join/#brlcad kesha_ (~kesha@14.139.122.114)
10:53.50 *** join/#brlcad kesha_ (~kesha@14.139.122.114)
11:06.18 *** join/#brlcad kesha_ (~kesha@14.139.122.114)
12:35.02 *** join/#brlcad caen23 (~caen23@92.83.162.185)
13:03.53 Notify 03BRL-CAD Wiki:Level zero * 5742 /wiki/User:Level_zero/GSOC13/logs: /* Week 6 */
13:04.31 Notify 03BRL-CAD Wiki:Level zero * 5743 /wiki/User:Level_zero/GSOC13/logs: /* Week 6 */
13:11.28 Notify 03BRL-CAD:starseeker * 56188 (brlcad/trunk/regress/CMakeLists.txt brlcad/trunk/regress/mged/overlay.mged and 2 others): Update regression scripts to use the plot3 suffix
13:31.08 *** join/#brlcad caen23 (~caen23@92.83.162.185)
13:33.40 starseeker interesting: http://www.cs.dartmouth.edu/~jdenning/papers/meshgit-s13.pdf
13:36.20 starseeker http://igl.ethz.ch/projects/winding-number/
13:48.18 Notify 03BRL-CAD:starseeker * 56189 brlcad/trunk/misc/CMakeLists.txt: Add missing file to misc/CMakeLists.txt
14:05.46 Notify 03BRL-CAD:carlmoore * 56190 (brlcad/trunk/misc/DoxyfileLibs-defaults.in brlcad/trunk/misc/DoxyfileLibs.in): remove trailing blanks/tabs, fix spelling, and insert a hyphen
14:06.58 Notify 03BRL-CAD:starseeker * 56191 brlcad/trunk/src/other/CMakeLists.txt: Fix names of stepcode files to be cleaned out in distcheck
16:01.41 *** join/#brlcad caen23 (~caen23@92.83.162.185)
16:22.02 Notify 03BRL-CAD:indianlarry * 56192 (brlcad/trunk/include/brep.h brlcad/trunk/src/librt/primitives/brep/brep.cpp): Added new grazing tolerance definition "BREP_GRAZING_TOL" currently set to 0.000017453(or 0.001 degrees) was using RT_DOT_TOL at 0.001 (0.05 degrees) but causing to many grazing differences with CSG comparison test. Also tighted up the utah_pushBack() so keeps UV with domain of interest(I think this was
16:22.05 Notify loosened for some of the STEP pullbacks). Added utah_pushBack() to previous halfstep loop in newton iterater which tries to fix over stepping. I the IN/OUT BREP stiching logic removed a loop that removed NEAR_HITs on ODD hit counts because it was being done before the remove duplicate points logic. Fixed sign problem on final SBV check of BREP root solver where I added VUNITIZE_TOL.
16:43.15 *** join/#brlcad Ch3ck (~Ch3ck@195.24.220.16)
16:52.29 *** join/#brlcad Ch3ck (~Ch3ck@195.24.220.16)
16:54.43 Ch3ck Hi i need some assistance in setting up an account on bzflagt
16:54.50 Ch3ck bz.bzflag.bz
16:55.06 Ch3ck i have already created the /usr/web/
16:55.20 Ch3ck well the SITE option i don't really understand how it works.
16:59.34 *** join/#brlcad Izak_ (~Izak@195.24.220.16)
17:21.47 brlcad hi Ch3ck Izak_
17:22.10 Ch3ck yes brlcad
17:22.39 Izak_ Hi Sean
17:22.49 *** join/#brlcad vladbogo (~vladbogo@188.25.237.68)
17:23.12 Izak_ usy got the internet installed a few minutes ago
17:27.46 brlcad excellent
17:27.53 brlcad what kind of connection is it?
18:08.17 ``Erik huzzah for connectivity
18:15.43 Izak_ yeah finally
18:18.24 *** join/#brlcad merzo (~merzo@170-201-133-95.pool.ukrtel.net)
18:34.20 *** join/#brlcad Notify (~notify@66-118-151-70.static.sagonet.net)
18:46.32 brlcad Izak_: Ch3ck: so the last point that I didn't yet mention is about bottom-posting and top-posting
18:47.11 Ch3ck ok
18:47.23 Izak_ What about that?
18:47.31 Ch3ck well i guessed I replied that.
18:47.36 Ch3ck on the mail.
18:47.37 brlcad you both are clearly only used to top-posting, but that is considered lazy in most open source communities, even highly offensive in some of them
18:48.06 Ch3ck wow I See.. :( didn't know about that..
18:48.25 Izak_ web Searching for the difference......
18:48.39 ``Erik ya talking email?
18:48.39 brlcad Answer:No
18:48.47 brlcad Question: is it better to top-post?
18:48.56 brlcad that's the classic comparison
18:49.08 brlcad it puts all the work on the reader instead of the writer
18:49.16 ``Erik http://catb.org/jargon/html/T/top-post.html
18:49.36 Ch3ck thanks for the link ``Erik
18:49.56 Ch3ck ok
18:49.59 Ch3ck I see
18:50.02 Izak_ thanks Erik
18:50.16 brlcad or more academically, http://en.wikipedia.org/wiki/Posting_style
18:50.51 brlcad the "Interleaved style" mentioned there is the most generally accepted form
18:51.16 Ch3ck ok
18:51.25 brlcad which is pasically bottom-posting per statement of relevance any eliminating any statements that are not relevant
18:51.29 Ch3ck will do better next time.
18:51.43 Ch3ck ok
18:51.48 Ch3ck Didn't know about this..
18:52.01 brlcad Ch3ck: and if you re-read my three or four e-mails over the weekend, you'll see how it was increasingly frustring
18:52.05 brlcad that was my "p.s."
18:52.25 Ch3ck yeah
18:52.33 brlcad p.s. please don't top-post
18:52.42 Ch3ck read about them but had no idea..
18:52.43 brlcad top-posted reply: okay, I'll get right on that
18:52.44 Ch3ck yeah
18:52.56 brlcad you need to say when you don't understand something that bluntly
18:53.03 Ch3ck :( Sorry for the misunderstanding
18:53.22 brlcad there is nothing positive to be learned or gained from hiding what you do not understand
18:53.57 brlcad there is no shame in not understanging
18:53.58 ``Erik most email clients parse the '>' prefix and "do the right thing". I believe even outlook can if you turn off html 'rich' email
18:54.24 Ch3ck ok
18:54.26 Ch3ck I see
18:54.35 brlcad there can be shame in willful ignorance or deception, not improving ;)
18:54.39 brlcad and that's clearly not something you want
18:54.44 brlcad not something we want
18:54.59 brlcad the conventions used in open source are almost entirely cenetered around efficiency
18:55.06 brlcad what is most efficient for EVERYONE
18:55.15 brlcad which is not necessarily what is most efficient for the author
18:55.35 brlcad for example, it's considered rude to say "hello" when joining IRC
18:55.38 Ch3ck I see
18:55.46 Izak_ So I need to think about the reader of the email NOT myself ?
18:55.46 Ch3ck get it perfectly now..
18:55.56 brlcad imagine if there are 200 people in the channel, and there were 200+ hello replies
18:56.18 brlcad in any other context, saying hello is the polite thing to do
18:56.22 Ch3ck Now I understand how you respond to emails.
18:56.39 ``Erik huzzah efficiency, "crocker's rules" :D
18:57.14 brlcad Izak_: yes because there is only one writer and many (dozens, hundreds, sometimes thousands) of readers
18:57.29 Izak_ My teacher used to bottom-post, but i considered it funny..
18:57.59 brlcad he knew there were more of you reading than him writing and it gave context for what he replies to
18:58.03 Izak_ that's in our email interactions
18:58.21 brlcad that said, pure bottom posting isn't always great -- you do NOT just want to reply to a whole long message at the bottom
18:58.39 brlcad that's where interleaved is better, and you actually remove portions you don't refer to that aren't relevant
18:59.08 ``Erik (it's also handy to remove parts of the quoted message that aren't relevant... I like to put a line with "<snip>" where trimming was done)
18:59.32 Ch3ck ok..
18:59.42 brlcad alright guys, glad to hear you have access re-established, and now accounts created so even if the lab explodes tonight, you can work on brlcad.org directly to do checkouts from svn, compile, create patches, etc
19:00.15 brlcad ``Erik is one of the server admins if you have any questions, or need software installed, ... or HAVE QUESTIONS ... ;)
19:01.24 brlcad will take a look at your updated patches soon as you can update them from a current svn checkout
19:01.27 brlcad (make sure they compile and run cleanly, match style, indented properly, comments, etc)
19:01.34 Ch3ck yeah
19:01.40 Ch3ck well tried using the indent.sh
19:01.56 brlcad that relies on emacs being set up like i'm used to
19:02.01 Ch3ck but it does nothing really prefer manually indenting code.
19:02.08 Ch3ck ok
19:02.13 brlcad you should know how to do it manually first
19:02.35 Ch3ck yeah thats what i'm doing.
19:02.46 ``Erik did we get an astyle config file checked in?
19:03.14 ``Erik ah, misc/astyle.opt
19:03.22 Izak_ don't understand the question ?
19:03.26 brlcad ``Erik: yeah, but not tested it
19:03.35 Ch3ck well I don 't really follow.
19:03.48 brlcad and if we're going to run it holistically, I'd like to have a debate about changing the indentation
19:04.02 ``Erik Ch3ck: was talking to brlcad about an auto-indentor, not really intended for you (yet) :)
19:04.48 Ch3ck o
19:04.49 Ch3ck k
19:05.22 brlcad you've not said 'ok' so many times since the applications were open
19:06.17 Ch3ck :) so what do i say then..
19:06.49 brlcad I don't know, what do you see everyone else saying? :)
19:07.04 *** join/#brlcad kesha_ (~kesha@14.139.122.114)
19:07.05 ``Erik hopes Ch3ck and Izak_ are getting a build going in a fresh svn checkout/update
19:07.13 Izak_ <PROTECTED>
19:07.14 brlcad some variety or just less frequent confirmation
19:07.34 brlcad ~cadsvn
19:07.34 infobot To obtain BRL-CAD from Subversion: svn checkout https://svn.code.sourceforge.net/p/brlcad/code/brlcad/trunk brlcad
19:08.13 brlcad you should be doing that or using the url on sourceforge for the svn+ssh:// url method today to update your patches as soon as possible
19:08.30 brlcad what is the speed of your connection?
19:09.03 brlcad what does http://www.speedtest.net/ say?
19:10.45 brlcad gotta run, ttyl
19:11.02 Ch3ck aight
19:11.07 ``Erik the bz server has a fast uplink and would let a mentor look directly at the build/src dir if an issue comes up
19:11.35 Ch3ck great
19:11.37 Izak_ at most 512KB per second
19:13.20 ``Erik what technology? adsl? isdn? satellite? partial T frame?
19:14.03 Ch3ck well not really familiar with networks
19:15.14 Ch3ck so don't know which specifically but not satellite and partial T
19:15.14 Ch3ck so will probably b adsl or isdn
19:15.57 ``Erik hm, if it's high latency, using bz will be a bit annoying with the lag... but if you have low bandwidth, the svn checkout and updates will take quite a while... *shrug* you'll have to decide which tradeoff to choose
19:26.55 Notify 03BRL-CAD Wiki:NyahCh3ck20 * 5744 /wiki/User:NyahCh3ck20/GSoc2013/Coding_Repor: /* 22 July - 28 July */
19:32.30 Notify 03BRL-CAD Wiki:Vladbogolin * 0 /wiki/File:Snapshot2.png:
19:32.41 Notify 03BRL-CAD Wiki:195.24.220.16 * 5746 /wiki/User:Izak/GSOC_2013_logs: /* From July 22th to July 27th */
19:34.25 Ch3ck but its pretty fast
19:34.33 Ch3ck by our standards here
19:35.39 Notify 03BRL-CAD Wiki:Vladbogolin * 0 /wiki/File:Snapshot3.png:
19:36.08 Notify 03BRL-CAD Wiki:Vladbogolin * 5748 /wiki/User:Vladbogolin/GSoC2013/Logs: /* Week 5 (15 July - 21 July) */
20:23.16 starseeker is liking the Qt screenshots :-)
20:31.30 ``Erik then you'll love this, starseeker: http://paste.lisp.org/display/138163
20:58.22 *** join/#brlcad mpictor (~mark@2601:d:b280:b5:d63d:7eff:fe2d:2505)
21:20.08 brlcad i ran into that error as well where it tried to compile the Qt bits
21:20.34 brlcad ended up succeeding the cmake test but not setting the paths up right somehow
21:20.56 brlcad Izak_: is that from speettest or a guess?
21:22.46 Izak_ a guess
21:23.56 brlcad if you just go to that website and hit the start test button, it'll give you a fairly good measure
21:27.16 *** join/#brlcad kesha_ (~kesha@14.139.122.114)
21:38.59 *** part/#brlcad Ch3ck (~Ch3ck@195.24.220.16)
22:00.47 *** join/#brlcad kesha_ (~kesha@14.139.122.114)

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