TITLE: 12/12 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 10mph Gusts, 8mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.30 μm/s
QUICK SUMMARY:
In Observing and Locked for 16 hours. useism is starting to head back up.
TITLE: 12/11 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Not much
Dave restarted the MC3 camera server and brought back said camera, that has been blue over the weekend at 17:04UTC.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 16:51 | FAC | Karen | Optics lab | N | Tech clean | 17:08 |
| 17:16 | FAC | Karen | MidY | N | Tech Clean | 17:55 |
| 18:07 | SQZ | Nutsinee | Optics lab | N | Parts search | 18:23 |
| 18:48 | FAC | Kim, Karen | Clean storage area by CER | N | Inventory | 19:28 |
| 19:07 | TCS | Camilla | Optics lab | N | Tool investigation | 19:37 |
| 21:03 | VAC | Janos | Mids | N | VAC checks | 21:26 |
| 21:39 | VAC | Travis | Optics lab | N | Look for a hotplate | 21:45 |
I've taken the SUS_CHARGE node to DOWN so that the automatic in-lock charge measurements don't run before tomorrow morning's Tuesday maintenance time (and I can confirm that doing this does not take H1 out of observing). To re-enable the automated in-lock charge measurements, the SUS_CHARGE node should be requested to INJECTIONS_COMPLETE before next Tuesday.
This is a big-picture overview of combs in recent months.
"Relative priority" is a new metric documented in G2302324 (Athena Baches, Abby Wang, and Nick Baker). It is not finalized-- in fact these values differ slightly from the version in the linked presentation due to bug fixes-- and should be understood as (a) having arbitrary units, (b) reflecting the general importance of spectra artifacts to CW searches, and (b) being useful only for comparing artifacts in similar data sets-- for example, it should not be used to compare artifacts from monthly spectra and ones from weekly spectra. In this case it is used to compare and rank combs across monthly spectra.
Monthly August, October, and November Fscan spectra and their auto-generated lines lists were used. I skipped September because I still need to troubleshoot some issues with the lines list for that month.
Color-coding and letter labels convey identical information.
| A | |
| B |
1.66 Hz comb related to OM2 heater driver and variations which appeared during testing in October. Now mitigated. (72967)
|
| C | |
| D |
near-30 Hz comb. Cause unknown.
|
| E |
set of near-100Hz combs with various offsets. Cause unknown
|
| no tag |
Entries that are not persistent over multiple months.
|
| Ranking | Comb spacing | Comb offset | Relative priority | Label |
| 1 | 9.47425 | 0 | 46 | A |
| 2 | 9.47539 | 0 | 45 | A |
| 3 | 1.6611234 | 0 | 44 | B |
| 4 | 9.480545 | 9.48 | 39 | A |
| 5 | 4.9842174 | 0 | 22 | C |
| 6 | 29.969515 | 0 | 17 | D |
| 7 | 99.998456 | 70.029 | 5 | E |
| 8 | 6.64457 | 1.659 | 5 | |
| 9 | 99.99846 | 29.9695 | 5 | E |
| 10 | 99.99864 | 0 | 5 | E |
| 11 | 99.99844 | 89.909 | 2 | E |
| 12 | 99.99846 | 0 | 2 | E |
| 13 | 199.9969 | 10.09 | 1 | E |
| Ranking | Comb spacing | Comb offset | Relative priority | Label |
| 1 | 9.475416 | 0 | 43 | A |
| 2 | 9.474265 | 0 | 43 | A |
| 3 | 9.48057 | 0 | 42 | A |
| 4 | 9.480574 | 0 | 39 | A |
| 5 | 0.996787 | 0 | 32 | C |
| 6 | 4.98425 | 0 | 30 | C |
| 7 | 1.10864403 | 0 | 23 | B |
| 8 | 29.969514 | 0 | 15 | D |
| 9 | 1 | 0 | 6 | |
| 10 | 99.99846 | 29.9694 | 5 | E |
| 11 | 99.998644 | 0 | 5 | E |
| 12 | 99.99846 | 70.029 | 4 | E |
| 13 | 99.99845 | 10.09 | 2 | E |
| 14 | 99.99845 | 0 | 2 | E |
| Ranking | Comb spacing | Comb offset | Relative priority | Label |
| 1 | 9.47429 | 0 | 47 | A |
| 2 | 9.4754423 | 0 | 34 | A |
| 3 | 9.480612 | 0.0003 | 34 | A |
| 4 | 9.475456 | 9.4748 | 33 | A |
| 5 | 0.996785 | 0 | 32 | C |
| 6 | 4.984252 | 0 | 29 | C |
| 7 | 29.96951 | 0 | 15 | D |
| 8 | 28.44192 | 9.48 | 8 | |
| 9 | 0.12332754 | 0.1166 | 8 | |
| 10 | 0.1233334 | 0.0614 | 7 | |
| 11 | 47.4031 | 28.4417 | 6 | |
| 12 | 1 | 0 | 6 | |
| 13 | 99.998458 | 70.029 | 4 | E |
| 14 | 99.99846 | 29.9694 | 4 | E |
| 15 | 99.99844 | 0 | 2 | E |
| 16 | 99.99844 | 89.9088 | 2 | E |
| 17 | 8.426278 | 5.5594 | 1 |
FAMIS 20006
Between roughly 6 and 4 days ago, the regular temperature spikes seen in the control boxes, diode room, and chiller room readbacks stopped, meaning the temperatures there were more stable for that time. This does not seem to have had an effect on laser perfomance that I can see. I have yet to find a cause of this; maybe a fan in the chiller/diode room area was changed? Whatever changed, it was undone ~4 days ago and the behavior of these temperature channels has returned to normal.
The PMC temp output jumped up by about 0.3 about 3 days ago; unsure yet as to why.
Mon Dec 11 10:04:58 2023 INFO: Fill completed in 4min 55secs
Travis confirmed a good fill curbside.
Full Week DQ report is written here: DQ12/4-12/10
Notes:
Thank you for the opportunity as the shifter
The MC3 camera image has been down since 12:10 Fri 08dec2023 PST. There was nothing wrong with the camera, it just needed a restart of the h1cam12 server process on h1digivideo1. I killed the process and let monit restart a new one.
TITLE: 12/11 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Austin
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 11mph Gusts, 9mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.22 μm/s
QUICK SUMMARY:
TITLE: 12/11 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Austin
SHIFT SUMMARY: Just got back into Observing at 07:59UTC after relocking. Two locklosses during my shift, but both were quick to recover from. SEI_CONF is back to WINDY since USEISM is down.
LOG:
00:00UTC Detector Observing and Locked for 17.5 hours
00:47 Lockloss (74725)
-- Relocking --
00:58 Manually aligned green arms, and then started an Initial Alignment
01:21 Initial Alignment completed, relocking
- Watched ISC_LOCK log, ADS, and saturation overview screen closely between LOWNOISE_COIL_DRIVERS and LOWNOISE_LENGTH_CONTROL in case we lost lock during TRANSITION_FROM_ETMX, but we were fine
02:00 NOMINAL_LOW_NOISE
-- Relocking End --
02:06 Observing
04:10 Changed SEI_CONF to WINDY due to lowering useism
- Went into the SEI_ENV code beforehand and swapped the SEI_CONF nominal states back to WINDY and EARTH_QUAKE from USEISM and USEISM_EARTHQUAKE(see 74727).
00:47 Lockloss (74728)
-- Relocking --
07:18 Earthquake mode activated due to incoming earthquake from Tonga
07:28 Back to CALM
07:55 NOMINAL_LOW_NOISE
-- Relocking End --
07:59 Observing
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 01:00 | PEM | Robert | LVEA | Y | Turn off laser vibrometer | 01:18 |
Lockloss 12/11 @ 06:46UTC due to sudden nearby ground motion
Also Verbals just announced an incoming 6.1 earthquake from Tonga, so I will attempt to get us back up but we might lose lock on the way up due to the earthquake.
Observing at 160Mpc and have been Locked for 2 hours. Relocking after the lockloss (74725) went quickly, and ITMY5/6 are still damping well with Ryan C's new gain settings(74721)!
04:10UTC Secondary microseism is now consistantly below 0.8 um/s(ndscope), so I just went into the SEI_ENV code and swapped the SEI_CONF nominal states back to WINDY and EARTH_QUAKE from USEISM and USEISM_EARTHQUAKE(screenshot of change). I then changed SEI_CONF to WINDY.
Lockloss 12/11 00:47UTC for unknown reasons. EX saturation right before lockloss, and the light on the MC_REFL camera got much brighter than I had ever noticed before.
02:06UTC Observing
TITLE: 12/11 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.29 μm/s
QUICK SUMMARY:
Detector Locked for 17.5hours and Observing. I'll keep an eye on the new violin settings.
TITLE: 12/10 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Quiet day, locked for 17:30 as of 0:00UTC.
I've finally found some settings that seem to work nicely for ITMY modes5/6, FM6+FM7+FM10 G= +0.02. They're trending down on broad, and narrow monitor filters, and on DTT. Tagging SUS
21:29UTC GRB-Short E458001
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 16:31 | FAC | Richard | CP1 | N | Grab the van | 16:36 |
| 21:00 | FAC | Richard | CP1 | N | Plug in van | 21:10 |
STATE of H1: Observing at 159Mpc
I used most of todays commissioning time for shaking and laser vibrometry to inform plans for the break. I replaced the MC3 camera over the viewport I had been using but couldnt get it to work. We will have to revisit it on a Tuesday.
The MC3 camera was brought back by Dave restarting the camera's server. alog74734
TJ, Ansel, Dave, Camilla
After finding that 1Hz and 5Hz DARM combs were caused by HWS camera sync frequency in 74617, we've turned off all HWS at 21:00UTC so we can check that nothing else from HWS is effecting DARM.
Stopped all HWS code (ETMY was already off 73915). Tuned off all cameras and RCX CLinks. Turned off the ITM SLEDs, ETMX laser will still be on but was tested in 69648 not to effect DARM.
As long as the computers aren't restarted I think that the H1:TCS-E{OPTIC}_HWS_ channels will remain reading their last values, if not Dave might need to "green-up" the CDS overview.
I temporarily took out the DIAG_MAIN notifications for all HWS. We will have to remember to put them back in though when we are done turning them on and off.
Unfortunately the 7 Hz comb is still present in DARM (figure 1) and in the magnetometer channel where we were tracking it (figure 2).
Extra: just to check that this really is a 7 Hz comb that started after the camera sync frequencies were moved to 7 Hz on Dec 5 (74617), and not something pre-existing, I re-plotted the magnetometer data for the time period when both were set to 5 Hz. This time period avoids any obscuring effects of the 1 Hz comb in magnetometer data. (The 1 Hz comb is much weaker than 7 Hz in DARM so it shouldn't really be an issue, but in the magnetometer data both are clear and there's a little more ambiguity there-- and anyway it's easy to check.) Indeed, no sign of 7 Hz during that hour except at frequencies that are also 5 Hz multiples (figure 3).
I put modified HWS() notifications back into DIAG_MAIN now Dave has a running script that turns the HWS camera/code off within 60 seconds of ISC_LOCK reaching state 580 and on within 60s of IFO being DOWN 74951. DIAG_MAIN may give the warning 'HWS code stopped for ITMX / HWS code stopped for ITMY' as soon as we loose lock for up to 60s, if this is annoying, we can make DIAG_MAIN cleverer. svn link
We requested INJECTIONS_COMPLETE so this node is back in it's nominal configuration and will run injections next Tuesday at 7:45am.