refactor DM support so it can be called from bluesky or pyepics

aps-8id-dys / ipython-8idiuser

8-ID-I ipython configuration for bluesky (and other)

1 stars 1 forks source link

refactor DM support so it can be called from bluesky or pyepics #36

Closed prjemian closed 4 years ago

prjemian commented 5 years ago

Transitional support for use in bluesky and SPEC, refactor the DM support for use in either bluesky or pyepics. Will need PyEpics structure similar to what is in 35-DM-support.py that uses epics.PV instead of EpicsSignal.

[x] build data structure
[x] write the workflow file
[x] execute the workflow from SPEC
[x] execute the workflow from bluesky

prjemian commented 4 years ago

ensure workflow helper runs all the time:

Add this to your list of cron jobs:

# make sure APS Data Management workflow helper daemon is running
# crontab line (run every 5 minutes)
#*/5 * * * * /home/beams/8IDIUSER/.ipython-bluesky/profile_bluesky/startup/spec_support/daemon.sh 2>&1 > /dev/null

prjemian commented 4 years ago

With comments such as this, time to log the output from the workflow process into its own file.

prjemian commented 4 years ago

With @sureshnaps , this code was test from both SPEC and bluesky 3 days ago and the workflow ran. Still #70 & #74 were observed. We made a change (for #74) to report the actual number of frames acquired so, at least, the workflow would not fail due to insufficient number of frames.