TITLE: 06/10 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 137Mpc
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 7mph Gusts, 5mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY:
17:21 UTC a tour group came through the control room.
Confirmed a slow Climb in IMY Mode5. Gain H1:SUS-ITMY_L2_DAMP_MODE5_GAIN was set at -0.04 and I changed it to 0.
Looking at alog 70057 https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=70057 I will try a gain of +0.01
Lockloss 19:50 UTC of unknown cause.
Locking Summary:
No Initial alignment was done before trying to lock again.
DRMI 1f didn't lock but i let it go to Aquire PRMI which then locked and we went on up.
NOMINAL_LOW_NOISE Reached at 21:04 UTC
Intention bit set to Observing 21:09 UTC.
Violin Modes:
ITMY mode 8 is increasing again. I will take the gain to 0 then then up to +0.04 as described in the following alog.
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=70057
That singular change of gain did not make any difference, but taking the gain back to 0 then turning on FM7 which is a -30 deg phase change then bringing the gain back up to 0.04 did start bringing ITMY Mode 5 down. Tagging SUS
IFO Current Status: NOMINAL_LOW_NOISE & Observing
TITLE: 06/10 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 135Mpc
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 8mph Gusts, 4mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY:
- SEI/DM/CDS ok
- H1 is locked and in observing as of 21:04 UTC
The first attachment shows the distribution of data during O3, ordered by how long into a high-power lock stretch the data were taken. High-power lock segments were identified by either H1:GRD-LASER_PWR_OK:1 or L1:GRD-PSL_OK:1. Solid lines show the data during observing mode only ([HL]1:DMT-ANALYSIS_READY:1); dashed lines show all data accumulated during high-power operation.
Half of observing-mode data were accumulated within the first 9 hours of lock, a third of data were accumulated within the first 6 hours of lock, and a fifth of data were accumulated within the first 3 hours of lock. The distributions are remarkably similar between H1 and L1, and so far, L1's distribution for the first few weeks of O4 seems similar to the distributions for O3.
The second attachment shows the distribution of data during O3, ordered just by total lock length (i.e., without regard to how far into a particular lock stretch the data were taken). Half of observing-mode data were accumulated during locks of more than 20 hours.
Lockloss occured at 19:50 UTC:
Lockloss select URL : https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1370461864
Cause currently unknown, awaiting analysis.
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 2mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.08 μm/s
Sat Jun 10 10:11:44 2023 INFO: Fill completed in 11min 43secs
TITLE: 06/10 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 138Mpc
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY:
Current IFO Status: NOMINIAL_LOW_NOISE and OBSERVING for 6+ hours.
TITLE: 06/10 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 140Mpc
SHIFT SUMMARY: Mostly quiet shift after relocking and riding out earthquakes.
Handing off to Tony for the day.
LOG:
No log for this shift.
H1 has relocked and is Observing as of 08:37 UTC. There was one SDF diff on the CALEX model when we reached NLN regarding a PCal X OSC time ramp that appears to have been changed at the time of last lockloss. Since this is just a time ramp, it seemed harmless enough to revert it, which I did (tagging CAL, screenshot attached).
TITLE: 06/09 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 136Mpc
SHIFT SUMMARY:
- IFO was stable and locked up until the end of my shift, passing H1 to Ryan with the IFO relocking
- Lock #1:
LOG:
No log for this shift.
TITLE: 06/10 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 10mph Gusts, 8mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY: Taking over from Austin. H1 lost lock @ 06:53 just before handoff; looks like an ASC ringup at 0.45Hz. Currently relocking ALS.
LOCKLOSS @ 6:53, looking at the lockloss select, potentially movement in CSOFT P, potentially INP1 P/Y and DHARD Y - scope attached - Tagging ISC
H1 has been locked for just over 5 hours. There has been a couple of DCPD and EX saturations alongside what looks to be CHARD P ringups, but the IFO looks to have stabilized.
Picket Fence was updated to replace the seismometer used on the channel 1 stream, which had not been working for some time.
Following up on EJ's alog, I have extended the code to check if the unresponsive filter is under local control by the model. I ran it this afternoon while H1 was in observe, running in 'nice' mode so as to not hammer the frontends with CA requests (delays between requests).
If we disregard locally controlled filters, the number of unresponsive filters is reduced to 3 (see attached). The top one runs on h1lsc, the other two on h1lscaux.
Here is the full list, with locally controlled filters marked with *
Total numer of filtermodules = 13367
num unresponsive 14
h1lsc {'LSC-EXTRA_AI_2': 'FM2 '}
h1lscaux {'LSC-LOCKIN_1_DEMOD_9_I': 'FM1 ',
'LSC-LOCKIN_1_DEMOD_9_Q': 'FM1 '}
h1sqz {'SQZ-RLF_VCXO_SERVO': 'FM2* '}
h1alsex {'LSC-X_ARM_DRIVE': 'FM3* FM5* '}
h1alsey {'LSC-Y_ARM_DRIVE': 'FM3* FM5* '}
h1sussqzin {'SUS-ZM1_M2_COILOUTF_LL': 'FM1* FM6* ',
'SUS-ZM1_M2_COILOUTF_LR': 'FM1* FM6* ',
'SUS-ZM1_M2_COILOUTF_UL': 'FM1* FM6* ',
'SUS-ZM1_M2_COILOUTF_UR': 'FM1* FM6* ',
'SUS-ZM3_M2_COILOUTF_LL': 'FM1* FM6* ',
'SUS-ZM3_M2_COILOUTF_LR': 'FM1* FM6* ',
'SUS-ZM3_M2_COILOUTF_UL': 'FM1* FM6* ',
'SUS-ZM3_M2_COILOUTF_UR': 'FM1* FM6* '}
Turned thses filters off:
h1lsc {'LSC-EXTRA_AI_2': 'FM2 '}
h1lscaux {'LSC-LOCKIN_1_DEMOD_9_I': 'FM1 ',
'LSC-LOCKIN_1_DEMOD_9_Q': 'FM1 '}
Added gain of 1 filters to:
h1sqz {'SQZ-RLF_VCXO_SERVO': 'FM2* '}
h1sussqzin {'SUS-ZM1_M2_COILOUTF_LL': 'FM1* FM6* ',
'SUS-ZM1_M2_COILOUTF_LR': 'FM1* FM6* ',
'SUS-ZM1_M2_COILOUTF_UL': 'FM1* FM6* ',
'SUS-ZM1_M2_COILOUTF_UR': 'FM1* FM6* ',
'SUS-ZM3_M2_COILOUTF_LL': 'FM1* FM6* ',
'SUS-ZM3_M2_COILOUTF_LR': 'FM1* FM6* ',
'SUS-ZM3_M2_COILOUTF_UL': 'FM1* FM6* ',
'SUS-ZM3_M2_COILOUTF_UR': 'FM1* FM6* '}
This should have no effect on anything.
Remove the controls from these filter modules:
h1alsex {'LSC-X_ARM_DRIVE': 'FM3* FM5* '}
h1alsey {'LSC-Y_ARM_DRIVE': 'FM3* FM5* '}
Turned these filters off after a model restart.
TITLE: 06/09 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 137Mpc
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 7mph Gusts, 5mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY:
At 20:10 UTC the SQZ_MANAGER went from FREQ_DEP_SQZ to SQZ_READY_IFO for some reason
20:15 UTC lockloss.
Relocking Notes: I had to Touch up X-ARM ALS Flashes.
Doors to Air handlers 1 & 2 were open from 1:35-138 local so if there is som etrending of the Air handlers during that time the plots may look diiffent than expected during those time.
Took ISC_LOCK to Initial Alignment 20:46 UTC
Started the Next Locking attempt 21:07
21:55 UTC Nominal Low Noise was reached.
Saved some SDF Changes to H1:ASC-ADS_PIT3_DEMOD_I_TRAMP for PIT 3-5 and Yaw 3-5 after speaking to Naoki about some changes.
Current IFO Status: Nominal Low Noise And Observing for 1 Hour.
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 20:34 | FMCS | Tyler & Bubba | AirHandlr2 | N | checking out the HVAC system | 21:56 |
TITLE: 06/09 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 137Mpc
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 2mph 5min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY:
- IFO locked and in observing for ~1 hr
- CDS/DMs ok
- Seismic motion a bit elevated from recent EQ, will monitor
J. Kissel, S. Koehlenbeck, B. Lantz Sina and I are putting together material to help motivate an SPI installation some time in the future (see most recent material in G2300655 and G2300846), and one of the open questions is whether we can demonstrate (via model, or extrapolated measurement) that the P & Y input to, say, PR3 would be better after linking the platforms together in PITCH & YAW than the local table PITCH (RY) & YAW (RZ). This aLOG shows the first attempt at demonstrating this with data, sticking with PR3, and thus the HAM2 - HAM3 ISI system. Executive Summary: This initial look shows great promise for an SPI's ability to improve HAM2 and HAM3 platform motion across the 0.01 to 10 Hz frequency band -- differential X (longitudinal), as well as differential Y and Z converted to pitch and yaw motion, is factors of 2 to 200 better than local X (longitudinal), RY (pitch), and RZ (yaw). The key concepts here are - As it's *always* worth repeating, the input to the suspension point is different from table motion, and the optic motion is different that optic motion, *especially* when it comes to cross-coupling between degrees of freedom, like suspension point Longitudinal and optic Pitch, or platform X / RZ vs. optic Yaw. Even within the ISI, there's a good amount of cross coupling between RX/RY tilt DOFs and Y/X translation degrees of freedom, so using the SPI to improve ISI RY could improve ISI Y, which benefits PR3 suspoint L, with benefits PR3 optic P. So the motivation for an SPI, via looking at only one diagonal DOF at once will never make a clear argument for "we need an SPI!" So, we're doing an incomplete job if we look at only one DOF at once and say "improvements in this one DOF will clearing improve that one DOF." We'll only really know the true quantified benefit once we install one and see. But it's still interesting to look at the data in this way to get a feel for if it makes sense to even try. - The SPI may be used for different frequency regions for different purposes. PR3, for example, may not be limited by residual seismic motion at some frequencies for some degrees of freedom. We just need to be conscious of this when make sweeping statements like "PR3 is completely dominated by OSEM noise, you won't see any improvement unless we improve the local sensors on the top mass of PR3 -- so why should we spend energy on an SPI?" because that sweeping statement is true at 10 Hz, but not true below ~3 Hz, and an improvement below 3 Hz might be benefit to the IFO in subtle ways like "we can reduce the bandwidth of the ASC loops, which means the ASC sensor noise doesn't couple into DARM at 10-15 Hz." - In modern parlance, when we say an "SPI" we really mean a 3 DOF collection of sensors rather than "just" a 1 DOF seismic platform interferometer: :: SPI L :: a longitudinal sensor -- the interferometer part, which uses an asymmetric michelson IFO (short arm stays local to the launching platform, and the long arm spans the 16 m distance between the two platforms) to determine the relative distance between the platforms. :: SPI P :: an "optical lever" like pitch sensor measuring differential pitch of the platform (expected to be dominated by the difference between local Zs rather than local pitch RYs) :: SPI Y :: an "optical lever" like yaw sensor, measuring differential yaw of the platform (expected to me dominated by the difference between local Ys, rather than differential yaw RZs) - Fundamentally, why an SPI wins in P and Y is the lever arm of sensing. The local sensing of pitch (RX / RY) or yaw (RZ) is the difference or sum of inertial sensors across the width of the table, a lever arm of ~1 [m]. One the other hand, if we can tie pitch/RY or yaw/RZ one platform (say HAM2) to the other (HAM3), but using the lever arm *between* the platforms -- L = ~16 [m] -- and this is *better* than the local interial sensing, we improve both local platform's motion by something like sqrt(2) / L. The details of of the improvement depend on a lot of things, and we'll get there, but at least conceptually, this is the promised improvement. - Another point to emphasize is that *we don't yet know the optimal controls topology and/or frequency region that these 3 DOFs will be used.* Depending on the results, it may be interesting to compare the local inertial sensors to the SPI sensors, or the local CPS to the SPI sensors. What frequency region we blend in the SPI vs. the local platform's inertial and displacement sensor array is still unclear. So the plots below compare both against the SPI. You'll see that the differential signals are better in some frequency regions and worse in others. This is all still to be understood and schemed upon, so my commentary below should be treated as "first impressions." - Remember that depending on the frequency band, the CPS or GS13s are "in loop," forming the error signal for the feedback loops, which have UGFs of around 30 Hz. I indicate a "CPS Rolloff Frequency" with vertical lines on all the plots -- where the vertical line is set at the frequency above which the CPS contribution to the super sensor is less than 1.0. (Note, this is different from what has traditionally been referred to as "the blend frequency," which is instead a center point of equal contributions of GS13 and CPS. Because - gain peaking is involved at that "blend frequency" cross-over point, - that gain peaking can be large and/or span across a lot of frequency space, - GS13 blend filters are not easy to plot because of the embedded inertial sensor calibration and - AFAIK, no one's plotted them in their easy-to-digest complementary form recently, I chose the more straight-forward, easily findable, "when does the CPS contribution to the feedback loop start to roll off" frequency. These frequencies are close, of course, but not the same.) - I'm concocting "differential motion" between the HAM3 and HAM2 platforms by coherently subtracting one platform's DOF from the other platform's corresponding DOF. Since the data is recorded and synchronized by the CDS system, one simply needs to download the two platform's data over the same time period and subtract one time series from the other and it's a "differential motion coherent subtraction." - Of course, sensor noise is always of concern when doing differential measurements. As best I can, I use the estimates of the GS13 and CPS sensor noise from our old friend SEI_sensor_noise.m (T0900450), and I (a) Assume every colocated sensor of a given type has identical noise (b) Scale them to the appropriate cartesian degree of freedom, assuming all sensors are incoherent, by taking the quadrature sum of the given sensor type's input matrix from /ligo/svncommon/SeiSVN/seismic/HAM-ISI/Common/Basis_Change_Matrices/aLIGO_HAM_ISI_2_3.mat (c) Look at the results, find where the *Z* DOF is limited by sensor noise the real data, and scale every type's sensor noise in (a) by a single scalar fudge factor to match the real data (d) For differential sensor noise between the 2 platforms, I then multiply that DOF's sensor noise by a factor of sqrt(2). What motivating data I'll show and why (I) SPI Longitudinal (the "interferometer" part of the SPI) would measure the differential distance between the HAM2 and HAM3 in X. So, to motivate the benefit of SPI L we'll compare an individual platform's X motion against the differential X, (HAM3 X - HAM2 X). (II) SPI Pitch (one "optical lever" part of the SPI) would primarily measure the differential Z (vertical) motion between HAM2 and HAM3 in Z. So, to motivate the benefit of SPI P we'll compare an individual platform's RY motion against the differential X, (HAM3 Z - HAM2 Z) *divided by the lever arm between the platforms, L.* (III) SPI Yaw (the other "optical lever" part of the SPI) would primarily measure the differntial Y (transverse) motion between HAM2 and HAM3. So, to motivate the benefit of the SPI Y, we'll compare an individual platform's RZ motion against the differential Y (HAM3 Y - HAM2 Y) *divided by the lever arm between platforms, L.* OK, Now to the data. For starter's I grabbed *one* 3 hours of data starting at -- last night, 2023-06-09 at 09:30 UTC (02:30a PDT, GPS 1370338218). The wind is low (< 10 mph), the microseism is around 0.1 [um/s], no earthquakes, and the IFO is locked, observing, in nominal low noise busy detecting gravitational waves. Note, that the RZ loops include Jim's new-and-improve blend filters that improve the local RZ performance by factors of 5 to 10 between 2 - 20 HZ. LOCALX_vs_DIFFX shows the performance metric comparisons for SPI L. - The differential GS13 signal is about the same as the HAM3 local sensor for most of the frequency band. There's *some* areas below 0.5 Hz where the differential X GS13 would be better, but out of the nominal frequency region where the GS13 is used in loop. - Below 7 Hz, the differential CPS is better than the local CPS by factor ranging from 2 to 20. - Below the "CPS rolloff frequency" for this DOF, 0.34 Hz, and SPI measuring this same differential motion (without being limited by its own sensor noise) would improve things over each local CPS by a factors of 2 to 5. Promising! LOCALRY_vs_DIFFZoverL shows the performance metric comparisons for SPI P. - Here, we see a HUGE difference in performance between the local sensors and platform-to-platform differential sensors. - Assuming that the SPI optical lever has sensor noise below this level of rotation, would should be able to get a huge amount of improvement, and we'd have our pick of which sensor to use where, since both local CPS RY and GS13 RY sensors are MUCH worse than differential Z. - The only place where the differential motion is comparable (note -- comparable, not worse!) is in the ~10 Hz region where differential HEPI pier motion between the two platforms is, well, different. *Very* promising! LOCALRZ_vs_DIFFYoverL - Similar to the SPI P plots there's lots of frequency regions where SPI Y, informed by differential HAM3 - HAM2 Y would be better than local RZ. However, this DOF is probably the most confusing, because we know that each local table Y is limited in the 0.07 to 5 Hz region by local RX tilt (from local RX sensor noise across the ~1 [m] lever arm). So differential Y is limited by RX tilt, where differential Z is not in anyway limited by tilt. So we don't expect to get *as much* benefit out of an SPI Y, but we'd definitely still get some if the chambers are left as is. However, we also know that the ISI local RX sensor noise can be improved by installing better CPS sensors, like we've done for the HAM7 HAM8 systems. So, the story is a little longer here, but still... *Very* promising! Next on the to-do list: (1) Gather HAM3-HAM2 data at different environmental times, to see whether any of the above conclusions from this one data set change. (2) Compare this differential GS13 and CPS data against Sina's projections for sensor noise (3) Use this (and other data we gather) data to try to concoct a control strategy (4) Use that control strategy to estimate the improved platform and suspension performance in various scenarios including (i) If we also improve the HAM-ISIs to use fine vertical CPS sensors (i) If we also improve PR3's top mass sensing noise (5) Present this kind of progress to the systems group
A few more plots that show the sanity checks I made that went into the plots presented above:
- HAM23_SPIMotivation_Z_CPS_ts.pdf Demonstrating that differential HAM3 Z - HAM2 Z is just the two time series subtracted, and there's no funny business going on in the time series data I used during this 3 hour time stretch.
- HAM23_SPIMotivation_Z_GS13CPS_noise_and_cal_check.pdf Demonstrating that the calibration of the data all makes sense, as well as the projections and fudge factors of ~0.5 and 1.2 on the sensor noise are legit.
- HAM23_SPIMotivation_Z_vs_DIFFZ_GS13.pdf showing GS13 inertial motion alone for both HAM2 and HAM3 compared to sensor noises.
- HAM23_SPIMotivation_Z_vs_DIFFZ_CPS.pdf showing CPS ground-to-platform relative motion alone for both HAM2 and HAM3 compared to sensor noises.
The raw data for this aLOG has been downloaded and saved to
/ligo/svncommon/SeiSVN/seismic/Common/Data/
2023-06-09_0930UTC_HAM23_timeseries.mat
The script to make the plots from that data lives in
/ligo/svncommon/SeiSVN/seismic/Common/SPI/Scripts/
plot_spi_motivation_20230609.m
A quick screenshot to show where I got the "CPS Rolloff Frequency" for each of the blend filters For the X, Y, and Z blend filter, which are all the "comp_250" filter, the CPS rolloff frequency is 0.34 Hz. For the RX and RY blend filters, which are the "many_notches" filter, the CPS rolloff frequency is 0.60 Hz. For the new RZ blend filter, called the "fc_yaw_filt_lp", the CPS rolloff frequency is at 0.34 Hz. As a bonus, included in the screenshot is a reminder of what the CPS2CART and GS132CART matrices look like for sensor noise projection.
Quick comment on the Noise projection plot
SEI_sensor_noise includes the local to cartesian-basis noise correction factors (added in 2021)
see SEI log 1786, or the help the SEI_sensor_noise
For Example.
>> freq = logspace(-1,2, 1000);
>> cps_noise_1mm = SEI_sensor_noise('ADE_1mm', freq);
>> proj = SEI_sensor_noise('projections');
>> stg1_cps_x_noise = proj.bsc.stg1.cps.x * cps_noise_1mm;
Regarding the influence of CPS DIFF on these results
J. Kissel, A. Pele, J. Warner
Arnaud reminded that CPS DIFF exists -- and asks the legit question "is CPS DIFF on, confusing your results and conclusions?"
In short: Yes, (HAM3-HAM2) CPS diff is ON, and influencing platform motion between 1.5 mHz and 0.48 Hz.
I then got a kitchen download from Jim, which I now convey here backed up with plots and MEDM screen screenshots. In general, CPS DIFF is really tough to find. You can find the "overview" that starts with
sitemap > ISI SENSCOR CONFIG > (upper right corner) Yellow Button "ISI DIFF" > CPS DIFF MTRX
This brings up the "start" of CPS DIFF -- the 2023-06-12_ISICPSDIFF.png screen, which ingests calibrated local CPS signals (prior to their corner-station sensor correction from the ITMY T240 in the biergarten), and "simply" subtracts them. One can see that for the corner station HAMs, there are only the two pairs subtracted and only in the IFO's longitudinal direction: (HAM3 - HAM2) X and (HAM4 - HAM5) Y.
In these cases, HAM3 is the "leader" and HAM2 is the "follower," and similarly, HAM4 is the leader, and HAM5 is follower.
Following the HAM3-HAM2 signal, that differential CPS signal is then fed into a single filter bank, H1:ISI-DIFF_HAM3_CPSX (see screenshot).
That filter module in use in that HAM3 bank is "better60mHz," which is a band-pass
- "active" (magnitude greater than 10%) between 0.0015 - 0.48 Hz,
- "focused" (magnitude greater than 90%) 0.022 - 0.088 Hz.
- "centered" (phase is 0 deg) on 0.034 Hz
See the response of this filter in 2023-06-12_ISICPSDIFF_HAM3-HAM2_better60mHz_Filter.png.
The output of that filter bank output is feed into a "soft limiter" that limits the signal to less than 10000 [nm] = 10 [um]. (see 2023-06-12_ISICPSDIFF_SmoothLimiter.png)
The typical counts coming out of our band-limiter is low 10s [nm] oscillating around 0 [nm], which maximum minute of the trends being at most 100-150 [nm], so *plenty* of head room. So, in short, the soft limiter it's doing anything.
The output of the soft limiter goes into the "leader" ISI's SUSINF "suspension input filter" H1:ISI-HAM3_SUSINF_X bank (see 2023-06-12_ISIHAM3_SUSINF.png), which again is the longitudinal direction of the IFO across HAM3-HAM2.
Finally, this output is summed into the *output* of the blend filters, i.e. the super sensor error signal for the X DOF's isolation filters.
2023-06-12_0930UTC_ISICPSDIFF_HAM3-HAM2_ControlSignal_3hrMinuteTrend.png shows the minute trend of the HAM3-HAM2 CPS DIFF band-limited control signal for the 3 hour stretch on 2023-06-09 09:30 UTC that I took the data in the main aLOG. 2023-06-12_0930UTC_ISICPSDIFF_HAM3-HAM2_ControlSignal_ASD.png shows the amplitude spectral density compared against CPS X DIFF = sqrt(2) * HAM "1 mm" ADE CPS X sensor noise (using the handy feature of SEI_sensor_noise Brian reminds me of above -- thanks Brian!).
This amplitude spectral density is consistent with the shape and amplitude of the (HAM3-HAM2) offline concocted ASD differential signal above 2023-04-13_0000UTC_HAM23_SPIMotivation_spiprcl_LOCALX_vs_DIFFX.pdf.
I attribute the difference in shape due to different averaging, windowing, and % overlap, and FFT parameters, so don't look too closely. This needs to be done more carefully offline, and I will eventually.
So,
- (HAM3-HAM2) CPS DIFF is *already* doing the same job that I describe that a future SPI L "the ifo part" connecting HAM3-HAM2 would do.
- Deciding which would do it *better* and/or which we should use in which frequency region is a question of which will have better sensor noise.
- Both should be a part of the discussion.
- CPS DIFF does *not* play a role in any of the material / data / plots discussing SPI P and SPI Y, since HAM3-HAM2 Z (for P) and HAM3-HAM2 Y (for Y) do not have any CPS DIFF.
Note, the plan to improve the "the HAM2 HAM3 CPS" won't impact this assessment; at the moment, we're only considering upgrading the *vertical* CPS sensors on the HAMs.
TITLE: 06/06 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 133Mpc
SHIFT SUMMARY: About to start maintenance day.
LOG:
H1 glitches nuc27 FOM isn't updating for Omicrom. I posted this in the LHO DetChar chat.ligo group.
I've had to restart the DARM FOM on nuc30 3 times and Ryan noted he did ~4 times during the evening. Tagging CDS.
I expected PEM magnetic injections to start at 7:25am, it was 14:30UTC to 14:48UTC. SUS_CHARGE started at 14:45UTC with lines at 11-14Hz when PEM_MAG_INJ was stilll at EY_EBAY_HIGH_INJ. So they overlapped by 2-3 minutes. Tagging PEM and Tagging SUS In-lock charge measurements caused a lockloss again at 15:00UTC 70062.
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 13:21 | CDS | Erik | Remote | N | Rebooting work stations | 13:21 |
| 14:17 | COMM | Camilla | CR | N | PRCL OLG Measurement | 14:27 |
| 14:30 | PEM | PEM_MAG_INJ GRD | Auto | N | Automatic magnetic injections | 14:48 |
| 14:45 | SUS | SUS_CHARGE GRD | Auto | N | Automatic in-lock charge measurements | 15:01 |
To fix the overlap between the magnetic injections and in-lock charge measurements, I've moved the start time of the magnetic injections up to 7:20am from 7:25am (tagging PEM).