Displaying reports 39521-39540 of 88987.Go to page Start 1973 1974 1975 1976 1977 1978 1979 1980 1981 End
Reports until 16:38, Thursday 01 August 2019
H1 CAL (ISC)
jenne.driggers@LIGO.ORG - posted 16:38, Thursday 01 August 2019 - last comment - 12:28, Monday 05 August 2019(50973)
Checked OMC ASC offsets to maximize optical gain

[JeffK, Jenne]

After Jeff noted that last night's lock had a somewhat low optical gain (kappa_C value of ~0.93), we moved the offsets in the OMC ASC QPDs to try to maximize optical gain.  The attachment shows the moving that we did.  It's possible that we could get a bit more if we were able to move in the direction that saturates the OMC SUS, but I'm not 100% sure about that, and to get it we'd have to pico the AS WFS so that we can move OM1 and OM2 to offload some of the alignment move. 

We were able to convice the optical gain to come back to a value of 0.96ish, which is closer to what we've been having at 37W injected power for the last several weeks of O3.  The offsets aren't very different from what they had been - for the most part the optical gain was happier where the alignment had been.

Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 12:28, Monday 05 August 2019 (51034)DetChar, ISC
@DetChar -- This change in OMC alignment position appears to coincide with the drastic increase in glitches (below ~15 Hz, as reported by DMT Omega and Omicron) since Aug 1 2019.

You can confirm this by looking at trends of offsets in the OMC ASC system, under 
    H1:OMC-ASC_QPD_A_PIT_OFFSET
    H1:OMC-ASC_QPD_A_YAW_OFFSET 
    H1:OMC-ASC_QPD_B_PIT_OFFSET
    H1:OMC-ASC_QPD_B_YAW_OFFSET

We had changed these offsets to increase the DARM optical gain, but at the time we'd not considered that this position may be worse for things like coupling of seismic / acoustic noise, alignment jitter, scattered light, etc.

We'll bring this up at today's commissioning meeting and see if we can address it *and* improve the optical gain.
H1 ISC
jenne.driggers@LIGO.ORG - posted 16:36, Thursday 01 August 2019 (50972)
ITMX A2L gains touched up, need to fix script

After the spot moves yesterday, I did a coarse job of setting the ITMX A2L gains.  Today I did a somewhat more careful job by turning on ITMX oscillators and changing the A2L gains to minimize the line in DARM.  The Y2L value didn't change, but the P2L value changed a small amount.

Attached are the A2L values after this change.

Side note, after redoing the PUM drivealign matrices in the suspensions, we need to update Gabriele's A2L script to match the new channel names.

Images attached to this report
LHO General
patrick.thomas@LIGO.ORG - posted 16:11, Thursday 01 August 2019 - last comment - 16:24, Thursday 01 August 2019(50970)
Ops Eve Shift Transition
TITLE: 08/01 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: Niko
CURRENT ENVIRONMENT:
    Wind: 13mph Gusts, 10mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.05 μm/s 
QUICK SUMMARY: Jeff K. is taking measurements at NLN_CAL_MEAS.
Comments related to this report
patrick.thomas@LIGO.ORG - 16:24, Thursday 01 August 2019 (50971)
23:22 UTC Observing
H1 CAL (CAL)
timesh.mistry@LIGO.ORG - posted 16:06, Thursday 01 August 2019 (50961)
NCAL Lab Tests -- Attempting to get PEM Measurements and Discovered a Wobble 20170731

[Jeff Kissel, Rick Savage, Timesh Mistry]

Overview:

This is a summary of progress so far on the hardware side of things as well as the lab test conducted on 20170731, a full log can be found in the text file 'NCAL_LabTest_PEM_20190731.txt' attached to this alog.

The plan was to collect PEM measurements (accelerometer and magnetometer)  of the NCAL before fully dis-assembling the NCAL unit. We tripped the wall sockets multiple times when trying to set up additional equipment for PEM measurements. We discovered a wobble when running the NCAL at ~10Hz, worse that what we have seen when previously running the NCAL as well as a bad screw in the back plate of the NCAL the is attached to the main flywheel.


a) Old Plan Plan (as of 29th July 2019):

Rick, Jeff and I decided that we would completely disassemble and reassemble the NCAL. This is so that we can do the following:
 
a) Apply safety measures such as loctite and lock washers to the relevant bolts.
b) Clean all the parts and remove any alloy shavings, dirt and debris.
c) Using wet and dry + alcohol, sand down the bores of the NCAL to remove the surface roughness so the masses fit easier.
d) Become familiar with how to disassemble and assemble the NCAL and write up procedure.
e) Torque the bolts. The torque setting have yet to be determined. I will be going off the values found in the attached document otherwise.
f) Get PEM measurements, voltage, current and other measurements before and after  re-assembly. (Suggestion from Krishna remotely)
 
b) New Plan (as of 31th July 2019):
a) Replace the bad screw
b) Clean surfaces of NCAL
c) Find the source of the wobble
d) Get PEM measurements, voltage, current and other measurements before and after  re-assembly. (Suggestion from Krishna remotely)
e) Become familiar with how to disassemble and assemble the NCAL and write up procedure.
f) Using wet and dry + alcohol, sand down the bores of the NCAL to remove the surface roughness so the masses fit easier.
g) Clean all the parts and remove any alloy shavings, dirt and debris.
h) Apply safety measures such as loctite and lock washers to the relevant bolts.
i) Torque the bolts. The torque setting have yet to be determined.
 
The reason the for the above is given below for those that are interested.
 
1) Review from Machine Shop:
a) Long winded summary:
This follows after a visit to TK Machining where we had left the NCAL with them and asked them to machine the NCAL masses and clean up the scores in the bores (holes) of the rotor. There was a communications break down and TK Machining was under the impression we wanted a 'hammer fit'. I recall specifying a Class 4 press fit (apparently not an engineering standard as no-one knows what I was talking about).
 
TK did not do any machining on the parts as they found the some of the masses could be fully inserted into their designated holes with little effort at room temperature (we had not given TK Machining the heating apparatus). Furthermore, TK Machining pointed out that some of the bores (mainly #1 and #5) had significant scoring such that this will certainty cause difficulties inserting and removing the masses. Moreover, TK Machining noted that the NCAL masses had sharp edges that would also lead to increased damage to the surface of the bores if the masses were not inserted and removed perfectly. When we asked TK Machining 'How would you tackle removing material from the NCAL masses and the surface of the holes?', they responded with the following:
a) The NCAL masses would be held in a lathe, clamped at each end and centered. A hand tool will then be used to remove material from the mass while the mass is spinning, measuring frequently.
b) The rotor will be taken to a honing machine and, by hand they will hone each hole, measuring frequently.
 
All in all, we took the NCAL back to LHO and between Rick, Jeff and myself, we reviewed the comments from TK Machining and came up with the plan at the top of this email.
 
2) Issues Discovered:
a) Wobble
In the process of running the NCAL for the PEM test. The NCAL has developed a wobble.
 
At 10Hz (1043 counts) there is a gentle rocking motion that can be seen from from looking at the orange comms cable. When placing my hand on the shell, I can feel a wobble. This is certainty worst than than before because this time around, when spinning at ~10Hz, the table that the NCAL is bolted to is visibly shaking. there is no play or excessive resistance in the bearings. I had a thought that the back plate is misaligned slightly and that could be the cause of the wobble but I have discovered another issue.
 
b) Bad Screw
I have found a 10-32 socket head cap screw that does not want to fit back into the main rotor that holds the rotor base. Upon further testing, I had 1 of 2 suspicions:

a) It is a metric M5 screw
b) It is a bad quality imperial 10-32 3/8 cap screw

I consulted with Chandra and Rick and the overall conclusion was that it is a bad 10-32. This is because:
1) After 1 1/2 turns with the offending screw would 'bind' (increase resistance) when tested in other 10-32 holes in the NCAL and when testing in a screw pitch gauge.
2) When putting the offending screw into the metric M5 screw pitch gauge, it would fit but would wobble (strike one for metric theory)
3) When comparing the threads of the offending screw to a 10-32 tap and other 10-32 screws, the threads match (strike two for metric theory).
4) There are no marking on the top of the head of the screw as this is typical of metric screws (strike three for metric theory).

What I suspect is that a longer 10-32 has been cut down to the required size (I think 3-8) and has not been done properly. I am going to order more 10-32 3/8 screws and replace the bad one. In addition I have already cleaned up the threads with a wire brush as Isopropanol.I have also clean the mating surfaces of the NCAL and the back plate with alcohol wipes and cleaned the threads of the remaining good screws.

The problem of the wobble still remains.
 
c) Tripping the wall sockets

When trying to power the spectrum analyser, we tripped the wall socket (Serial Number: 168RP1-17). fter resetting the wall socket, tediosly, we tried each plug one by one on the wall and did not trip the wall. We found that using the we could apply no more than 3 plugs to the wall before it tripped. It did not matter if we used a power extension or directly into wall.

To get around this issue, we used a extension from anther wall socket (Series Number: 168RP1-20) in combination with the wall socket in this combination:

Socket 168RP1-20 :  Spectrum Analyser, DC power supply, Oscilloscope, PC Monitor
Socket 168RP1-17 :  Beckhoff motor controller

When using the power stip, we found we could only use 3 slots as plugging in a 4th plug would trip the wall socket.

Non-image files attached to this report
H1 General
yannick.lecoeuche@LIGO.ORG - posted 16:00, Thursday 01 August 2019 (50969)
Shift Summary - Day

TITLE: 08/01 Day Shift 15:00 – 23:00 (08:00-16:00), all times posted in UTC

STATE of H1: Corrective Maintenance

INCOMING OPERATOR: Patrick

SHIFT SUMMARY: Started shift in Observing and was eventually knocked out of lock by a 6.6 EQ in Chile, which took about 3 hours to ring down. Went through the locking process without initial alignment, managed to get to NLN. Commissioners are currently driving.

LOG:

15:00 (08:00) Start of shift

15:06 (08:06) Ethan, Timesh to Optics Lab

15:12 (08:12) Timesh out of Optics Lab

15:17 (08:17) Karen to Optics Lab

15:38 (08:38) Ethan out Optics Lab

15:42 (08:42) Karen out of Optics Lab

17:30 (10:30) Out of Observing for calibration measurement

17:47 (10:47) Laurence, Dripta to Optics Lab

18:17 (11:17) Calibration measurement complete, going back to Observing

18:33 (11:33) Switching to EQ config for 6.5 in Chile

18:44 (11:44) Laurence out of Optics Lab

18:52 (11:52) Lockloss from EQ

20:09 (13:09) Dripta out of Optics Lab

21:02 (14:02) Ethan to Optics Lab

21:05 (14:05) Timesh to Optics Lab

21:08 (14:08) Timesh out of Optics Lab

21:14 (14:14) Ethan out of Optics Lab

22:03 (15:03) At NLN, holding there for corrective maintenance

23:00 (16:00) End of shift

H1 General
jim.warner@LIGO.ORG - posted 15:08, Thursday 01 August 2019 - last comment - 14:31, Thursday 30 June 2022(50967)
ALS SDF diffs after updating initial alignment references

Back to NLN, Jenne and Jeff have updated ALS references, SDF diffs in attached screenshots.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 16:28, Thursday 01 August 2019 (50968)

JeffK noted that we don't have a good all in one place how-to on setting the initial alignment offsets.  So, here's an attempt at it.  This assumes that the QPDs are all close enough to center (or can be made to be so by moving TMS) that you do not need to use the picomotors.  Using the picos requires more thought and care.

