You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Address bits of code that are less likely to fail in testing so far but could fail if conditions are met (flow control choices - most common seem to work ok)
find_possible_darks() will run into an unhandled exception at this line if header.stop["exit_status"] == "abort" since exp_time will not be defined in that case.
another thing to add to the list is how to handle if the stop document DOES NOT EXIST. This can happen if someone tries to ^C a bluesky session AFTER RE.abort() or RE.stop(). Currently, the ^Z and killing the process is the only way to recover, and in that case, the stop document is never written to data store. bluesky/bluesky#1626
Some minor work is needed.
Address bits of code that are less likely to fail in testing so far but could fail if conditions are met (flow control choices - most common seem to work ok)
As per @hyperrealist in #89
find_possible_darks()
will run into an unhandled exception at this line ifheader.stop["exit_status"] == "abort"
sinceexp_time
will not be defined in that case.find_possible_darks()
may return a pandas DataFrame here or a python dictionary here depending on the execution path.And then also:
np.copy()
from fccd.py and overscan.pyFar future for a new issue after this one is addressed:
The text was updated successfully, but these errors were encountered: