FRS7394
Hugh, Dave:
We replaced the last calls to perl scripts (wd_dackill_reset.pl) with direct PV access. I think we have now completely decommissioned perl scripts from IFO operations.
I looked at a couple times when power into the IMC was increased, and the power change shows up on sensors, specifically IO GigE 2 (IMC_IN), IMC-WFS_A_DC_PIT, and IM4_TRANS_YAW. The IMC mirror alignment and PZT also respond. Plots attached are 1) power to 10W, 2) power to 27W, both with sensors, and 3) power to 27W showing IMC mirror alignment.
Inspected the foam sealant around the 7 cable ports (two between the Enclosure and the Anti-room, and five between the laser room and the LVEA) in the PSL laser room. A couple of the ports had almost no foam sealant installed, and in a few other ports the foam sealant had fallen out. Installed, replaced, and renewed the foam sealant around all 7 cable ports in the PSL enclosure. The laser room is now much better sealed. This should increase positive pressure inside the laser room by a small amount.
WP 7784 I have updated the PLC code for the remote control of the motorized fiber polarization controller to help deal with the fact that it does not save the position of the paddles between power cycles if those positions are set through the remote interface. There is now a 'Restore' button next to the power buttons on the medm screen. This will set the positions of each of the paddles to their last read position. The intention is for this button to be clicked after the power is turned back on to move the positions of the paddles to what they were before the power was turned off.
seed/pump Co-resonance temperature set to 41 C. Double checked with seed transmission scan using the homodyne. The manual flipper weren't flipped up before LVEA went laser safe so we have no camera to look at the transmitted seed beam.
Pump laser has to be taken off PSL due to an on-going work that would trip off the laser locking constantly. Cranked up OPO common path gain to 0 to tighten the loop a bit. This left us with 13 deg phase margin. So much for that idea. High peak around UGF. Back to -18dB as usual.
I also went out and unplugged the fast PZT output from TTFSS as it produces 232 Hz harmonics when TTFSS is not locked so the PZT doesn't get overdriven. Forgot to post an alog about this investigation.
Seed fluctuates a lot. At least 40% fluctuation or so.
The skies look clearer and the smoke haze, with the help from some nice winds, has been somewhat reduced. The current map (www.airnow.gov) shows our air quality in the moderate category. There are large areas of unhealthy air to our west and north. Wind direction over the next couple of days will influence our local air quality. If you are concerned about the air quality; or are feeling the effects of the current conditions, please consult your physician or contact site safety.
08:00 Particle Counts
| Location | 0.3um | 0.5um |
|---|---|---|
| Staging building | 7.6M | 1.5M |
| Outside the OSB | 7.4M | 1.5M |
| OSB Office Area | 2.5M | 230k |
| In the Control Room | 17.2k | 2k |
The LVEA has transitioned to LASER SAFE.
This is to facilitate vacuum work
The TCSX CO2 laser has been switched off. The TCSY CO2 laser is to remain off during this period.
This transition is under work permit 7785.
Hang, Sheila, Stefan We closed some more WFS loops: A) MICH_P/MICH_Y loop: - We phased and compared the AS_A_36 against the 72 signals. Since the AS_A_36 had a cleaner error signal, we decided to use AS_A_36_Q for the BS for now. That loop is now engaged at the beginning of the CARM reduction sequence, and never turned off. - Also, so far we drive DHARD to ETMs only. We will have to enable the ITM feed-back as well. - We also turned on INP1 (gain -1) and PRC2 (gain 500). PRC2 slightly draws down the recycling gain at the moment, but closes just fine. - Next we closed CHARD with low gain (engaged at 0.03, then increased to 0.3). But when we tried the +46dB we got a gain oscillation in pitch. SO for now we stay at low gain in CHARD. - We tried to put all of that in Guardian (REFL_POP_WFS), but the PRC2 and CHARD engagement gave us some problems. So for now Guardian doesn't engage PRC2/CHARD.
We have seen one of our bounce modes, which we hadn't seen until today since the installation of the bounce mode dampers.
The mode we see is at 9.726Hz, and seems to be ITMX.
Jim W suggested that ITMX might be the problem since the suspension was left damped overnight while the ISI was isolated, which we know causes problems. I tried the same phase as the O2 damping: -90 degrees, gain of 1
This bounce mode appeared again tonight, and is ringing down without any active damping.
Originally from alog 30737: ezcareadpast: ============= From the shell command line: ezcareadpast.py H1:ASC-PRC1_Y_GAIN 1161131166 Or in pyhton: import ezcareadpast as e value=e.ezcareadpast('H1:ASC-PRC1_Y_GAIN',1161131166) wfsreliefpast: ============== Set all optic to the alignment they had at the specified GPS time - uses both alignment and top stage output: wfsreliefpast.py 116114000 Both scripts are available in /opt/rtcds/userapps/release/asc/h1/scripts/, as well as in /opt/rtcds/userapps/release/isc/h1/scripts/. They are also made available globally through a soft link in /ligo/cds/userscripts.
I took the TF of the OPO TEC Loop, with the plot attached below.
The blue curve is the original loop, with UGF @30mHz, and a phase margin of ~44deg.
I increased the gain by a factor of 1.9, making the Gain = 1.33 in the LOOP SHAPE manual in MEDM. (Other filters unchanged)
Now we have a UGF@50mHz, and a phase margin of 50deg. This should make the loop more stable and faster. (Red curve.)
For the SHG, the loop looks good enough with UGF @25mHz, and phase margin ~50deg.
Notes on how to take the loop TF:
OPO/SHG TEC servo screen --> little screen under Excitation
Set the frequency and amplitude (10E-3V worked well) --> Switch on --> Click reset
You will need to integrate for a good while until the number stops fluctuating.
If you change the frequency or amplitude, you need to hit reset.
We should make sure these excitations are off after taking the measurements.
Peter, Fil, Jason, TJ, TVo
We started the day thinking the laser head could be the issue, but once we swapped the cables and plumbing to a brand new laser, it didn't solve our problem of not being able to lase. Peter found that if he wiggled and loosened an RF cable that goes from the Sine-to-Square wave comparator box to the 4-way splitter box, then we start to actually lase intermittently. This confused us for a while and we decided to inject our own square wave with a function generator and bypass the comparator box, with 0-5V peak to peak @ 40.68 MHz and it started lasing at 55 Watts. Then we added the comparator box and it still worked using our own source.
This lead us further upstream towards the RF distribution box D1000124 and found that there was a bad cable. The comparator box is expecting at least 4-5 volts peak to peak but was only getting approximately 40mV. This fooled us because it looked like a decently shaped RF signal and we thought it was OK, but the power was all wrong. Once we replaced the cable, it worked pretty well.
Tomorrow we'll replace the plumbing and cabling to make sure the old laser and old RF driver still works and return the spare laser and RF driver to storage, so we're not fully out of the woodwork but I think we found a big missing puzzle piece and we have at least one laser that works. Not sure why this cable went bad all of a sudden.
It's been pretty windy all afternoon, but the last hour or two it's a teeny bit more windy than it had been, and we've struggled to hold ALS lock (green arms are okay, but locking to the PSL is not okay). So, I changed the ISI Config guardian to MORE_WINDY at about 18:05 Pacific (01:05 UTC).
At the same time, I did an initial alignment (just in case). Between these 2 changes, and the wind is a teeny bit better again, we're holding lock a little better.
The wind speed has started dropping, so I have reverted the ISI config to its nominal state of WINDY at about 18:48 Pacific, 01:48 UTC.
Edgard B.
Following up on LHO:43512 and LHO:43513, I continued gathering transfer functions for designing QUADs the full Length-Pitch ISIFF filter.
I took almost all of the transfer functions needed for the ISIFF in every single QUAD.The only pair missing are M0 drive P in ETMY and ITMY.
_________________________________________________________________________________________
All of the templates+measurements are saved with date of Aug 19 in:
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/[]/Common/Data/ 2018-08-19_H1SUS[]_M0_ISIFF_FilterDesign_ST2L_M0_TF.xml 2018-08-19_H1SUS[]_M0_ISIFF_FilterDesign_ST2L_M0_TF.xml
Where [] is either ITMY, ETMY, ITMX or ETMX.
I calculated the FF filters for ETMX and ITMX using the measurements and the attached code.
The filters are shown in the second attachment, and there are a couple of things to note, broken down per QUAD here:
ETMX:
- Determining the L to L filter is easy (attachment 2, page 1). L2L = 2730 N/m = 2.12 [cts/nm]. This is about what I expected for this filter, as I made a pure DC measurement for it earlier in the week (shown in the 1st attachment) and obtained 2.16 [cts/nm].
- The L2P filter is to be determined by choosing a suitable lever arm factor l_eff=L2P/L2L. This factor is shown in page 3 of the pdf, note that the phase of l_eff is ~60 degrees. After checking the source for such an strange behavior, it turns out it is an artifact of having a really low l_eff, which makes it almost impossible to determine it properly. In conclusion:
+ From the DC Measurement I estimated l_eff ~ 6.4 E-5 m.
+ If I take the real part of the value at 0.25 Hz in the second attachment, figure 3. l_eff ~ 8.5 E-5 m.
+ Since this values are so small (see, for example, ITMX below) , I think it might be better to set up the length filter and set L2P=0 and tune L2P manually from there if necessary.
ITMX:
- Attachment 2 , figure 4 shows the L2L filter, from there we I estimate a value of L2L = 2820 N/m = 2.19 [cts/nm].
- from the data on figure 6 we estimate l_eff=1 E-3 m. Note there are no problems with the phase of this one and it is at least one order of magnitude larger.
Summary: Previously we detected no contamination of ADC channels by fans or from magnetic fields from the on-board power supply, but saw drifting lines. After powering I/O and AA chassis with linear supplies, the drifting lines were much reduced. There are three remaining more subtle issues: 1) Coherence between blank ADC channels in a 0.94 Hz comb, produced by a flashing LED that indicates link state, 2) A 1.000 Hz comb in the duotone channel that is coherent with some blank ADC channels, 3) An occasional drifting line, that produces coherence between blank channels, suggesting a rouge oscillator in the AA or I/O chassis.
A previous log noted that the new I/O chassis has much lower contamination from fans and power supply magnetic fields than previously tested I/O chassis, but that there were drifting intermodulation peaks, possibly associated with the 24V power from a Sorenson switching power supply ( https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=42907 ).
During the DetChar f2f, we powered the I/O chassis with a linear supply and found that the drifting peak features were mostly gone. I have since been looking into more subtle features in the blank channels of the I/O chassis. Figure 1 shows that the blank channel spectra are smoother (no evidence of drifting peaks) and the coherence between channels is significantly less than it was before replacement of the 24V switching supply (compare Figure 1 to https://alog.ligo-wa.caltech.edu/aLOG/uploads/42907_20180715170051_Figure4-CoherenceBetweenEmptyADCChannels.pdf ). But Figure 1 also shows that there are features associated with LED flashes.
The odd harmonic series in the magnetometer signal of Figure 1 appears more strongly in the magnetometer signal when the magnetometer is near to flashing LEDs (link indicators) on the ADNACO-R1BP1B board (photos are also included in Figure 1). The coherence at LED frequencies between the magnetometer and the blank ADC channels reaches 0.1. The blank ADC channels are coherent with each other at the LED frequencies even when there is no magnetometer connected, so the signal on the blank channels isn’t cross talk, and is probably associated with the periodic load on the power supply.
Dave B. notes that if the system were working as expected, the link LEDs should not be flashing.
In addition to the near-1 Hz comb, there was also a 1.000 Hz comb. Figure 2 shows that a 1.000 Hz peak, appears strongly (1 count) in ADC channel 31 (the duotone channel), and less strongly in other ADC channels (coherence reaching 0.01). The LED flash peak is also apparent at 0.94 Hz in Figure 2, though all ADC channels are blank. Both peaks have an associated comb, odd harmonics for the LED peak and all harmonics for the 1 Hz peak.
The second page in Figure 2 shows that the duotone signals are at about 10^4 times the size of the 1 count peak at 1 Hz. The direct cross talk of the 960 and 961 Hz lines in, say, channel 15, visible in the power spectrum plot of the second page of Figure 2 at about 4e-2 counts, does not seem large enough to produce the 1 Hz comb in channel 15 through the same 1e-4-scale non-linear mechanism. It may be that the 1 Hz comb on other channels has a different source or mechanism. We might be able to modify the duotone, such as by avoiding the zero cross region, to further study this. Since search groups had problems with1.000 Hz and near-1.000 Hz combs in DARM during O2, I think it is important to understand/eliminate these peaks.
A final issue was that, although drifting peaks were reduced when the I/O and the AA chassis were placed on linear supplies, I found drifting peaks (Figure 3) in a couple of many spectra. I suppose that this peak could be associated with some rouge oscillator in the chassis.
Dave Barker, Sumeet Kulkarni, Philippe Nguyen, Robert Schofield
Rolf Bork noted in our meeting last week that we could work with the vendor to get modified firmware to ensure that LEDs do not blink during normal operation. These indicators are related to the PCIe bus speed of the host computer. We have found that changing the PCIe riser card from 3-slot to 4-slot on the original front-end hardware drops the PCIe bus speed from 5 GT/s to 2.5 GT/s. In switching to long-distance PCIe RFM, we remove the need for the 4-slot riser cards.
There was a misunderstanding, the on-board LEDs indeed should be flashing to indicate our ADC/DAC/BIO cards are PCIe-1 version cards with a reduced data transfer rate of 2.5GT/s.
Another reason to go for custom firmware on these boards. I confirmed this behavior with the two long-distance I/O chassis at LLO for PEM MID. The LEDs do blink on the slots with the Gen1 adapters (ADC, DIO)
J. Kissel
Using the lock stretch that Sheila called out in LHO aLOG 43263, I gathered data that shows the new violin mode forest after we've replaced ETMX, ETMY, and ITMX (with ITMY been exposed to air for ~9 months, which undoubtedly also changes the violin mode frequencies). Attached are comparisons of the Fundamental (~500 Hz), 1st Harmonic (~1000 Hz), and 2nd Harmonic (~1500 Hz) DARM ASDs from O2 (after the July 2017 EQ) and this most recent lock stretch.
I've begun to update the LHO violin mode table (Violin_Mode_Table_v2) in prep for identification of this new forest. I've used the in-air data from LHO aLOGs 40525, 42180, 38857.
So far, I can identify 29 of the fundamental 32 modes, with a 2 mHz resolution. They're tabulated below (and not yet in the table), since I've not yet associated them with a test mass (though some appear to be "obvious" given the large separation).
In hopes to identify the mode Sheila calls out as the worst, I've pushed a 503.085 Hz filter to all new test masses, on MODE 1. This way when we do get a decent lock stretch, we can identify the mass "passively" by turning on the filter with some small gain, to see on which test mass we get action. As before, we'll started by assuming the mode is controllable by driving in Pitch.
| Frequency | Potential Match w/ in-air |
| 501.553 | IY |
| 501.628 | IY |
| 501.692 | IY |
| 501.755 | IY |
| 502.784 | IX |
| 502.909 | IX |
| 503.085 | EY / IY |
| 503.198 | EY / IY |
| 503.676 | EY / IY |
| 503.733 | EY / IY |
| 504.143 | EY / IY |
| 504.176 | EY / IY |
| 504.606 | EY / IY |
| 504.719 | EY / IY |
| 504.850 | EY |
| 504.889 | EY |
| 504.942 | |
| 505.077 | |
| 505.186 | |
| 507.360 | EX |
| 507.493 | EX |
| 508.844 | EX |
| 508.938 | EX |
| 510.714 | EX |
| 510.723 | EX |
| 511.180 | |
| 513.405 | |
| 516.678 | EX |
| 516.778 | EX |
In order to gather this data, I just used the standard violin mode templates from O2 (see LHO aLOG 37921), which are linked off of the VIOLIN MODE monitor MEDM screen.
Remember, we tried to separate the mode frequencies between test masses, and cluster a given test mass, to make them more easily identifiable (see E1700342, G1701332), but the reality of implementing such a system didn't work out as planned (an already minimal supply of fibers, few sets of fiber breakages, changes in frequency after welding and annealing, etc.). See some details in LHO aLOGs 41216, 40292, and 38965, but most my memory of the failure of the plan is verbal from telecons -- perhaps others can retrace the steps.
I have started adding some violin mode bandpass filters for ETMX, but have not had a change to test them out yet.
I added bandpass, +60, -60 degree phase shifts for 508.36 Hz, 508.844 Hz, 510.714 Hz and 516.678 Hz, in the filter banks under Mode2, Mode 11, Mode 12, and Mode 13 respectively.
The 503.085 Hz mode is on ITMY, and has been damped with the MODE1 filter, with -70 gain, no extra phase ( this can definitely be tuned in the future though), and feedback to pitch.
Note: This comment should have appeared after Georgia's comment below.
The link to the wiki page above isn't working. Here is a link : Violin mode table v2
504.891 Hz is on ITMX, can be damped with a gain of -3 and a phase of -60 degrees. (FM1 in ITMX mode 1 is a 50 mHz wide filter centered at 504.891, this is narrower than our other filters because there is a nearby mode at 504.953 Hz.)
Unfortunately it looks like we have two modes on ITMY that are only separated by 4 mHz. I was able to damp a mode at 501.629 Hz on ITMY with the same MODE4 filter Georgia used to damp the mode at 501.625Hz, but with a negative gain and +60 degrees of phase. I was suspicious that these could be the same mode, so I compared a spectrum with a resolution of 2 mHz from 2:42 UTC today (before Georgia damped ITMY) with the lock at 5:09 UTC, and it looks like they are actually two modes separated by about 4mHz. (Screenshot)
To deal with this, I created a filter called doublet in MODE4 which has 0dB of gain and a phase of -31 degrees at 501.624 and -3dB with -147 degrees at 501.628 Hz. A brave soul might be able to engage this filter with the bandpass that Georgia made earlier and no additional phase shift to damp both modes at once.
Edit: I got to try the doublet filter but it isn't very effective at damping the higher frequency mode which is rung up at the moment.
I also tried to damp 501.755Hz, but I don't think this is on ITMY. I copied my filter to ETMX MODE3, and tried 2 phases of pitch, but we lost lock before I could try yaw or longitudinal for ETMX.
I added a few more violin mode damping filters for ITMY. I promise I'll update the wiki table with this information soon.
The 503.198 Hz mode (MODE5) is on ITMY YAW, and was damped easily with -10 gain (haven't optimised any of the phases yet).
I tried to tackle the ITMY forest around 501.6 Hz but had trouble with cross coupling, accidentally ringing up neighbouring modes. I narrowed the filters and had some success damping
- The 501.625 Hz mode in pitch with a gain of 15 (filter bank MODE4)
- The 501.555 Hz mode in yaw with a gain of 20 (filter bank MODE6)
- The 501.692 Hz mode had some success with a gain of -5, before we dropped lock for other reasons. Will come back to it (filter bank MODE7).
J. Kissel
We don't yet have enough long lock stretches to get more precise than 0.005 mHz resolution, but I attach a few 1 mHz BW ASDs in the recent lock stretches that Sheila mentions (and some that I've found / reported),
- 2018-08-21 07:25 - 07:54 UTC,
- 2018-08-21 02:43 - 03:11 UTC,
- 2018-08-20 21:50 - 22:25 UTC,
- 2018-08-15 19:19 - 20:48 UTC,
where, because the last from several days ago, was 1.5 hrs, I was able to get a 0.5 mHz BW ASDs.
The message -- I can concur with Sheila's assessment that these two modes at 501.625 and 501.629 are 4 mHz apart -- however, only in 1 of the 4 measurements is the lower, 501.625 mode rung up. Thus, I think (thus far, we're not yet on DC readout) this is a weakly coupled mode that was rung up by our damping exploration attempts, so if we can design a filter that only tackles 501.629, then we might be OK. (It may not even be ITMY, but the 4 mHz mode separation does smell very much like a barely-elliptic mode splitting.)
I think Sheila and Georgia are on the right track of refining the band-pass filter to be that much more narrow. Mode frequencies for these violins are stable to temperature and test mass alignment at the ~10 microHertz level, so I think plant inversion -- or at least a very narrow (0.5 mHz) band-pass -- might be OK (see second attachment; figure 2 from G1601163 and/or G1700038).
Updated the table with some gains and phases for modes 504.606 Hz, 504.719 Hz, 504.85 Hz, all on ITMX and requiring low gains (<~5). And 504.953 Hz on ITMY (high gain, -30).
Posting this screenshot as a message to all the other v-modes out there. Blue reference is before damping, red is after.
In response to Sheila's request to compare the two following locks:
Aug 21 2018 02:42:00 UTC > Aug 21 2018 03:11:00 UTC [1218854538 > 1218856278]
Aug 21 2018 05:09:00 UTC > Aug 21 2018 05:29:00 UTC [1218863358 > 1218864558]
I ran 1mHz resolution PSDs. Results are below.
LOCK Aug 21 2018 02:42:00 UTC
Freq. [Hz] SNR
501.3750 77
501.5556 33815
501.6251 10114
501.6913 2815
501.6972 184
501.7553 181884
501.8750 76
502.7849 21376
502.9092 185016
503.0863 111095
503.1984 8470
503.6779 36286
503.7335 82344
504.1442 1609
504.1778 6259
504.6075 19039
504.7205 103589
504.8516 8474
504.8900 26733
504.9529 33514
505.0786 29540
505.1875 230981
507.3609 143884
507.4945 1342
508.8452 783438
508.9403 590
510.7142 915952
510.7255 268
511.1820 147617
513.4059 398372
513.5119 159
516.6806 693925
516.7800 5140
Lock Aug 21 2018 05:09:00 UTC
Freq. [Hz] SNR
501.5540 147
501.6293 478058
501.6925 2127
501.7553 612669
502.7849 17214
502.9091 183754
503.0860 50717
503.1984 88
503.6779 48336
503.7335 45705
504.1442 5292
504.1778 17130
504.6075 45363
504.7205 529860
504.8516 386988
504.8900 1223
504.9529 534100
505.0786 50532
505.1875 238858
507.3609 269516
507.4945 1032
508.8452 459774
508.9404 271
510.7142 492155
510.7254 108
511.1819 184454
513.4059 193424
513.5119 159
516.6806 423031
516.7799 4596
I am sorry I have just noticed these round of violin modes alog entries.
I will investigate further but as a quick comment to add to the comments above:
Jeff suggested that the frequency separation of 4mHz of the two modes may indicate frequency splitting of modes associated to the same fibre. However based on the data we have from all fibres of both LIGO detectors this is very improvable. Frequency splitting observed so far is on the order of tens to hundreds of mHz, there only one case of about 1mHz separation at LLO ITMX and it is not certain to be associated to the same fibre.