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
In speaking with Bruce, he shared an opinion that assets directories are needed for more than just detectors, i.e. other kinds of instruments that aren't considered to be detectors. This opinion is consistent with the motivation of assets, we just didn't spend a lot of time thinking about the name used in the backend.
The mechanism is sufficient to create whatever arbitrary instrument directories as-is, of course, but it might better to reflect the intended usage throughout the API and database layers.
The text was updated successfully, but these errors were encountered:
I realized this awkwardly conflicts with the fact that beamlines are called "instruments" as well. Perhaps a more specific name like beamline_daq_instrument would be better.
In speaking with Bruce, he shared an opinion that assets directories are needed for more than just detectors, i.e. other kinds of instruments that aren't considered to be detectors. This opinion is consistent with the motivation of
assets
, we just didn't spend a lot of time thinking about the name used in the backend.The mechanism is sufficient to create whatever arbitrary instrument directories as-is, of course, but it might better to reflect the intended usage throughout the API and database layers.
The text was updated successfully, but these errors were encountered: