Reports 1-1 of 1 Clear search Modify search
VAC (General)
takahiro.yamamoto - 20:10 Thursday 09 January 2025 (32289) Print this report
Slack notification about closing GVs
Because a code implementation became complicated, I had postponed to enable the alert about closing GVs until preparing an alias name as K1:*** instead of KGRVAC:***.
But we faced a trouble related to GVs today (See also klog#32286) and we couldn't catch enough information to improve the interlock system.
So we decided to enable the alert about closing GVs as a mitigation way (NOT a solution) of losing information with the non-DAQ situation.

It works fine for now but current implementation is temporal one for non-K1:*** channels same as klog#32116.
Comments to this report:
takahiro.yamamoto - 2:59 Friday 10 January 2025 (32290) Print this report

I tried to reproduced a change in the pressure value (KGRVAC:CCG_BSY_01:VAL:PRESS) after it became larger than the threshold of guardian notification from the guardian log (See Fig.1).
Log is recorded only when pressure value was larger than the threshold of guardian notification and pressure value is changed, so sampling interval is not a constant value.

Guardian threshold was set as 8.0e-6Pa in klog#32116. The first log appears at 10:55:35.885674 JST. That is, the time when the pressure value first reached the Guardian threshold. Interlock threshold which was shown as red line in Fig.1 was set as 9.4e-6Pa in klog#32173. Readout value first reached interlock threshold at 10:57:52.902407 JST. It took 147s to increase from 8.0e-6Pa (Guardina threshold) to 9.4e-6Pa (interlock threshold). Fig.2 is a same plot with longer duration. Attached text file is an original guardian logs used to make these plots.
 

Images attached to this comment
Non-image files attached to this comment
Search Help
×

Warning

×