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.
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. Jon ------------------------------------------------------------------------------ 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
