.. _nustar_dcs_status: Subsystem Status ================ Levels of integration --------------------- The level of integration of sub-systems and sub-system components is indicated by level nmubers. Each level includes the requirements of all lower levels: .. csv-table:: Sub-system integration status levels :header: "Level number", "Requirements" :widths: 5, 95 0, - None. 1, " - Individual components have reached at least level 3." 2, " - Individual components have reached at least level 5. - A strategy for coordinating the individual components is defined." 3, " - Individual components have reached at least level 7. - A coordinating IOC is implemented that allows high level control and monitoring of the sub-system via the sub-system state machine." .. csv-table:: Component IOC integration status levels :header: "Level number", "Requirements" :widths: 5, 95 0, - None. 1, " - EPICS integration is planned. - A decision on the implementation of the IOC is made." 2, "- Device support for the component is ready. - Firsts tests confirm that the chosen implementation is viable." 3, " - Basic functionality of the component is implemented in the IOC. - Confirmed with successful operation under testing conditions." 4, " - The component can be safely operated and monitored from the IOC alone. - It does not need frequent manipulation via other means. - The record database includes useful settings for - alarm thresholds - hardware limits - scan rates - units and value conversion - deadbands" 5, " - All functionality needed for operation during experiments is implemented in the IOC. - No physical access to the component is required to start up the IOC, operate the component as needed, and shut down the IOC. - Stable long term operation is possible. - State of the IOC can be saved and restored on demand using autosave (preferred) or BURT." 6, " - Process variable lists are available (preferrably automatically generated) that are used in external tools, such as the database archiver, the datastream archiver, the gateway. - Mapping from hardware channel addressing to physical detector channels (e.g. hostX:busY:moduleZ:channelA -> detA:scintillatorB:pmtC) is done via record aliases." 7, " - High level controls and monitoring of the component IOC allow integration with other components of the sub-system. - Parameters for different states of operation are defined." R3B --- .. csv-table:: LOS Status :header: "Component", "IOC status" FQT, 4 HV, 3 LV, 1 PC, 1 VME-crate, 1 .. csv-table:: PSPX Status :header: "Component", "IOC status" HV, 4 LV-Febex, 3 LV-12V, 0 Vacuum pressure, 3 PC, 1 Turbo pump, 0 .. csv-table:: ROLU Status :header: "Component", "IOC status" HV, 3 Motor, 4 .. csv-table:: Target Status :header: "Component", "IOC status" Motor, 4 .. csv-table:: DSSSD Status :header: "Component", "IOC status" (information needed) .. csv-table:: MUSIC Status :header: "Component", "IOC status" HV, 0 LV, 0 Gas system, 0 .. csv-table:: Fiber Status :header: "Component", "IOC status" HV, 3 Motor, 1 LV, 1 PCs, 1 .. csv-table:: GLAD Status :header: "Component", "IOC status" Current, 1 Temperature, 1 .. csv-table:: Neuland Status :header: "Component", "IOC status" HV, 5 FQT, 4 LV, 3 PCs, 1 .. csv-table:: TOFD Status :header: "Component", "IOC status", "Notes" HV, 3 FQT, 4 LV, 3 PCs, 1 Motor, 2, Missing limit switches .. csv-table:: DAQ infrastructure :header: "Component", "IOC status" MBS, 1 Scalers, 1 LTSM, 1 .. csv-table:: Network infrastructure :header: "Component", "IOC status" SC switches, 0 .. csv-table:: Clock infrastructure :header: "Component", "IOC status" BuTiS receiver, 1 BuTiS switch, 1 .. csv-table:: Timing infrastructure :header: "Component", "IOC status" WR switch, 0 Saftlib, 0