At 22:00UTC I ran the MICH and SRCL FF measurements (see /lsc/h1/scripts/feedforward/README.txt) after the IFO had been locked 4 hours. The MICH comparism plot showed that the MICHFF has degraded with cold OM2 74861, some of this may be as the IFO was still thermalizing.
Gabirele fit the SRCL measurements. At 23:33UTC I loaded Gabirele's new SRCLFF (in FM7). I fit and saved the new MICHFF in FM4 .
After we lost lock 74874, I turned on both of these at 00:45UTC, saved/loaded in ISC_LOCK and Austin accepted in sdf snap and observe.snap. MICH comapre plot is greatly improved, note that as we are ~ 10 minutes into the lock that there is more noise.
The DARM FOM on the wall has looked a little peak-y today, indicating that perhaps we've got some excess jitter coupling as a result of having changed OM2's thermal state this morning.
I used a time after the IFO had been locked for 3.5 hours, and retrained the Jitter noise subtraction. I then set it in the NOISE_CLEAN guardian to come on in Observe. Since we lost lock and relocked, I've now watched this come on successfully. I also accepted the updated Jitter subtraction coefficients, as well as the JITTER_SUM_GAIN being 1, so that it is on and engaged in Observing.
In the attached plot, you can see that the laser noise subtraction that has been on for several months now is still doing well (green traces), and that the jitter noise (yellow) does a good job of removing many of these peaks.
TITLE: 12/18 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Austin
SHIFT SUMMARY:
IFO is LOCKING and at CARM_TO_ANALOG
16:09 UTC - Lockloss from NLN - alog 74864
16:48 UTC - Lockloss at Max_Power - due to 6.0 EQ in China
17:00(ish) UTC - Power cycled Nuc35 due to the screen crashing and not responding.
17:12 UTC - Fire alarm panel went off. Tyler called a few seconds after saying it was a false alarm/to be expected due to work he was doing. Alarm stopped shortly after
18:00 UTC Reached OMC_Whitening but violins are quite high - NLN reached at 19:07 UTC. It took 1 hour and 7 mins for violins to be low enough to go through whitening (Tagging SUS).
19:07 UTC - Reached OBSERVING
22:01 UTC - COMMISSIONING - went into planned commissioning. Expected to continue until around 00:00 UTC.
22:35 - 22:39 UTC - Took a broadband calibration measurement. (screenshot)
23:46 UTC - Lockloss during commissioning during Simulines calibration - alog 74874
Other: MX/Woodshop Access Door Issue - people with access can’t get in. Fil is working on it and seems to have fixed it.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 23:11 | EE | Nutsinee | Optics Lab | Local | Running tests | 00:04 |
| 17:59 | SUS | Randy | CS, EX, EY | N | Site tour of all locks | 19:28 |
| 17:21 | SUS | Randy | MX | N | Inventory | 19:25 |
| 17:40 | FAC | Kim | MX | N | Technical Cleaning | 19:25 |
| 16:41 | FAC | Karen | Optics Lab, MY | N | Technical Cleaning | 18:16 |
the broadband measurement mentioned is located at /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20231218T223413Z.xml. We had this measurement taken to evaluate the state of the calibration with OM2 in the cold state. The OM2 was cooled off again in LHO:74861.
TITLE: 12/19 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Aquisition
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 3mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.33 μm/s
QUICK SUMMARY:
- H1 is currently relocking at ACQUIRE DRMI 1F
- SEI/CDS/DMs ok
As Ryan did last week 74741. I have taken PEM_MAG_INJ and SUS_CHARGE from WAITING to DOWN so that they do not run tomorrow. Instead, tomorrow Louis will try the risky DARM loop swaps and calibration. To re-enable the automated measurements, the nodes should be requested to INJECTIONS_COMPLETE before next Tuesday.
I've requested both the SUS_CHARGE and PEM_MAG_INJ nodes to INJECTIONS_COMPLETE so that the automated injections will run again starting next Tuesday.
Lockloss during commissioning during simulines calibration. Investigation ongoing since we have lost lock 3 times during simulines in the last week (with one successful run) - currently unsure if simulines is a culprit.
I looked into this. The lockloss was likely not caused by Simulines injections. I ran simulines about two minutes before we lost lock but simulines exited almost immediately due to an error in one of its configuration files and I confirmed that it did not start any injections before it exited.
I took the noise injection of jitter and arm ASC with cold OM2. The templates I ran are as follows. The noise injection of LSC will be taken after FF is updated for cold OM2.
IMC_PZT_P_inj.xml
IMC_PZT_Y_inj.xml
CHARD_P_EXC.xml
CHARD_Y_EXC.xml
DHARD_P_EXC.xml
DHARD_Y_EXC.xml
DSOFT_P_exc.xml
DSOFT_Y_exc.xml
CSOFT_P_exc.xml
CSOFT_Y_exc.xml
IFO is in NLN and OBSERVING as of 19:07 UTC (54 min lock).
Mon Dec 18 10:07:48 2023 INFO: Fill completed in 7min 44secs
Jordan confirmed a good fill curbside. He noted there is an ice ball around the end of the discharge line.
TC mins were -75C,-70C.
Here's a comparison of Pcal to DeltaL External and GDS Calib Strain broadband measurements with OM2 hot and cold.
File path to DTT template: /ligo/home/dana.jones/Documents/OM2_heating/OM2_hot_v_cold.xml
Dana, Louis
These broadband measurements were taken as part of the regular calibration sweeps when H1 was fully thermalized. To get the measurements, I used this command (for a sample report ID):
pydarm ls -r 20230802T000812Z | grep PCALY2DARM_BB | grep pcal
which returned:
>> pcal: /ligo/groups/cal/H1/reports/20230802T000812Z/PCALY2DARM_BB_20230727T161527Z.xml
Then to get the exact start time of the injection I used:
grep TestTime /ligo/groups/cal/H1/reports/20230802T000812Z/PCALY2DARM_BB_20230727T161527Z.xml
See this link for a list of calibration measurements. To calibrate the Delta L External and Pcal measurements I used the following files found in /ligo/home/dana.jones/Documents/OM2_heating/:
deltal_external_calib_dtt_20230621T211522Z.txt
deltal_external_calib_dtt_20230628T015112Z.txt
deltal_external_calib_dtt_20230716T034950Z.txt
deltal_external_calib_dtt_20230823T213958Z.txt
deltal_external_calib_dtt_20230830T213653Z.txt
deltal_external_calib_dtt_20231027T203619Z.txt
pcal_calib_dtt_20230621T211522Z.txt
pcal_calib_dtt_20230628T015112Z.txt
pcal_calib_dtt_20230716T034950Z.txt
pcal_calib_dtt_20230823T213958Z.txt
pcal_calib_dtt_20230830T213653Z.txt
pcal_calib_dtt_20231027T203619Z.txt
These files were generated using the following two commands (again, for a sample report ID):
pydarm export -r 20230802T000812Z --deltal_external_calib_dtt
and
pydarm export -r 20230802T000812Z --pcal_calib_dtt.
Note: For the most recent curve (23/12/10), I applied the 23/10/27 calibration TF as this was the latest valid one available.
In addition, for GDS_CALIB_STRAIN I applied a gain of 3995 in the Poles/zeros tab to convert to meters (see .xml file).
User note for calibration tab in DTT: Make sure when applying different calibration transfer functions to each curve that you set the start time appropriately—you can’t just use the same time for all of them or the system won’t know which one to choose. For each measurement, set the corresponding calibration start time to, say, 1 day before.
Here's a PCALY-to-GDS_CALIB_STRAIN broadband comparison with the OM2 in the hot state (gold trace, 2023-12-10) and in the cold state (cyan trace, 2023-12-18), see bb_hot_cold_om2.png. Both measurements were taken while the IFO was thermalized. Pcal corrections have been applied to PCALY_RX_PD_OUT. The two traces don't line up exactly but their differences are down to the percent level. Sheila is pulling up GDS_CALIB_STRAIN spectra from before and after the OM2 cooling for comparison purposes. This plot suggests that she will be able to overlay the two and compare them as long as we're not interested in making any determinations close to ~few percent level.
Lockloss from NLN - brief investigation via lockloss tool shows EX as the first thing that saturated.
At 16:40UTC (8:40am) I changed H1:AWC-OM2_TSAMS_POWER_SET from 4.6 to 0. This will cool off OM2 over the next few hours. Temperature is already dropping, plot.
Ibrahim is currently relocking the IFO. Accepted sdf in safe.snap, will need to accept in observe.snap.
After ~2 hours the temperature read by the thermistor is leveling out, plot.
TITLE: 12/18 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 2mph Gusts, 0mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.31 μm/s
QUICK SUMMARY:
IFO is in NLN and OBSERVING as of 00:37 UTC (~15 hr 30 min lock)
Full DQ shift report is here.
TITLE: 12/18 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
- Following the EQ lockloss from earlier, H1 is back to NLN @ 0:16/OBSERVE @ 0:36 (SQZ was having trouble tuning the sqz angle due to commissioner changes, but Naoki reverted these changes so we should have no further issue)
- 0:29 - inc 4.9 EQ from Mexico
- Other than the EQ it was an uneventful night, nothing else to report
LOG:
No log for this shift.
The trouble of SQZ happened after I changed the ADF servo flag in sqzparams to False. I wanted to see SQZ drift without ADF servo, but FC IR kept unlocking after this change so I reverted it. I am not sure why FC IR got unstable without ADF servo.
We found this was due to incorrect logic in SQZ_MANAGER. If the use_sqz_angle_adjust flag is false, the node never arrives at True and goes down to SQZ_READY_IFO, unlocked FC after 120s, thinking that it's failing to reach IR_LOCKED. Edit in svn 26967.
Lockloss @ 23:25 UTC from some sudden, local seismic activity.
I first noticed the channel on Picket Fence for the station on the Olympic Peninsula turn yellow, then PRG and circulating power signals started going unstable, then lockloss all within about 10 seconds. EQ mode activated one minute later. USGS doesn't show any nearby earthquakes, but judging from the order the Picket Fence stations saw the motion, it seems to have come from off the western WA coast.
USGS now shows a M4.6 earthquake somewhat nearby in Canada which is the likely cuplrit.
The picket-fence signals, of which I'm looking at the MAX channel, which just gets the maximum value of any of the 5 stations we're reading data from, and it looked to have given us an almost 2 minute warning for this incoming EQ. The signals on the seismometer reached the EQ transition threshold (400 nm/sec) almost 2 minutes before we saw the motion on site.
Hsiang-Yu, Ansel Neunzert
We notice 23.8092 Hz, the odd harmonics peak of 1.9 Hz comb, show up again on 12/11~12 ,12/14 and 12/16 (Fscan-observing on 12/15 is not working). After raising this, I also check last week's DQ shift record. It also existed on 12/5, 12/6, 12/8 and 12/9. This comb was known before and have LLO alog 66036 and git issue. The attach figure is fscan-observing screenshot on 12/16.
Sorry. It should 11.9 Hz.
It looks like there was a major change in the 11.9 Hz comb on Nov 1, and then a smaller decrease after Nov 14 and an increase on & after Dec 5. No ideas yet for what might be related, just logging the times. Plot attached shows the height of the n=3 line at 35.71389 Hz over time, in normalized average daily Fscan spectra (so the y-axis is in arbitrary units). Second figure shows the same quantity, but tracked over a much longer time period.