Eventually move all these cells below. This create the 3D viz so that we can see what we're actually going to mill.

why epsilon?

In the original, authoring notebook, there is an option to scrub through the layers on the overlay with a slider and also to send by later to the overlay. Then there is a visual debugging with TSS bit of code with three types of checks: basic, carriage collision and stock collision. I haven't included them here. We can discuss.

the machinestate should update automatically if the notebook, if it doesn't open the socket

move to connection notebook

I have effectively removed this check for now, given that we have gotten rid of the end mill table and just ask for diameter and number of flutes.

@gab This input is working now!

Given the choice of tool diameter and # flutes affects feed and speed, perhaps we should bring that section above with end mill set up down here or vice versa.

I actually think this should go in setup, at the end of this notebook, alongside specifying material dimensions . There's so much going on the choice of endmill that it would be better supported in the Setup notebook.

it is kind of odd to specify material type here and not in setup but perhaps it doesn't matter. Maybe just as a way to show that it increases the chipload and changes the speed and feed

This should go in setup

this should also go in setup

Also, shouldn't the first two cells below be children of the endmill selection cell? Numbers of flutes and diameter are specified there.