The attachment is my desktop when I'm doing this, so you can see all of the windows that I'm looking at. 

  • ndscopes:
    • bottom left: reacquire lock 'scope from my Locking screen
    • bottom middle: ADS 'scope from my Locking screen
    • right side: New template in ..../jenne.driggers/Templates/Scope/green_wfs_setpoints.yml
  • medm screens:
    • sitemap, just because I always have the sitemap open
    • ALS camera setpoint screens, from each ALS end overview screen, then CAM ITM PIT green button.
    • tiny A2L screen: these are the A2L spot position gains from each test mass's PUM stage.  You can pull them each open individually from each SUS, or get this compact screen from my Locking screen, near the top right.
    • Compact QPD screen for the 4 IR transmon QPDs, to make sure that we're not falling off the IR QPDs.  Get this from my Locking screen, "ASC Pointing" button.
    • Green QPD offset sliders, get from either of the ALS end overview screens.
    • Sliders for the 2 TMSs.
  • Terminal windows:
    • One running setEndGreenQPDOffsets_XARM.py
    • One running setEndGreenQPDOffsets_YARM.py

Process for each arm (can be done in parallel since each arm is independant of the other for this work):

  • Ensure IFO is at 2W with all ASC engaged and converged (DC readout is a good spot for this).  Make sure that the ADS error signals are close to zero.
  • Ensure green shutters are open (sitemap -> LSC -> Shutters, then "Open" on the two shutters in the second from right column)
  • Ensure that the green laser is locked on the TEM00 mode to the cavity.
    • If it is not, you can noodle around the green QPD offset sliders.  Since these are in-loop with the pointing PZTs on the ALS in-air table, this effectively changes the pointing of the green laser into the vacuum, and into the cavity.
  • Run the setEndGreenQPDOffsets_[X,Y]ARM.py script, which will adjust the green QPD offset sliders to adjust the green laser input pointing to match the arm cavity (the metric in the script is zeroing the ALS WFS signals on the bottom row of the right-most ndscope). 
    • Watch the QPD offsets to make sure they aren't moving the spots too close to the edges of the QPDs.  Top two rows of the rightmost ndscope have Ylims set to +/-1, so it should be easy to tell when you're getting too close.  The third row is the sum of light on the QPDs, so you know that if that starts dropping you're getting too close to the edge.  We've been operating at offsets of more than 0.8 for all of O3, so while that's not great, it's not unacceptable (since these are unused in Observation mode).
  • Slowly move the TMS (steps of 0.1 urad seem fine with the standard 2 sec ramp) to get the beam closer to center on the IR QPDs.  Hopefully the green offset script will be pulling the green offsets closer to center, if they were close to their edges.  If they don't, you should stop here and reconsider things.  You may need to use the picos. 
  • Once you've got the TMS moved to center the IR QPDs and the script has converged such that the green wfs signals are close to zero, you should set the camera offsets.
  • Now, you're done and you should ensure that your new setpoints are saved in the down and observe SDF snapshots of the ALS end stations.

If you must pico, I'd recommend only pico-ing the IR QPDs since they're much easier to think about and independent of other beams.  I'd start the green QPD setpoint scripts to make the green QPDs follow your movement.  Then I'd make a small step in TMS alignment in the direction that will put the green QPD offsets closer to zero, and then pico the IR steering picos to get the IR QPDs closer to zero.

 

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 16:51, Friday 23 August 2019 (51477)ISC, OpsInfo
I've edited the code that sets the green QPD offsets (/opt/rtcds/userapps/trunk/als/h1/scripts/setEndGreenQPDOffsets_XARM.py and setEndGreenQPDOffsets_YARM.py) -- check out LHO aLOG 51476 for further commentary.
sheila.dwyer@LIGO.ORG - 17:59, Monday 18 November 2019 (53335)

This procedure needs to be modified because we are now setting green references with our spots centered on the optics.  We would like to center the IR on the IR QPDs once we have our spots in their final positions, however, not necessarily with the spots centered.

jenne.driggers@LIGO.ORG - 19:02, Wednesday 29 January 2020 (54800)

Since Craig added in the TMS servoing to center the IR QPD, we should still be able to follow this procedure at DC readout.  At DC readout, in the current situation, we are servoing the spots to the centers of all 4 test masses at 2W input power.  This is the position we want to set the initial alignment references to. 

