Hello!

I have been working on eventually calculating how much force is being applied to three stages of the quadruple pendulum. The channels I am currently plotting in the figures attached are the DARM control signal (H1:CAL-CFTD_DELTAL_CTRL_DBL_DQ), the penultimate mass control signal (H1:CAL-CFTD_DELTAL_CTRL_PUM_DBL_DQ), the upper intermediate mass control signal (H1:CAL-CFTD_DELTAL_CTRL_UIM_DBL_DQ), the top test mass control signal (H1:CAL-CFTD_DELTAL_CTRL_TST_DBL_DQ), the external excitation signal (H1:CAL-CFTD_DELTAL_EXTERNAL_DQ) and Pcal y (H1:CAL-PCALY_RX_PD_OUT_DQ) - I should include Pcal X next time. By plotting these channels I can map out how much each stage of the quadruple pendulum is moving (or being actuated upon), the Pcal injections, and eventually compare the force needed to control each stage to keep our interferometer locked.

Right now I am plotting the meters per root Hz for each channel. I am also applying an anti-whitening filter so that I can convert the signals from counts back into the physical displacements. 

The path to the file to plot these figures is: /ligo/home/caroline.capuano/Force_on_ETMX_for_each_stage/phase_and_mag_of_h.py

All you need to do is run "python phase_and_mag_of_h.py" and it should produce both plots.

Currently I am taking data from LIGO Hanford at the GPS start time of 1425831025 for a duration of 1000 seconds.

There is a weird bump around 100 Hz for the external excitation signal, so Craig suggested I find another time of when we were locked and compare to see if the hump is still present.

To do next:
- figure out what filters to divide by so that I can calculate the force being applied to the three stages aka N/rtHz.
- maybe try quick_psd instead of welch's method and see if that makes a significant difference

Two index number changes this morning:

1. Adjust_Power was 1000, we have changed this to 521. This now fits it in linearly in the state graph and doesn't mess with other scripts, checks, and things that check for low noise conditions above 600.
2. Darm_Offset was brought back to 427 from 432. A few days ago (alog84703) it was changed with the thought that the move would bring the state back into order, but we plan to move the state back to it's old place between DRMI_TO_POP and ENGAGE_RF_VIOLINS when we can. Sorry for the confusion.

TITLE: 06/03 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.27 μm/s
QUICK SUMMARY:

IFO is in DOWN for PLANNED ENGINEERING

Today is a light maintenance day in with the plan being to continue locking H1 to NLN.

The highest state we are able to get to is: LOWNOISE_LENGTH_CONTROL.

Workstations were updated and rebooted.  This was an os packages update.  Conda packages were not updated.

TITLE: 06/03 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

Just had another lockloss so I'm just putting the detector in IDLE for the night. I have a list of things from Elenna to check/try with relocking, but I won't be able to get to any of them before the end of my shift, so they can be checked tomorrow morning. This last lockloss was during OFFLOAD_DRMI_ASC while I was trying to adjust SRM, although I don't think I caused the lockloss? It took a while for DRMI to catch this time, so maybe running an initial alignment is warranted. The highest state we were able to get to today was LOWNOISE_LENGTH_CONTROL.

The list Elenna gave me is:

• Watch ADS for problems (we weren't seeing any ringing up, but ADS were taking more than 10 mins to converge in MOVE_SPOTS (84734)
• Check that CHARD Y gain goes to 300 at the end of MAX_POWER (once we are at 60W and ADS have converged) (84732)
• Watch for DHARD P oscillation during TRANSITION_FROM_ETMX (84736)
• Try to damp violins at full power (I put Rahul's new damping settings into lscparams for 2W (84720), so during damping at higher powers we will need to see whether the current settings or the 2W settings work best for those three modes) Tagging SUS, OPS Info

LOG:

23:00UTC Commissioning and sitting in POWER_10W
23:20 Started trying to increase power
01:49 Lockloss from LOWNOISE_LENGTH_CONTROL while sitting there running measurements
    - Started a manual initial alignment
        - Stopped at PRX_LOCKED, touched up PRM, then finished IA
    - Stopped at OFFLOAD_DRMI_ASC, touched up SRM, then continued
    - Lockloss in DRMI_TO_POP
        - Probably due to DRMI alignment not being the greatest
    - Stopped at OFFLOAD_DRMI_ASC, touched up SRM, SR2, and PRM, then continued
    - Lockloss in LOWNOISE_ESD_ETMX due to a CHARD P ringup that started in TRANSITION_FROM_ETMX
    - Lockloss from OFFLOAD_DRMI_ASC while I was trying to touch up alignment using SRM. Not sure if my fault?

Writing this alog on behalf of most of the control room...

After we redid the input matrix for CHARD and INP1 10W, we checked the PRC2 and INP1 bandwidth. We were also concerned about the overall gain of CHARD P and Y since they seemed to be way too low

• We stepped the offset of INP1 pitch and yaw as a rough bandwith measurement. We found that INP1 yaw gain to be too high by a factor of 10, and the INP1 P gain to be just fine.
• we ran OLGs of PRC2 pitch and yaw, and found the gain to be about a factor of 3 too high for both, which may have been responsible for some 0.8 Hz buzzing we saw in the ASC signals whenever we tried to raise the CHARD gains
• After this, we were able to raise the CHARD P gain to achieve a UGF around 3 Hz, as desired.
• We were still unable to raise the CHARD Y gain to a reasonable value without ringups
  • it seemed anywhere between 20 and 40 dB too low, but it was hard to tell from the measurements.

We decided to power up anyway, and saw that the pitch ADS was able to run fine, now that the CHARD pitch gain was nominal. However, yaw ADS still had problems during move spots.

• We stepped up power from 10 W by hand, and then ran through the power 25W state by hand (which also changes loop gains, engages soft yaw, etc).
• Then we ran move spots successfully- towards the end of the state is where we had to drop the yaw ADS gains due to an instability.

Everything looked good, so I took us up in power from 25W to 60W, stopping frequently to check for instabilities. We made it, but again the ADS was unstable, so Georgia used the Camera servo guardian to move off the ADS to camera servos, and everything was fine.

I stepped through lownoise ASC by hand, skipping the lownoise steps of CHARD P and Y since those gains were not nominal.

• Then, I rescaled the overall lownoise gain of CHARD P and engaged its lownoise filters, no problem.
• I measured the CHARD Y OLG and found the gain  still very low. But this time I could step it up from 3 to 300 as needed and the higher gain made the buildups look a little better.
• Since the gain was back to nominal, I scaled to the lownoise gain and engaged the lownoise filters.
• The gain scaling is saved in the guardian.

Lots of the of the usual wobbly stuff in the ASC and buildups at high power, but the overall alignment and control looks good: PRG is still around 50 at full power.

We then ran through lownoise coil drivers and the ETMX ESD transition. We had one guardian error at the end of TRANSITION FROM ETMX due to divide by zero error since the convergence checker looks for something that is like [ADS error signal / ADS CLKGAIN] and the ADS CLKGAINs were zero. Georgia and I fooled the guardian by setting the CLKGAINs to 1 momentarily, and then undoing them once the state completed.

We ran all the way through LOWNOISE LENGTH CONTROL, although the LSC feedforward is no longer well-tuned, so I turned it off momentarily so we could check OLGs.

The LSC feedforward is currently so bad that we should go from-scratch when we retune it instead of the iterative method.

We had a fast unknown lockloss while sitting in this state- no one was doing anything and we don't see an obvious cause.

We think we have properly SDFed and guardianized all changes from today.

My only worry: we were not able to raise the CHARD Y gain until we reached maximum power, but obviously we are having ADS stability issues since this gain is too low. Currently I have set the guardian to have what I think is the "correct" CHARD Y gain (300 once all loops are closed), but if it's too high, drop it back to 3.

Recommended to do list:

• check PRCL OLG
• Check PRCL/SRCL/MICH sensing at high power
• consider turning off some LSC notches, many seem unnecessary
• Run MICH/SRCL (PRCL?) LSC feedforward measurements, tune, etc
• determine if we want to run camera servos sooner during power up/locking process
• Check SRCL offset

M. Todd, E. Capote, C. Cahillane

We ran an OLG measurement for LSC-MICH1 loop, once we were in LOWNOISE_LENGTH_CONTROL.

At first we saw that the guardian had not turned off some strange notch filters we did not expect to see.

Craig spotted these as BounceRoll filters, which we turned off and reran the measurement.

Soon after the measurement was done, we lost lock so we are wondering if these notches were responsible or if we need to watch out in other LSC loops.

Now that we're at 60 W of input power, I double checked the ISS secondloop array pointing after the vent.
We're missing slightly, seemingly pitched off the ISS QPD.

The ndscope has Y1 dashed white lines at where the ISS PD values are now.
The ISS secondloop PD values from March 12 are the actual traces.

We're still locking, and so I leave ISS picoing undone for now.  
We'll have to leave the ISS secondloop open and pico back onto the array at some point. 

Based on the attached PSD, this could be responsible for our huge peak at 29 Hz in DARM. 

TITLE: 06/02 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

Much of today was work in ASC land with H1 locked most of the day at 10W (but started powering up at the end of the shift) and also had the arrival of even more members of the Syracuse LSC Team!  But there was also work on the Squeezer toward the end of the day.  The plan for tomorrow's Maintenance Day is to continue with Vent Recovery locking work.

Rahul addressed rung up violin modes from this morning and he requested the Oli (EVE operator) to apply these settings new settings (noted in alog 84720).

The day started out with the drama of a fire out beyond End-Y (Fire Dept phoned the Control Room notifying us that they were fighting a fire on SR240 (see attached photo from the roof of the Corner Station).
LOG:

• 1441-1510 Manual Initial Alignment (w/ only PRX Touch up)
  • ALS_YARM had 1 STALLED episode---->Due to MANUAL ALIGNMENT!!
  • ALIGN_IFO had 2-3 STALLED episodes while I was trying to get to "PRX_LOCKED" (but this was during DOWN and the IMC was not locking)---->Due to MANUAL ALIGNMENT!!
  • SRC ALIGN OFFLOADED ran fine and no SR2 tweaks needed!
• 1455-1512 Optics Lab clean (kim)
• 1456-1701 Forklifting and unloading of trailer outside of Hi-Bay--if too loud, send a text! (randy)
  • Could certainly see him start this work on SEI's ITMY 10-30 BLRMS (loudest on Z) on nuc28 and also on the 3-30Hz seismometer plots
• 1510 Locking: 
  • LOCK #1:  DRMI locked up in 10min;  LOCKLOSS at PREP ASC
  • LOCK #2:  Held at OFFLOAD DRMI ASC (while checking on fire and due to lockloss above, had PR GAIN glitches---I believe Sheila said it was SRC mode hops...tried touching up PRM/SRM to improve POP18, but then there was a lockloss).
  • LOCK #3:  This is when lots of commissioners started arriving.  Eventually made it to CHECK VIOLINS (and Rahul started damping because they were off the screen on nuc30!)
• 1520 Kim notified us of Fire on SR0-240 (beyond EY, see attached photo); ~2 acres on Mile Post 16 of 240
  • 1529 Fire Dept phoned Control Room with status call:  mentioned about 2acres had burned, was around Mile Post 16 of SR-240 and it was only at the fence line of the road (would notify us if it jumped the fence (it did not).
  • 1552 Smoke no longer noticeable via Corner Station roof cam
• 1530-1705 Violin Damping by Rahul (1705 Gave the go-ahead to Power Up)
• 1555-1622 Checking arms for tumbleweeds (chris.eric)
• 1600-1631 MX cleaning (kim)
• 1605-2211 Running pipe for Air Dryer for the Air Compressor under the mezzanine in the Mechanical Room (ken)
• 1830 Tuesday Coordination Mtg
• 1948-2018 Snorkel lift move from EX to MX (randy, eric)
• 1954 Replace GC Switch (nyath, jonathan)
• 2000-2025 TCS Chiller check/fill/FAMIS (corey)
• 2038-2255 fiber collimator laser work in optics lab (jeff)
• 2130 Tour for Wenatchee Valley College (maggie)
•  

Control Room (Corey, Sheila, Elenna, Oli, Georgia, Craig, Julia, Matt, Keita, Ryan S, Camilla

Notes of what's been done so far today, we've spent the majority of the day locked at POWER_10W, adjusting the ASC sensing matrix and gains:

• After Initial Alignment, DRMI tends to lock on it's own after ~2minutes.
• Take ISC_LOCK in DRMI_LOCKED_CHECK_ASC and touch up SRM and PRM to increase RF18 (and decrease RF90.
  • ndscopes needed: LSC > LOCKING > ! Locking scopes > "Scopes: Buildups (slow)"
• [optional, only do if needed] Can pause at CARM_5_PICOMETERS if loosing lok at PREP_ASC_FOR_FULL_IFO and  then touch up SRM and PRM to increase RF18 (and decrease RF90).
• Then can go all the way to PREP_ASC_FOR_FULL_IFO. Stop here and move any ASC signals that are not on zero to zero. Maybe to move optics or use the usesrapps/../asc/h1/scripts/move_arm_dev.py script e.g. 'python3 move_ARM_dev.py CH P 0.01' for CHARD P. At the same time, watch that the RF90 stays low and RF18 and circulating power stays high. 
  • ndscopes needed: LSC > LOCKING > ! Locking scopes > "Scopes: Buildups (slow)" and "Scopes: ASC signals"
  • If error signals are saturated, turn off the soft limiters via the ASC screen e.g. H1:ASC-INP1_P_SMOOTH_ENABLE.
  • For this lock, we:
    • Touched SRM to improve SRC2
    • Turned off limiters IMP1 PIT YAW and touched IM4 to improve IMP1.
    • Touched PRM to improve PRC2
    • Used move arm dev script for CHARD e.g. python3 move_ARM_dev.py CH P 0.01 (zoom in to check if they are away from zero)
• Take ISC_LOCK in CHECK_VIOLINS_BEFORE_POWERUP
  • Today we needed to wait here while Rahul damped IY mode 6 84720
  • Elenna noticed that the gain in CHARD was ~ 30dB less than she remembered.
• Went to POWER_10W
  • Checked HWS data here
  • Elenna ran dither sensing matrix checks to make the phaser plots and designed ASC input sensing matrix for INP and CHARD 84726:
    • CHARD P: -1 A_RF45 + 0.6 B_RF45
    • CHARD Y: -1 A_RF45 + 0.8 B_RF45
    • INP1 P: 1.5 A_RF45 + 1 B_RF45
    • INP1 Y: 2 A_RF45 + 1  B_RF45
    • Sheila put these in the guardian
  • Georgia and Julia added offsets into the ASC loops to check the sensing of them 84724.
  • Sheila checked Elenna's suggested matrix made sense with Georgia's phase change measurements.
  • During this time at 10W, the circulating power / LSC-REFL_A started oscillating at 0.02Hz, Craig remembered they found this yesterday (84702) was due to the ADS PIT 4 and 5 loops. We turned these off and oscillation stopped, plot attached. We expect they are just over-compensating for the CHARD gain being too low.
  • Keita, Craig and I slowly turned on the matrix one at a time; INP1 Y, P, CHARD Y, P. By turning off gain, putting new matrix in, for INP1 we then brought error signal to zero by stepping IM4 and slowly brought the gains back to nominal.
  • Matt and Keita then ran CHARD_P_olg_shaped_exc.xml. When Elenna ran this while we were at 2W in, the gain was -30dB, now it's at -15dB.
  • Sheila, Julia and I turned H1:ASC-CHARD_P_GAIN up from 20 to 80 (+12dB) while watching the ASC output and input signals stayed fine, and then Elenna and Keita reran the CHARD_P_olg, found it was close to 0dB, leaving gain here.
  • Elenna and Keita ran CHARD_Y_olg_shaped_exc.xml, it started at -20dB, they raised the H1:ASC-CHARD_Y_GAIN up from 3 to 10, 30, and 300 we started seeing that CHARDY and/or INP1Y were now unstable buzzing around 0.8Hz, took back to 3. Even with gain of 10 the buzzing came back.
  • We turned ADS PIT 4 and 5 loops back on, hoping that with the CHARD P gain increase it would be fine now. 

Julia, Georgia, Sheila, Camilla, Elenna

This might be out of date already as some ASC input matrices have already been updated.

On Sunday we had some locklosses as we powered up from a 0.02Hz oscillation. One known issue is we have taken out some gain out of our CHARD loops. We wanted to check our sensing (input) matrices CHARD, INP1 (which both use the refl wfs) and PRC2 (which uses new in vac pop_x).

We sat at 10W, with the input matrix Sheila found last week:

While Elenna measured the phasing using an 8 Hz line, Julia and I added offsets into the loops and looked at the responses in the different sensors.

• When we stepped INP1_P, we saw a differential response in REFL_A and REFL_B RF45 (first screenshot)
• When we stepped INP1_Y, we saw a small common response in REFL_A and REFL_B RF45 (second screenshot), and maybe a small response in RF9 (which is what was in loop)
• When we stepped CHARD_P, we saw a differential response in REFL_A and REFL_B RF45, same as INP1_P (third screenshot) and a small response in REFL_A and REFL_B RF9 in the Q quadrature (sad)
• When we stepped CHARD_Y, we saw a small differential response in REFL_A and REFL_B RF45 and perhaps also in RF9 (fourth screenshot)
• When we stepped PRC2_P, we saw a differential response in REFL_A and REFL_B RF45, RF9, and a step in POP_X (a bit weak?) (fifth screenshot)
• When we stepped PRC2_Y, saw saw a strong response in REFL_A and REFL_B RF9, and POP_X (fifth screenshot)

Some of this is a bit different to what Sheila saw last week, but our ifo alignment has changed. We want to find intrixes that are sensitive to each DOF and ideally are insensitive to the other DOFs.

• It seems like RF9 is not a good sensor of INP1
• For some reason our steps showed a similar repsonse in A and B RF45 to INP1 and CHARD in P, which was the opposite of what Elenna saw in her radar plots?
• POP_X is good at only sensing PRC2, but PRC2 yaw shows up in other sensors...

While writing this another input matrix for INP and CHARD has been put in - https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=84711 - and seems to be working so stay tuned.

We plan to work on our gain heirarchy and hopefully power up further soon!

This morning while Corey and the commissioning team were trying to lock and power up the interferometer, the violin modes were pretty rung up. For most of the modes, I was able to damp them down using nominal settings except three of them which are listed below along with the settings which seems to be working for now. 

• ITMx mode 3 - FM1+FM9+FM10 Gain = -20 (+60 deg phase)
• ETMY mode 1 - FM1+FM6+FM8+FM10 Gain= -0.1
• ITMY mode 05 and 06 - FM6+FM7+FM10 Gain = +0.01 (-30 deg phase)

TJ, Camilla, Checking as Sheila was concerned about this as Georgia/Craig need to move the ITMX SPOT GAIN "CENTER" 84702.

Attached are the HWS Live plots comparing when we get to 10W and 120s later for ITMX and ITMY now. And also for ITMX and ITMY at our last 10W power up before the vent (note that then we don't pause at 10W and continue increasing power during the 120s). 

Can see no obvious new point absorbers, ITMY looks perfect and ITMX has the same point absorbers as before, it;s possible there's a new point absorber on the right of the optics (orange arrow in attached) but it doesn't look scary. We will continue to check this but it's possible that our alignment has just changed (has since 66198) so that we can now see this point.

Changed the DARM_OFFSET ISC_LOCK state number to be in order, after ENGAGE_ASC_FOR_FULL_IFO