TITLE: 06/16 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 20mph Gusts, 7mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY:
TITLE: 06/16 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Busy day of commissioning! See other alogs for details on commissioning activities. H1 is currently relocking automatically and up to TRANSITION_FROM_ETMX.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
15:22 | SAF | LASER HAZARD | LVEA | YES | LVEA is LASER HAZARD | Ongoing |
14:55 | FAC | Kim | MY | N | Technical cleaning | 16:01 |
14:55 | FAC | Nelly | MX | N | Technical cleaning | 15:49 |
14:59 | FAC | Christina | MX, MY | N | Looking for equipment | 16:59 |
15:02 | PEM | Robert | LVEA/CR | - | Shaker measurements | 16:01 |
15:23 | FAC | Randy | MY | N | Checking on forklift battery | 15:52 |
16:02 | VAC | Jordan, Travis | LVEA | - | Isolating HAM1 turbopump | 16:20 |
16:20 | PEM | Robert | LVEA | - | Checking on things | 16:33 |
16:40 | VAC | Jordan | LVEA | - | Valve HAM1 turbopump back in | 16:43 |
16:47 | PCAL | Tony | PCAL | Yes | Serial numbers | 17:16 |
17:48 | AOS | Betsy, visitors | MY | N | 3IFO shipping planning | 18:48 |
20:09 | ISC | Keita, Jennie | OptLab | Local | ISS array work | 23:36 |
20:20 | PEM | Robert | LVEA | - | Sweep LVEA | 20:26 |
20:21 | ISC | Rahul | OptLab | Local | ISS array work | 22:31 |
20:51 | AOS | Betsy, Mitchell, Rick, Jason, visitors | MY | N | 3IFO shipping planning | 23:51 |
21:47 | CAL | Tony | PCalLab | N | Retreiving BNC cable | 21:52 |
22:10 | VAC | Gerardo, Jordan | LVEA | YES | Grabbing leak detector cart | 22:14 |
Ibrahim, Rahul
The first round of B&K test results for BBSS & HRTS were posted in LHO alog 84654 . Now were are presenting the second round of test results after making the following improvements on BBSS - (a) added four side dampers (D1101299), two on each side, (b) two lower structure Y-brace strut - D1900589. Please see figure (IMG_2926) for reference. We have also removed the four optical posts which were earlier attached to the HRTS. Finally we attached four Vibration Absorbers (D1002424) to BBSS.
The B&K test results are attached below as a pdf document. We have taken 9 measurements with different boundary conditions, each of which is explained below. For each case the tri-axis accelerometer was mounted on the BBSS frame (marked as position P1 or P2 here) - X axis is along the longitudinal side of the BBSS, Y axis is the vertical and Z is transverse. For HRTS, it's shown in page 9 of the pdf document.
Test 1a (see page 2): case - BBSS (without HRTS) and no side dampers or Y-brace attached to BBSS, Accelerometer position P1.
Test 1b (see page 3): case - BBSS & HRTS and no side dampers or Y-brace attached to BBSS, Accelerometer position P1.
Next ,side dampers and Y-brace attached.
Test 2a (see page 5): case - BBSS & HRTS with side dampers and Y-brace attached to BBSS (No Vibration Absorbers), Accelerometer position P1. Hammer hits on the center of the structure.
Test 2b (see page 6): case - BBSS & HRTS with side dampers and Y-brace attached to BBSS (No Vibration Absorbers), Accelerometer position P2. Hammer hits on the center of the structure.
Test 3 (see page 7): case - BBSS & HRTS with side dampers and Y-brace attached to BBSS (No Vibration Absorbers), Accelerometer position P1. Hammer hits on the side of the structure (left or right).
Test 4 (see page 8): case - BBSS & HRTS with side dampers and Y-brace attached to BBSS (No Vibration Absorbers), Accelerometer position P2. Hammer hits on the side of the structure (left or right).
Test 5 (see page 9): case - BBSS & HRTS with side dampers and Y-brace attached to BBSS (No Vibration Absorbers), Accelerometer attached to HRTS. Hammer hits on HRTS.
Next ,side dampers Y-brace and Vibration Absorbers attached.
Test 6a (see page 11): case - BBSS & HRTS with side dampers, Y-brace attached to BBSS and Vibration Absorbers, Accelerometer position P1. Hammer hits on the center of the structure (X axis or longitudinal direction).
Test 6b (see page 12): case - BBSS & HRTS with side dampers, Y-brace attached to BBSS and Vibration Absorbers, Accelerometer position P1. Hammer hits on the center of the structure (Y axis or vertical direction).
Test 6c (see page 13): case - BBSS & HRTS with side dampers, Y-brace attached to BBSS and Vibration Absorbers, Accelerometer position P1. Hammer hits on the center of the structure (Z axis or transverse direction).
Test 7a (see page 14): case - BBSS & HRTS with side dampers, Y-brace attached to BBSS and Vibration Absorbers, Accelerometer position P1. Hammer hits on the side of the structure (X axis or longitudinal direction).
Test 7b (see page 15): case - BBSS & HRTS with side dampers, Y-brace attached to BBSS and Vibration Absorbers, Accelerometer position P1. Hammer hits on the side of the structure (Y axis or vertical direction).
Test 7c (see page 16): case - BBSS & HRTS with side dampers, Y-brace attached to BBSS and Vibration Absorbers, Accelerometer position P1. Hammer hits on the side of the structure (Z axis or transverse direction).
Test 8a (see page 17): case - BBSS & HRTS with side dampers, Y-brace attached to BBSS and Vibration Absorbers, Accelerometer position P2. Hammer hits on the center of the structure (X axis or longitudinal direction).
Test 8b (see page 18): case - BBSS & HRTS with side dampers, Y-brace attached to BBSS and Vibration Absorbers, Accelerometer position P2. Hammer hits on the center of the structure (Y axis or vertical direction).
Test 8c (see page 19): case - BBSS & HRTS with side dampers, Y-brace attached to BBSS and Vibration Absorbers, Accelerometer position P2. Hammer hits on the center of the structure (Z axis or transverse direction).
Test 9a (see page 20): case - BBSS & HRTS with side dampers, Y-brace attached to BBSS and Vibration Absorbers, Accelerometer position P2. Hammer hits on the side of the structure (X axis or longitudinal direction).
Test 9b (see page 21): case - BBSS & HRTS with side dampers, Y-brace attached to BBSS and Vibration Absorbers, Accelerometer position P2. Hammer hits on the side of the structure (Y axis or vertical direction).
Test 9c (see page 22): case - BBSS & HRTS with side dampers, Y-brace attached to BBSS and Vibration Absorbers, Accelerometer position P2. Hammer hits on the side of the structure (Z axis or transverse direction).
The raw data (.csv files) generated by the B&K software are stored at the following location,
/ligo/home/rahul.kumar/Desktop/scripts/bnk_csv_files
Ryan S., Elenna
Thge MOVE_SPOTS state is taking 13 minutes (!) to complete, because the YAW3 ADS DOF is very far off and taking a significant time to converge. Both Jenne and I have found that bumping up the YAW3 gain (PRM yaw) slowly helps converge the loops much faster.
Ryan kindly helped me update the state code to slowly increase the gain if the convergence is taking too long. We added a new timer 'ADS', that waits for one minute after the new A2L gains are ramped (so an additional minute after the 2 minute ramp time of the A2L gains). If, after that first minute, there is still no convergence, then the YAW3 gain is doubled. After that, the 'ADS' timer waits 2 minutes, and again doubles the gain. This process can happen up to three times, which should increase the YAW3 gain to a maximum value of 8. Jenne and I have found that the gain can go as high as 10 in this state. The two minute waits give the other ASC, like SRC1 and INP1 Y time to converge as the ADS pulls the PRM in faster. Once the convergence checker returns true, the YAW3 gain is set back to 1.
We will monitor how this proceeds on this locking attempt. I updated the guardian notify statements so it states when the gain is increased.
This was a sucess- this run through took only 7 minutes. I am shortening the 2 minute wait before increasing the gain to 90 seconds. If that still works, maybe we can go to 60 seconds.
To be more specific, the first attempt as described above meant the state took 6 minutes, 50 seconds. I loaded the change to reduce the wait time from 120 to 90 seconds, which only shortened the state length to 6 minutes, 30 seconds. The gain was only ramped to 8 for a very short period of time. I still think we can make this shorter, which we can do by making that wait time 60 seconds, and maybe taking bigger steps in the gain each time. However, we are still in the RCG upgrade, so I will hold off on changes to the guardian for now.
YAW3 is still limiting the length of the state. In this morning's relock, YAW3 convergence took nearly an additional minute more than the other loops. Once we have caught YAW3 up to everything else, we could make the state even shorter by raising the gain of other ADS loops. Two minutes of the state are taken up in the ramp of the A2L gain, so it is taking an additional 4 minutes, 30 seconds to wait for loop convergence.
Now it seems that PIT3 is taking too much time to converge, so I updated the guardian to also increase the PIT3 gain in the same way.
Lockloss @ 21:56 UTC after 3 hrs locked - link to lockloss tool
Massive ETMX glitch. Now taking the time to reconcile SAFE SDFs before the RCG upgrade tomorrow.
In preparation for the RCG upgrade, we are using the relocking time to reconcile SDF differences in the SAFE file.
Here are some of mine:
I have also determined that the unmonitored channel diffs in the LSC, ASC, and OMC models are guardian controlled values and do not need to be saved.
Not accepting or reverting the h1sqz, h1ascsqzfc, or slow controls cs_sqz sdfs, attached. As these have the same observe and safe files.
Accepted H1:TCS-ETMX_RH_SET{LOWER,UPPER}DRIVECURRENT as ndscope-ing shows they are normally at this value.
Some of these SDFs may have then led to diffs in the OBSERVE state. I have reverted the roll mode tRamp, and accepted the OSC gains in the CAL CS model.
I updated the OPTICALIGN OFFSETs for each suspension that we use those sliders on. I tried using my update_sus_safesnap.py script at first, but even though it's worked one other time in that past, it was not working anytime I tried using it on more than one suspension at a time (it seems like it was only doing one out of each suspension group). I ended up being able to get them all updated anyway eventually. I'm attaching all their sdfs and will be working on fixing the script. Note that a couple of the ETM/TMS values might not match thesetpoint exactly due to the screenshots happening during relocking and after they had moved a bit with the WFS
All looks well, aside from the known issue with LAB2 and LVEA5 seems frozen, I'll investigate that tomorrow during maintenance.
LVEA5 being off is expected, it's a pumped dust monitor so we turned it off for observing.
Closes FAMIS37206, last checked in alog84428
HEPI pump trends look mostly normal, HPI-PUMP_LO_CONTROL_VOUT has dropped slightly (~30).
A single blank line was added to the end of the filter file for H1SUSAUXEX to test whether the IFO can enter the OBSERVE state with unloaded filter changes.
If loaded, this change would have no effect on the behavior of the filters.
Alenna noted that we will have CP-Y spots on the ballast baffle even when the CP is propertly aligned (which is why we eventually want to remove/fix the baffle), so I swept the CP in pitch and yaw and found a minimum in scatter coupling at about -300 p, 300 y. The varying noise from the pump on HAM1 interfered with the measurement, so I think I can further minimize the coupling once the pump is off.
Accepted in SAFE and OBSERVE SDF tables as Robert left them. This new position has been causing ITMY saturations during LOWNOISE_COIL_DRIVERS due to the increased drive from the DAC, but this doesn't seem to be causing any noticeable locking issues.
Oli, Camilla, Sheila, RyanS
It was pointed out (84972) that our new SRCL offset is too big at the beginning of the lock, affecting the calibration and how well we are squeezing. Camilla had the idea of taking the unused-but-already-set-up THERMALIZATION guardian and repurposing the main state so it steps LSC-SRCL1_OFFSET from the LSC-SRCL1_OFFSET value at the end of MAX_POWER to the official offset value given in lscparams (offset['SRCL_RETUNE']). This stepping starts at the end of MAX_POWER and goes for 90 minutes. Here is a screenshot of the code.
To go with this new stepping, we've commented out the line (~5641) in ISC_LOCK's LOWNOISE_LENGTH_CONTROL (ezca['LSC-SRCL1_OFFSET'] = lscparams.offset['SRCL_RETUNE']) so that the offset doesn't get set to that constant and instead keeps stepping.
To get this to run properly while observing, we did have to unmonitor the LSC_SRCL1_OFFSET value in the Observe sdf (sdf).
Attached is a screenshot of the grafana page, highlighting the 33 Hz calibration line, which seems to be the most sensitive to thermalization. Before, when the SRCL offset was set static, it appears that the 33 Hz line uncertainty starts at about 1.09 and then decays down to about 1.02 over the first hour. With the thermalization adjustment of the SRCL offset from 0 to -455 over one hour, the 33 Hz uncertainty starts around 0.945 and then increases to 1.02 over the first hour. Seems like we overshot in the other direction, so we could start closer to -200 perhaps and move to -455.
We decided to change the guardian so that it starts at -200 before then stepping its way up to -455 over the course of 75 minutes instead of 90 minutes.
With the update to the guardian to start at -200, each calibration line uncertainty has actually stayed very flat for these first 30 minutes of lock (except for the usual very large jump in the uncertainty for the first few minutes of the lock).
This shows the entire lock using the thermalization guardian with the SRCL offset ramping from -200 to -455, The line uncertainty holds steady the entire time within 2-3%!
WP12620 TW0 offload
The file copy to permanent archive ran from Fri 09:25 - Sat 10:42 (25hrs 07mins).
This morning, when H1 was out-of-lock and with the operator's permission I restarted NDS0 with its new daqdc file.
At 10:06 I started the deletion of the old files on h1daqtw0 in nice mode. Starting SSD-RAID disk usage was 92%.
Deletion completed at 12:08 (took 2hrs 3mins). This completes WP12620.
Sheila, Elenna, Camilla
Sheila was questioning if something is drifting for us to need an initial alignment after the majority of relocks. Elenna and I noticed that BS PIT moves a lot both while powering up /moving spots and while in NLN. Unsure from the BS alignment inputs plot what's causing this.
This was also happening before the break (see below) but the operators were similarly needing more regular initial alignments before the break too. 1 year ago this was not happening, plot.
These large BS PIT changes began 5th to 6th July 2024 (plot). This is the day shift from the time that the first lock like this happened 5th July 2024 19:26UTC (12:26PT): 78877 at the time we were doing PR2 spot moves. There also was a SUS computer restart 78892 but that appeared to be a day after this started happening.
Sheila, Camilla
This reminded Sheila of when we were heating a SUS in the past and causing the bottom mass to pitch and the ASC to move the top mass to counteract this. Then after lockloss, the bottom mass would slowly go back to it's nominal position.
We do see this on the BS since the PR2 move, see attached (top 2 left plots). See in the green bottom mass oplev trace, when the ASC is turned off on lockloss, the BS moves quickly and then slowly moves again over the next ~30 minutes, do not see simular things on PR3. Attached is the same plot before the PR2 move. And below is a list of other PR2 positions we tried, all the other positions have also made this BS drift. The total PR2 move since the good place is ~3500urad in Yaw.
To avoid this heating and BS drift, we should move back towards a PR2 YAW of closer to 3200. But, we moved PR2 to avoid the spot clipping on the scrapper baffle, e.g. 77631, 80319, 82722, 82641.
I did a bit of alog archaeology to re-remember what we'd done in the past.
To put back the soft turn-off of the BS ASC, I think we need to:
Camilla made the good point that we probably don't want to implement this and then have the first trial of it be overnight. Maybe I'll put it in sometime Monday (when we again have commissioning time), and if we lose lock we can check that it did all the right things.
I've now implemented this soft let-go of BS pit in the ISC_DRMI guardian, and loaded. We'll be able to watch it throughout the day today, including while we're commissioning, so hopefully we'll be able to see it work properly at least once (eg, from a DRMI lockloss).
This 'slow let-go' mode for BS pitch certainly makes the behavior of the BS pit oplev qualitatively different.
In the attached plots, the sharp spike up and decay down behavior around -8 hours is how it had been looking for a long time (as Camilla notes in previous logs in this thread). Around -2 hours we lost lock from NomLowNoise, and while we do get a glitch upon lockloss, the BS doesn't seem to move quite as much, and is mostly flattened out after a shorter amount of time. I also note that this time (-2 hours ago) we didn't need to do an initial alignment (which was done at the -8 hours ago time). However, as Jeff pointed out, we held at DOWN for a while to reconcile SDFs, it's not quite a fair comparison.
We'll see how things go, but there's at least a chance that this will help reduce the need for initial alignments. If needed, we can try to tweak the time constant of the 'soft let-go' to further make the optical lever signal stay more overall flat.
The SUSBS SDF safe.snap file is saved with FM1 off, so that it won't get turned back on in SDF revert. The PREP_PRMI_ASC and PREP_DRMI_ASC states both re-enable FM1 - I may need to go through and ensure it's on for MICH initial alignment.
RyanS, Jenne
We've looked at a couple of times that the BS has been let go of slowly, and it seems like the cooldown time is usually about 17 minutes until it's basically done and at where it wants to be for the next acquisition of DRMI. Attached is one such example.
Alternatively, a day or so ago Tony had to do an initial alignment. On that day, it seemed like the BS took much longer to get to its quiescent spot. I'm not yet sure why the behavior is different sometimes.
Tony is working on taking a look at our average reacquisition time, which will help tell us whether we should make another change to further improve the time it takes to get the BS to where it wants to be for acquisition.
We had to accept some SDFs to get into Observing.
00:01 UTC Observing
Putting these here as well.
I think these diffs result from errors in our safe SDFing from earlier.