Making mxtools.flyer more generic – 2

[JunAishima]

The object is to be able to do the following sequence:

flyer.update_parameters(*args, **kwargs)  # update parameters for the existing flyer
RE(bp.fly([flyer]))  # the only RE call needed

• Integrate functions - configure_flyer(), actual_scan()

• Integrate other functions - these are within flyer so need to use pv_object.put(value)

  • scans.setup_eiger_triggers()
  • scans.setup_eiger_arming()
  • scans.setup_eiger_stop_acquire_and_wait() - do we need this? already do this in flyer.unstage()

• Develop standard functions in flyer - update_parameters(*args, **kwargs) to set values

• kickoff() should remain the same as once things are set up, it is always the vector that sets things off.

#131

[JunAishima]

tested on FMX with profile_collection using updated code from mxtools

basically worked, so all of the major components look to be correct (though not fully confirmed - there were parameter setting issues probably due to not having the kwarg wait=True set for the put() commands.

[JunAishima]

tested on FMX with profile_collection using updated code from mxtools

basically worked, so all of the major components look to be correct (though not fully confirmed - there were parameter setting issues probably due to not having the kwarg wait=True set for the put() commands.