SudarshanK, PaulM
Summary:
We moved the Pcal beam spot on EndX by about 8 mm in y direction such that the beams are close towards the center of the optic from their optimal position of +/- 111.6 mm.
Details:
We moved the inner (top beam) using the last steering mirror on the Tx module and moving the mirror mount screw clockwise in pitch. We were able to get the Pcal beam close to our desire location with about a quarter turn of the screw. The beam came out on the receiver side without clipping in vacuum but the receiver side optics had to be adjusted to get the beam into the RxPD.
For outer beam (bottom beam) we moved the beam by moving the mirror mount clockwise in yaw. We were not able to get the entire beam out of the vacuum when Pcal beam was moved to the desired position. We have no way of knowing if the clipping is happening on the way to the ETM or the way out from the ETM. We didn't feel comfortable (on Rick's advice) to translate the beam to relieve the clipping. We are hoping the beam is clipped on the way out and we can use the TxPD signal to calibrate the displacement. We will be able to figure this out once we have a locked interferometer by comparing the displacement measured by the interferometer and predicted by the Pcal photodetectors (TxPD in this case).
This new Pcal beam position will introduce a calibration error on hardware injection at a level of 2% at 2 kHz and much smaller at lower frequencies. However, if the clipping is happening on the way to the ETM this will introduce significant error not only on hardware injection but the study that I am trying to do so we will have to come up with a plan to relieve the clipping.
The position of the Pcal beam spot before and after are as follows:
Before | After | |
Upper Beam | [1.9, 0.3] | [2.5, -8.4] |
Lower Beam | [-1.0, 0.3] | [-1.3, 8.6] |
Also, the injection of high frequency lines are scheduled using the Guardian as described in alog 37765. The frequencies we will be running are: [5001.3, 4751.3, 4501.3, 4251.3, 4001.3, 3501.3, 3001.3, 2001.3]
In light of trying to take new measurements on the HWS IR pointing offsets at EX, I noticed that there was no space left on the disk so I ran a thinning script that Nutsinee had written for this problem and cleared up about 200 GBs of oldest HWS data.
The bash script that initiates this cleaning is: /data/H1/thinning_script.sh
Which calls a python script that folders to clear out based on the earliest GPS date.
Currently the user has to manually initiate this process or else the disk space will eventually get full without much notice.
ECR-E1700256, WP 7085
I added 16 SUS DAC overflow channels to the GDS broadcaster. This has increased the number of overflow accumulated counters by 16 (4 per main QUAD). Here is the full list of overflow channels (ADC and DAC) now in the GDS data flow:
[H1:FEC-29_DAC_OVERFLOW_ACC_2_4]
[H1:FEC-29_DAC_OVERFLOW_ACC_2_5]
[H1:FEC-29_DAC_OVERFLOW_ACC_2_6]
[H1:FEC-29_DAC_OVERFLOW_ACC_2_7]
[H1:FEC-30_DAC_OVERFLOW_ACC_2_0]
[H1:FEC-30_DAC_OVERFLOW_ACC_2_1]
[H1:FEC-30_DAC_OVERFLOW_ACC_2_2]
[H1:FEC-30_DAC_OVERFLOW_ACC_2_3]
[H1:FEC-88_DAC_OVERFLOW_ACC_2_0]
[H1:FEC-88_DAC_OVERFLOW_ACC_2_1]
[H1:FEC-88_DAC_OVERFLOW_ACC_2_2]
[H1:FEC-88_DAC_OVERFLOW_ACC_2_3]
[H1:FEC-88_DAC_OVERFLOW_ACC_3_1]
[H1:FEC-88_DAC_OVERFLOW_ACC_3_2]
[H1:FEC-88_DAC_OVERFLOW_ACC_3_3]
[H1:FEC-88_DAC_OVERFLOW_ACC_3_4]
[H1:FEC-8_ADC_OVERFLOW_ACC_0_12]
[H1:FEC-8_ADC_OVERFLOW_ACC_0_13]
[H1:FEC-98_DAC_OVERFLOW_ACC_2_0]
[H1:FEC-98_DAC_OVERFLOW_ACC_2_1]
[H1:FEC-98_DAC_OVERFLOW_ACC_2_2]
[H1:FEC-98_DAC_OVERFLOW_ACC_2_3]
[H1:FEC-98_DAC_OVERFLOW_ACC_3_1]
[H1:FEC-98_DAC_OVERFLOW_ACC_3_2]
[H1:FEC-98_DAC_OVERFLOW_ACC_3_3]
[H1:FEC-98_DAC_OVERFLOW_ACC_3_4]
here is the FEC to OPTIC map
29 = ITMX
30 = ITMY
88 = ETMX
98 = ETMY
08 = OMC
Summary: In response to the recent CW injection recovery report, I investigated why there is a ~61 usec delay residual (see this plot, as well as the attached plot with 61 usec delay plotted), and to understand the amplitude offset (see this plot). I have identified that there was a missing 61 usec delay that should have been included in the inverse actuation filtering assumed timing advance, see below. The transfer function provided to the CW group for hardware injections is similarly affected, and requires including a 61 usec advance. This resolves the phase offset issue as seen in the CW injections. Amplitude offsets are a little more complicated without comparing with the true injected waveform; see below. Details: First, addressing the amplitude offset: the calibration team carefully monitors the photon calibrator power sent to the test mass using a calibrated photodetector sampling a fraction of the beam sent to the ETM, or reading back the full beam reflected from the test mass. This ensures we know exactly how much the mass was actually displaced by the radiation pressure. The inverse actuation filter used by hardware injections relies on a calibrated excitation point, which is less reliable than the readback photodetectors. Thus, I would not rely on this calibration to better than the ~5 percent level. Also, the inverse actuation filter has a gain on the anti-(analog AI) of 1.0098. This is because there have been measurements at LHO to show that at least some of the analog AI chassis have a gain of 1/1.0098 = 0.9903 (see LHO aLOGs 18628 and 18518), whereas LLO sets the model to have unity gain and allow for an offset (see LLO aLOG 18315). So there is some uncertainty on the overall gain of the inverse actuation filter at the ~1% level due to the AI gain alone. Thus, for better comparison of the CW hardware injection amplitudes, it would be better to analyze the photodiode readback channels to verify the expected waveform matches what was actually injected. For the residual phase, the originally quoted uncompensated delay was ~240 usec (see LLO aLOG 27562). The delay is a combination of the digital delays, as well as any residual phase effects from the approximated AI filtering and roll-off filters which would require time advances (not possible in Foton). Well, it turns out that I neglected to include the 61 usec delay when summing the digital delays. (D'oh!) Thus, the uncompensated delay is not ~240 usec but rather ~300 usec. The hardware injection pathway from a given waveform, through the inverse actuation filter, through the Pcal output generating strain, can be expressed as: m N 1 W V 1 cts 1 V W N 1 m h h(t) x [ --- x --- x f^2 x -------- x --- x --- x ----- x ----- x ----- x roll-off ] x [ 61 usec delay x AI(D) x 61 usec delay x ----- x AI(a) x --- x --- x sus.norm x ----- x --- x --- ] h m sus.norm N W AI(a) V AI(D) cts V W f^2 N m where the first term in brackets is the inverse actuation filter (not accounting for any digital delays) and the second term in brackets are the pieces lying between the Pcal excitation point and the induced strain. I had neglected to include the first 61 usec delay in the second bracketed term. It can be easier to see the accounting of delays in this DCC diagram and Pcal path components in the calibration subway map. Fortunately, this resolves the issue with CW injections, since they will have a 61 usec delay induced due to this oversight. It also means that all other injections should assume a ~300 usec timing advance in all waveforms. I also attach an updated file to be used for H1 CW hardware injections that includes the missing 61 usec advance to account for the 61 usec delay.
Sudarshan and I updated the node to start from 5001.3hz and then go down in steps of 250hz until it passes 4000hz, then steps of 500hz until 2000hz.
Code was loaded into the node and started. See attached for log and new code.
Swept on July 25, 2017 at 19:20UTC
This morning I completed the weekly PSL FAMIS tasks.
HPO Pump Diode Current Adjustment (FAMIS 8432)
With the ISS OFF, I adjusted the HPO operating currents. All currents were raised by 0.1 A, changes summarized in the table below:
Operating Current (A) | ||
Old | New | |
DB1 | 49.0 | 49.1 |
DB2 | 52.0 | 52.1 |
DB3 | 52.0 | 52.1 |
DB4 | 52.0 | 52.1 |
I did not adjust the operating temperatures this week. I have attached a screenshot of the main PSL Beckhoff screen for future reference. The ISS is now turned back ON, and the HPO is outputtting ~154.9 W. This completes FAMIS 8432.
PSL Power Watchdogs Reset (FAMIS 3660)
I reset both PSL power watchdogs at 16:02 UTC (9:02 PDT). This completes FAMIS 3660.
TITLE: 07/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
Wind: 10mph Gusts, 8mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY: Maintenance Day has begun.
TITLE: 07/25 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: TJ
SHIFT SUMMARY: After the initial lockloss of the shift, I have been unable to get past REDUCE_RF45_MODULATION_DEPTH without OMC DCPD saturations. After the first couple of locklosses at this point, I went stepwise through each guardian state from DC_READOUT_TRANSITION. While watching the ISC_LOCK log at REDUCE_RF45_MODULATION_DEPTH, it seems that the CHARD P loop never really converges. It vacillates between converged and waiting for convergence. If you select any higher guardian state, it will immediately move on when it registers converged and OMC DCPD saturation alarms start. SRC1_Y error signal on the StripTool starts running away from zero once the DCPD saturations start. Performed IA after 3rd lockloss during relocking; did not help. ETMy violin mode 5 has been an unresponsive nuisance during this saga, but I can't say for sure that it is entirely responsible.
On the bright side, PCAL X RX PD seems to have fixed itself at the lockloss from the step at another lockloss reported in alog 37726. See attached screenshot.
LOG:
Prior to 13:20, see Shift Summary above.
13:20 Called Keita for help
14:25 Lockloss while Keita was working to remove OMC whitening. We decide to forego trying to relock since maintenance day is starting in 35 minutes.
14:51 JeffB to diode room, then to cleaning area
14:59 JeffK starting TFs on BS and PR3
To operators:
The reason why I wanted to remove whitening was because OMC DCPDs were railing for whatever reason (violin?). As soon as DCPD starts constantly railing it becomes hard to damp violins and PI (Travis had a hard time taking care of PI).
I tried to manually punch in 0 to PDB gain and 2000 to PDA gain quickly enough but it took me longer than I wanted, IFO didn't like it.
I could have written a script to do it quicker, but JeffK later showed me that you can do it in the guardian.
Open OMC_LOCK, then ALL, then MANUAL, then REMOVE_WHITENING (or ADD_WHITENING), and get back to MANAGED.
Another note (July14th) for REMOVE_WHITENING steps when violins rung up (with note about Manager of OMC_LOCK node): here.
All appeared quiet prior to lockloss. Cause unknown.
TITLE: 07/25 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 53Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY: No issues handed off. Lock is 19.5 hours old.
TITLE: 07/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 53Mpc
INCOMING OPERATOR: Travis
SHIFT SUMMARY:
LOG:
J. Kissel Still hunting for what's limiting our range, we took Valera's suggestion to drive stage 2 (ST2) the test masses' BSC-ISIs to check for, among other mechanisms, (a) scattered light problems, (b) charge coupling issues, or (c) mechanical shorting / rubbing The measurements indicate that ETMX and ITMY are the worst offenders, in that their ambient noise falls as ~1/f^{1/2} between 10 and 100 Hz, with some resonant features at 70 and 92 Hz. The features are presumably the first few cage bending modes, for which we have Vibration Absorbers that have already knocked down the Q of the ~70 Hz modes, thankfully. I've used the measurements to "calibrate" the error point of the ISI's ST2 Isolation Loops, and project the ambient noise to equivalent DARM displacement noise (a.k.a. primitive noise budgeting), see first attachment. Each come within a factor of 3-5 at their worst parts during ambient conditions; too close for comfort. Also, of course, there should be no such coupling at all if the cage were properly isolated from the suspension, and this appears to be a straight-forward linear coupling. Note that the precision of the projection is not great -- I did not try hard to get it right. There are addendum plots that show the residual between model and measurement. I don't think this is a / the limiting source now, since there is little coherence during ambient conditions, but this will certainly be a problem in the future if the coupling remains this bad for ETMX and ITMY. It definitely deserves a more careful calibration, further study with other degrees of freedom, and mapping out a broader frequency band. Perhaps we should check the coherence with these ST2 ISI channels after Jenne's subtraction of jitter (see LHO aLOG 37590) -- though the slope doesn't quite match up (from eye-ball memory). ITMX's coupling is about 1/2 as bad, and ETMY does not show any visible signs of bad coupling at this excitation level (which is damning evidence that it's related to charge, since ETMY has the largest effective bias voltage at the moment). %%%%%%% Details %%%%%%%% Measurement Technique (all while in nominal low noise): - choose obvious, simply to imagine coupling degrees of freedom: the longitudinal axis for the optics in the arm cavity (X for ETMX and ITMX, Y for ETMY and ITMY) - measure ambient error signals in those directions using DTT. - In the same DTT template, create a band-passed excitation where you suspect you're having problems (10-100 Hz), shape it to look roughly like that ambient spectra you see. I used ellip("BandPass",4,1,40,10,100)zpk([0.1],[1; 10],1,"n")gain(0.159461)gain(1e-4) copied and pasted to the 4 excitation banks (thanks Daniel!) so that I can pick and chose what I'm driving, and with what amplitude. - Grab a bunch of relevant response signals; the excitations, the error signals, the calibrated displacement (the pre-calibrated SUSPOINT signals are especially nice -- though the suffer from spectral leakage up to above 10 Hz). - Slowly creep up the drive (I started with 0.001 [ct] to be extra careful) until you start to see hints of something / coherence. - In case the coupling is non-linear, record the results at three different drive levels (I chose factors of three, 500 ct, 1500 ct, and 4500 ct, filtered by the above band-pass.) Analysis Techniques - Remember, to calibrate DELTA L EXTERNAL, one must apply the transfer function from /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/ControlRoomCalib/caldeltal_calib.txt i.e. copy and paste that file into the "Trans. Func." tab of the calibration for the channel, after creating a new entry called (whatever) with units "m". - For calibrated transfer functions of ISI displacement in local meters to DELTA L in global differential arm meters, just plot transfer functions between SUSPOINT motion (which comes pre-calibrated) and DELTA L EXT. - Store the transfer function between the ISI ST2 ISO error point and DELTA L EXT for the loudest injection - For "good enough" calibration of the error point, make a foton filter (in some junk file) that looks like the transfer function of error point to DELTA L EXT, and install into DTT calibration for that channel. Guess the gain that makes the driven error-point spectra line up well with the DELTA L spectra. For ETMX this was foton design: resgain(70 Hz, Q=8, h=8) * resgain(92 Hz, Q=30, h=10) * zpk(100,1,1) equiv zeros and poles: z=[10.6082+/-i*69.1915, 3.42911+/-i*91.9361, 100], p = [4.2232+/-i*69.8725, 1.08438+/-i*91.9936, 1], g = 1 dtt calibration: Gain: 1e-14 [m/ct] Poles: 4.2232 69.8725, 1.08438 91.9936, 1 Zeros: 10.6082 69.1915, 3.42911 91.9361, 100 For ITMY this was the same thing, but without the 92 Hz resonant feature: foton design: resgain(70 Hz, Q=8, h=8) * zpk(100,1,1) equiv zeros and poles: z=[10.6082+/-i*69.1915, 100], p = [4.2232+/-i*69.8725, 1], g = 1 dtt calibration: Gain: 1e-14 [m/ct] Poles: 4.2232 69.8725, 1 Zeros: 10.6082 69.1915, 100 This calibrates the channel, regardless of if there's excitation or not (assuming all linearity and good coherent original transfer function) --- in the region where your transfer function is valid, then this will calibrate the ambient noise. Since I didn't take enough data to really fill out the transfer function, I only bother to do this in the 10-100 Hz, and did it rather quickly -- only looking for factors of ~2 precision for this initial assessment. So as to not confuse the main point of the aLOG, I'll attach supporting plots as a comment to this log.
I attach support plots that show For each test mass: The DELTA L EXTERNAL spectra during excitations, along with calibrated displacement of each excitation, the resulting transfer function, and coherence. For those who may have to repeat the measurement, I attach screenshots of the DTT configuration and what channels I used explicitly. The template's too big to attach, but it lives in /ligo/home/jeffrey.kissel/2017-07-242017-07-24_BSCISI_ST2_BB_Injections.xml Also, shown for ETMX and ITMY, the projected ST2 Error Point both under excitation and during ambient conditions, with the residual transfer function shown below to expose how poor the calibration is.
Jeff and I added his data to the simple noise budget. We are still using a pre-EQ darm noise in this plot, and you can see that the couplings he found explain some of our unexplained noise around 60-70 Hz.
Adding a couple plots to show that ETMX ST2 coherence to CAL_DELTAL has changed, but measured motion doesn't seem to have changed. First plot is the coherence for 500 averages from the long lock on June 22, 2017 from 18:00 UTC on (in blue) to a similar window from the lock last night (red). The lump at 70-ish hz in red is new, not visible in the pink trace from June. Second plot shows the ST1 L4Cs and ST2 GS13s (both in meters) for the same periods (the June measurement is red and blue, last night are green and brown). The ST2 motion especially is nearly identical around the lump at 70 hz. Talking to Sheila, this maybe implies that scatter at EX is worse now than before.
I looked at all of the other BSCs as well for the lock segment last night, but none of the them showed the same coherence as ETMX.
For the record, here are two alogs from LLO on tests we've done:
BSC injections before O2 (when we found the problem with ITMY). We plan to repeat these before the end of the run.
O2 HAM injections (all clear to at least x10 above ambient).
If we are making a budget of the stage 2 motion to DARM then we should take into account the rotation motion also, since the bottom of the cage has ~2 meter lever arm
For off-site interested parties, I've committed the above template to the seismic repository here: /ligo/svncommon/SeiSVN/seismic/BSC-ISI/H1/Common/Data/2017-07-24_BSCISI_ST2_BB_Injections.xml and corresponding key to all of the 100+ references in the template (as well as documentation of measurement times) is in the same location, with a similar name: /ligo/svncommon/SeiSVN/seismic/BSC-ISI/H1/Common/Data/2017-07-24_BSCISI_ST2_BB_Injections_ReferenceNotes.txt
I've replotted some of Jeff's data for the stage to beam direction drive to Darm and added a plot from Ryan and Valera's (24820) similar data.
There are the four stage 2 motion to Darm transfer functions from H1 (I made the ETMY data dotted because it has no coherence)
There is a 1/f^2 line (light blue) which is what you might expect for the coupling from a charged path on the test mass to a moving charge (not quite a matching slope, but the transfer function phases all look like 0 degrees)
I wasn't able to recover transfer functions from the LLO data so I plotted the amplitude ratio for the one platform where there is excess signal in Darm (ITMY in green). The vertical black lines mark the limits of where there is excess signal and where you can believe that we have a decent estimate of the transfer function. The sensitivity on the other LLO chambers is much less (at least a factor of 5)
One more plug for a rotation measurement, a good measurement of the rotation to Darm transfer function on ETMX and/or ITMY would let us do some geometry to guess at the height of the coupling location (again assuming a point like integration between the cage and the suspension cage)
H1 locked for 16 hrs @ 52Mpc. Nothing to report other than some commissioning work that took place.
23:56 a2l/commissioning work
01:05 Intention bit "Undisturbed"
Pep Covas, DetChar, Anamaria Effler, Rick Savage, Robert Schofield
Summary: Ravens peck at the ice on the cryopump GN2 vent lines around the site, and the signal from simulated pecking at EY suggests that this pecking is the source of certain common DARM glitches identified by DetChar. Evidence from PEM coupling functions, beam tube shaking, P-Cal periscope resonance measurements, and beam-spot perspecive photos, support a hypothesis that the raven pecks vibrate the GN2 vent tube, which is connected to and vibrates the vacuum enclosure and P-Cal periscope, thereby varying the optical path length of light that is scattered from the test mass and reflected back from the P-Cal viewport glass such that it recombines in varying phase with the main beam. The back-reflection of light from the viewport glass is made likely by the position and orientation of the P-Cal periscope mirrors, including the P-Cal beam relay mirrors. So we may still have some noise even if we remove the camera mirrors and baffle the periscope. We request more PEM injection time to study this possibility and for newly identified scattering at EY. The scattering problem might be solved (and we might be able to keep camera mirrors) if we can adjust the mirrors so that the image of the test mass beam spot is not perpendicular to the viewport glass.
DetChar has reported many first round Hvetos for Y-end microphones, such as the ones visible at about 94 Hz in Figure 1. Jordan played the microphone signal for me and I recognized the sound as similar to what I had heard when I found ravens on the outside cryopump/LN2 lines at EY. Last Friday we got some PEM injection time and Pep and I went out to study this coupling to DARM.
We took a closer look at the cryopump lines that I had seen the ravens on, and found many peck marks, consistent with the size of a ravens’s beak, in the ice that accumulates on the cryopump nitrogen gas vent line (see Figure 2). Figure 2 also shows a raven caught in the act of pecking ice, not at EY, but at the corner station. I guess we can’t blame them for desiring shave ice on a hot desert afternoon. Figure 2 also shows Pep chipping at the EY ice to see if such imitation pecking could account for the glitches in DARM.
Figure 3 is a comparison of spectrograms of an EY microphone and DARM for the imitation pecks and the time of the cluster of glitches just before 20:00 UTC in the Hveto plot of Figure 1. The signals on the microphone and the effect in DARM were similar for our chipping and the event from Hveto.
Light insulation on the vent line could allow the nitrogen to warm up slowly without ice accumulation, or, alternatively, a loose sheet metal shell could prevent pecking without icing up. And there is ice at a different location below the LN2 dewar for desperate ravens.
We repeated one of the standard acoustic injections to compare acoustic coupling to the pre-run PEM injections and to see if measured coupling functions could account for the raven coupling. Figure 4 shows that coupling for acoustic injections has increased since the November measurement, especially at the ~94 Hz peak.
The new coupling function for the –Y mic (6.2e-17m of DARM per Pa of sound pressure at about 94 Hz) underestimates the effect of the bird pecks in DARM, by nearly a factor of ten, while the new coupling function from the BSC10 ACCX (about 2e-8 m/m), for the same acoustic injection, gives a much closer estimate of 1.4 times the actual peak height in DARM (data shown in Figure 5). Thus, the VEA sound level from the pecking doesn’t seem loud enough to account for the effect in DARM, and the coupling route is likely through the direct mechanical connection of the pecked GN2 vent tube to the vacuum enclosure.
We ran the shaker that was set up on the beam tube to excite the P-cal periscope and found a stronger response at ~94 Hz than we had in the past. A look at the resonances measured for the P-Cal periscope at LLO show a strong 93 Hz resonance that was damped with a SUS damping cube (https://alog.ligo-la.caltech.edu/aLOG/uploads/33697_20170512084726_2017-05-11_Phase3a_L1_BSC5_PCAL_Periscope_Vert.pdf ). Because the 94 Hz feature excited by the birds in DARM is excited by somewhat localized shaking in the region of the periscope, a known scattering site, and because of the similar resonance measured for the LLO periscope, it is likely that the peck coupling is produced by scattering associated with the periscope.
A detailed understanding of the scattering may help us ensure that it is corrected for O3. The inability to mitigate the scattering (including the ~94 Hz peak) with black glass in the viewports (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=31261) suggests that the problem is not scattering from outside the ports, but from the periscope structure or the viewport glass. The viewport glass can reflect the light scattered from the test mass directly back to the test mass if the camera and P-Cal beam relay mirrors place the image of the beam spot directly in front of the viewports so that the scattered light path is perpendicular to the viewport. One of my photos from the point of view of the test mass beam spot showed such a retroreflection (https://alog.ligo-wa.caltech.edu/aLOG/uploads/8281_20131027132038_Figure1-ViewFromETMXBeamspot.jpg). Based on the linked and other beam spot perspective photos, I think that the view port glass may be the dominant problem. The relay mirrors place the beam spot image nearly perpendicular to the glass in all 3 paths, including the P-Cal beam, so removing 2 paths, the camera relay mirrors, may not be enough to completely mitigate the retroreflections (not to mention that we would like to keep the camera mirrors). It might be possible to angle the mirrors slightly so that the scattered light hits the viewport at a larger angle. If not, we may need to move the mirrors or add more.
We need more PEM injection time to shake the P-Cal beam viewports in order to see if they are reflecting scattered light. Also, Pep and I found that exciting the cryopump produced scattering shelves for some resonance that is at a lower frequency than the P-call baffle resonances and we need time to study this.
Very nice investigation. Once upon a desert scorching, ignorant of scientists working, Over a quaint and curious site of shining machinery did I soar— There I landed, gently tapping, disturbing not the machine’s clacking, On the chill pipe softly rapping, lapping the ice’s cold succor. “A cool treat,” I fluttered, “and then away I’ll soar— Only this and nothing more.” Ah, be thou not so craven to name me a common raven; And dismiss these pecks I’ve graven upon your precious noise floor Eagerly I read your logbook, hoping that this humble rook Might one day not be overlook’d -- overlook’d in LIGO’s lore- This this somber, clever avian might find a place in LIGO’s lore- Part of science for evermore.
Brilliant! Both Robert and Andy!
A company came out today to take measurements for an estimate to insulate the GN2 exhaust line to prevent ice build up at both end stations and corner station.
Keita pointed out that we have only been using OMC DCPD B for at least the last lock. I trended the relative gains of DCPD A and DCPD B, and it looks like we've been in this situation since 16July2017 at around 05:30 UTC.
The attached is a 5 day trend of the gains. The 2 spikes earlier are when we were either adding or removing a layer of whitening, due to the violin modes being too high. On the 16th, it looks like the guardian was started to switch the whitening, but then maybe got stopped halfway. This explains why it has looked like the shot noise was too high the last few days.
Clearly we need to write into the READY_FOR_HANDOFF OMC lock state to ensure that the 2 gains are both at their nominal values. Also, it looks like someone accepted the wrong values into the Observe SDF file, so we've been able to go to Observing with the wrong values :( No good. The safe SDF file was correct. I'll fix the Observe file.
EDIT: Looking through the guardian log file, it looks like the code gets a bit confused when you try to use these states before we're using the DCPDs for DARM. So, now if we're at DC_Readout_Transition or before (and don't need to do any gain ramping), we skip the gain changes and just change the whitening. If we're on DC_Readout or after, the change will happen as before. Either way, at the end of the state is now a check to see if the DCPD gains are equal (they should both be 1000). The new code is in the svn and has been reloaded, although not actually used.
Tagging CAL and DetChar.
The exact time of departure from this configuration is Jul 16 2017 05:24:00 UTC (1184217858) and return to normal is Jul 18 2017 18:58:00 UTC (1184439498) We (the calibration group) have recommended that any observation time within the period be marked with a CAT1 veto, citing that the detector was in a non-O2-standard configuration and the calibration is suspect. Yes, it is plausible to reconstruct the calibration during these times, but given our limited person-power we have elected to abandon the effort at this time.
No problem, I made a flag and inserted it in to the segment database. H1:DCH-CAL_NON_O2_STANDARD_CONFIG:1 captures this time.