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
Now that lightpath has a hardcoded configuration we can tell all the devices that need to be loaded quite easily. It would be nice if downstream beamlines are included as well, maybe contained within a namespace i.e
mfx_dg1_pimxrt.hxx_valve
Current Behavior
Only devices on the beamline that match the hutch are included.
The text was updated successfully, but these errors were encountered:
If we do load these devices I expect the existing infrastructure to automatically create namespaces for them of the form beamline.stand.name... so for us, that's unfortunately hxd.hxx.valve, for example. We may need to rethink how we set these namespaces up.
Expected Behavior
Now that
lightpath
has a hardcoded configuration we can tell all the devices that need to be loaded quite easily. It would be nice if downstream beamlines are included as well, maybe contained within a namespace i.eCurrent Behavior
Only devices on the beamline that match the hutch are included.
The text was updated successfully, but these errors were encountered: