On Nov 5 2013 8:21 PM, Jon Elson wrote:
> EBo wrote:
>> I would ask if you wanted to do this estimation in real-time in the
>> code, or if you wanted to do this as a front-end filter.
> Yes, it seems to make a lot of sense that these really pathological
> G-code files
> with pointlessly short, colinear or nearly colinear segments could be
> reduced,
> but that it might be a long regression that could take an 
> indeterminate
> length
> of time to compute.

technically yes, but in practise the time these things take is not to 
bad for decent code.  There are some games you can play to guess where 
the breaks are.

One point about pathological cases is that they are perfect 
unit/regression tests.  You always do the right thing in that case (even 
if it is not efficient), and for the normal case it does something 
desirable.

BTW, if you get this working a little better you will be able to write 
an algorithm to simply walk the pixels along an edge of an image and do 
envelope engraving at machine speeds.

> One other comment, is that with higher performance computers, there's 
> no
> reason the trajectory planner has to run at 1 KHz, it could probably 
> be
> turned up quite a bit.  This may only make sense on high-speed 
> cutting
> machines.

that helps too, but I see the above as being really useful for defining 
and testing the boundary conditions (the other extreme is a single 
straight line -- does the acceleration, at speed, and deceleration act 
as expected?  How about higher order profiling like jerk 
minimization...).

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to