Reports 1-1 of 1 Clear search Modify search
MIF (Noise Budget)
takafumi.ushiba - 21:34 Friday 21 November 2025 (35627) Print this report
Automeasurement of the transfer functions for Type-A suspension noise budget

[Yamamoto, Ushiba]

We are testing automeasurement scripts.
The script automatically runs Diaggui between 12 a.m. and 5 a.m. JST from Tuesday to Saturday, unless the directories /Users/Commissioning/Scripts/NightlyMeasurements/Files/Src/ and /Users/Commissioning/Scripts/NightlyMeasurements/Files/Fail/ contain no XML files.
If the excitation remains even after 5am, please stop the script runing on k1ctr2 by interrupting the script with Ctrl+C.

Please read the script /users/Commissioning/scripts/NightlyMeasurements/scripts/nightly_measurement-devel.py if you would like to know more details of the script.

Comments to this report:
takaaki.yokozawa - 9:11 Sunday 23 November 2025 (35633) Print this report
I stopped the script 7:35:00 23rd Nov.
After confirmed the LIGO detector is not observation state, I tried start the PEM injection test, but due to the unlock of IFO, I gave up the measurement this morning.
takafumi.ushiba - 15:22 Sunday 23 November 2025 (35634) Print this report

Yokozawa-san,

Could you tell Yamamoto-kun and me what kind of issues you faced for injection measurement?
It will be helpful to fix the bug of the script.

As written in the original post, the script is designed not to conflict with the other acitivities by running only between 0:00 to 5:00 JST from Tuesday to Saturday.
So, please keep running the script if there is no conflict with the other activities.

takahiro.yamamoto - 20:56 Sunday 23 November 2025 (35637) Print this report

According to the excitation flag shown in Fig.1, a script seemed to work fine if an injection around 15:00 JST on 11/23 Sat. (t=15h in Fig.1). is a human activity not due to the script.

We made lots of injections for a debug of the script during 18:00-21:00 JST on 11/22 Fri. (t=[-6h, -3h]). And the, lots of injection with IFO lock were done in during 0:00-5:00 JST on 11/23 Sat. (t=[0h, 5h]). This behavior follows our expectation. After then, injection wasn't done except around 15:00 JST on 11/23 Sat. (t=15h). If it's due to this script, The fact that there was no injection during IFO lock around t=6h, 10h and 12h is strange. So I believe that the injection on Saturday evening should be a human activity though I cannot find a related klog, and the script properly suspended injections around 5:00 JST on 11/23 Sat. And also, there was no injection around 7:00 JST on 11/24 Sun. (t=1d,7h). I guessed that injections around 7:40 JST on 11/24 Sun. were done after stopping the script though I cannot find a related klog again.

Anyway, Because what mentioned above includes some imagines, we need to gather information about more detailed timeline of weekend activities in order to confirm that it's not really a bug of script or not.

Images attached to this comment
takaaki.yokozawa - 8:05 Monday 24 November 2025 (35642) Print this report
Sorry for inconvenient.

On Saturday 15:00(JST), For the test of the speaker at Yend, I once(or several times) turned on the Excitation.
This test itself was succeeded, but I did't leave the klog about this test, sorry.

On Sunday, as shown in klog, I performed the PEM injection test, but I didn't touch the interferometer before stopping the auto measurement job.

I didn't join the mine work at Sunday, so I didn't know the issue at Sunday.
yuta.michimura - 8:17 Monday 24 November 2025 (35643) Print this report
takahiro.yamamoto - 16:02 Monday 24 November 2025 (35652) Print this report
Thank you for cooperating to gather information!

I could confirm that all 3 unidentified injections didn't make by the auto-measurement script. So the script can be considered to be working well as our expectation.
(But we noticed that current implementation has minor problem when IFO cannot be locked such as a case of vacuum issue in this time. The script falls infinite waiting loop after requesting IFO lock when available time for measurements comes again. This issue can be fixed before the vacuum issue will be solved and we can use fixed version of this script on next time.)
takahiro.yamamoto - 12:06 Thursday 27 November 2025 (35686) Print this report

A developing version of the script used on 11/21 (*-devel.py) was pushed to the stable version as nightly_measurement.py because we could confirm this version didn't have serious problem.
So please use nightly_measurement.py from tonight.
I will resume updates of *-devel.py to add additional protection, logging, etc.

kenta.tanaka - 23:21 Thursday 27 November 2025 (35701) Print this report

I (may) run the automeasurement script for TypeA noise budget on the k1ctr3 PC. This script will work until 4:50 JST because tomorrow PEM work will start from 5:00 JST. If the script still run even after 5:00 JST,  please stop the script runing on k1ctr3 by interrupting the script with Ctrl+C.

(This script seems not to print any log on terminal screen? "_logging" function seems to be commented.)

hirotaka.yuzurihara - 8:44 Friday 28 November 2025 (35703) Print this report

For the TCam photo session, we stopped the script at around 8:40. (But, due to the large microseicm, it's difficult to lock the interferometer in OBSERVATION state.....)

kenta.tanaka - 22:35 Friday 28 November 2025 (35713) Print this report

I (may) run the automeasurement script for TypeA noise budget on the k1ctr4 PC. This script will work until 4:50 JST because tomorrow PEM work will start from 5:00 JST. If the script still run even after 5:00 JST,  please stop the script runing on k1ctr4 by interrupting the script with Ctrl+C.

kenta.tanaka - 22:33 Monday 01 December 2025 (35730) Print this report

Ushiba, Tanaka

I (may) run the automeasurement script for TypeA noise budget on the k1ctr1 PC. This script will work until 8:59 JST because there seems to be no work tomorrow morning according to "Commissioning work".

takahiro.yamamoto - 23:06 Tuesday 02 December 2025 (35742) Print this report
The nightly_measurement script was scheduled and launched on k1ctr4 during the 0:00-5:00 time slot.

The existing version of this script is running because I didn’t have enough time to test the new version today.
So please stop it before starting morning work tomorrow.
takafumi.ushiba - 23:03 Friday 05 December 2025 (35775) Print this report

Thanks to the recovery of the IFO by Yokozawa-san (klog35774), we can perform the nightly measurement today.
So, I ran the nightly measurement script on k1ctr15 with no time constraint (I change the time for commissioning to 00:00 UTC - 23:59 UTC on Friday and Saturday).
So, if you plan to work with IFO before finishing the nightly measurement script, please stop the script by accessing k1ctr15 with remote desctop and send Ctrl+c command from the terminal.

takafumi.ushiba - 9:23 Saturday 06 December 2025 (35776) Print this report

Though all measurements were finished. nightly measurement scripts didn't finish in this morning, so I finished it manually.
Figure 1 shows the src and fail directry in this morning, which seemed empty.
Figure 2 shows the nightly measurement script output on the terminal, which says nothing to be done.
Is it the behaviour what we expected or bug (I thought the script finishes when both src and fail directry become empty)?

Images attached to this comment
Search Help
×

Warning

×