Famis 21121
 

When I walked up to the TCSX chiller the Ruler was on the ground. But judging by the remnants of the adheisive and the Max Level sticker I'd wager that the water level was greater than 30.

I also went back to clean up the old adhesives and apply some new double sided tape to the ruler. So it should stop falling now.  

ENDY Station Measurement:
During the Tuesday maintenace, the PCAL team (Jennie W. and I) went to ENDY with WSH (PS4) and took an End station measurement.
The ENDY Station Measurement was Mostly carried out according to the procedure outlined in Document LIGO-T1500062-v15. Except for the very last measurment. Rick and I have spoken about trying to reduce the light entering the Rx Sphere during a background measurement similar to measurment #9 by placing the normal PCAL enclosure covers back on before the start of the background. I somehow misinterpreted his suggestions and put the covers on for measurement #9. This change was hand written in to the measurment document LIGO-T1500062-v15 and is attached. Once we started to do the analysis I realized that Putting the covers on for Measurement #9 was a blunder because; only the measurement #9 was covered with pannels. Which means we won't be subtracting enough light from the rest of the measurements #7 and #8. Effectively ruining this measurement. So this needs to be it's own measurement on future attempts to take backgrounds with the covers on.

Before I touched anything, I took a pictures of the beam spot.

Martel:
We started by setting up a Martel Voltage source to apply some voltage into the PCAL Chassis's Input 1 channel and we record the times that a -4.000V, -2.000V and a 0.000V signal was sent to the Chassis. The analysis code that we run after we return uses the GPS times, grabs the data and created the Martel_Voltage_Test.png graph. We also did a measurement of the Martel's voltages in the PCAL lab to calculate the ADC conversion factor, which is included on the document.

There was also another error in the data when we were at the end station taking the measurement. Which lead to the BadTimeEy.pdf which is attached. A number of the plots during the time marked on the Document either had no data or had some "disturbance" during the time indicated on the document for measurment #2. We able to "salvage" some of this data by reducing the duration of our measurements from 240 seconds to 78 seconds and change the gpstime on measurment #2 to get usable data for all plots.
New Measurement #2 GPSstart time is now: 1368291685.

After the Martel, measurement the procedure walks us through the steps required to make a series of plots while the Working Standard is in the Transmitter Module. These plots are shown in WS_at_TX.png.

Next steps include: WS in the Receiver Module, These plots are shown in WS_at_RX.png.
Followed by TX_RX.png which are plots of the Tranmitter module and the receiver module operation without the WS in the beam path at all.
The last picture is of the Beam spot after we had finished the measurement.
All of this data is then used to generate LHO_ENDY_PD_ReportV2.pdf which is attached.

All data and Analysis has been commited to the SVN.
https://svn.ligo.caltech.edu/svn/aligocalibration/trunk/Projects/PhotonCalibrator/measurements/LHO_ENDY/

Last Tuesday during maintenance time I took transfer function measurements on SUS OMC to check it's health and functionality after SD & RT OSEM were found to be not working - see LHO alog 69500 for details. The TF results for all six dof are shown in the plots here. I think they look healthy and functional (I have compared it against last 3 years of measurements).

There is some cross-coupling seen in Roll dof (coming from Vertical dof) and Yaw dof (coming from Pitch dof) however Jeff Kissel believes they should be nicely damped when the damping loops are ON. The magnitude for Pitch dof has also dropped by a factor of four (from 2020 data, orange line) - is that a cause of concern for us?. I would also like to mention that during this measurement I got the coil driver state wrong (analog low pass was left ON, for double stage suspension like OMC LP should be OFF while taking TF) and secondly the coherence wasn't great (was getting saturations in DAQ output and I tried my best in the limited time to optimized the excitation amplitude). I am also attaching individual OSEM data below.

The templates are stored at the following location,

/ligo/svncommon/SusSVN/sus/trunk/OMCS/H1/OMC/SAGM1/Data

2023-05-16_2000_H1SUSOMC_M1_WhiteNoise_L_0p02to50Hz.xml
2023-05-16_2000_H1SUSOMC_M1_WhiteNoise_P_0p02to50Hz.xml
2023-05-16_2000_H1SUSOMC_M1_WhiteNoise_R_0p02to50Hz.xml
2023-05-16_2000_H1SUSOMC_M1_WhiteNoise_T_0p02to50Hz.xml
2023-05-16_2000_H1SUSOMC_M1_WhiteNoise_V_0p02to50Hz.xml
2023-05-16_2000_H1SUSOMC_M1_WhiteNoise_Y_0p02to50Hz.xml

The above measurements were taken with a bw of 0.03Hz. All the nominal settings were restored after the measurements were done.

Thu May 18 10:09:49 2023 INFO: Fill completed in 9min 48secs

Gerardo confirmed a good fill curbside.

I have installed a 'hwinj' application at both sites that handle opportunistic hardware injections for the detchar and stochastic groups:

The command takes two arguments: the injection group (in this case "detchar" or "stochastic"), and a specific injection name.  The available injection names/waveforms are configured in the hwinj.yaml config file.  By default injections are scheduledf or 10 seconds after the command is executed.  You need to pass the '--run' option to actually execute the injection (see --help for more info).  The detchar injection will be followed by a GraceDB upload, and the script should handle automatically fetching the authentication cert for the user executing it.  The '--dry' option can be used to test everything without actually initiating the injection or gracedb upload.

These injections should happen in nominal low noise.  Assuming everything is configured correctly and the DIAG_EXEC guardian nodes are properly tied into the overall guardian IFO status, initiation of these nodes should take us out of OBSERVING automatically.

The setup current supports three different injections, one "safety" injection for detchar (~7 min), and a long (30 min) and short (13 min) injection for the stochastic group.  The relevant injection commands would then be:

We should coordinate with the detchar and stochastic groups to run these injections during this last week of engineering run.

TITLE: 05/18 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 130Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 2mph Gusts, 1mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

H1 has been locked for almost 4hrs (w/ Jenne fixing squeezing 2hrs into the lock to optimize sensitivity.  It currently is in Observing and will stay so until PEM Team is ready to work with H1.  I have taken GRD IFO to MANAGED.

On OPS Overview the SEI EY HEPI Pump pressure has been RED. On CDS Overview we have excitations on for CalInj (which is "blue" not "red"), OMC, CalEY).

Nuc30's DARM dtt looks to have crashed again (Jenne restarted remotely), and I just resized it.

This morning, H1 was not in Observing because the squeezer was not injecting squeezing.  I requested the Sqz_manager to DOWN, then FREQ_DEP_SQZ.  That worked, and the IFO automatically flipped to Observing.

TITLE: 05/17 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 134 Mpc
SHIFT SUMMARY:

- Came into to a relocking IFO only to be delayed by an EQ (Guatemala - 6.4), holding in READY until ground motion has calmed down

- Lock #1:

• Had touch PRM just a hair (~10 microradians) in YAW and it caught but failed again in DRMI - my cue for an initial alignment
• Ran into an issue regarding the ALS X beatnote after the IA - alog - attaching a ss of a long term trend of the beatnote, it looks to have leveled out
• Acquired NLN @ 1:48 UTC where we started undergoing PEM injections
• Afterwards, I ran a quick bb cal suite, while Vicky was doing some sqz angle alignments - alog
• In OBSERVING @ 4:19 UTC
• EX saturations @ 3:06/4:50/5:55

- The IFO is currently going on a 5 hour stretch, leaving the IFO in OBSERVE, relatively quiet night tonight :)

LOG:

No log for this shift.

Took H1 to NLN_CAL_MEAS to run Calibration Suite Measurements.

• Opened terminal and entered/ran:  "pydarm measure --run-headless bb" at 2045utc.
• Measurement completed at 2051utc.

Attached is a screenshot of the sitemap > CAL CS > Calibration Monitor screen shortly after starting the measurement.

• Measurement at:  /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20230518T034545Z.xml

'pydarm report' command gave attached report: 

• /ligo/groups/cal/H1/reports/20230517T163625Z/H1_calibration_report_20230517T163625Z.pdf

Since the PEM accelerometers were installed on SQZT 0+7 a couple days ago (in-table locations in 69671), I checked table coherences with some relevant SQZ signals I could think of. A couple interesting finds, but don't totally know what to make of them yet:

• SHG coherences, with OPO TRANS + FC REFL, as well as SQZT0 motion.
  • 200 Hz - 800 Hz - Coherence of SQZ green power with SQZT0 accelerometer from seems slightly higher than I expected? Especially given the high levels of table motion seen in that same frequency band.
  • 1.2 kHz and 1.45 kHz - there seems to be strong coherence of SHG with table motion in these high frequency bands too? And the >1 kHz motion seems to get into our other green signals, like OPO_TRANS and FC_REFL.
  • With OPO ISS running, I guess it stablilizes OPO_TRANS power against the 200-800 Hz fluctuations of SHG green (w/in ISS or OPO loop bandwidths)? But FCGS doesn't have an ISS, so that SHG motion propagates to FC green locking, unlike OPO green locking with ISS.
