I checked to make sure the line and the BP matches. Changing the phase both on the main PI medm screen and on the damping filter doesn't make a different. The PLL green light is on but Shelia mentioned that PLL is not actually locked and I don't know how to make it locked (some other modes with PLL green light indicator also have red PLL lock status). I also tried to zero the gain as Sheila suggested.
TITLE: 11/02 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Nominal Low Noise/Commission
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT: Wind: 16mph Gusts, 13mph 5min avg Primary useism: 0.03 μm/s Secondary useism: 0.29 μm/s
QUICK SUMMARY: Before Stefan left he asked me to make some TF measurement. So I'm going to spend some time doing that before setting the intent bit. Locking went smoothly.
After today's changes to the PMC servo, which included increasing the loop gain, we noticed a familiar bump around 4.2kHz in DARM. Lowering the PMC gain from 16dB to 0dB made the bump smaller in DARM (see images). Given the coherence with REFL9, it seems that this is coupling through frequency noise.
We also made a small exploration around the already good PMC input beam alignment. This didn't have much impact, but it revealed that small changes in the alignment can change the input offset to the PMC servo. That is, the offset which maximizes the PMC throughput can be changed with small alignment tweaks. Using this effect, we made a 0mV input close to optimal (see second image).
Tagging PSL and ISC.
J. Kissel In order to improve the uncertainty on the parameters the lines are measuring, I've adjusted the line heights of a good fraction of the calibration lines. I'll leave them in like this overnight, and see if we get the expected improvement in the uncertainty (especially as reported by the front-end). Line Freq Former New PCALY 36.7 750 500 331.9 2900 5000 7.9 20000 5000 ETMY UIM 33.7 60 180 ETMY PUM 34.7 27 81 Note the reduction of the 7.9 and 36.7 Hz modes. We don't always increase line heights ;-).
23:03 Fil out of LVEA WP6292
23:05 Dick G into CER
23:15 Dick back
23:34 Robert and Ansel out to EY, then EX
Since the cdsutil avg function kept failing, we replaced it by the average of 20 ezcareads - 0.2sec apart.
This was done in a separate state - PREP_TR_QPD_SUM_OFFSET.
Admittedly not the most aestetic fix, but it seems to work reliably.
Notes:
0) A2L gains of order two are getting suspicious, because it essentially means some coils are shut off.
1) ITMY_Y2L was always large (~-2) , but since 10/29 7UTC it is even bigger.
2) ITMX_Y2L also got big (~2) on 10/29 7UTC
Not sure what to make of this...
Tagging SUS.We should check functionality of coils.EDIT: Checked the functionality of the coils by taking a quick transfer function between COILOUT_EXC channels (OSEM basis excitation channels closest to the DAC output), and the various coil driver monitor channels. Though I've not taken the time to calibrate or understand the signals, I see no differences between the quadrants, and plenty of coherence between all drives and responses. I don't think there's anything wrong with the ITM L2 actuators. Note to self -- next time include OSEM sensors and optical levers in your template for those who don't trust the functionality of the coil driver monitor channels. The templates (attached) live here: /ligo/home/jeffrey.kissel/2016-11-02/ (apologies for my laziness -- I figured it would be faster to just create new templates than to find the one's Ed used to characterize the monitor signals that are likely committed to the SusSVN. #slapsownwrist) Also note that - The IFO was DOWN during this measurement. - I turned off the PIT optical lever damping during the measurement so as to not confuse anything.
PSL101 Yellow alarm at 6:59UTC 300NM
I added a PRM_SPOT_MOVE state similar to the PR2_SPOT_MOVE and PR3_SPOT_MOVE states (see alog <a href="https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=30754">30754</a>)
It allows moving IM3 to adjust only the PRM spot position.
To use it, just like with the other two scripts, turn off the PRC1 ASC loops.
The only issue with this state is that IM3 is very close to saturation already, so there is not much room.
J. Kissel, M. Evans Matt over heard me talking to Yuki about PCAL actuation and asked the time-honored question of whether the current "large" calibration lines were causing any non-linear impact in the DARM sensitivity. I've not proved this suspicion wrong in a few months, and not after starting the huge 7.9 Hz SRC detuning tracker line, so I figured I'd oblige. As such, I've turned off the PCALY lines during this lock stretch at 05:51:42 UTC, and restored them at 06:11:00 UTC. (Note, for those who are looking behind me, we were running A2L for the majority of the time between reaching nominal low noise and starting this test. Commissioning also broke the lock just after the test.) The current line amplitudes do not adversely affect the DARM sensitivity in any other way than expected. Also for the record BNS range was identical between ON vs OFF as well.
Since we didn't have the interferometer today, I stiched together some previous measuremnts of frequency noise and transfer function. In particular:
alog 30610: Out-of-loop frequency noise sensors (POP9, REFL45, POP45): Caveat: The alog only accurately calibrated them at high frequency - I suspect the sensor disagreement at low frequency is a deviation form the simple scalar calibration.
alog 29893: Transfer function in m/W (the template also has m/ct). Caveat 1: This was measured at 50W - need it at 25W, Caveat 2: The transfer function is known to vary, see alog 30440.
That said, I can ignore all the caveats for now (until we redo the measurments at 25W) and use the three out-of-loop frequency noise sensors to predict the DARM contribution. Specifically, I cast POP9, REFL45 and POP45 into REFL9 counts using alog 30610, and then apply the transfer function from aLog 29893. I woudn't trust the result better to about a factor of 3 - mostly because we don't have an accurate frequency noise calibration of those sensors at low frequencies. But the result is in the attached plot.
Clearly, this needs to be redone with more precision. But if this theory holds up, then what we are seeing is REFL9 sensing noise (due to scatter or donut jitter or something else), being imprinted on frequency noise, coupling to DARM.
Over the weekend I wanted to try modulating PR2 in yaw, pitch, and length, as well as CPs, etc. to see the effect on shaking-enhanced scattering peaks. I haven’t got a chance to do more than the first of these yet but the attached plot shows that the peak in DARM did modulate with a slow yaw injection at PR2, while nearby parts of the spectrum did not. The plot suggests a better parking place, but the stationarity of the optimal yaw needs studying.
For both PMC locking and injection locking, servo board and field box board were modified as per FRS 6500 (FRS id=6500 and alog 31047).
After the modified boards went in, we removed the 20dB attenuator on the PSL rack RF patch panel for 35.5MHz for PSL EOM.
This seems bump up the ILS and PMC length locking optical gain by about a factor of 10 (for ILS the analog gain was changed to compensate).
We also remeasured the demod phase for ILS and PMC length locking. For ILS we didn't see much change (1ns), but PMC was significant, we ended up changing 3ns, i.e. 39 degrees for 35.5MHz.
Demod setting are shown in the first two pictures, ILS (first attachment) and PMC (second). Third picture shows that the ILS is on the left bottom of the four delay lines, and PMC is on the right bottom.
The fourth picture shows the OLTF of PMC that is pretty close to the one we have now. Note that UGF is much much higher than before simply because of the optical gain and the demod phase (might have to change).
Unfortunately the floppy for SR785 failed, so we'll remeasure the ILS loop gain again tomorrow.
Here are the spectra of HVMons and Mixer_out, both in counts at the input and in calibrated in Volts.
J. Kissel, for M. Evans, D. Sigg, K. Kawabe With these electronics changes comes new compensation filters scattered throughout the PMC model, which has resulted in SDF differences. The following filter banks now have new filters that have been accepted into the SDF system as ON: H1:PSL-PMC_INOFFSET_CALI FM3 "LP1" zpk([],[1],1,"n") H1:PSL-PMC_MIXER FM2 "aWhite" gain(-0.005) H1:PSL-ILS_MIXER FM2 "aWhite" gain(-0.005) H1:PSL-ILS_HV_MON FM10 "aWhite" zpk([100],[1],-1,"n")
Robert called from EY to info me that he was going into the VEA area near the BRS
I get a notification that Not all nodes arrived. Sheila had a look at the configuration and it seems that the BRS IS turned off and things look ok.
I switched to VERY_WINDY_NOBRSXY. There are two people out at end stations and both end station lights are on. No answer on the phone.
WP6288 Dave, Jim:
We cleanly power cycled h1iscex and its IO Chassis this morning between 11:45 and 12:06 PDT. We were not able to reproduce the slight offset on an ADC channel (see attached). Note this channel is actually only seeing ADC bit-noise, so the offset is in the micro-volt level.
Sheila,.Jeff, Ed
This was an attempt to fix the drop in green arm power that happened last sunday. 30884
Since it didn't work, operators will continue to see that green power from the X arm is low.
If this can't be fixed, we can just rescale the normalization.
Then I found that until Maintenance morning (1 Nov 18:26 UTC to be precise) this mode has been using OMC DCPD as its input signal. It was magically switched to be using TRY QPD. I put the gain back to where it was in the matrices. We'll see how it goes.
Okay doing that somehow kill the input signal alltogether. I let through the signal from TRY QPD again but zero the damping gain.
Nevermind. Reverted it. Things became bad real fast as soon as I let through signal from TRY QPD for Mode27.
And PI broke the lock. This is the 4th lockloss caused by PI tonight.
And 5th time. The time constant is about the same as previous locklosses so I guess switching input from TRY QPD to OMC DCPD doesn't matter. In fact I couldn't get any signal from OMC DCPD so that's even worse since I have zero chance of damping it. I'm going to try the original setting again but this time alter the gain (which I have also tried).
And 6th time.