REF: direct-to-PV vs signal protocol by way of cl #463
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Typhos supports two paths to get data from ophyd Signals.
EpicsSignal
to see which PVs it is using and passing that along to PyDMThis PR allows for an escape hatch for (1) in scenarios where we want typhos to use method (2).
This escape hatch comes in the form of a control layer
cl
check to see if the user has customized it beyond what ophyd supports.Motivation and Context
Related to pcdshub/atef#17
Where we want archived data to be sourced rather than live data
How Has This Been Tested?
Interactively, so far
Where Has This Been Documented?
This PR text.
Screenshots (if appropriate):
This is a typhos screen using this PR that gets data from the EPICS archiver: