Vlad, S. Karki
We have generated the new suspension model tags for both ETMs with the updated mass for O3 (LHO alog #49398), updated violin mode frequencies (updated by Rahul). The parameters files can be found here:
svn/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production/h1etmx_options.m
svn/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production/h1etmy_options.m
svn/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production/h1etmx.m
svn/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production/h1etmy.m
The script used to genrate these new tags and the tagged models for each ETMs can be found at the following location:
svn/sus/trunk/Common/MatlabTools/tagsusdynamicalmodel.m
svn/sus/trunk/Common/SusModelTags/Matlab/quadmodelproduction-rev9308_ssmake4pv2eMB5f_fiber-rev8442_h1etmx-rev9880_h1etmx_options-rev9876_released-2019-11-06.mat
svn/sus/trunk/Common/SusModelTags/Matlab/quadmodelproduction-rev9308_ssmake4pv2eMB5f_fiber-rev8442_h1etmx-rev9880_h1etmy_options-rev9876_released-2019-11-06.mat
We have used these newly generated tagged suspenion models to create suspension filter files for both PCALX and PCALY. The newly generated filters differ from the filters currently in the PCAL systems by the amount equal to the change in mass of the ETMs between O2 and O3. This is reflected in the attached plot #1 (PCALX) and #3 (PCALY). Remember, the masses were not updated in the Pcal model during O3A resulting in a small systematic error and the Pcal force coefficient were fudged during the beginning of O3B to reflect the mass change. Once these updated filters are installed, the fudge factor in the Pcal force coefficient will also be removed. Attached plots #2 and #4 make comparison between the new filters to be installed and the MATLAB suspension model filters. They agree with each other at 0.005 % (0.5 hop) level at 100 Hz.
The script used to generate these new filters can be found here:
svn/aligocalibration/trunk/Runs/O3/H1/Scripts/PCAL/checkQuackSUSPcal.m
We plan to install these filters with updated PCAL Simulink model and new MEDM screen during tomorrow's maintenance.
I had a look at three of the locklosses that happened durring ENGAGE_ASC over the weekend.
In all three cases, we were hitting the soft limits on SRC2, and SRC1 Y in the seconds before the locklosses. The error signals of the AS centering loops, DC3+4, are pretty far from 0 at the same times, and there is an oscillation in DHARD at around 4Hz.
One idea to try to untangle what is happening here is to turn off some of the soft limiters, I have edited the guardian for the moment to remove soft limiters on SRC1+ SRC2, as well as INP1.
Business/safety items:
Tuesday Maintenance Activities:
See the attachment for a picture of the whiteboard
Shifter: Adrian Helmling-Cornell
Fellows: Ethan, Vlad
Some highlights for the first week-long DQ shift of O3b:
Full report here
Tyler G. Chris S. The instrument air compressor received different equipment isolation to (hopefully) mitigate noise during operation. The changes made were springs which deflected at a lower weight (approx .830" at 250lbs of load) as well as a soft silicone pad placed between the springs housing and the concrete slab. This task was completed at approx 8:45am
Tagging DetChar & PEM
I have attached the spectrogram of the strain, where you can see the air compressor noise coming through - at first look, it seems it has not gotten better.
8:45 am would make it 16:45 in the attached image (right where the big red bar is).
Just as a heads up, there will be large equipment on site setting up the wind fence poles. The crew will be as calm as they can, but we have already seen some noise caused by these trucks traveling to and from the end station.
Our plan is to stay in Observing unless the noise becomes egregious.
FAMIS11038
Laser Status:
Front End Power is 32.32W (should be around 30 W)
70W Output Power is 69.9W
Front End Watch is GREEN
70W Watch is GREEN
PMC:
It has been locked 5 days, 22 hr 18 minutes (should be days/weeks)
Reflected power = 11.56Watts
Transmitted power = 52.47Watts
PowerSum = 64.03Watts.
FSS:
It has been locked for 0 days 20 hr and 44 min (should be days/weeks)
TPD[V] = 5.025V (min 0.9V)
ISS:
The diffracted power is around 2.4%
Last saturation event was 0 days 20 hours and 44 minutes ago (should be days/weeks)
Possible Issues:
None
TITLE: 11/11 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
Nuc5 (seismic blrms has been having one of its DMT viewers (3-30Hz one) crash a few times during the last two shifts)
Wind Fence deliveries/work scheduled for today, our goal is to stay in OBSERVING during this work.
LOG:
TITLE: 11/11 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 114Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.35 μm/s
QUICK SUMMARY: Trucks on site for the wind fence. They will be doing some work and will be making some noise today. We already see a bit of a drop in the range.
TITLE: 11/11 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 6mph Gusts, 5mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.34 μm/s
Fairly heavy fog out on the drive in (& crystals also visible). useism is steady below the 90th percentile for the last 24+hrs. Winds are calm.
QUICK SUMMARY:
Finally, H1 hasn't dropped out of lock when it saw me driving down the road! (knock on wood!) Just had a GRB alert so almost done standing down for that. H1's been locked 11.5+ hrs.
TITLE: 11/11 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 116Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: locked all shift, SQZ relocked early in shift
LOG:
Just as I was walking out the door, we were dropped out of observing by the squeezer unlocking. The SQZ_LO_LR node was stuck, so I looked at the graph and then requested DOWN and then back to LOCKED. It was still stuck. The issue was that the beam diverter was not open and there was no other side to the conditional checking that. So I opened the beam diverter and then added a notification in that state.
TITLE: 11/11 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 4mph Gusts, 3mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.41 μm/s
QUICK SUMMARY: One lock loss, and then calm after that.
I noticed DIAG_MAIN flashing "BRSX C code has stopped" after we got back to low noise. I looked at the BRS and it all seems to be okay, its just the H1:ISI-GND_BRS_EMTX_CBIT channel that isn't very stable, see attached.
Perhaps coincidence, but in the DIAG_MAIN logs, the last time this happend was after we reached low noise 2 locks ago (~2:30 UTC).
Cause unknown. Seemed to be fast, no signs of a struggle or anything ringing up.
Attempt 1:
Attempt 2:
Attempt 3:
This fast lock loss seems exactly the same as one of the ones from yesterday (alog53122), which we have seen recently. Again, I'm not sure if the squeezer is actually causing the lock loss, but it is one of the only channels I can find doing anything before the lock loss.
Ethan, Adrian, Sheila
A few minutes before Nov 01 2019 20:41:42 UTC, the instrument air compressor was put on isolation springs in order to mitigate scattering in DARM at 35 Hz (see alog 52879). The first attached plot shows when the compressor was placed on springs. The horizontal red line in the figure it set slightly above 35 Hz.
Following up on this a few days later (Nov 6), we see there is still some scattering at 35 Hz that is consistent with the behaviour of the air compressor. This seen in the second attached figure.
Some work could be undertaken to better isolate the compressor and/or locate the coupling site.