-
Notifications
You must be signed in to change notification settings - Fork 0
Unpowered vs Masked
Ryan Slominski edited this page Mar 4, 2026
·
1 revision
- CED property, set there and ported into SRM/HCO
- When set, component/element/device does not appear on EDM screens
- Use for components/beamline elements/devices that are not intended to be used during the Physics run
- HCO/SRM group sign-offs still available (i.e. groups can sign Not Ready, Checked, Ready)
- Completing HCO on an unpowered device/component/element is like doing an inversehot-checkout where you verify that in no way can the thing affect beam in any way
- HCO/SRM property only, not set or read by CED
- Must be entered with an expiration date
- When a component is masked, all group sign-offs for the component are masked; when the component is unmasked (either by expiration or user), all group sign-offs go to Not Ready
- Masks are for components that are broken or out-of-service and need repair. The mask expiration is the date by which they will be addressed, or the end of the run, whichever comes first.
- Credited Controls, show-stopper, or critical components never get masked
- You can have an unpowered masked component, meaning it is both broken/out-ofservice with repair planned, and do not want it showing up on EDM / control screens
- We do not want any vacuum elements hidden on screens, regardless of if they have had their controls removed
- If the device works after a standard HCO, but we do not intend to use if for the upcoming run, and its controls have been removed, it should not be masked, just marked Unpowered