did something happen to sampler? the limit3.0 test fails with no output.
cradek: I dunno, let me look into it
cradek: trunk? rt?
blocks: dlopen: /home/jepler/emc2.cvs/rtlib/blocks.so: cannot open shared object file: No such file or directory
EMC: 03jepler 07TRUNK * 10emc2/tests/limit3.0/test.hal: blocks is dead
oh, I missed an error, sorry
"it doesn't work. I don't know what the error is"
a guy I know was bitching about something similar earlier
I saw result (0 length) but didn't look at stderr
I will cry now
in return you must fix this bug in offs
then I will complain that stderr is unnaturally redirected to a file
that will make me feel better
yes I'm sure
cradek: at that problem spot there are actually two primitives that are about to become zero-length, it looks like. One's the arc you spotted, the other's the line
looking at all the resulting contours (including the ones with the wrong winding numbers), I see one problem: there are some intersections not being found (the single arc shouldn't be able to intersect anything else): http://emergent.unpy.net/index.cgi-files/sandbox/offs-unfound-intersections.png
I don't understand that image at all
phew - it's not just me
I keep trying to zoom out
the path has been offset so much that it's unrecognizable.
after that step, another step is supposed to find all the self-intersections, turning them into separate contours.
then according to a winding rule, usually only certain contours are output
but in this case, I've shown all the contours
because the highlighted arc intersects another primitive part of a path, my self-intersection-detect-and-fix code is wrong
I think I have a general idea why, too (something I thought I could put off until I had islands specified in the input)
when there are self-intersecting paths then my winding rule may give the wrong results and lead to the bug in the last screenshot last night
how hard is it to change the direction the path is "wound"?
you mean whether you specify an enclosed area by going cw or ccw? just a sign change somewhere
otherwise I'm as unsure what your question means as you are unsure what the image shows
I was thinking that going along the path the other way could give different results, due to the order in which intersections are encountered
maybe it's time for me too
hmmm. I wonder if it's "easy" to remove loops by checking to see if the endpoints of an offset line are on the same side of the "centerline" between the two segments
ie, consider a lne between the center of the original line and the center of the offset line
if the start points of both segments are on the same side of that center line, then the offset line is valid (not a backtrack)
if the start points are not on the same side of the centerline, then the poffset path is a loop, and should be removed
EMC: 03jepler 07TRUNK * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: allow display of rapids in preview to be disabled
EMC: 03jepler 07TRUNK * 10emc2/share/axis/tcl/axis.tcl: allow display of rapids in preview to be disabled
that sounds neat
fenn_ is now known as fenn
jepler: i dont think it makes sense to offset a self-intersecting path.. can't you just remove any self-interscting loops in the path before doing any offsetting?
the original path wasn't self-intersecting, it's the calculated offset path that is
so I think it's a matter of detecting that, which it does correctly most of the time
huh - interesting: http://www.osadl.org/Single-View.111+M5f4c5c0c4a3.0.html
The only issue I see is whether the whole system or software PLC honors read, logic, and then write principal that a PLC is based on.
that was my concern as well
it seems to say that things will change "immediately", which is the opposite of a PLC
IMO it just looks like what a PLC does.
it seems more likea C-style HAL than a PLC :)
Does look that way.
fenn: yes, it is the offset path which becomes self-intersecting. the code has to resolve all those self-intersections.
when a single contour becomes self-intersecting, the solution is to break it into two simple contours. That's the case I wrote so far. The second case is that contours A and B intersect; I didn't write that yet, because I thought it couldn't occur if you didn't start with multiple contours.
Some thoughts re PLC and linux. http://i.cmpnet.com/ddj/images/article/2007/rtl_pdf/rkaiser01.pdf
iC looks neat; somebody should adapt it so you can write .comps with its features
That thought scares me more than the current way that HAL handles logic.
I should correct that last thought. Scares me more than the way that HAL can be programmed to handle logic.
I wouldn't use it as a PLC, someone emailed me that link this morning, and I thought it looked intriguing
some of what it has would be great for HAL though, if it could work within the kernel code
things like callbacks for parameter changes
cvs seems to be down?
hmm trace route only gets to the router.
It was working this morning.
oh - maybe it is raining there.. ;)
micge1 is now known as micges