Camilla Nutsinee
We are leaving ADF line on for the night. If people don't like the line it can be turned off on the squeeze overview screen by toggling the ADF on/off button here. Changes related to this injection have been accepted in SDF.
E. Goetz, J. Kissel As Evan and I were continuing to debug the PCAL calibration lines processed for the first time against DELTAL_EXTERNAL as a live measure of the calibration's systematic error, we were distracted by the noise in the magnitude and phase of the "final answer." As such, I've converted all DEMOD_I and DEMOD_Q banks, which filter out the 1w and 2w components of the demodulated PCAL, DARM_ERR, and DELTAL_EXTERNAL signals at each calibration line frequency to have a 0.1 Hz low pass in FM1 and a 0.025 Hz low pass in FM2. The first attachment shows the reduction in noise as a I switch from "all banks using 0.1 Hz LPs" (on the left of the plot) and eventually "all banks using 0.025 Hz LPs." The second attachment shows that I've SDF accepted these values. The third attachment shows an example on of these demods (in this case the "LINE5" PCAL line demod).
Since there was 60 of these filter banks, and I want to make the swithc quickly, I "wrote" this "quick" unsophisticated command line to switch each the filters each "LINE" in one go. Posted here just in case we need switch back, or change to a different corner frequency low pass some time in the future.
export LINE=LINE8;z switch H1:CAL-CS_TDEP_PCAL_${LINE}_PCAL_DEMOD_I FM1 OFF; z switch H1:CAL-CS_TDEP_PCAL_${LINE}_PCAL_DEMOD_Q FM1 OFF; z switch H1:CAL-CS_TDEP_PCAL_${LINE}_PCAL_DEMOD_I FM2 ON; z switch H1:CAL-CS_TDEP_PCAL_${LINE}_PCAL_DEMOD_Q FM2 ON; z switch H1:CAL-CS_TDEP_PCAL_${LINE}_ERR_DEMOD_I FM1 OFF; z switch H1:CAL-CS_TDEP_PCAL_${LINE}_ERR_DEMOD_Q FM1 OFF; z switch H1:CAL-CS_TDEP_PCAL_${LINE}_ERR_DEMOD_I FM2 ON; z switch H1:CAL-CS_TDEP_PCAL_${LINE}_ERR_DEMOD_Q FM2 ON; z switch H1:CAL-CS_TDEP_PCAL_${LINE}_EXT_DEMOD_I FM1 OFF; z switch H1:CAL-CS_TDEP_PCAL_${LINE}_EXT_DEMOD_Q FM1 OFF; z switch H1:CAL-CS_TDEP_PCAL_${LINE}_EXT_DEMOD_I FM2 ON; z switch H1:CAL-CS_TDEP_PCAL_${LINE}_EXT_DEMOD_Q FM2 ON;
The Camera_servo guardian went to wait_for_cameras, but had an error because of a typo in self.failure vs. self.Failure (it cares about capitalization). I capitalized the incorrect version, selected a different state, and reloaded. Reminder that I had to jump to another state so that it would load and run through the main part of Wait_for_cameras to pick up that new variable name. Seems fine now.
I added fudge factors to squeezer BLRMS NULL gain so the monitors read 0dB when we are not squeezing. All of the changes have been accepted in SDF.
| BLRMS | 30mins after NLN (brown trace) | 3 hours after NLN (mint trace) | Comment | |||
| # | center freq | BLRMs calc | DARM calc | BLRMs calc | DARM calc | |
| 1 | 80Hz | n/a (new lines) | -0.9 | n/a | -0.4 | Check for lines |
| 2 | 135Hz | -1.2 | -1.4 | -0.8 | -1.4 | A bit off |
| 3 | 325Hz | -1.5 | -1.9 | -1.8 | -2.3 | Underestimated |
| 4 | 750Hz | -2.4 | -2.5 | -3.0 | -3.1 | Great |
| 5 | 1700Hz | -2.2 | -2.1 | -3.2 | -3.0 | Great |
| 6 | 4650Hz | 0 | 0 | -1.8 | -1.8 | Great |
Checking on the reliability of these BLRMs by comparing the BLRMs H1:SQZ-DCPD_RATIO_{1-6}_DB_MON with DARM SQZ vs No SQZ. Above 750Hz, BLRMS#4,5,6 exactly agree with whats seen in DARM.
#1 80Hz BLRM isn't making sense, maybe we're not taking into account the PCALX 77.7Hz line (alog68289). #3 325Hz seems like the scaling is underestimating SQZ in the BLRMS and something is off with #2 135Hz but this is a region we've ben seeing varying noise.
I have accepted in the LSC Observe.snap the new PRCL FF that Gabriele tuned this morning (first screenshot).
I have unmonitored in the LSC Observe.snap the PRCL1 gain, since the THERMALIZE guardian needs to change it over the first several hours of the lock. Second screenshot)
I have unmonitored the ASC Observe.snap camera offsets, since guardian needs to set those to a different value each lock. Third screenshot.
E. Goetz, J. Kissel
We found that the EXT DEMOD PCAL LINE1 narrow bandpass filter was incorrectly set for an old frequency of 33.7 Hz, resulting in an output that was nonsense at the DEMOD frequency of 17.1 Hz. This was changed to a bandpass filter of width 0.1 Hz (design string: butter("BandPass",6,17.05,17.15)). The other DEMOD bandpass filters were centered correctly, but they had a wider width. We also changed it so that all of the bandpass filters use the narrower bandwidth using the same design string.
TITLE: 04/27 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
SHIFT SUMMARY:
LOG:
Current IFO Status : NOMINAL_LOW_NOISE, it's been locked for35 minutes
Y End Wind fence Work, historicaly, has been particularly noisy for ground motio. So Jim asked me to put the "Bad_stuff" filter back on.
Bad Stuff filter : H1:ISI-ETMY_ST1_SENSCOR_Y_NORM_FILT4_SW1R and pause the Gaurdian: H1:GRD-ISI_ETMY_ST1_SC
BIG RED was moved with out incident and was finished at 15:18
LOCKLOSSES:
Lockloss From NLN_CAL_MEAS from a strange Earthquake type even that was local but didn't register on Seismic.
SEI_CONF went to Earthquake mode after we lost lock. -Ground motion
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1366657197
Lockloss from FIND_IR -unknown
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1366660421
Lockloss from Find IR -unknown
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1366661697
Lockloss check_IR - see Tj's alog 69103
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1366662777
Lockloss from ENGAGE_ASC -beam splitter alignment
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1366663316
Lockloss ENGAGE_DRMI_ASC - poo beam splitter alignment again
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1366663930
ICS_LOCK reloaded after Gabriele's changes.
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 19:56 | LVEA | LAZSER HAZARD | LVEA | YES | THE LVEA IS LASER HAZARD | 03:56 |
| 15:05 | FAC | Tyler | Water Tank | N | Moving BIG RED the forklift to LSB | 15:17 |
| 15:14 | SEI | Mitchel, Randy, Jim | Wind -Y | N | Wind fence repair | 17:30 |
| 15:23 | Commish | Gabriele | Ctrl Rm | N | Injections for measurements | 16:30 |
| 15:42 | EE | Fil | SQZ Bay | Yes | Termination of cables | 16:42 |
| 16:04 | SEI | Jim | Corner station | N | Moving a Chevy Bolt | 16:34 |
| 16:49 | Commish | Elena & Gabriele | Ctrl Rm | N | 10 minutes of \ | 17:28 |
| 16:50 | FAC | Cindy | H2 | N | Vacuuming & technical cleaning | 17:23 |
| 17:12 | VAC | Gerardo | MX | N | Vacuum pump Work | 19:00 |
| 17:13 | COMMISH | Elena | Ctrl Rm | N | Dhard measurements | 17:30 |
| 17:46 | FAC | Kim & Cindy | FCES | N | Technical cleaning | 18:34 |
| 17:47 | Commish | Elena | Ctrl Rm | N | DHARD MeasHAM1 FeedFWD | 17:49 |
| 17:52 | ASC | Elena | Ctrl Rm | N | ASC OpenLoop Gain Meas | 18:17 |
| 17:59 | EE | Marc & Fernando | End Y, End X | N | Checking on racked Power supplies | 18:55 |
| 18:23 | OPS | Ryan S | Ctrl RM | N | Mag Injections | 18:33 |
| 18:49 | Commish | Gabriele | Ctrl Rm | N | PRCL Noise INJ to Retune Feed FWD | 19:49 |
| 20:22 | CDS | Jonathan & Fil | MX | N | Booting PEM MX | 21:31 |
| 20:30 | VAC | Travis & gerardo | End Y , Mx | N | Vacuum pump checks | 21:50 |
| 21:04 | EE | Marc | CER | N | Making measurments | 22:05 |
| 21:19 | SEI | Jim | Wind-Y | N | Wind fence work and Time travel. | 23:19 |
| 22:35 | PEM | Ryan S | Ctrl Rm | N | PEM Mag Injections | 22:45 |
TITLE: 04/27 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 12mph Gusts, 9mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY:'
- IFO locked at NLN for 0:38 minutes and injections are currently ongoing
- All DMs/CDS/Alert handler ok
- LVEA is still LASER HAZARD
Elenna, Gabriele
We noticed coherence between DARM and INP1_P and INP1_Y. So we redesigned the loops to have a much larger roll-off at 10 Hz and above, for both P and Y
Elenna, Gabriele
Same treatment for PRC2 PIT adn PRC2 YAW, sicne those showed coherence too. Attached plots compare the old and new controllers.
We have adjusted the new filters for PRC2 and INP1 to be used by the guardian from Engage ASC for Full IFO onward. We are using probably a factor 10 less gain for INP1 P now than normal for powering up. This may be a problem, so please keep an eye on ASC stability during power up. Normally we would have the factor 10 gain for INP1 all the way through Max Power, and then the gain would be lowered in Lownoise ASC.
I have accepted these new filters in the observe SDF.
Looks like some low frequency improvement from this change!
Comparison of ASC control signals with the old (RED) and new (BLUE) controllers. CHARD controllers are the same, but the noise improved probably due to the reduction in the other loops' noise
I think we don't see an improvement in INP1_P because we are hitting the numerical limit of the PSD computation
We have successfully powered up with these new loops.
Filiberto and Jonathan We setup a link to the h1pemmx ipmi port today. Fil ran a fiber (fiber #5) from the patch panel in EX to the sw-ex-h1fe switch. We linked that in to interface 1/3/3. The other end was in mid-x, we added a media converter convert from fiber to ethernet. We booted h1pemmx and reset its ipmi address. Now both MX and MY computers are reachable by ipmi (provides remote power, console, ...). Again we used a bi-directional optic so that we only needed one fiber strand.
Mid day Update!
Big Red was moved with out breaking lock!
IFO Status : Re-locking after a localized spike in ground motion caused a lockloss.
Issues relocking.... Lockloss at FIND_IR, Seesm like a very similar issue to last nights locking issues.
We are trying to resolve the issue, and relocking will commence.
The lock loss Tony mentions here seems to have been caused by some seismic event that was seen at all 3 VEAs. This is visible on the linked lock loss page, but I'm also including some trends. This burst was about 30s in length, and seemed mostly at higher fruquencies than we typically see in earthquakes. Time for the event was 18:59 utc.
On attached trends, left two plots are peakmon, which doesn't show much until after the lockloss seen by IMC-F. Whatever this was, it was big enough to get the SEI system to switch to earhquake mode (went over 1k nm/s on peakmon), but mostly after all the commotion. Middle two plots are the ITMY ground sensors and the X&Y sensor correction signals for the corner station ISI. RIght two plots are the end station ground signals and their beamline sensor corrections signals. These all show that the motion was seen and reacted to by all of the ISI. Signal seems to have similar impact at each building.
Second attached image are asds for the ITM and ETM STS. The live red, blue, light green are the ITM asds 10 minutes before, the rest of the unicorn vomit are the ETM ITM ground during the event. All of the extra motion is between .5 and 5 hz, and looks like generall same magnitude at all stations.
Still not sure what happened, maybe a very small local earthquake? There was no fence work going on at EY. I don't think construction on 240 would impact the whole site this way.
Daniel, Naoki, Nutsinee
A following up of LHOalog68991 we injected frequency dependent squeezing with high CLF into DARM and looked at the coherence between our sqz laser intensity noise and DARM. In the end we increased CLF power by a factor of 8 and made DARM noise around 1.3kHz worse by 10.8%. Multiplying our previous CLF intensity noise projection of 3.7e-21m/sqrt(Hz) by sqrt(8) then add to our DARM noise floor at nominal CLF power of 2.95e-20 m/sqrt(Hz) in quadrature you get
sqrt((2.95e-20)^2+(10.46e-21)^2) = 3.13e-20 m/sqrt(Hz)
that is off from what we observed, 3.27e-20 m/sqrt(Hz), by 4.5%. It's not too crazy. Daniel's theory was intensity noise tumbles in phase but the ADF peak doesn't. If we tumble the phase of the ADF peak and project our noise floor from the mean value instead we might be closer. Something we intend to do during the next lock.
A coherence measurement between DARM and SQZ intensity noise demodulated at 3.125 MHz doesn't show much coherence but it's not nothing. The coherence is small but it does go up with CLF power. We are not sure what this means but the measurement could be an indication that our high CLF power could be intensity noise related.
The ADF phase dependecy turned out to be a bust.
One effect we were not able to include into our projection is the RF intensity noise on the green pump.
To get a calibration factor for Anamaria in order to run coincident magnetic injections at both sites in the future, I drove the CS vertex coil with a gain of 600,000 between 18:28 and 18:33 UTC. Response in DARM and my injection settings are attached.
Looking back on this injection duration, I was unintentionally saturating the vertex magnetometers (oops). Since we want these to remain functional, I reran the injection with a (much) lower gain of 65,000 and saw a lower response in DARM, but enough for this to work for an initial calibration.
Coupling function html report for this time can be found here: https://ldas-jobs.ligo.caltech.edu/~adrian.helmling-cornell/mag_inj_test/injection_1366848018_1366671318/
I think there was an IFO configuration change which is why DARM differs at 300 and 800 Hz. Because the floor sensor is out, it's hard to see the 10-40 Hz broadband injection in other EX sensors (attached example), but maybe it's visible in DARM. Fil and I will swap the EX floor box tomorrow - hopefully it starts working then.
When the gain of the ISS second loop was changed, the input offset was not adjusted. This results in the output of the 2nd loop ISS to saturate after a lock loss, until the offset slowly gets compensated by the offset loop. But, this now typically takes like 5 minutes. I adjusted the offset (H1:PSL-ISS_THIRDLOOP_OUTPUT_OFFSET) from 587.3 to 1272. We will have to check after the next lock loss that this actually works.
Just had a lock loss. Looks a lot better now.
I disabled the diffraction servo by setting H1:PSL-ISS_SECONDLOOP_REFERENCE_IN_MTRX_1_4 to 0 (from 10). This should stabilize the power after the IMC, rather than keep the pwer at the PSL AOM constant. The downside is that we may run out of range of the AOM, since we only work at 2% diffraction power.
Tagging PSL.
The diffraction servo value that Daniel has made 0 from 10 had been hard-coded into the DOWN state of the IMC_LOCK guardian, so was getting overwritten.
RyanS and I just set the value in the guardian to zero, loaded, and checked it in to the svn.
First hour trend during a lock with the diffraction compensation off: The powers are no longer drifting a significant amount after the mode cleaner.
WP 11121
End Station microphones at both End Stations have been upgraded.
Plan is to start upgrade of microphones in Corner Station next week.