Forum post

This PR is my next iteration of rest machining for FreeCAD. It discards the old approach of using internals of the Area class to determine previously cleared regions, and instead computes those regions by processing the gcode from earlier operations. This is trickier, but comes with the advantage of being more flexible: in this version of the rest machining feature, any operation (most notably Adaptive operations) can be the source tool path for rest machining.

Even with the improvements from this iteration, only Area operations (Pocket, Pocket3D, Profile) can take advantage of rest machining. I hope to implement rest machining for Adaptive tool paths in my next pass improving this feature.

Here is the FreeCAD file I've been using to test this feature. It contains 3 parts with test tool paths:

The first part is the part I used to test my initial implementation of rest machining. There are 3 operations. The first operation is a Pocket on the right side, 6mm tool, with no special features. The second operation is a Pocket covering the full top area with a 1.5mm tool, with rest machining enabled. The third operation is a Pocket3D on the entire volume with the same 1.5mm tool, with rest machining enabled. The implementation producing these results is new, but this functionality already exists in the version of rest machining currently in FreeCAD.

The second part tests rest machining after an adaptive operation. The first operation is an Adaptive operation in the top region with a 6mm tool. The second operation is a Pocket3D on the full volume with a 1.5mm tool.

The third part tests speed optimizations and drilling. It has an absurdly dense Adaptive operation on the left region (visibility limited to the first 50k segments as a necessity to improve rendering performance). After that there is a drilling operation on the right side, then a Pocket operation on the right side with rest machining enabled. In addition to demonstrating that rest machining can process drilling gcode commands, this part demonstrates that bounding box filtering of far-away gcode commands works correctly (without that, generating the Pocket would be very slow).

Todo:

• squash commits, and label the full commit with [Path]