Later in the acquisition sequence the power is increased to 10W, and then the beam spots are moved to their final high power positions, then we further increase the power and continue on to NomLowNoise.

sheila.dwyer@LIGO.ORG - 14:31, Thursday 30 June 2022 (63785)

Before setting the green camera references, we should remember to check that the camera image is good and that any mask applied is appropriate.  We can check this by opening up the digital camera screen and taking a snapshot, then finding the snapshot in /ligo/data/camera

 

H1 CAL (ISC)
jeffrey.kissel@LIGO.ORG - posted 14:37, Thursday 01 August 2019 (50966)
Calibration Measurements: Sensing Function Measurement during Current (maybe Permanent?) New Global Alignment
J. Kissel

Given that we now see evidence for an even lower optical gain (via the calibration lines) with the IFO's new global alignment position, and we haven't been able to take a sensing function measurement since Jul 17th, I "snuck" in a sensing function measurement suite this morning (thankfully just before the giant chilean EQ that knocked us out of lock).

The processed data is attached, and I've added it to the collection of data we've been gathering to help inform us of for what we'll eventually need to correct for in offline analysis and recalibration of h(t).

The message: in this new global alignment position, 
    - the optical gain is indeed lower (3.029e+06 ct/m), and consistent with the reported \kappa_C of 0.93 (given the reference model optical gain is 3.25e+06 ct/m)
    - the cavity pole remains at 410 Hz (though this number has been bouncing around quite a bit in O3).
    - the low frequency response (whether it be from parasitic L2A2L coupling or SRC cavity detuning), appears to now align with the physical model of a pro-spring, with f_s = 7.103 Hz (well, an f_s^2 = -50.453 Hz^2), and a Q_s of 11.67.

In order to confirm that this is an optical spring (now) as opposed to parasitic L2A2L coupling, we'd have to run the gamut of tests that we've run in order to decide that *previously* the low-frequency response was dominated by parasitic L2A2L (see a summary in G1901353). 

I've at least run the now normal PCALX vs. PCALY comparison, to confirm that the low frequency response is still not a PCAL spot-position torque issue. (the fact that the magnitude is ~0.5% different between the two has been brought to the PCAL team's attention and is now under investigation.)

I also attach the now standard plot which shows the MCMC fit values for the sensing function parameters over the entire run. We still have yet to compare these against the calibration-line-determined TDCFs. If we're going to be sticking with this global alignment, today's lock stretch will likely define thestart of a new epoch (and we already know that 2019-Jun-11 defined the start of the 2nd epoch in O3 when we powered up from 35W to 37 W.).

Raw data files live here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOSensingTFs
    2019-08-01_H1_DARM_OLGTF_LF_SS_5to1100Hz_15min.xml
    2019-08-01_H1_PCALY2DARMTF_LF_SS_5t1100Hz_10min.xml
    2019-08-01_H1_PCALX2DARMTF_LF_SS_5t1100Hz_10min.xml

    2019-08-01_H1_PCALY2DARMTF_BB.xml                     2019-08-01 18:10:22
    2019-08-01_H1_PCALX2DARMTF_BB.xml                     2019-08-01 18:12:40

    2019-08-01_H1_OMCDCPDSUM_to_DARMIN1.xml

Scripts to produce the attached plots:
/ligo/svncommon/CalSVN/aligocalibration/trunk/trunk/Common/pyDARM/src/sensing.py    rev 8127

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Scripts/FullIFOSensingTFs/
    process_sensingmeas_20190801.py
    plotMCMC_vs_GDSTDCFs.py
    process_sensingmeas_manydates_wPCALX.py
Non-image files attached to this report
H1 DetChar
adrian.helmling-cornell@LIGO.ORG - posted 14:27, Thursday 01 August 2019 (50946)
More O3 blip glitch statistics

An update to alog 50841

Glitch DB now has Hanford data up to the end of July 2019. Instead of the ~200 events we were looking at previously, there is now data from over 1000 blip glitches from O3.

