Reports 1-1 of 1 Clear search Modify search
OBS (SDF)
takafumi.ushiba - 12:48 Thursday 20 November 2025 (35605) Print this report
Changes of observation.snap during post O4c commissioning

Please write the log related to the SDF updates during the post O4c commissioning as the comment of this post.

I accepted the following SDFs.

k1calcs (fig1):

These changes are related to CAL activity yesterday (not yet reported).
So, I accepted them.

Images attached to this report
Comments to this report:
takaaki.yokozawa - 9:22 Friday 21 November 2025 (35617) Print this report
Related with those works klog35615 and klog35616,
I changed the SDF observation related with PEM model.

Images attached to this comment
ryutaro.takahashi - 13:30 Friday 21 November 2025 (35623) Print this report

I accepted the following SDFs related to the offload.

Images attached to this comment
takafumi.ushiba - 21:56 Friday 21 November 2025 (35628) Print this report

4 SDF diffs and 24 NOT INIT channels remain on k1pemex0 (fig1 and fig2).
These changes would be related to the PEM model update reported on slack, though  I could not find the klog post.

In addition, 24 NOT INIT channels remain on k1pemey0 (fig3).
Since this change is not written in the slack and I also could not find any logs, I'm not so sure the details but it would be the same update for k1pemex0.

In any case, I cannot judge the SDF should be accepted, reverted, and monitored, so I keep the SDFs as they are.
I hope the responsible persons will manage these SDFs properly soon.

Images attached to this comment
takaaki.yokozawa - 13:00 Saturday 22 November 2025 (35630) Print this report
According of the following work klog35615, I added the new monitor channels and accepted the SDFs.

Images attached to this comment
dan.chen - 13:42 Wednesday 26 November 2025 (35677) Print this report

We accepted the following SDF change caused by klog35676.

 

Images attached to this comment
dan.chen - 13:26 Thursday 27 November 2025 (35689) Print this report

We accepted the following SDF change caused by klog35688.

Images attached to this comment
ryutaro.takahashi - 9:45 Friday 28 November 2025 (35710) Print this report

I accepted the following SDFs related to the offload.

Images attached to this comment
takaaki.yokozawa - 3:29 Sunday 30 November 2025 (35716) Print this report
I accepted the following SDFs related to the initial alignment.
https://klog.icrr.u-tokyo.ac.jp/osl/?r=35717
Images attached to this comment
takafumi.ushiba - 12:07 Monday 01 December 2025 (35720) Print this report

I checked the SDF diffs found in this morning and partially accepted.
Since I could not identified the remaining changes are what we expected, I left them as they are.

k1vissrm (fig1):

Due to the bug of VIS guardian reported in klog35492, the OPTICLIGN_OIFFSET values are changed if suspensions go to TRIPPED state from MISALIGNED state.
Since the SRM was once tripped during PEM injection according to klog35685, these changes probably happen accidentially.
So, I reverted these changes.

k1visommt1 (fig2):

Since there are mysteris on these SDF diffs, I kept them as they are.
Since SDF values accepted in klog35716 are somehow different the EIPCS values at that timing (fig3), we would like to know the procedure of the accepting SDFs to confirm where is the problem.
Are SDFs accepted with the procedure written in JGW-G2516706-v6?

k1alspll (fig4):

These changes are related to the work reported in klog35679 and its reply posts.
According to klog35680, K1:IMC-SERVO_FASTGAIN was changed but this is typo.
The actual channel changed in klog35680 is K1:CARM-SERVO_FASTGAIN (I confirmed it from Tanaka-kun).
So, these changes are what we expected, so I accepted these SDFs.

Images attached to this comment
ryutaro.takahashi - 9:25 Friday 05 December 2025 (35773) Print this report

I accepted the following SDFs related to the offload.

Images attached to this comment
ryutaro.takahashi - 12:43 Thursday 11 December 2025 (35842) Print this report

I accepted the following SDFs (indicated by red square) related to the offloads (IY-BF, IY-F0, IX-F1/3). 

Images attached to this comment
ryutaro.takahashi - 9:52 Friday 12 December 2025 (35853) Print this report

I accepted the following SDFs (indicated by red square) related to the offload

Images attached to this comment
ryutaro.takahashi - 10:06 Friday 26 December 2025 (35972) Print this report

I accepted the following SDFs (indicated by red square) related to the offloads (IX-F2/BF, EY-F1IY-F0). 

Images attached to this comment
takahiro.yamamoto - 9:56 Wednesday 21 January 2026 (36184) Print this report
This was a troubleshooting for the accidental shutdown of K1TEST0 (see also klog#36183).

k1sdfmanage (Fig.1)

K1:PICO-.*, K1:STEPPER-.*

They are Pico and Stepper history and can be always accepted in safe.snap.

K1:VIS-ITMY_TEMPERATURE_HEATER_SV

It's a setpoint of heater temperature accepted in down.snap.

k1grdconfig

K1:.*_GOOD_.* (Fig.2-8)

Alignment record can be also always accepted in safe.snap.

K1:SYS-LOCKLOSS_.* (Fig.9)

They are information about the latest lockloss. It's just monitored to keep values after the power cycle of the front-end.

K1:CAM-.* (Fig.10)

These are the TCam controller values. I'm not sure monitoring these values in safe.snap is necessary or not because these value are touched not only by Guardian but also various scripts. Anyway they were accepted.

K1:SYS-HWP_.* (Fig.11)

They are the history of HWP rotation. In general, they should be accepted in the state of DOWN on IO guardian. But in this time, they were accepted (and RT model was restarted) in PROVIDING_STABLE_LIGHT state to keep values at that time.
Images attached to this comment
Search Help
×

Warning

×