| 00:46.30 | *** join/#brlcad schwinn434_ (n=schwinn4@cpe-75-81-202-25.we.res.rr.com) | |
| 00:51.49 | *** join/#brlcad schwinn434 (n=schwinn4@75.81.202.25) | |
| 01:58.21 | *** join/#brlcad schwinn434_ (n=schwinn4@cpe-75-81-202-25.we.res.rr.com) | |
| 02:04.53 | *** join/#brlcad BigAToo (n=BigAToo@pool-96-230-124-196.sbndin.btas.verizon.net) | |
| 02:42.36 | *** join/#brlcad schwinn434 (n=schwinn4@cpe-75-81-202-25.we.res.rr.com) | |
| 02:44.53 | *** join/#brlcad schwinn434_ (n=schwinn4@75.81.202.25) | |
| 02:52.30 | *** join/#brlcad Ralith (n=ralith@216.162.199.202) | |
| 04:07.09 | CIA-30 | BRL-CAD: 03brlcad * r34910 10/brlcad/trunk/BUGS: elena found an odd bug in mged's command-mode parsing. semicolons are the separator but for some reason output of mged commands is being suppressed for all but the last command. |
| 04:07.55 | *** join/#brlcad IriX64 (n=WarLock@bas2-sudbury98-1178015175.dsl.bell.ca) | |
| 04:12.43 | brlcad | per elena's questions earlier: mged -c whatever.g "tree \[string trim \[ tops -n\] \]" |
| 04:13.16 | brlcad | have to quote the globbing characters [], {}, & ? |
| 04:14.27 | ``Erik | ahhhh, that's right, forgot about that |
| 04:15.14 | brlcad | semicolon should / does work .. but there's some sort of bug there |
| 04:15.54 | brlcad | mged -c test.g "puts hello ; puts world" <= works for example |
| 04:16.19 | brlcad | even interlaced with mged commands .. but for some reason mged commands aren't printing unless they're last |
| 04:16.33 | ``Erik | what about the stdout/stderr issue? |
| 04:16.35 | brlcad | have to trace it |
| 04:17.08 | brlcad | that's mostly legacy, all textual logging goes through bu_log, which has always written to stderr |
| 04:17.29 | brlcad | would be a pretty significant change so it's not been attempted yet |
| 04:19.37 | brlcad | that was originally so the streamable tools could still log and send their data to a stream (e.g. for piping input to output on things like "pixhalve -s1024 some.pix | pix-png > file.png", and still seeing logged output) |
| 04:19.55 | brlcad | everything uses the same logging mechanism so it goes to stderr |
| 04:20.50 | brlcad | notes elena probably needs to read http://brlcad.org/wiki/SGI_Cube |
| 07:24.49 | *** join/#brlcad _clock_ (n=_sushi_@77-58-151-159.dclient.hispeed.ch) | |
| 07:48.01 | *** join/#brlcad IriX64 (n=IriX64@bas2-sudbury98-1178015175.dsl.bell.ca) | |
| 08:02.24 | *** join/#brlcad jdoliner (n=jdoliner@c-68-51-75-169.hsd1.il.comcast.net) | |
| 08:09.14 | CIA-30 | BRL-CAD: 03d_rossberg * r34911 10/rt^3/trunk/ (4 files in 2 dirs): |
| 08:09.15 | CIA-30 | BRL-CAD: change the data-type for color values from unsigned int to double (0 <= r/g/b <= 1) |
| 08:09.17 | CIA-30 | BRL-CAD: although color values are stored as unsigned int this implementation detail should be hidden from the user |
| 08:18.38 | *** join/#brlcad _clock_ (n=_sushi_@77-58-151-159.dclient.hispeed.ch) | |
| 08:47.52 | CIA-30 | BRL-CAD: 03Jdoliner 07http://brlcad.org * r1525 10/wiki/User:Jdoliner: |
| 09:49.01 | *** join/#brlcad mafm (n=mafm@165.Red-81-35-69.dynamicIP.rima-tde.net) | |
| 10:25.35 | *** join/#brlcad Elrohir (n=kvirc@p5B14FC4C.dip.t-dialin.net) | |
| 13:22.50 | *** join/#brlcad BigAToo (n=BigAToo@pool-96-230-124-196.sbndin.btas.verizon.net) | |
| 14:18.52 | *** join/#brlcad BigAToo (n=BigAToo@pool-96-230-124-196.sbndin.btas.verizon.net) | |
| 15:40.11 | *** join/#brlcad elena (n=elena@89.136.118.141) | |
| 15:48.31 | *** join/#brlcad d-lo (n=claymore@bz.bzflag.bz) [NETSPLIT VICTIM] | |
| 15:48.31 | *** join/#brlcad roberthl (n=robert@silentflame/member/roberthl) [NETSPLIT VICTIM] | |
| 16:01.01 | *** join/#brlcad jdoliner (n=jdoliner@c-68-51-75-169.hsd1.il.comcast.net) | |
| 16:02.12 | *** join/#brlcad alecs1 (n=alex@193.186.164.88) | |
| 16:02.59 | alecs1 | hi, does BRL-CAD support tolerancing? I couldn't find it in the docs |
| 16:03.31 | d-lo | depends on what you mean. To what are you wanting to apply a tolerance to? |
| 16:03.33 | alecs1 | (tolerancing as in gd&t, that's the more known buzzword) |
| 16:04.11 | louipc | make this hole 1" dia +- .005" |
| 16:04.54 | alecs1 | well, to components in the tree; but I'm no BRL-CAD expert either, just evaluating and asking if it's not in the docs |
| 16:05.13 | louipc | brl-cad doesn't have that feature as far as I know |
| 16:05.26 | louipc | but I'm no authority on it :P |
| 16:06.03 | d-lo | I would say no, it doesn't support GD&T. |
| 16:06.41 | alecs1 | thanks |
| 16:06.46 | alecs1 | do you know of other open-source programs that support it |
| 16:12.03 | CIA-30 | BRL-CAD: 03starseeker * r34912 10/brlcad/trunk/ (11 files in 7 dirs): Add bbsize command per user request - reports a quick summary of how big the bounding box of an object is. |
| 16:12.34 | louipc | nope |
| 16:12.50 | louipc | qcad maybe... that's 2d though |
| 16:18.16 | alecs1 | I see, thank you :) |
| 16:23.23 | CIA-30 | BRL-CAD: 03starseeker * r34913 10/brlcad/trunk/src/tclscripts/lib/ (Db.tcl Mged.tcl): Don't need the bbsize command support on obsolete tcl code. |
| 17:02.38 | brlcad | definitely do not support tolerancing |
| 17:06.00 | brlcad | starseeker: unless I read the commit wrong, you missed the bbsize.c file |
| 17:06.58 | starseeker | aaah, nuts |
| 17:07.00 | starseeker | sorry |
| 17:07.40 | CIA-30 | BRL-CAD: 03starseeker * r34914 10/brlcad/trunk/src/libged/bbsize.c: Yeah, it might help to add the key bbsize file. |
| 17:07.56 | brlcad | thx |
| 17:08.04 | starseeker | np :-) |
| 17:38.13 | CIA-30 | BRL-CAD: 03brlcad * r34915 10/brlcad/trunk/NEWS: fixed compilation support for mac os x 10.5, problem compiling with ogl support enabled (mac ld issue with /usr/X11/lib/libGL.dylib cyclicly referring to framework dylib) |
| 17:45.39 | *** join/#brlcad alecs1 (n=alex@budweis.scch.at) | |
| 17:54.31 | *** join/#brlcad BigAToo (n=BigAToo@64.74.225.82) | |
| 17:56.03 | *** join/#brlcad BigAToo1 (n=BigAToo@64.74.225.82) | |
| 17:58.13 | CIA-30 | BRL-CAD: 03homovulgaris * r34916 10/brlcad/trunk/src/libpc/pcMathGrammar.h: fleshing FunctionGrammar 1/2 |
| 18:03.28 | jdoliner | indianlarry whenever you read this, I think I've worked out the kinks in my algorithmic woos. But would love to talk about it with you, just to do some sanity checks. |
| 18:08.23 | ``Erik | sanity check: you have none :D |
| 18:08.43 | ``Erik | (which is why ya fit in here) |
| 18:08.54 | jdoliner | :D |
| 18:09.09 | jdoliner | it certainly feels that way these days |
| 18:09.22 | indianlarry | what you come up with Joe |
| 18:09.23 | jdoliner | I close my eyes and see triangles intersecting each other |
| 18:09.58 | jdoliner | k so we wanted to have a convention for which way the edge we return should point |
| 18:10.39 | jdoliner | and this convention should depend on the normals of both of the triangles we intersect |
| 18:11.01 | indianlarry | okay |
| 18:11.23 | jdoliner | so we decide that the edge will be parallel to (norm1Xnorm2) |
| 18:11.56 | CIA-30 | BRL-CAD: 03irpguardian * r34917 10/brlcad/trunk/src/proc-db/human.c: |
| 18:11.56 | CIA-30 | BRL-CAD: Added poseable support for the torso. Also made the arms and legs now properly position themselves and attach to torso. |
| 18:12.01 | CIA-30 | BRL-CAD: Legs and arms are still not properly positioned when the body is rotated however. |
| 18:12.01 | indianlarry | follow so far |
| 18:12.03 | jdoliner | so if we do this |
| 18:12.22 | jdoliner | then when we have an edge and the triangle it came from |
| 18:14.00 | jdoliner | then in triangle1 the (edgeXNorm) points to the internal side, in triangle2 it points to the external side |
| 18:14.26 | jdoliner | just a fact of life that this is going to be reversed |
| 18:14.41 | jdoliner | but the important part is that it'll be consistent |
| 18:15.57 | jdoliner | so if we take our corner jabbing into a triangle |
| 18:17.27 | jdoliner | we would get a the trimming curve back with the lines s.t. the normal points the opposite direction of the faces normal |
| 18:17.39 | jdoliner | which signifies an internal face |
| 18:18.20 | jdoliner | oh forgot to mention abut the output that we need to reverse the line for mesh1 |
| 18:18.50 | jdoliner | but yeah I'm confident in that case |
| 18:19.36 | jdoliner | now the trickiness comes when it hits an edge |
| 18:20.23 | jdoliner | so it now passes up which edge the intersection came from |
| 18:20.33 | jdoliner | so suppose we get back the line pq |
| 18:21.06 | jdoliner | and we know that point p came from line ab |
| 18:21.10 | ``Erik | yuh oh, libpc issue, no boost lazy.hpp |
| 18:21.40 | jdoliner | then we know that the lines to include are: |
| 18:21.58 | jdoliner | ap and bp |
| 18:22.37 | jdoliner | because those are consistent with the direction of pq |
| 18:23.11 | ``Erik | src/libpc/pcMathGrammar.h:42:41: error: boost/spirit/dynamic/lazy.hpp: No such file or directory |
| 18:23.37 | jdoliner | so really the only tricky part is that ab might have more than 1 point on it |
| 18:25.13 | jdoliner | so we basically need to record where these points are in a slightly more sophisticated way |
| 18:25.36 | jdoliner | which is just going to be a polyline that keeps them all in order and then we take the segments out of it at the end. |
| 18:26.39 | indianlarry | just thinkin that basically any loop that contains an outside edge would in fact be an an outside edge and be ordered as such |
| 18:27.50 | indianlarry | are you making loops from your intersections yet |
| 18:28.11 | indianlarry | or just the list of intersecting segments |
| 18:29.31 | jdoliner | sort of, I have the could all ready to go to make loops, but I need to implement the stuff I just mentioned to be able to pass it the right segments |
| 18:30.40 | jdoliner | before this I was just grabbing the segments however they came out and it worked great on them |
| 18:33.02 | indianlarry | maybe not visualizing correctly |
| 18:33.49 | indianlarry | but seems like you could lose ap or pb depending on the boolean logic of your combination |
| 18:35.15 | jdoliner | yeah one of them won't be in the final result |
| 18:35.24 | jdoliner | one is internal and the other is external |
| 18:36.07 | indianlarry | yeah okay, do you keep seperate loop list for each face |
| 18:36.35 | CIA-30 | BRL-CAD: 03brlcad * r34918 10/brlcad/trunk/src/other/boost/spirit/dynamic/lazy.hpp: missing lazy.hpp, now used by pcMathGrammer.h though might still be missing some other files |
| 18:36.41 | jdoliner | yes |
| 18:37.10 | jdoliner | for each face in the original mesh there's actually possible multiple face loops |
| 18:37.52 | indianlarry | yeah and an inner can probably turn into an outer after the combination... |
| 18:38.18 | jdoliner | how do you mean? |
| 18:39.07 | jdoliner | oh, well if we do Mesh A - Mesh B then the inners of B will be an outer of the result |
| 18:39.27 | indianlarry | is you cut a face in falf and there was an inner loop -- yeah |
| 18:39.39 | jdoliner | k yeah |
| 18:39.46 | indianlarry | sorrry slow typer |
| 18:39.58 | jdoliner | :) young nimble fingers |
| 18:40.13 | indianlarry | sounds similar to the nurbs loops |
| 18:40.30 | jdoliner | yeah it's actually really elegant after we have all the faces pointing the right way |
| 18:40.37 | indianlarry | is the first loop the outer and the rest inner loops |
| 18:41.01 | jdoliner | well couldn't there be multiple outers? |
| 18:41.35 | jdoliner | an outer loop is just one that intersects a triangle edge correct? |
| 18:41.51 | indianlarry | not sure how the meshes are handles but for the nurbs there's only one outer |
| 18:42.12 | indianlarry | i think multiple outers would be treated as seperate faces |
| 18:43.39 | jdoliner | okay I think I see what it means for nurbs |
| 18:44.17 | jdoliner | is it just the curve along the outside of the defined surface? |
| 18:44.18 | indianlarry | are you looking at bots or meshed faces |
| 18:44.50 | indianlarry | yes the outer boundry of the face |
| 18:45.18 | jdoliner | I believe bots |
| 18:45.46 | jdoliner | yeah it just has an array of faces which could occur in any order |
| 18:46.26 | jdoliner | although there can be quads in the bag as well |
| 18:47.13 | CIA-30 | BRL-CAD: 03brlcad * r34919 10/brlcad/trunk/src/other/boost/spirit/ (5 files in 3 dirs): add a few more missing boost files to unbreak the build after recent pcMathGrammer changes |
| 18:58.42 | indianlarry | if bots then probably don't need to worry about loops and such right |
| 18:59.58 | jdoliner | yeah, I deal with things on a triangle by triangle basis |
| 19:01.45 | indianlarry | sorry joe i think i'm leading you astray |
| 19:03.05 | indianlarry | guess you still need to maintain proper facet orientations |
| 19:03.51 | jdoliner | yes |
| 19:04.51 | indianlarry | i guess a polyline accross a facet -> many facets |
| 19:05.32 | jdoliner | yes |
| 19:06.30 | jdoliner | I mean I can't do any sort of geometry internal to my faces, any detail I want to include has gotta be done with triangles |
| 19:07.48 | indianlarry | yep the corner into a face of a triangle turns into a handfull of facets |
| 19:08.41 | indianlarry | did the BOOLE folks have walking algrithm for this already? |
| 19:15.59 | indianlarry | or were they just doing bezier ? |
| 19:20.29 | CIA-30 | BRL-CAD: 03erikgreenwald * r34920 10/isst/ (24 files in 4 dirs): import of ISST |
| 19:22.55 | elena | brlcad, are you here? |
| 19:25.32 | CIA-30 | BRL-CAD: 03erikgreenwald * r34921 10/isst/trunk/src/gui.c: acronymize |
| 19:32.04 | elena | ``Erik, did you feed the squirrel again? |
| 19:45.27 | brlcad | hi elena |
| 19:45.35 | elena | hi. |
| 19:45.38 | brlcad | few comments about your work yesterday |
| 19:46.07 | elena | did you see the log of the chat with erik? |
| 19:46.13 | brlcad | semicolon is the command separater -- what you were trying should have worked |
| 19:46.16 | brlcad | yes |
| 19:46.23 | elena | :) |
| 19:46.25 | elena | ok |
| 19:46.38 | brlcad | never leaves IRC .. that's what 'screen'+'irssi' are for :) |
| 19:46.52 | elena | :) |
| 19:47.13 | brlcad | you can see the result with something like this: mged -c test.g "puts hello ; puts world" |
| 19:47.38 | brlcad | there is some odd issue causing output to be quieted (though I believe it does run the commands still) |
| 19:47.58 | brlcad | haven't confirmed yet though |
| 19:48.11 | brlcad | secondly, I presume you've seen http://brlcad.org/wiki/SGI_Cube ? |
| 19:48.19 | brlcad | that shows three specific ways to script mged |
| 19:48.21 | elena | but "tops ; tops" doesn't work :( |
| 19:48.29 | brlcad | it does and it doesn't |
| 19:48.37 | brlcad | I believe it's just not printing the result |
| 19:48.38 | elena | i haven't. |
| 19:48.42 | elena | thanks for the tip. |
| 19:48.49 | brlcad | but actually runs the commands |
| 19:49.05 | elena | i spent all day reading about tcl :) |
| 19:49.19 | elena | ok. |
| 19:49.25 | brlcad | to do the tree of tops that you suggested, it was simply a matter of escaping the globbing characters |
| 19:49.27 | elena | and about the stderr output? |
| 19:50.10 | brlcad | for example: mged -c whatever.g "tree \[string trim \[ tops -n\] \]" |
| 19:51.17 | CIA-30 | BRL-CAD: 03erikgreenwald * r34922 10/isst/trunk/src/ (gui.c main.c sql.c): fix headers |
| 19:51.32 | brlcad | by default, mged has a globbing evaluation mode enabled so that glob characters (*[],?{}.) are specially recognized so you can do pattern matching on objects, e.g. "draw *" or "draw [a-f]*" |
| 19:52.04 | brlcad | so you either have to turn globbing off (set glob_compat_mode 0) ... or ... escape the glob characters ala \[ \] |
| 19:53.25 | brlcad | btw, if you had multiple top-level objects, that example won't work -- you'd need to iterate over each object and call tree |
| 19:53.55 | elena | i've noticed. this is why i started to read more about tcl. |
| 19:54.16 | elena | it seems to me that it will help with the drupal integration. |
| 19:54.24 | brlcad | something like: foreach obj \{ \[ string trim \[ tops -n \] \] \} \{ tree $obj \} |
| 19:54.57 | brlcad | since you're in php land, it may very well be easier to just run one command at a time and do your string parsing on the php side |
| 19:55.26 | elena | less fun. |
| 19:55.32 | elena | maybe less efficient, too. |
| 19:55.57 | brlcad | it should be fairly insignificant compared to what all you're doing and how often this is called |
| 19:56.09 | brlcad | but fun is a good motivator |
| 19:56.10 | elena | ok. i'll think about it. |
| 19:56.11 | brlcad | :) |
| 19:56.43 | brlcad | note that the http://brlcad.org/wiki/SGI_Cube example shows those three ways I mentioned, but is actually just a posix shell script driving mged |
| 19:57.15 | brlcad | the cat <<EOF section is one of the three I mentioned, where it pipes multiple commands to mged |
| 19:57.53 | elena | i'll study it. |
| 19:57.59 | elena | thank you. |
| 19:58.28 | brlcad | if you want to capture stderr more easily, you can feed stderr to stdout with 2>&1 |
| 19:58.42 | elena | i did that. |
| 19:58.48 | brlcad | k |
| 19:58.52 | ``Erik | wonders if turning off globbing in the .mgedrc would be good for an account that just runs mged batch-mode |
| 19:59.27 | elena | @Erik: doesn't matter, i could turn it off at the begining of the script. |
| 19:59.29 | brlcad | possible, but it really just saves a couple keystrokes, which are embedded in a script anyways |
| 19:59.40 | brlcad | now if your script gets big/unreadable ... |
| 20:00.07 | ``Erik | or at the beginning of the script, yes... escaping all the glob characters in a nontrivial script can quickly become ugly |
| 20:13.33 | *** join/#brlcad _sushi_ (n=_sushi_@80-219-43-170.dclient.hispeed.ch) | |
| 20:39.32 | *** join/#brlcad alecs1 (i=alex@193.170.134.247) | |
| 20:51.54 | CIA-30 | BRL-CAD: 03indianlarry * r34923 10/brlcad/trunk/ (12 files in 5 dirs): |
| 20:51.56 | CIA-30 | BRL-CAD: added near hit, near miss processing to shotline |
| 20:51.58 | CIA-30 | BRL-CAD: also started to pull out debugging code and wrap into |
| 20:52.00 | CIA-30 | BRL-CAD: 'brep' utility command in libged |
| 21:16.46 | *** join/#brlcad docelic (n=docelic@78.134.203.84) | |
| 21:20.05 | CIA-30 | BRL-CAD: 03irpguardian * r34924 10/brlcad/trunk/src/proc-db/human.c: Added poseable support for the head and neck, so now the entire body has poseable support. |
| 21:22.44 | *** join/#brlcad Patmcc19 (n=chatzill@71-223-27-160.phnx.qwest.net) | |
| 21:25.22 | CIA-30 | BRL-CAD: 03ebautu * r34925 10/web/trunk/htdocs/more/sites/all/themes/fireflystreamcom/template.php: Fixed error in theme comment wrapper |
| 21:26.26 | CIA-30 | BRL-CAD: 03ebautu * r34926 10/web/trunk/htdocs/more/sites/all/modules/brlcad/scripts/ (. 7.14/ 7.14/metadata.txt): Scripts for integration with Drupal |
| 21:27.45 | CIA-30 | BRL-CAD: 03ebautu * r34927 10/web/trunk/htdocs/more/sites/all/modules/brlcad/brlcad.module: Added suport for multiple BRL-CAD versions (script not yet ready). Multistep submission is incomplete, too. |
| 21:30.11 | CIA-30 | BRL-CAD: 03Ebautu 07http://brlcad.org * r1526 10/wiki/More_Changelog: /* June, 17 - today */ |
| 21:49.09 | *** join/#brlcad Elrohir (n=kvirc@p5B14FC4C.dip.t-dialin.net) | |
| 22:09.06 | *** join/#brlcad BigAToo (n=BigAToo@pool-96-230-124-196.sbndin.btas.verizon.net) | |