get_posmov_fvc_data upcoming needs

[joesilber]

Currently, get_posmov_fvc_data matches each pos move db entry to FVC coordinates of positioner, for each positioner of each petal. It does the matching via timestamps. It then outputs a CSV file per positioner, containing those results + a bunch of other columns from the posmovedb.

Coming soon:

• Saving EXPOSURE_ID and EXPOSURE_ITER to the database. Should simplify matching.
• Saving OBS_X, OBS_Y, PTL_X, PTL_Y, PTL_Z to the database. These are from platemaker and from postransforms at the time of measurement.
• I want to:
  • Shift all calibrations and xytest analysis out of PECS and into desimeter.
  • Use desimeter or platemaker results interchangeably.
  • Provide tools in desimeter that can do the analysis "instantly" for operators on the mountain.

To handle this, I suggest that we:

1. Include the new columns in get_posmove_fvc_data.
2. Factor out the part where it grabs data from posmovedb.
3. Factor out the part where it saves a particular CSV file format.
4. Make a new (similar) script for grabbing data without having to run desimeter.

So both get_posmov_fvc_data and the new script---let's call it get_posmov_data---can use (2) and (3) as well.

Does that sound like a good approach? Or would it be easier to just extend get_posmove_fvc_data with more options?