TITLE: 06/23 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
SHIFT SUMMARY:
Locked at NLN at 13:37, in Observing at 13:58.
All of the Picket-fence seismometers except TOOM (South OR) and PNT (South BC) lost connected around 18:30.
We went out of Observing at 18:53:34 by mistake but we went back into observing 30 seconds later 18:54:04.
We went out of Observing at 19:08 for some planned PEM work at EndX, back into Observing at 20:03. We went out of Observing at 21:37 for some injections.
While trying to stop a transient injections exitation, the CW injections were accidentally stopped at 22:26. Still ongoing trying to get these back up and running.
In and out of Observing as we try to figure it out
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 14:40 | FAC | Karen | VAC prep, Optics | N | Technical cleaning | 15:20 |
| 15:43 | FAC | Karen | Woodshop | N | Tech clean | 16:32 |
| 17:19 | FAC | Kim | H2 | N | Tech clean | 17:41 |
| 18:58 | PEM | Robert | EndX | N | PEM work | 20:03 |
Ran stochastic short and long hardware injections, in coincidence with LLO. These are of the style described in alog 69723.
hwinj stochastic short --gps 1371592362 --run
hwinj stochastic long --gps 1371593299 --run (Interrupted by earthquake. LLO lost lock, so I ctrl-c'd)
I used a little under an hour of commissioning time, from about 12:05 to about 1 PM PST, in part when LLO was down, to improve on the shaker coupling measurements at EX that I made yesterday.
Attached is a strain noise spectrum comparing the sub-100 Hz performance of H1 and L1 (inspired by a similar plot that Elenna made). The data was taken in the recent 5-hr long coincident lock, so H1 has its improved low-frequency noise that came from reducing the input power to 60 W. The L1 noise is lower by a factor of 2-3 in the 15-30 Hz band, and the H1 noise is lower below about 13 Hz.
Also noteworthy are broad noise peaks (as might be produced by scattered light) in H1 at 26 Hz, 39 Hz, and 52 Hz -- i.e., these peaks are separated by 13 Hz, though there's not a noticeable peak at 13 Hz.
I ran a fine resolution to see if I could find a corresponding 13 Hz peak to match the others in series. There appears to be something at 13.07 Hz, see attachment.
Some of the peaks in the series from 13.75-14.4 Hz are roll modes. Searching back through some alogs, the catalogued roll modes are as follows: ITMY 13.85 Hz, ITMX 13.9 Hz, ETMY 13.84 Hz, ETMX 13.77 Hz (see 43728, 57668). Not sure what the rest are.
Enabled H1:SQZ-LASER_RFAM_LF, adding ct2V filter and setting gain to 1. SDF updated.
We've been locked for 06:04, we went out of Observing at 19:08 for some planned PEM work at EndX which is still ongoing. We are currently feeling an EQ from the North MidAtlantic (5.2), seismic went into EQ mode at 19:42.
I wrote some guardian code to decrease the lockloss time. For improving DRMI wait time: The code starts a 60 second timer. When the timer ends (if 5 minutes hasn't elapsed) then it checks the last 60 seconds of POPAIR_B_RF90 data to see if the max value of the flashes is below the threshold of 200. If so, then it will send guardian to ACQUIRE_PRMI. If the max value of the POPAIR data is equal or above the threshold then it will reset the 60 second timer and check again on the next passing of run(self). This should decrease the wait time at ACQUIRE_DRMI_1F from 5 minutes to 1 minute if DRMI_LOCK won't be achieved. For improving PRMI wait time: Does the same as the DRMI code above except the POPAIR max threshold is set at 20. And if the threshold isn't reached, then it sends guardian to CHECK_MICH_FRINGES. This should decrease the wait time at ACQUIRE_PRMI from 10 minutes to 1 minute if PRMI_LOCK won't be achieved. These thresholds were chosen after looking at various times during lockloss. Finding when the guardian state would change from ACQUIRE_DRMI_1F (101) -> DRMI_LOCKED_PREP_ASC (102) or when ACQUIRE_DRMI (101) -> ACQUIRE_PRMI (50) and comparing the max values for POPAIR_B_RF90_I_ERR_DQ. Similarly for ACQUIRE_PRMI (50) -> PRMI_LOCKED (51) or ACQUIRE_PRMI (50) -> CHECK_MICH_FRINGES (48). These threshold values can be easily updated as needed. My code's location is /ligo/home/bricemichael.williams/DRMI__PRMI_POPAIR_check_speed_up.py and just needs to be copied into the ISC_LOCK code file. I made notes in my file where the parts of the code go and discussed with Camilla and TJ about testing it on Tuesday (6/27) during start-up after commissioning.
Enabled H1:SQZ-LASER_RFAM_LF, adding ct2V filter and setting gain to 1. SDF updated.
I compared the sensitivity with 75W vs 60W. The sensitivity below 50Hz significantly improved with 60W. On the other hand, the sensitivity at high frequency does not really change. As shown in the SQZ measurement in alog70686, the shot noise without squeezing improves by ~1dB with 75W as expected (sqrt(75/60)~1dB), but the squeezing level is also lost by ~1dB with 75W and therefore the shot noise almost does not change in the end.
Fri Jun 23 10:09:21 2023 INFO: Fill completed in 9min 20secs
Jordan confirmed a good fill curbside.
Here's a new BruCo scan for a good range time after the LSC FF improvements from yesterday:
https://ldas-jobs.ligo-wa.caltech.edu/~gabriele.vajente/bruco_GDS_1371513618
In summary:
TITLE: 06/23 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 140Mpc
SHIFT SUMMARY:
LOCK#1:
LOCK#2:
LOCKs Post Alignment & with Laser Noise Suppression issue
LOG:
TITLE: 06/23 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 134Mpc
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 6mph Gusts, 4mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.06 μm/s
QUICK SUMMARY:
As posted earlier, there were issues getting through the LASER NOISE SUPPRESSION step. Luckily, Evan saw my posts on ligo.chat and gave me suggestions for stuff to check from status descriptions I posted. In addition to the note earlier, we had various messages:
From this Evan pointed me to ISS 2nd Loop Offset alogs:
Luckily, with the above changes, for the next lock attempt, LASER NOISE SUPPRESSION was not an issue.
Once at NOMINAL LOW NOISE, it took the Camera Servo about 22min before we could go to OBSERVING.
And after looking at the range forthe last hour, it appears to be lower than what we had for the last lock, so perhaps my changes were not optimal and could be improved.
Not sure if I turned "OFF" the 2nd Loop the correct way. On the 2nd Loop Screen, I would toggle the 2nd Loop via H1:PSL-ISS_SECONDLOOP_CLOSED (on right of screen), but I'm thinking I should have been toggling H1:PSL-ISS_SECONDLOOP_ENABLE (middle of 2nd loop screen) instead.
Noting here for future reference... (and tagging OpsInfo)
The "cleanest" way we have to engage/disengage the secondloop is with the IMC_LOCK guardian. In the LOCKED state, the IMC is locked and the secondloop is OFF. When the ISS_ON state is requested, the guardian moves to CLOSE_ISS (which actually does the process of engaging the secondloop), and then to ISS_ON, where the secondloop is considered to be ON. The secondloop can be turned off again by requesting the LOCKED state, where the guardian will move through OPEN_ISS.
H1's Longest Lock Duration: 26hrs 51min
There was no obvious environmental reason for a lockloss at 0751utc.
Green arms were a bit off (as well as the BS for PRMI). First locking attempted failed while ASC was engaging for DRMI.
1371541886 I can see no LSC or ASC instabilities before lockloss. The lock was not "FAST" (>30ms) as classified in G2201762 and lockloss was upstream of IMC as the IMC stayed locked for 0.3s after light fell off AS_A, see attached.
R. Short, J. Driggers
Daniel had noticed that the ISS secondloop gain had been set back to -5 dB when the IFO relocked to 60W last night. Since we now want this at -2 dB in our 60W configuration (alog 70684), I've updated the ISS_acquisition_gain in lscparams.py to be -2 and committed to svn. While we were out of Observing this afternoon starting at 22:45 UTC, I changed the gain to -2 dB, accepted the change in SDF, and reloaded the IMC_LOCK guardian.
This usually doesn't work without adjusting the input offset. Also, you would want to test this with the IMC alone, since the AC-coupling is finicky. On the other hand, changing the gain after the servo is engaged is trivial.
Plot 1 shows the dark noise in LSC-REFL_A_LF and REFL_B_LF (yellow/black), with 10W laser input with ISS second loop (red/blue) and w/o ISS second loop (magenta/cyan). The photocurrent in REFL_A and REFL_B was about 16mW each for the 10W measurements. It will turn to about 10mW in full lock. So, we are now about a factor 4 above dark noise.
Plot 2 shows the RIN of the 2 REFL PDs and their average, together with the ISS second loop sensors. The ISS inner and outer sensors have about 7-8mW of light each, so the measurements are limited by the shot noise of the inner PD. In full lock these sensors see about 60mW.
Here are 2 plots when the interferometer is locked. The ISS second loop sensors see about 60mW of light, whereas for this time LSC-REFL_A/B see about 8mW each.
The first plot shows a large excess in REFL power fluctuations below ~200Hz. EVen the flat part 300Hz shows some excess. It should be about 70% of the 16mW measurements, but shows a very similar level. Looking at the coherence between REFL_A and B indicates that this is a real signal and not noise.
The second plot shows relative intensity noise. To get the curves calibrated correctly one should match the peak near 4.5kHz since this seems rela intensit noise from the laser. (There is a factor of 0.3 in the calibrations of the RIN of REFL_A/B to acocunt for the interferometer reflectivity at DC. This factor should be 1 when the interferometer isn;t locked.)
Here is comparison between early in the lock and after 4 hours.
The hump in the reflected power is clearly getting larger as time progresses, and is its coherence with PRCL. The input power as measured by the ISS second loop outer sensor doesn't have a large correlection with the reflected power (some is expected due to the shot noise of the inner sensor).
Q1: Why is PRCL coherent with the power in reflection? If theer is a couplinh, shouldn't it be at least second order?
Q2: What's the flat noise above 300Hz that we see in the reflection power?
Here is the power trend during this lock.
And these are the plots more than 7 hours into a 60W lock. The REFL PD now seems to be shot noise limited above 100Hz.
Here is a comparison between the noise measured in reflection at 75W and 60W and against the dark noise. Some observations:
The outer loop RIN is always reported about 8% higher than the innner loop one. This is not real. In the PSL ISS model of the second loop ISS both detector values are divided by the DC value of the inner loop detector. Since the outer loop detector sees about 8% more light, the RIN in the outer loop detector is overestimated by this amount. To get a better value multiply by 0.922. With this correction both RIN spectra agree with each other.
A better calibration of the REFL/ISS PDs measured with 10W input and all TMs misaligned.
| Measured | Calibration | |
| IMC-PWR_IN | 9.855 W | 1 W/W |
| PDSUMINNER | 7.477 mA | 0.7588 mA/W |
| PDSUMOUTER | 8.115 mA | 0.8235 mA/W |
| REFL_A_LF | 16.70 mW | 1.694 mW/W |
| REFL_B_LF | 15.59 mW | 1.582 mW/W |
Here is a 60W trend for completness.
It turns out that those awg scripts don't release their exitations nicely, which means that we weren't going to be able to go to Observe until they were cleared. In clearing them, I accidentally stopped the CW hardware injections. Once those were back in place, we're back to Observing.
The rest of this alog is some details, in case we need to refer to them long-term.
When trying to figure out how to stop an individual excitation (the Transient hardware excitation point) I misunderstood the meaning of the channel numbers on the GDS TABLE from the calinj's GDS screen (see attachment), and inadvertently stopped the CW injection rather than the Transient injection path. Those numbers are for *testpoints*, not awg slots (which is consistent with what the top row of the table says, but it didn't click for me). Erik reminded me later that I could have checked awg slots with
diag> awg show 42(where 42 is h1calinj's number), but it's still not clear that you can selectively clear a single excitation. Jamie and the CDS folks are going to follow this up.In the end, I did an awg clear 42 * and also tp clear 42 *, and that released all the excitations (since we already had to restart the CW injections).
Apparently there is a 'monit' process that should automatically restart the CW injections if they are stopped for some reason like this. However, Dave found that since tconvert has an output (due to a warning), that monit process was not being successful. Dave worked some magic, and tconvert no longer gave a warning, which meant that the monit process was able to restart the CW injections. After that was done, we were able to go back to Observe long term.
Until we understood the issue with the startup script, I had been holding us out of Observe since we didn't have the CW injections. Keith let me know that they have monitoring downstream for when those are or are not in place, so it would have been fine if the CW injections were not in place for a few hours to a ~day, until we were able to debug. I tried to set us to Observing, however every few minutes the auto-startup-process was trying to start the injection, which begins with setting a gain to zero (so that it can later be ramped on), so that SDF diff kept popping us out of Observe. Dave stopped the monit process, so we went back to Observe and stayed there for a few minutes. By then, Dave had fixed the tconvert warning issue, and we went back out of Observe one last time, Dave restarted the monit process, and it restarted the CW injections. Now we're *really* back in Observe.
EDIT: Dave's alog about the magic: alog 70775
It seems that the --gps option has been removed and no longer works (it did work last Fri). We successfully used the --time option to give it the gps time.