after_key = 'LHO_1409042566'
b4_key = 'LHO' # 1403879360 # Hot OM2, 2024/07/01 14:29UTC
(aligoNB) anthony.sanchez@cdsws29: python H1/darm_intergal_compare.py
Figures made by this script will be placed in:
/ligo/gitcommon/NoiseBudget/aligoNB/out/H1/darm_intergal_compare
Fetching data from nds.ligo-wa.caltech.edu:31200 with GPS times 1409042566 to 1409043166
Successfully retrieved data from nds.ligo-wa.caltech.edu:31200 with GPS times 1409042566 to 1409043166
data is 60.1 days old
Fetching data from nds.ligo-wa.caltech.edu:31200 with GPS times 1403879360 to 1403879960
Successfully retrieved data from nds.ligo-wa.caltech.edu:31200 with GPS times 1403879360 to 1403879960
running lho budget
Saving file as /ligo/gitcommon/NoiseBudget/aligoNB/out/H1/darm_intergal_compare/compare_darm_spectra_OM2_hot_vs_cold_no_sqz.svg
Saving file as /ligo/gitcommon/NoiseBudget/aligoNB/out/H1/darm_intergal_compare/compare_darm_range_integrand_OM2_hot_vs_cold_no_sqz.svg
Saving file as /ligo/gitcommon/NoiseBudget/aligoNB/out/H1/darm_intergal_compare/compare_cumulative_range_OM2_hot_vs_cold_no_sqz.svg
Saving file as /ligo/gitcommon/NoiseBudget/aligoNB/out/H1/darm_intergal_compare/cumulative_range_big_OM2_hot_vs_cold_no_sqz.svg
Script darm_intergal_compare.py done in 0.23667725324630737 minutes
H1's current coherence with jitter, LSC signals, ASC signals plot.
Bruco - Brute force coherence. Looks at the coherence between many channels. was the next thing I wanted to Try but I was greeted with a permissions denied when trying to ssh into the cluster with my A.E creds.
I ran a bruco on GDS CLEAN with data from the current lock after 11 hrs of lock time. My instructions. I have been running my brucos on the LHO cluster lately because it seems like every time I run on Caltech I get some error.
bruco command:
python -m bruco --ifo=H1 --channel=GDS-CALIB_STRAIN_CLEAN --gpsb=1409075057 --length=600 --outfs=4096 --fres=0.1 --dir=/home/elenna.capote/public_html/brucos/GDS_CLEAN_1409075057 --top=100 --webtop=20 --plot=html --nproc=20 --xlim=7:2000 --excluded=/home/elenna.capote/bruco-excluded/lho_DARM_excluded.txt
Results:
https://ldas-jobs.ligo-wa.caltech.edu/~elenna.capote/brucos/GDS_CLEAN_1409075057/
Greatest hits:
- ASC coherences: CHARD P, CHARD Y, DHARD Y, previously discussed in various alogs about spot positions, etc 79776, 79790, 79807
- Some SRCL, I wrote "there may be some worsening of the coupling 100-200 Hz" in my FF tuning alog and that's exactly what happened. I can reasses the fit. 79755
- MICH, only at low frequency, previously discussed in FF alogs, 79755
- PRCL, low frequency perhaps due to ASC and the 100 Hz coupling perhaps due to SRCL? also previously discussed 79807
- LSC REFL RIN coherence across a large part of the band- this is the kind of thing that prompted us to try a PRCL offset in April, 76805, 76814
- Some OMC REFL
- IMC REFL ?
- One of many PEM ACC coherences, this one in the PSL- this one looks like the IMC REFL coherence, ?
- this "shape of coherence" is also appearing in various ISS sensors too. Is this jitter or intensity noise?
- SUS ITMY L3 which is maybe a red herring, or maybe just another manifestation of the various ASC coherences?
- HAM1 L4C coherence, HAM1 feedforward perhaps not performing as well as it could
- HAM2 GS13, ?
At Livingston, we have been using a separate DIAG_COH guardian to monitor the health of the feed forward. It is similar to Bruco in functionality, in sense that it computes coherence. It does it automatically every 3 hrs within an observing period and computes band limited coherence of channels according to a set config file. An additional feature is that it stores previous coherence values to a file as reference and compares current values with that. If it differs drastically say 2 sigma, it displays a message in DIAG_MAIN warning that certain FF is under performing compared to reference.