The median peak frequency has definitely dropped between runs, as seen in figures 1 and 2. However, there is a clear bimodality, with a large population in the most common peak frequency bin from O2. In addition, a higher proportion of events occupy the high-peak frequency tail of the distribution.

The medium minimum frequency has dropped by ~15 Hz, as shown in figures 3 and 4.

The quality factor, time between blip glitches and SNR have not changed appreciably, but it seems as if the distribution of the duration of glitches falls off slower in O3 than in O2, as shown in figures 5 and 6.

Images attached to this report
H1 ISC
jenne.driggers@LIGO.ORG - posted 14:14, Thursday 01 August 2019 (50965)
Summary of spot positions before Tues and yesterday

Here is a quick summary of our spot positions on the test masses.  One column is the positions that we had been using before this week's Tuesday maintenance camera bump, one column is the spots that gave good buildups at 2W yesterday which is also the set of positions that the initial alignment is currently set for, and the final column is the spots that were better at 37W yesterday.

For the most part, we are closer to the center of our optics at the current 37W positions than our previous 37W positions. 

  Pre-Tuesday 2W and 37W 2W Post-Tuesday 37W Post-Tuesday Displacement change at 37W Pre- vs. Post-Tuesday
ITMX pit P2L = -3.965 -> 21.7 mm P2L = -0.1 -> 4.4 mm P2L = -3.5 -> 19.6 mm 2.1 mm closer to center
ITMY pit P2L = -3.0 -> 17.4 mm P2L = 0.8 -> 0.3 mm P2L = -2.0 -> 12.9 mm 4.5 mm closer to center
ETMX pit P2L = 4.3 -> -15.7 mm P2L = 0.7 -> 0.8 mm P2L = 3.3 -> -11.1 mm 4.6 mm closer to center
ETMY pit P2L = 4.3 -> -15.7 mm P2L = 0.7 -> 0.8 mm P2L = 0.9 -> -0.2 mm 15.5 mm closer to center
ITMX yaw Y2L = 0.055 -> 0.2 mm Y2L = 0.055 -> 0.2 mm Y2L = 0.055 -> 0.2 mm No change
ITMY yaw Y2L = 0.0 -> 0 mm Y2L = 0.0 -> 0 mm Y2L = 0.0 -> 0 mm No change
ETMX yaw Y2L = 3.6 -> 13.2 mm Y2L = 2.8 -> 10.3 mm Y2L = 2.8 -> 10.3 mm 2.9 mm closer to center
ETMY yaw Y2L = 3.6 -> 13.2 mm Y2L = 2.8 -> 10.3 mm Y2L = 4.4 -> 16.2 mm 3 mm away from center

 

H1 CDS
david.barker@LIGO.ORG - posted 12:12, Thursday 01 August 2019 - last comment - 13:29, Thursday 01 August 2019(50962)
summary of SDF snapshot files

Following last Friday's meeting regarding IFO relocking, one action item for CDS was to report on the current status of the SDF reference snapshot files.

In the attached text file, for each model, the status of the safe.snap, down.snap (if used) and OBSERVE.snap are shown. If the reference file exists, its modification date is shown. If the reference points to a different state's file, that state's name is shown.

I've ommitted non-control models (e.g. IOP and SUSAUX).

 

Non-image files attached to this report
Comments related to this report
david.barker@LIGO.ORG - 13:29, Thursday 01 August 2019 (50963)

This list can be generated by running the command

sdf_files_report

H1 ISC (DetChar, OpsInfo)
jeffrey.kissel@LIGO.ORG - posted 10:12, Thursday 01 August 2019 (50960)
DELTAL EXTERNAL ASD Before vs. After Alignment Changes
J. Kissel

A sincere applause to the heroic efforts of all whom have help us get back to an observation ready detector!

Picking up where Jenne left off at ~2am last night (see LHO aLOG 50954), I post a simple comparison between the ASDs of DELTAL EXTERNAL before the alignment shift (Monday, 2019-07-29 05:00 UTC) and after the alignment shift (Today, 2019-08-01 10:00 UTC).

GDS-CALIB_STRAIN reports our range is consistently ~5 Mpc lower than prior, so I was curious as to where we were different / losing out.

