Size: 10236
Comment:
|
Size: 11666
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 12: | Line 12: |
*7/24 For daily run, only lock loss events will be monitored. *7/19 Glitch events in ER on 7/13 are reprocessed. [[https://www.icrr.u-tokyo.ac.jp/~yuzu/bKAGRA_summary/html/20190713_GlitchPlot.html|Yuzu summary]] *7/13 SNR thresholds are optimized to ER trigger rate. |
*8/20 Test version for data analysis pipeline result [[https://www.icrr.u-tokyo.ac.jp/~yuzu/bKAGRA_summary/html/20190713_GlitchPlot_locked_cbc.html|CBC]] [[https://www.icrr.u-tokyo.ac.jp/~yuzu/bKAGRA_summary/html/20190713_GlitchPlot_locked_burst.html|Burst]] *8/14 Only main channel trigger is used. *8/10 For daily run, both glitch and lockloss are monitored during nightly data taking. Trigger list is updated to adapt X-arm configuration. |
Line 20: | Line 21: |
Line 21: | Line 23: |
8/15~ (X-arm nightly, only time with K1:MIF-WE_ARE_DOING_NOTHING == 1) ||<:>'''Channel'''||'''SNR threshold'''|| ||CAL-CS_PROC_XARM_FREQUENCY_DQ||<:> 21 || ||<:>'''Lock state : X-arm'''|| 7/13 (MICH ER) ||<:>'''Channel'''||'''SNR threshold'''|| ||IMC-CAV_TRANS_OUT_DQ||<:> 35 || ||PSL-PMC_TRANS_DC_OUT_DQ||<:>30 || ||LSC-REFL_PDA1_RF17_Q_ERR_DQ||<:>6 || ||LSC-POP_PDA1_RF17_Q_ERR_DQ||<:>8 || ||LSC-AS_PDA1_RF17_Q_ERR_DQ||<:>15 || ||CAL-CS_PROC_IMC_FREQUENCY_DQ||<:>15 || ||<:>'''Lock state : LSC'''|| 6/8 (X-arm ER) ||<:>'''Channel'''||'''SNR threshold'''|| ||LSC-CARM_SERVO_MIXER_DAQ_OUT_DQ||<:> 10 || ||AOS-TMSX_IR_PD_OUT_DQ||<:> 10 || ||IMC-MCL_SERVO_OUT_DQ||<:> 30 || ||IMC-SERVO_SLOW_DAQ_OUT_DQ||<:> 7 || ||IMC-CAV_TRANS_OUT_DQ||<:> 10 || ||IMC-CAV_REFL_OUT_DQ||<:> 10 || ||PSL-PMC_TRANS_DC_OUT_DQ||<:> 30 || ||PSL-PMC_MIXER_MON_OUT_DQ||<:> 10 || ||<:>'''Lock state : IMC'''|| Old information is more below. == Overview == The main purpose is to study glitches and lock loss by visual inspection. Also, collecting information for glitch database is done through voting form for each glitch event. Using the result, we aim to do noise hunting, glitch characterization, and labeling for machine learning application. Here is slides describing how to use: [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=10371|slides]] GlitchPlot uses trigger information provided by Omicron. GlitchPlot does clustering of the triggers and summarize the trigger information for each events based on the Omicron output. For each events, plots for triggered channel and relevant channels are provided on [[https://www.icrr.u-tokyo.ac.jp/~yuzu/bKAGRA_summary/html/|Yuzu Summary]]. The relevant channels are basically chosen from * Trigger channel * Unsafe channels * Important upstream channels * Relevant VIS channels * PEM near the trigger channel sensor Using [[https://github.com/gw-detchar/Kozapy|Kozapy]] batch codes, following plots are provided: * Time series * Spectrum before trigger and after trigger * Spectrogram * Coherencegram with trigger channel * Q-transform (Under testing) The parameter for plots are determined based on trigger information. Also, lock state summary around the trigger time is provided. == Specification detail == === Trigger clustering === For the trigger clustering method, please refer p3 of [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=10368|slides]]. === Plot channel list === For the exact channel list for each trigger, please refer $channelname.dat in [[https://github.com/gw-detchar/tools/tree/kashiwa/GlitchPlot/Script|GlitchPlot github]]. === Plot parameter === For the exact method for plot parameter determination, please refer plotter.py and condor_jobfile_plotter.sh in [[https://github.com/gw-detchar/tools/tree/kashiwa/GlitchPlot/Script|GlitchPlot github]]. The intent and the variable name in the shell script is as follows. *Time series *GPS start time ($gpsstart), end time ($gpsend) * The center is the trigger time. * Time span is roughly larger one of [4sec, trigger duration * 10]. (Adjusted to fit the spectrogram requirement) *Output directory ($outdir) *Channel ($chlist[@]) *Lock state segment bar: flag($lock), guardian channel($lchannel), guardian value($lnumber), segment bar title($llabel) *Data file type ($data) *Full data is used. *If time span is too long, down sample is applied. *Spectrum *List of GPS start time ($gpsstarts30[@]), end time ($gpsend30[@]) * Trigger time and 2sec before and after the trigger is avoided. * About 30 sec is used each before trigger and after trigger spectrum. * The length is adusted to the multiple of the FFT length. *Output directory ($outdir) *Channel ($chlist[@]) *FFT length ($fft30) * 1/band width (Adjusted to the nearest 2^n sec.) *Spectrogram, coherencegram *GPS start time ($gpsstart), end time ($gpsend) * The center is the trigger time. * Time span is roughly larger one of [4sec, trigger duration * 10]. * The length is adjusted to be Stride * n *Output directory ($outdir) *Channel ($chlist[@]) *Lock state segment bar: flag($lock), guardian channel($lchannel), guardian value($lnumber), segment bar title($llabel) *Stride ($stride) * To have enough time resolution to see the glitch. *FFT length ($fft) * stride = FFT length * n *With and without whitening (Spectrogram) *Q-transform (Under testing. GWpy default parameter is used.) *GPS start time ($gpsstart), end time ($gpsend) *Output directory ($outdir) *Channel ($chlist[@]) *Lock state segment bar: flag($lock), guardian channel($lchannel), guardian value($lnumber), segment bar title($llabel) *Lock segment summary *GPS start time ($gpsstart), end time ($gpsend) * Same as time series *Output directory ($outdir) *Channel ($channel) *Trigger time ($gpstime) and duration ($max_duration) * Taken from Omicron information === Source code === [[https://github.com/gw-detchar/tools/tree/kashiwa/GlitchPlot/Script|GlitchPlot github]]. Master branch: On Kamioka server, plotter.sh runs by crontab every 15 min. plotter.py is called. it gives clustered Omicron trigger information as a text file. The text files are sent to Kashiwa server by rsync. kashiwa branch: On Kashiwa sercer, GlitchPlot.sh runs by crontab every 15 min. Using text file sent from Kamioka, condor_jobfile_plotter.sh runs to throw jobs into condor to make plots. = Info log = == Trigger channel list log == 8/15~ (X-arm nightly, only time with K1:MIF-WE_ARE_DOING_NOTHING == 1) ||<:>'''Channel'''||'''SNR threshold'''|| ||CAL-CS_PROC_XARM_FREQUENCY_DQ||<:> 21 || ||<:>'''Lock state : X-arm'''|| 8/10~ (X-arm nightly, only time with K1:MIF-WE_ARE_DOING_NOTHING == 1) ||<:>'''Channel'''||'''SNR threshold'''|| ||CAL-CS_PROC_XARM_FREQUENCY_DQ||<:> 21 || ||LSC-CARM_SERVO_MIXER_DAQ_OUT_DQ||<:> 15 || ||AOS-TMSX_IR_PD_OUT_DQ||<:> 15 || ||IMC-SERVO_SLOW_DAQ_OUT_DQ||<:> 12 || ||IMC-CAV_TRANS_OUT_DQ||<:> 45 || ||PSL-PMC_TRANS_DC_OUT_DQ||<:> 35 || ||<:>'''Lock state : X-arm'''|| |
|
Line 33: | Line 177: |
7/19~ (only 0:00~8:00) ||<:>'''Channel'''||'''SNR threshold'''|| ||IMC-CAV_TRANS_OUT_DQ||<:> 45 || ||PSL-PMC_TRANS_DC_OUT_DQ||<:>40 || ||LSC-REFL_PDA1_RF17_Q_ERR_DQ||<:>16 || ||LSC-POP_PDA1_RF17_Q_ERR_DQ||<:>18 || ||LSC-AS_PDA1_RF17_Q_ERR_DQ||<:>25 || ||CAL-CS_PROC_IMC_FREQUENCY_DQ||<:>25 || ||<:>'''Lock state : LSC'''|| |
|
Line 43: | Line 198: |
7/12~ and 7/13 11:30~24:00 ||<:>'''Channel'''||'''SNR threshold (8:00~24:00)'''||'''SNR threshold (0:00~8:00 and 7/13 11:30~24:00)'''|| ||IMC-CAV_TRANS_OUT_DQ||<:> veto ||<:> 10 || ||PSL-PMC_TRANS_DC_OUT_DQ||<:>veto ||<:> 30 || ||LSC-REFL_PDA1_RF17_Q_ERR_DQ||<:>veto ||<:> 30 || ||LSC-POP_PDA1_RF17_Q_ERR_DQ||<:>veto ||<:> 30 || ||LSC-AS_PDA1_RF17_Q_ERR_DQ||<:>veto ||<:> 30 || ||CAL_CS_PROC_IMC_FREQUENCY_DQ||<:>veto ||<:> 30 || ||<:>'''Lock state : MICH'''|| 7/10~ ||<:>'''Channel'''||'''SNR threshold (8:00~24:00)'''||'''SNR threshold (0:00~8:00)'''|| ||IMC-CAV_TRANS_OUT_DQ||<:> veto ||<:> 20 || ||PSL-PMC_TRANS_DC_OUT_DQ||<:>veto ||<:> 40 || ||PEM-ACC_MCF_TABLE_REFL_Z_OUT_DQ||<:>veto ||<:> 40 || ||PEM-ACC_PSL_PERI_PSL1_Y_OUT_DQ||<:>veto ||<:> 20 || ||PEM-MIC_PSL_TABLE_PSL4_Z_OUT_DQ||<:>veto ||<:> 20 || ||<:>'''Lock state : IMC'''|| 7/5~7/9 (buggy setting) ||<:>'''Channel'''||'''SNR threshold (8:00~24:00)'''||'''SNR threshold (0:00~8:00)'''|| ||IMC-CAV_TRANS_OUT_DQ||<:> 100 ||<:> veto || ||PSL-PMC_TRANS_DC_OUT_DQ||<:>100 ||<:> veto || ||PEM-ACC_MCF_TABLE_REFL_Z_OUT_DQ||<:>100 ||<:> veto || ||PEM-ACC_PSL_PERI_PSL1_Y_OUT_DQ||<:>100 ||<:> veto || ||PEM-MIC_PSL_TABLE_PSL4_Z_OUT_DQ||<:>100 ||<:> veto || ||<:>'''Lock state : IMC'''|| |
|
Line 57: | Line 245: |
Old information is more below. == Overview == The main purpose is to study glitches and lock loss by visual inspection. Also, collecting information for glitch database is done through voting form for each glitch event. Using the result, we aim to do noise hunting, glitch characterization, and labeling for machine learning application. Here is slides describing how to use: [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=10371|slides]] GlitchPlot uses trigger information provided by Omicron. GlitchPlot does clustering of the triggers and summarize the trigger information for each events based on the Omicron output. For each events, plots for triggered channel and relevant channels are provided on [[https://www.icrr.u-tokyo.ac.jp/~yuzu/bKAGRA_summary/html/|Yuzu Summary]]. The relevant channels are basically chosen from * Trigger channel * Unsafe channels * Important upstream channels * Relevant VIS channels * PEM near the trigger channel sensor Using [[https://github.com/gw-detchar/Kozapy|Kozapy]] batch codes, following plots are provided: * Time series * Spectrum before trigger and after trigger * Spectrogram * Coherencegram with trigger channel * Q-transform (Under testing) The parameter for plots are determined based on trigger information. Also, lock state summary around the trigger time is provided. == Specification detail == === Trigger clustering === For the trigger clustering method, please refer p3 of [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=10368|slides]]. === Plot channel list === For the exact channel list for each trigger, please refer $channelname.dat in [[https://github.com/gw-detchar/tools/tree/kashiwa/GlitchPlot/Script|GlitchPlot github]]. === Plot parameter === For the exact method for plot parameter determination, please refer plotter.py and condor_jobfile_plotter.sh in [[https://github.com/gw-detchar/tools/tree/kashiwa/GlitchPlot/Script|GlitchPlot github]]. The intent and the variable name in the shell script is as follows. *Time series *GPS start time ($gpsstart), end time ($gpsend) * The center is the trigger time. * Time span is roughly larger one of [4sec, trigger duration * 10] *Output directory ($outdir) *Channel ($chlist[@]) *Lock state segment bar: flag($lock), guardian channel($lchannel), guardian value($lnumber), segment bar title($llabel) *Data file type ($data) *Full data is used. *Spectrum *List of GPS start time ($gpsstarts30[@]), end time ($gpsend30[@]) *Output directory ($outdir) *Channel ($chlist[@]) *FFT length ($fft30) *Spectrogram *GPS start time ($gpsstart), end time ($gpsend) *Output directory ($outdir) *Channel ($chlist[@]) *Lock state segment bar: flag($lock), guardian channel($lchannel), guardian value($lnumber), segment bar title($llabel) *FFT length ($fft) *Stride ($stride) *With and without whitening *Coherencegram *GPS start time ($gpsstart), end time ($gpsend) *Output directory ($outdir) *Channel ($channel) $chlist[@] *Lock state segment bar: flag($lock), guardian channel($lchannel), guardian value($lnumber), segment bar title($llabel) *FFT length ($fft) *Stride ($stride) *Q-transform (Under testing. GWpy default parameter is used.) *GPS start time ($gpsstart), end time ($gpsend) *Output directory ($outdir) *Channel ($chlist[@]) *Lock state segment bar: flag($lock), guardian channel($lchannel), guardian value($lnumber), segment bar title($llabel) *Lock segment summary *GPS start time ($gpsstart), end time ($gpsend) *Output directory ($outdir) *Channel ($channel) *Trigger time ($gpstime) and duration ($max_duration) === Source code === [[https://github.com/gw-detchar/tools/tree/kashiwa/GlitchPlot/Script|GlitchPlot github]]. Master branch: On Kamioka server, plotter.sh runs by crontab every 15 min. plotter.py is called. it gives clustered Omicron trigger information as a text file. The text files are sent to Kashiwa server by rsync. kashiwa branch: On Kashiwa sercer, GlitchPlot.sh runs by crontab every 15 min. Using text file sent from Kamioka, condor_jobfile_plotter.sh runs to throw jobs into condor to make plots. = Info log = == Trigger channel list log == 7/25~ (only 0:00~8:00) ||<:>'''Channel'''||'''Requirement'''|| ||IMC-CAV_TRANS_OUT_DQ||<:> Lock loss || ||PSL-PMC_TRANS_DC_OUT_DQ||<:>Lock loss || ||LSC-REFL_PDA1_RF17_Q_ERR_DQ||<:> Lock loss || ||LSC-POP_PDA1_RF17_Q_ERR_DQ||<:> Lock loss || ||LSC-AS_PDA1_RF17_Q_ERR_DQ||<:> Lock loss || ||CAL-CS_PROC_IMC_FREQUENCY_DQ||<:> Lock loss || ||<:>'''Lock state : MICH'''|| 7/19~ (only 0:00~8:00) ||<:>'''Channel'''||'''SNR threshold'''|| ||IMC-CAV_TRANS_OUT_DQ||<:> 45 || ||PSL-PMC_TRANS_DC_OUT_DQ||<:>40 || ||LSC-REFL_PDA1_RF17_Q_ERR_DQ||<:>16 || ||LSC-POP_PDA1_RF17_Q_ERR_DQ||<:>18 || ||LSC-AS_PDA1_RF17_Q_ERR_DQ||<:>25 || ||CAL-CS_PROC_IMC_FREQUENCY_DQ||<:>25 || ||<:>'''Lock state : LSC'''|| 7/13 (MICH ER) ||<:>'''Channel'''||'''SNR threshold'''|| ||IMC-CAV_TRANS_OUT_DQ||<:> 35 || ||PSL-PMC_TRANS_DC_OUT_DQ||<:>30 || ||LSC-REFL_PDA1_RF17_Q_ERR_DQ||<:>6 || ||LSC-POP_PDA1_RF17_Q_ERR_DQ||<:>8 || ||LSC-AS_PDA1_RF17_Q_ERR_DQ||<:>15 || ||CAL-CS_PROC_IMC_FREQUENCY_DQ||<:>15 || ||<:>'''Lock state : LSC'''|| 7/12~ and 7/13 11:30~24:00 ||<:>'''Channel'''||'''SNR threshold (8:00~24:00)'''||'''SNR threshold (0:00~8:00 and 7/13 11:30~24:00)'''|| ||IMC-CAV_TRANS_OUT_DQ||<:> veto ||<:> 10 || ||PSL-PMC_TRANS_DC_OUT_DQ||<:>veto ||<:> 30 || ||LSC-REFL_PDA1_RF17_Q_ERR_DQ||<:>veto ||<:> 30 || ||LSC-POP_PDA1_RF17_Q_ERR_DQ||<:>veto ||<:> 30 || ||LSC-AS_PDA1_RF17_Q_ERR_DQ||<:>veto ||<:> 30 || ||CAL_CS_PROC_IMC_FREQUENCY_DQ||<:>veto ||<:> 30 || ||<:>'''Lock state : MICH'''|| 7/10~ ||<:>'''Channel'''||'''SNR threshold (8:00~24:00)'''||'''SNR threshold (0:00~8:00)'''|| ||IMC-CAV_TRANS_OUT_DQ||<:> veto ||<:> 20 || ||PSL-PMC_TRANS_DC_OUT_DQ||<:>veto ||<:> 40 || ||PEM-ACC_MCF_TABLE_REFL_Z_OUT_DQ||<:>veto ||<:> 40 || ||PEM-ACC_PSL_PERI_PSL1_Y_OUT_DQ||<:>veto ||<:> 20 || ||PEM-MIC_PSL_TABLE_PSL4_Z_OUT_DQ||<:>veto ||<:> 20 || ||<:>'''Lock state : IMC'''|| 7/5~7/9 (buggy setting) ||<:>'''Channel'''||'''SNR threshold (8:00~24:00)'''||'''SNR threshold (0:00~8:00)'''|| ||IMC-CAV_TRANS_OUT_DQ||<:> 100 ||<:> veto || ||PSL-PMC_TRANS_DC_OUT_DQ||<:>100 ||<:> veto || ||PEM-ACC_MCF_TABLE_REFL_Z_OUT_DQ||<:>100 ||<:> veto || ||PEM-ACC_PSL_PERI_PSL1_Y_OUT_DQ||<:>100 ||<:> veto || ||PEM-MIC_PSL_TABLE_PSL4_Z_OUT_DQ||<:>100 ||<:> veto || ||<:>'''Lock state : IMC'''|| 6/8 during ER ||<:>'''Channel'''||'''SNR threshold'''|| ||LSC-CARM_SERVO_MIXER_DAQ_OUT_DQ||<:> 10 || ||AOS-TMSX_IR_PD_OUT_DQ||<:> 10 || ||IMC-MCL_SERVO_OUT_DQ||<:> 30 || ||IMC-SERVO_SLOW_DAQ_OUT_DQ||<:> 7 || ||IMC-CAV_TRANS_OUT_DQ||<:> 10 || ||IMC-CAV_REFL_OUT_DQ||<:> 10 || ||PSL-PMC_TRANS_DC_OUT_DQ||<:> 30 || ||PSL-PMC_MIXER_MON_OUT_DQ||<:> 10 || ||<:>'''Lock state : IMC'''|| |
|
Line 253: | Line 269: |
*8/20 Test version for data analysis pipeline result [[https://www.icrr.u-tokyo.ac.jp/~yuzu/bKAGRA_summary/html/20190713_GlitchPlot_locked_cbc.html|CBC]] [[https://www.icrr.u-tokyo.ac.jp/~yuzu/bKAGRA_summary/html/20190713_GlitchPlot_locked_burst.html|Burst]] *8/14 Only main channel trigger is used. *8/10 For daily run, both glitch and lockloss are monitored during nightly data taking. Trigger list is updated to adapt X-arm configuration. |
GlitchPlot
This project is for glitch and lock loss study. You can see the result on Yuzu Summary.
Feedback from users are very welcome ! Please inform C. Kozakai and H. Yuzurihara.
Recent update
8/20 Test version for data analysis pipeline result CBC Burst
- 8/14 Only main channel trigger is used.
- 8/10 For daily run, both glitch and lockloss are monitored during nightly data taking. Trigger list is updated to adapt X-arm configuration.
Old information is more below.
The latest trigger channel list
8/15~ (X-arm nightly, only time with K1:MIF-WE_ARE_DOING_NOTHING == 1)
Channel |
SNR threshold |
CAL-CS_PROC_XARM_FREQUENCY_DQ |
21 |
Lock state : X-arm |
7/13 (MICH ER)
Channel |
SNR threshold |
IMC-CAV_TRANS_OUT_DQ |
35 |
PSL-PMC_TRANS_DC_OUT_DQ |
30 |
LSC-REFL_PDA1_RF17_Q_ERR_DQ |
6 |
LSC-POP_PDA1_RF17_Q_ERR_DQ |
8 |
LSC-AS_PDA1_RF17_Q_ERR_DQ |
15 |
CAL-CS_PROC_IMC_FREQUENCY_DQ |
15 |
Lock state : LSC |
6/8 (X-arm ER)
Channel |
SNR threshold |
LSC-CARM_SERVO_MIXER_DAQ_OUT_DQ |
10 |
AOS-TMSX_IR_PD_OUT_DQ |
10 |
IMC-MCL_SERVO_OUT_DQ |
30 |
IMC-SERVO_SLOW_DAQ_OUT_DQ |
7 |
IMC-CAV_TRANS_OUT_DQ |
10 |
IMC-CAV_REFL_OUT_DQ |
10 |
PSL-PMC_TRANS_DC_OUT_DQ |
30 |
PSL-PMC_MIXER_MON_OUT_DQ |
10 |
Lock state : IMC |
Old information is more below.
Overview
The main purpose is to study glitches and lock loss by visual inspection. Also, collecting information for glitch database is done through voting form for each glitch event. Using the result, we aim to do noise hunting, glitch characterization, and labeling for machine learning application. Here is slides describing how to use: slides
GlitchPlot uses trigger information provided by Omicron. GlitchPlot does clustering of the triggers and summarize the trigger information for each events based on the Omicron output.
For each events, plots for triggered channel and relevant channels are provided on Yuzu Summary. The relevant channels are basically chosen from
- Trigger channel
- Unsafe channels
- Important upstream channels
- Relevant VIS channels
- PEM near the trigger channel sensor
Using Kozapy batch codes, following plots are provided:
- Time series
- Spectrum before trigger and after trigger
- Spectrogram
- Coherencegram with trigger channel
- Q-transform (Under testing)
The parameter for plots are determined based on trigger information. Also, lock state summary around the trigger time is provided.
Specification detail
Trigger clustering
For the trigger clustering method, please refer p3 of slides.
Plot channel list
For the exact channel list for each trigger, please refer $channelname.dat in GlitchPlot github.
Plot parameter
For the exact method for plot parameter determination, please refer plotter.py and condor_jobfile_plotter.sh in GlitchPlot github. The intent and the variable name in the shell script is as follows.
- Time series
- GPS start time ($gpsstart), end time ($gpsend)
- The center is the trigger time.
- Time span is roughly larger one of [4sec, trigger duration * 10]. (Adjusted to fit the spectrogram requirement)
- Output directory ($outdir)
- Channel ($chlist[@])
- Lock state segment bar: flag($lock), guardian channel($lchannel), guardian value($lnumber), segment bar title($llabel)
- Data file type ($data)
- Full data is used.
- If time span is too long, down sample is applied.
- GPS start time ($gpsstart), end time ($gpsend)
- Spectrum
- List of GPS start time ($gpsstarts30[@]), end time ($gpsend30[@])
- Trigger time and 2sec before and after the trigger is avoided.
- About 30 sec is used each before trigger and after trigger spectrum.
- The length is adusted to the multiple of the FFT length.
- Output directory ($outdir)
- Channel ($chlist[@])
- FFT length ($fft30)
- 1/band width (Adjusted to the nearest 2^n sec.)
- List of GPS start time ($gpsstarts30[@]), end time ($gpsend30[@])
- Spectrogram, coherencegram
- GPS start time ($gpsstart), end time ($gpsend)
- The center is the trigger time.
- Time span is roughly larger one of [4sec, trigger duration * 10].
- The length is adjusted to be Stride * n
- Output directory ($outdir)
- Channel ($chlist[@])
- Lock state segment bar: flag($lock), guardian channel($lchannel), guardian value($lnumber), segment bar title($llabel)
- Stride ($stride)
- To have enough time resolution to see the glitch.
- FFT length ($fft)
- stride = FFT length * n
- With and without whitening (Spectrogram)
- GPS start time ($gpsstart), end time ($gpsend)
- Q-transform (Under testing. GWpy default parameter is used.)
- GPS start time ($gpsstart), end time ($gpsend)
- Output directory ($outdir)
- Channel ($chlist[@])
- Lock state segment bar: flag($lock), guardian channel($lchannel), guardian value($lnumber), segment bar title($llabel)
- Lock segment summary
- GPS start time ($gpsstart), end time ($gpsend)
- Same as time series
- Output directory ($outdir)
- Channel ($channel)
- Trigger time ($gpstime) and duration ($max_duration)
- Taken from Omicron information
- GPS start time ($gpsstart), end time ($gpsend)
Source code
Master branch: On Kamioka server, plotter.sh runs by crontab every 15 min. plotter.py is called. it gives clustered Omicron trigger information as a text file. The text files are sent to Kashiwa server by rsync.
kashiwa branch: On Kashiwa sercer, GlitchPlot.sh runs by crontab every 15 min. Using text file sent from Kamioka, condor_jobfile_plotter.sh runs to throw jobs into condor to make plots.
Info log
Trigger channel list log
8/15~ (X-arm nightly, only time with K1:MIF-WE_ARE_DOING_NOTHING == 1)
Channel |
SNR threshold |
CAL-CS_PROC_XARM_FREQUENCY_DQ |
21 |
Lock state : X-arm |
8/10~ (X-arm nightly, only time with K1:MIF-WE_ARE_DOING_NOTHING == 1)
Channel |
SNR threshold |
CAL-CS_PROC_XARM_FREQUENCY_DQ |
21 |
LSC-CARM_SERVO_MIXER_DAQ_OUT_DQ |
15 |
AOS-TMSX_IR_PD_OUT_DQ |
15 |
IMC-SERVO_SLOW_DAQ_OUT_DQ |
12 |
IMC-CAV_TRANS_OUT_DQ |
45 |
PSL-PMC_TRANS_DC_OUT_DQ |
35 |
Lock state : X-arm |
7/25~ (only 0:00~8:00)
Channel |
Requirement |
IMC-CAV_TRANS_OUT_DQ |
Lock loss |
PSL-PMC_TRANS_DC_OUT_DQ |
Lock loss |
LSC-REFL_PDA1_RF17_Q_ERR_DQ |
Lock loss |
LSC-POP_PDA1_RF17_Q_ERR_DQ |
Lock loss |
LSC-AS_PDA1_RF17_Q_ERR_DQ |
Lock loss |
CAL-CS_PROC_IMC_FREQUENCY_DQ |
Lock loss |
Lock state : MICH |
7/19~ (only 0:00~8:00)
Channel |
SNR threshold |
IMC-CAV_TRANS_OUT_DQ |
45 |
PSL-PMC_TRANS_DC_OUT_DQ |
40 |
LSC-REFL_PDA1_RF17_Q_ERR_DQ |
16 |
LSC-POP_PDA1_RF17_Q_ERR_DQ |
18 |
LSC-AS_PDA1_RF17_Q_ERR_DQ |
25 |
CAL-CS_PROC_IMC_FREQUENCY_DQ |
25 |
Lock state : LSC |
7/13 (MICH ER)
Channel |
SNR threshold |
IMC-CAV_TRANS_OUT_DQ |
35 |
PSL-PMC_TRANS_DC_OUT_DQ |
30 |
LSC-REFL_PDA1_RF17_Q_ERR_DQ |
6 |
LSC-POP_PDA1_RF17_Q_ERR_DQ |
8 |
LSC-AS_PDA1_RF17_Q_ERR_DQ |
15 |
CAL-CS_PROC_IMC_FREQUENCY_DQ |
15 |
Lock state : LSC |
7/12~ and 7/13 11:30~24:00
Channel |
SNR threshold (8:00~24:00) |
SNR threshold (0:00~8:00 and 7/13 11:30~24:00) |
IMC-CAV_TRANS_OUT_DQ |
veto |
10 |
PSL-PMC_TRANS_DC_OUT_DQ |
veto |
30 |
LSC-REFL_PDA1_RF17_Q_ERR_DQ |
veto |
30 |
LSC-POP_PDA1_RF17_Q_ERR_DQ |
veto |
30 |
LSC-AS_PDA1_RF17_Q_ERR_DQ |
veto |
30 |
CAL_CS_PROC_IMC_FREQUENCY_DQ |
veto |
30 |
Lock state : MICH |
7/10~
Channel |
SNR threshold (8:00~24:00) |
SNR threshold (0:00~8:00) |
IMC-CAV_TRANS_OUT_DQ |
veto |
20 |
PSL-PMC_TRANS_DC_OUT_DQ |
veto |
40 |
PEM-ACC_MCF_TABLE_REFL_Z_OUT_DQ |
veto |
40 |
PEM-ACC_PSL_PERI_PSL1_Y_OUT_DQ |
veto |
20 |
PEM-MIC_PSL_TABLE_PSL4_Z_OUT_DQ |
veto |
20 |
Lock state : IMC |
7/5~7/9 (buggy setting)
Channel |
SNR threshold (8:00~24:00) |
SNR threshold (0:00~8:00) |
IMC-CAV_TRANS_OUT_DQ |
100 |
veto |
PSL-PMC_TRANS_DC_OUT_DQ |
100 |
veto |
PEM-ACC_MCF_TABLE_REFL_Z_OUT_DQ |
100 |
veto |
PEM-ACC_PSL_PERI_PSL1_Y_OUT_DQ |
100 |
veto |
PEM-MIC_PSL_TABLE_PSL4_Z_OUT_DQ |
100 |
veto |
Lock state : IMC |
6/8 during ER
Channel |
SNR threshold |
LSC-CARM_SERVO_MIXER_DAQ_OUT_DQ |
10 |
AOS-TMSX_IR_PD_OUT_DQ |
10 |
IMC-MCL_SERVO_OUT_DQ |
30 |
IMC-SERVO_SLOW_DAQ_OUT_DQ |
7 |
IMC-CAV_TRANS_OUT_DQ |
10 |
IMC-CAV_REFL_OUT_DQ |
10 |
PSL-PMC_TRANS_DC_OUT_DQ |
30 |
PSL-PMC_MIXER_MON_OUT_DQ |
10 |
Lock state : IMC |
6/12~7/5
Channel |
SNR threshold |
IMC-CAV_TRANS_OUT_DQ |
100 |
PSL-PMC_TRANS_DC_OUT_DQ |
100 |
PEM-ACC_MCF_TABLE_REFL_Z_OUT_DQ |
100 |
PEM-ACC_PSL_PERI_PSL1_Y_OUT_DQ |
100 |
PEM-MIC_PSL_TABLE_PSL4_Z_OUT_DQ |
100 |
Lock state : IMC |
6/7~6/12
Channel |
SNR threshold |
LSC-CARM_SERVO_MIXER_DAQ_OUT_DQ |
100 |
AOS-TMSX_IR_PD_OUT_DQ |
100 |
IMC-MCL_SERVO_OUT_DQ |
30 |
IMC-SERVO_SLOW_DAQ_OUT_DQ |
7 |
IMC-CAV_TRANS_OUT_DQ |
10 |
IMC-CAV_REFL_OUT_DQ |
10 |
PSL-PMC_TRANS_DC_OUT_DQ |
30 |
PSL-PMC_MIXER_MON_OUT_DQ |
10 |
Lock state : X-arm |
Update log
8/20 Test version for data analysis pipeline result CBC Burst
- 8/14 Only main channel trigger is used.
- 8/10 For daily run, both glitch and lockloss are monitored during nightly data taking. Trigger list is updated to adapt X-arm configuration.
- 7/24 For daily run, only lock loss events will be monitored.
7/19 Glitch events in ER on 7/13 are reprocessed. Yuzu summary
- 7/13 SNR thresholds are optimized ER trigger rate.
- 7/12 Trigger channel is changed for MICH optimized set.
- 7/10 Changed SNR threshold.
- 7/9 Bug fix for SNR threshold lowering.
- 7/5 SNR threshold is lowered during 0am-8am. Instead, daytime events are all rejected.
- 7/5 Missing plot for PEM trigger channel is fixed.
- 7/4 ER events are reprocessed.
- 7/4 Started this wiki.