• CLF coherence with SQZT0 accelerometers ~ 400 Hz, even though CLF_REFL_PD has an ISS running, and the PD is installed on SQZT7. Not totally surprising I guess, but kinda interesting to see it.

The IFO has been locked for 1:20 and PEM injections are currently ongoing.

After finishing an initial alignment and trying to lock ALS, we can into an issue regarding ALS X. The ALS guardian was complaining about a low beatnote. I tried to troubleshoot this by adjusting the crystal frequency to get the fiber lock beat frequency (top left of PLL overview) to ~39 MHz, but the value would just go bad again shortly after. After talking with Shiela, she suggested we lower the Beatnote RF minimum to -15 from -10 (found on the bottom right of the PLL overview sceen), and this seemed to do the trick. The scope attached is the recent trend of the beatnote in question, which in the past hour has gotten very poor, which is interesting because this was around the time the initial alignment was being done.

Update: Further up into the lock, it seems that the beat note is improving? Strange - scope attached

Naoki, Daniel, Vicky

Today we re-installed the mini-circuits amplifier, a ZHL-500HLN+, onto the CLF RF6 PD, cable ISC_SQ_222. This reverts the change from Jan. 27, 2023 (LHO:67038), when we went to a high CLF configuration to study what the problem of high CLF powers. Now for O4, we want to nominally operate with very low CLF powers, so we have reverted to dumping 95% of the optical power into the fiber as designed on SQZT0 (69457), and today restored this RF amplifier to the RF6 path. I think this now reverts up the major CLF path changes we made to study high-CLF issues prior to starting O4.

With the same 6uW of optical power incident on the RF6 PD, we now have CLF_REFL_RF6_DEMOD_RFMON = -26 (was -47) on a noise floor of -52 (was -55), see the trends here. I think we can now afford to turn down the CLF powers a bit more.

With 6uW on CLF_REFL and this added +21dB RF6 power, we re-measured the CLF transfer function. Here, we measured UGF ~ 2.4 kHz and phase -159, with CLF CMB gains set as: common gain = 15 (was 22), and fast gain = 6 (was 31), consistent with when we previously used this exact amplifer. The CLF path should be back to its nominal low-power configuration now for O4, and we explore lower-power CLF operation when IFO relocks.

A while ago we used the ifr RF synthesizer to drive the LO of the homodyne. This was still running. We now turned the ifr unit off and put the homodyne LO back to the 3.125MHz distribution amplifier.

TJ, Dave:

We have installed a new EPICS IOC which hosts PVs to support OPS stand-downs due to astrophysical events reported by external agencies (e.g. GraceDb).

The IOC runs on cdsioc0, is under systemd process control and is configured by puppet.

I have created a simple MEDM (see attachment) for testing. In the example shown it is reporting the system in standdown mode. The IOC reports the event's details, along with a calculated time-to-end.

After the calibration update this morning, I need to retrain the NonSENS noise cleaning.  However, the NDS team is still in progress on understanding why we can't get past GDS-CALIB_STRAIN channels right now.  Once we can get that past data, I should be able to retrain.  Until then, the NOISE_EST is zeros, so GDS-CALIB_STRAIN_CLEAN will be the same as GDS-CALIB_STRAIN_NOLINES.

Jennie, Sheila

Sheila and I looked at the steps Elenna changed the DARM offset through, the last time the contrast defect measurement was taken (see LHO #69361). To get an idea of how much light seen at the anti-symmetric port (calibrated in terms of power into HAM6) is insensitive to DARM motion I plotted the scaling of the light at ASC-AS_C_NSUM_OUTPUT with DARM offset changing (OMC-DCPD_SUM_OUTPUT).

Attached is the plot (pdf) of total power into HAM 6 versus the power that gets through the OMC.

The uncertainty in the AS measurement is was estimated using the y cursors on ndscope (shown in png).

0.837W of power is predicted for no DARM offset, and 82% of the light coming into HAM 6 is sensed by the OMC DCPDs.

We also tried to use the total power on OMC REFL to do a similar calculation of the light rejected from the OMC that is insensitive to DARM motion but due the noise on this signal we made need bigger DARM offset steps to see a clear trend.

Since this measurement, whitening has been implemented on the OMC REFL PD by Daniel.

Code is Plot_OMC_REFL_2023-05-12.ipynb in /ligo/home/jennifer.wright/git/OMC_mode_matching/

Figure is in /ligo/home/jennifer.wright/git/OMC_mode_matching/figures