It appears to be a collection of minor things (no surprise).

We'll of course be doing more thorough investigations, but I thought people might wanna start here.

Since we still can't obtain GDS-CALIB_STRAIN from DTT, I attach a proxy -- DELTAL_EXTERNAL (uncorrected for time-dependence / optical plant changes) -- for your perusal.

I also attach a few-day trend of the time-dependent correction factors. It shoulds that our optical gain has dropped further (was 0.97 because we haven't yet corrected for the 35W to 37W power up), and the cavity pole is lower (now 398 Hz, as opposed to 405 Hz).
I'll be measuring the optical plant in full later today.
Images attached to this report
H1 General
jeffrey.bartlett@LIGO.ORG - posted 08:19, Thursday 01 August 2019 (50959)
Ops Owl Shift Summary
Ops Shift Log: 08/01/2019, Owl Shift 07:00 – 15:00 (00:00 - 08:00) Time - UTC (PT)
State of H1: Locked at NLN, range 114.2Mpc
Intent Bit: Observing
Support: Jenne
Incoming Operator: Niko
Shift Summary: After Jenne relocked the interferometer at the start of the shift, it was smooth sailing for the remaining 6 plus hours of the shift. Environmental conditions were good with low wind and microseism.   
 
Activity Log: Time - UTC (PT)
07:00 (00:00) Take over from Patrick
08:24 (01:24) Back at NLN
08:34 (01:34) Back to Observing
15:00 (08:00) Turn over to Niko

 

H1 General
yannick.lecoeuche@LIGO.ORG - posted 08:04, Thursday 01 August 2019 (50958)
Ops Day Shift Transition

Ops Shift Transition: 08/01/2019, Day Shift 15:00 – 23:00 (08:00-16:00) - UTC (PT)

State of H1: Locked

Intent Bit: Observing

Weather: 0-3mph wind

Primary 0.03 – 0.1Hz: 0.01 um/s

Secondary 0.1 – 0.3Hz: 0.1 um/s

Outgoing Operator: Jeff

Quick Summary: Been locked and Observing for 6.5 hours

H1 General
jeffrey.bartlett@LIGO.ORG - posted 04:15, Thursday 01 August 2019 (50957)
Ops Owl Mid-Shift Summary
   IFO is locked and observing with 112.5Mpc of range. Environmental is calm. With luck the second half of the shift will go as smoothly as the first. 
H1 ISC
jenne.driggers@LIGO.ORG - posted 01:45, Thursday 01 August 2019 - last comment - 13:53, Thursday 01 August 2019(50954)
Spot moves, good 2W buildups

[Jenne, JeffK, Patrick, Kara, Niko, JeffB]

As Jeff noted in his earlier alog 50952, I think that the Yarm alignment that was arrived at yesterday was such that the IR beam came into resonance with the beam spot on the other side of the ITMY point absorber than we usually sit at.  When all the ADS loops were closed except for PIT3 (which moves PRM to set the spot position on ITMY in pitch) and we couldn't move the PRM to get the ADS error signal close to zero without causing DHARD and other ASC loops to oscillate, I thought I'd try moving the ITMY P2L gain to get a rough idea of what value would zero the PIT3 ADS line.  It turned out that a value of +2 (which corresponds to a spot position of -5.2mm in pitch) was pretty good.  This is quite different from our old nominal ITMY P2L value of -3.0 (which corresponds to a spot position of +17.4mm in pitch). 

While at 2W I moved all of the A2L values of the test masses to move the spots and try to improve the buildups.  Recall that ITMX isn't used in-loop, but needs to be adjusted to reduce angular noise in DARM that drowns out the other A2L lines.  I was able to get a power recycling gain of 48 with a POP18 value in the high 60s, which is much better than we usually do at 2W.  I reset the green initial alignment setpoints to match these spot positions.  When we increased power to 20W, buildups still looked good, so we went ahead and increased further to the full 37W input power but this caused all of our buildups to drop quickly.  Also, the OMC ASC was saturating the OMC suspension(true with the usual QPDs and when I tried to switch over to the dither.  Haven't tried deacon.).  I had the OMC ASC loops open, and I had just started moving the spots around a bit, and we lost lock.  To prevent this, next lock I will try to move spots a bit while we are still at 20W, where the OMC SUS didn't saturate.

