-
Notifications
You must be signed in to change notification settings - Fork 1
re-install latest production release of ophyd #123
Comments
Current ophyd version points to local development directory.
|
Now, start bluesky session and look for startup problems.
|
One local fix already implemented: |
Looks like the GatherPlugin is not necessary now since the code that calls it (from
|
The changes in ophyd to implement timeout and retry are fundamental to PV connections throughout the ophyd code (EpicsSignal, EpicsMotor, area detector) and would require massive duplication. Not the best place, or even a good place. Better to implement in an ophyd branch. |
@danielballan : Can you help with this ophyd branch? Ophyd release 1.3.3 installed at beam line and bluesky session starts. This issue is done. Will open a new one once the new ophyd branch with timeout and retry are implemented. |
During user operations in November and December, we encountered problems (#114) such that the instrument had to stop using the bluesky software. Through various discussions and testing (prjemian/ipython-vm7#1, #114, bluesky/ophyd#776, bluesky/ophyd#776, bluesky/ophyd#782, bluesky/ophyd#783), some of our problems were likely due to use of a non-production release of ophyd.
To take advantage of various changes since the latest production release (1.3.3), we used 1.4.0rc3 (and then with additional modifications). The master branch of the ophyd repository is well past the 1.3.3 release but the additional changes are not fully tested.
We should re-install the 1.3.3 release locally, then apply any additional modifications locally to regain the changes we hoped to see from the 1.4.0rc3 release.
The text was updated successfully, but these errors were encountered: