Changes for 2.0 #196
Description
A draft issue for now, but jotting down the requirements that we have for scanspec 2.0
- We need to be able to get the scan path at the servo rate rather than the detector exposure rate
- We need to add detector triggering information into the scanspec so we can put gaps between the triggers where the velocity is still constrained
- We might want to lift the turnaround code up into scanspec (using ruckig or velocity profile) so that we can control the motion in the gaps, which would require knowing the max velocity etc. so the axis would be a datastructure. This might make the kinematic code problematic so maybe the first 2 points are sufficient for this