Upon trying to reacquire, Patrick noted that the ALS COMM beatnote was lower than normal, around -14dBm (we've been running at about -10dBm, but it really ought to be higher than that.).  We do not usually move PR3, but since the alignment of the IFO changed drastically today Patrick paused the INIT_ALIGN guardian when it was working on the green alignment and moved PR3 to get the COMM beatnote up to -3dBm.  This caused the Xarm IR portion of initial aligment to not catch lock, so I hand-moved PR2 and IM4 to compensate for the PR3 pitch move and then let the ASC take over once the Xarm caught lock. 

Earlier today we were losing lock at CARM_TO_TR because there wasn't enough light on the Yarm QPD_B.  I temporarily had put in CARM_TO_TR to move the carm offset closer to zero than normal, which allowed enough light to hit the Y QPD_B that we could make the transition.  But, after Patrick's recent initial alignment, that was moving us too close to zero so I have once again removed it and the carm offset reduction sequence is back to its normal settings.

Next lock we went to DC readout, and saw that again the POP18 and PR gain buildups were good.  We then went to 20W where I tried for a while to improve the buildups, but was not cery successful.  I did a bit, but not back to our 2W place.  And, these moves put us much closer to the locations that we had been on our test masses.  Kind of disappointing.  I went to 37W and tried a bit more spot moving, but no real changes there.  With these new spots and a small extra OMC QPD offset I was able to leave the OMC ASC engaged on the QPDs without saturating the suspension.  At this point, I am beat.  The IFO is at NomLowNoise, kind of okay range, so we can come back and address remaining issues tomorrow.

Some SDF snapshots:


A few more notes and words on Kara and my work earlier today on moving the TMSX (mentioned in JeffK's alog 50952):  When the IFO was pretty well aligned (Jeff and Niko had moved the arms in soft to get the ADS error signals except PIT3 small), Kara and I noted that both the IR and green QPDs on the TMS were quite far off center in pitch.  So, we pitched the TMS slowly to get the IR QPDs a little better centered, and in parallel moved the green QPD offsets to keep the ALS WFS error signals small.  At some point when we were pretty close, we started running the Kiwamu script that changes the green QPD offsets automatically.  It happens that when the IFO was pretty well aligned, the IR QPDs on TMSY were reasonably well centered, so we left TMSY alone and just reset the Y green QPD offsets.  Thankfully the offsets were happy to go closer to the center of the QPDs, so we avoided having to do any picoing today.

After moving TMSX to recenter the IR QPDs, I have commented out the step in increase_power that put an offset into TMSX pitch alignment.


JeffB has just put us into Observing for the night.  We can work to finish fine tuning the IFO tomorrow.  For tonight, commissioners out.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 13:53, Thursday 01 August 2019 (50964)

I have now propagated these SDF diffs also to the safe / down snapshots.

H1 General
jeffrey.bartlett@LIGO.ORG - posted 00:10, Thursday 01 August 2019 (50956)
Ops Owl Shift Summmary
Ops Shift Transition: 08/01/2019, Owl Shift 07:00 – 15:00 (00:00 -08:00) - UTC (PT)
State of H1: Unlocked
Intent Bit: Corrective Maintenance
Weather:  It is a clear and starry morning. No rain in the forecast, Winds are a Calm to Light Breeze. Temperatures are in the low 70s to mid-60s.  
Primary 0.03 – 0.1Hz: 0.009um/s
Secondary 0.1 – 0.3Hz: 0.03um/s
Outgoing Operator: Patrick
Quick Summary: IFO is unlocked after an earthquake induced lockloss. Jenne has been working with Patrick on relocking.
Displaying reports 39521-39540 of 88987.Go to page Start 1973 1974 1975 1976 1977 1978 1979 1980 1981 End