The step_width used in Generator.py is always generated automatically. I think it would be useful to specify a value for this setting for my finishing cuts, as these cuts need to be very precise.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
you are right, the initial step width is defined as a quarter of the tool_radius. But the surfacing algorithm will adjust this setting later dynamically - see "get_max_height_dynamic" in src/pycam/PathGenerators/__init__.py.
Here the algorithm will calculate the surface points for , and the point in the middle. If these three surface points form a straight line, then no further computation is required. Otherwise the algorithm will add more middle points recursively until the surface is straight or their distance is close to zero.
Read more: http://www.anderswallin.net/2010/10/adaptive-sampling-drop-cutter/ http://fab.senselab.org/node/174
Did you notice any precision problems with the surfacing algorithm or were you just curious about the inner details?
cheers,
Lars
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The step_width used in Generator.py is always generated automatically. I think it would be useful to specify a value for this setting for my finishing cuts, as these cuts need to be very precise.
Hi,
you are right, the initial step width is defined as a quarter of the tool_radius. But the surfacing algorithm will adjust this setting later dynamically - see "get_max_height_dynamic" in src/pycam/PathGenerators/__init__.py.
Here the algorithm will calculate the surface points for , and the point in the middle. If these three surface points form a straight line, then no further computation is required. Otherwise the algorithm will add more middle points recursively until the surface is straight or their distance is close to zero.
Read more:
http://www.anderswallin.net/2010/10/adaptive-sampling-drop-cutter/
http://fab.senselab.org/node/174
Did you notice any precision problems with the surfacing algorithm or were you just curious about the inner details?
cheers,
Lars