Reports 1-1 of 1 Clear search Modify search
DGS (General)
takahiro.yamamoto - 17:34 Saturday 12 April 2025 (33384) Print this report
Removing MCF related models from SYS guardians
It's a temporary solution for klog#33383.

Models related to MCF cannot be launched and related EPICS records are absence. As a result, SYS guardians raised EzcaConnectErrors. So I modified them to remove a raised error.

SYS_DAQ:
It already has a function to skip checks of selected models for the maintenance time.
I just added MCF related models to the skipped list.
After recovering MCF, they must be removed from the skipped list.
Skipped list is shown on guardian notification to prevent forgetting (a science flag cannot be raised with any guardian nofications).

SYS_SDF:
I ported a skip function in SYS_DAQ to SYS_SDF.
Other correspondence is the same as for SYS_DAQ.

SYS_EXC:
K1:GRD-SYS_EXC_OK is used to find the data in which the excitation is absence also for the commissioning purposes. So we cannot use the notification area in order to show skipped models. Skipping model checks without notification allows a science flag to be raised even wih excitaitions. So I modified to check that a model is really dead. Only when the model is dead, SYS_EXC can skip without notifications. In this case, other guardians prevent raising a science flag. If models in the skip list is alive, SYS_EXC skips them with notification. This implementation allows for both reliability during observation and convenience during commissioning.
Comments to this report:
takahiro.yamamoto - 17:38 Thursday 17 April 2025 (33454) Print this report

I noticed that the recovery work of MCF (klog#33438) didn't include a temporal solution of SYS guardians in klog#33384.
As a result, OK flags of SYS_SDF, SYS_DAQ, and SYS_EXC guardians were not raised as shown in Fig.1 (it's always for SYS_SDF guardian).

I removed MCF models from the skip list in these guardians.

Images attached to this comment
Search Help
×

Warning

×