GlitchPlot

This project is for glitch and lock loss study. Also applicable to event validation of GW candidate. You can see the result here.

Original developer: Chihiro Kozakai (production of plots), Hirotaka Yuzurihara (web page).

The latest trigger channel list

4/7~4/20 O3GK

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.

Also, GlitchPlot uses lock loss information based on lock state information of guardian.

For each events, plots for triggered channel and relevant channels are provided here. 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.

There is channel list of 2 types of suggestion. The intent of this list is to pick up suspicious channels which is related to noise source.

• Suggestion 1: picked up by higher coherence than usual
• Suggestion 2: picked up by high SNR in Q-transform

The event web page shows the result in the following order. 1. Lock state 2. Trigger channel plots 3. Suggestion 1 channel plots 4. Suggestion 2 channel plots 5. Channels affected by DARM DoF 6. Other channels

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.
• 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

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 server, 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.

Job structure

O3GK configuration (2020/12/16: It is stopped.)

1. On k1sum1: From the Omicron result, triggered event and the parameters are summarized as text files. The files are rsync-ed to Kashiwa server.

By crontab, 4-59/15 * * * * /users/DET/tools/GlitchPlot/Script/plotter.sh > /tmp/GlitchPlot.log 2>&1

2. On chihiro.kozakai@m31-02: Based on text file sent from k1sum1, plots are produced using condor.

By crontab,

4-59/15 * * * * /home/chihiro.kozakai/detchar/KamiokaTool/tools/GlitchPlot/Script/GlitchPlot.sh > /tmp/GlitchPlot.log 2>&1
10 */3 * * * /home/chihiro.kozakai/detchar/KamiokaTool/tools/GlitchPlot/Script/plotter_lockloss.sh > /tmp/GP_lockloss.log 2>&1

3. On k1det0: Plots on Kashiwa server is rsync-ed. Then html for the web page is generated and accessible on GWDET server.

By crontab, 30 */3 * * * /users/DET/tools/GlitchPlot/Script/GlitchPlot_html.sh > /tmp/GlitchPlot.log

Note for developer

• Please modify output directory.
• Job structure should be modified. Step 2 should be moved to detchar account. If web server is implemented on Kashiwa server, Step 1 and 3 also have to be moved to Kashiwa server.
• It is better to use low-latency pipeline result for RRT. CBC and burst pipeline configuration is under constructing.
• Please reconsider channel list. At least, SRCL related channels will be required. ASC maybe also important.
• Top page maybe better to start from the latest date.