Draft: Merging all the motion controller drivers & handlers under libMotion
Creating libMotion to host motion controller drivers and handlers. Deprecating libZaber and libGalil. Keeping probe-station-specific code under libWaferProbe (will revisit later when resuming work on the probe station)
Merge request reports
Activity
Hi @yanght
The way that the probe station code is handled needs a complete redo. Not just be moved around. See @dantrim's start on this in !199 (merged).
The gist is:
- All libraries that are just copies of external dependencies need to be moved to
exts/
. Ideally via agit submodule
. !199 (merged) does this. - All custom code needs to be cleaned up and made more generic (ie: a
libMotion
library that does stage controller). The probe station code should be moved out of labRemote and into a dedicated application.
The current plan for this is to merge !199 (merged) and tag it. That way one can also go to a semi-working version of the probe station code, but with a cleaner organization of the code. Then the probe station code will be removed completely. Then a complete new
libMotion
library would be written in labRemote.My understanding is that you are interested in the last step, which can in principle start now. Just ignore all existing code. If you need the zaber or galil libraries, then start from the
dantrim_remove_motion_control
branch used for !199 (merged) (or give @dantrim a lot of good chocolate to prioritizes completing the MR).- All libraries that are just copies of external dependencies need to be moved to
mentioned in merge request !235 (merged)