Earlier today I took data for redoing the MICH and SRCL feedforward filters, following my instructions from alog 47185.
* Measured MICH FF with both mich and srcl ff off
* Turned on mich ff (feb 28 filter), then measured Srcl ff.
I apparently don't actually understand the nuances of the fitting scripts as well as I thought, so I haven't actually created new filters. I checked the current coherences of MICH and SRCL with DARM, and they are both quite low (1e-2 level), so they're already fine for now anyway.
Note that the PRCL coherence is still around 5e-2, so we will want to address this. Hopefully it'll be fixed by the TCS tuning to minimize frequency noise coupling, but if that doesn't work, we may need to consider using the PRCL FF filters.
I am accepting things in SDF, so that we can go to Observe.
Why does IMC-MCL_FM_TRIG_THRESH_[ON/OFF] change? This filter bank isn't in use after we acquire lock, so it shouldn't matter. I've reverted to the value that was in both the safe and observe snap files.
We are also leaving on several lines, for monitoring overnight. Dan's script will kill these if we lose lock. This does, however, mean that we are *ignoring* excitations in the LSC and ISS models. We will revert these to being monitored when we are done with this test, end of next week at the absolute latest (i.e. before O3).
To make this work, Dan has made some changes to the TCS guardian, that we likely want to keep anyway. Also, in order to prevent dropping out of Observe, we've not-monitored the CO2 rotation stage go-to-power buttons.
To help us remember what things must be undone before the actual observing run, we have made a large note on the whiteboard in the control room. As is noted on it, please don't erase this note until these things have been done.
To adjust the CO2 powers tonight while also remaining in observation mode I have told the TCS guardian not to change the CO2 levels when we are in nominal low noise. The new state looks like this:
class PRE_HEATING(GuardState):
"""Idle state that can go to ADJUSTING_POWER
if the IFO power is changed. Uses a range window
so that the CO2 power isnt adjusting power constantly.
"""
index = 5
@fault_checker
def run(self):
# Check if the current CO2 power is within
# some range of where it should be.
isc_lock_state = ezca[':GRD-ISC_LOCK_STATE_N']
# Don't adjust CO2 powers whilst in nominal low noise
if is_co2_out_of_range() and isc_lock_state != 600:
return 'ADJUSTING_POWER'
else:
return True
Lines that are running [Hz]:
These are run using the script /opt/rtcds/userapps/release/isc/h1/scripts/run_lines.py
This script will start and watch the ISC_LOCK guardian state, if we leave state 600, nominal low noise, then it will switch off the lines and close the excitation points:
LSC-OUTPUT_MTRX_11_9
LSC-MOD_RF9_AM_EXCITATIONEN
LSC-REFL_SERVO_COMEXCEN
If the script is left running it will wait until we are back in state 600 and ramp the lines on and switch on the excitation points above.
It is currently running on a terminal on ZOTWS21, workspace 1.
The OPS Overview FOM that displays the Observatory Mode is displaying only a white box when Observing is selected as the mode. See screenshot.
Commissioning at 1:03 UTC. Dropped out due to TCS fiddling.
Back to Observing 1:06 UTC.
Commissioning at 1:09 UTC due to SQZ unlocking.
Back to Observing at 1:13 UTC.
Commissioning at 1:18 UTC then back to Observing at 1:20 UTC.
Commissioning at 1:25 UTC.
Observing at 1:27 UTC.
Commissioning at 1:29 UTC.
Observing at 1:34 UTC.
Commissioning at 1:35 UTC.
Observing at 1:36 UTC.
Commissioning at 1:39 UTC.
Observing at 1:41 UTC.
Then back to Commissioning at 0:44 due to SQZ Guardian.
Sheila exported our currently-in-use inverse sensing filter, and checked it into the svn. It is at: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/Foton/2019-03-16_H1CALCS_InverseSensingFunction_Foton_SRCD-2N_Gain_tf.txt
We exported the D2N filter, but not the actual gain filter, which has a gain of the order 1e-7.
In the attached figure, I plot the February filter versus the new one. I have imported the .txt files to make these plots, so we're pretty sure that we've exported the correct filters.
FRS12545.
If any of the component HnEPICS_*.ini files used by h1edc to create its full channel list are modified, the CRC bit in h1edc's STATE_WORD will turn red, and its MSGDAQ will report "Modified file detected". In the same way as for real-time front end models, this indicates that a h1edc and DAQ restart is necessary to add/remove the new slow channels to the DAQ.
I wrote a bash script (h1edc_generate_daq_ini_file.bsh) which generates the H1EDC.ini file in exactly the same way h1edc does when it is started. The script runs every minute, as a controls cronjob on h1fescript0. If a modified H1EDC.ini file is generated, the original is archived and the file is updated. The h1edc model then detects the CRC change of this file and raises the CRC condition.
Attached snippet of the CDS overview shows the CRC bit (green square). Note the DAQ bit and DAQ-CRC are still blank until h1edc is added to the DAQ tomorrow.
TITLE: 03/18 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: None
SHIFT SUMMARY:
LOG:
15:54 FIl into CER
16:00 Meeting
16:33 LVEA Sweep - Richard, Betsy, Jenne, and DS
17:15 Robert, Kara, and Sharan out to LVEA - coil
17:30 LVEA Sweep done
17:56 Robert, Kara, and Sharan back
18:22 Dave Barker restarted h1edcu (CDS Overview)
18:35 Patrick and Sheila out to LVEA - ISCT1
19:03 Sheila and Patrick back
19:16 Kara, Sharan, and Robert out to LVEA
20:28 Lockloss - maybe due to PEM group activity in the LVEA
21:56 NLN 96.3Mpc
Ed, Sheila, Jenne, Patrick
We locked at 35W this morning following work done last night reported in 47606 and comments.
We didn't go to observing, instead PEM injections went ahead, but we tried to do some checks that will make it easier to go into observing soon.
This morning, Daniel, Richard, Jenne, and I performed a sweep of the LVEA in prep for logging some ER14 Observation Mode overnight this week. We did not prep everything for O3 since this and next week are still heavy in PEM injection and Calibration work which need equipment plugged into lots of places. We also DID NOT do the end stations since we have quite a few Tuesday Maint items at the end stations tomorrow and will perform the list then. The checklist item status after the morning sweep is as follows:
Items which required attention this morning, or are noted here as being the configuration for future sweeps:
IN COMPUTER ROOM
NEAR H1 PSL and RACKS
NEAR HAM2/3 RACKS
NEAR Y-arm Manifold
NEAR H2 PSL enclosure
NEAR HAM6 SQZ area
Here are the same trends created with NDSCOPE. Zooming out automatically shifts to Minute trends and adds the min and max. There isn't a way to turn these traces off currently. The background can be reversed to white. I personally find the black background easier on the eyes.