Differences between revisions 1 and 12 (spanning 11 versions)

DQ Shift checklist (2020 Apr 7-20)

Task No.	Theme	Substance
1.	Check SummaryPage works or not	See https://gwdet.icrr.u-tokyo.ac.jp/~controls/summary/monitoring/ Status should be OK
2.	Check Sensitivity & Binary range transition	See https://gwdet.icrr.u-tokyo.ac.jp/~controls/summary/today/ When you find some transitions, post to klog
3.	Check Spectral line noise (Yesterday)	See https://gwdet.icrr.u-tokyo.ac.jp/~controls/summary/yesterday/detchar/fscan/ When you find new or disappeared lines, post line information (frequency, transition time, etc.) to klog
4.	Check Lockloss data	See https://gwdet.icrr.u-tokyo.ac.jp/~controls/summary/today/ We can get the GPS time list at lockloss (GPS end). See below for more challenging characterization.
5.	Check the input power	The EPICS channel showing the input power is K1:LAS-POW_IMC_DC_OUT_DQ
6.	DQ shift Reports	Post the findings on klog, for example, klog12282

Additional DQ challenge: Lockloss investigation

If you have an access to the control room machines or main data server, please try to find the cause of lockloss by checking the following important channels! Many of the listed channels can be found in SummaryPages, however it might be difficult to look closer only with it.
Did any suspensions move drastically?
- Check the following oplev channels:
  - K1:VIS-{PRM, PR2, PR3, BS, SR3, SR2, SRM, ITMX, ITMY, ETMX, ETMY}_TM_OPLEV_{PIT, YAW}_DIAG_DQ (urad) for large suspensions.
  - K1:VIS-{MCI, MCO, MCE, IMMT1, IMMT2, OMMT1, OMMT2, OSTM}_TM_OPLEV_{PIT, YAW}_OUT_DQ (not calibrated in urad except MCI, MCE, MCO) for type-C suspensions.
Did any error signals have obvious glitch or saturation?
- Error signal channels are K1:LSC-{DARM, MICH, PRCL, MCL}_IN1_DQ. (This DQ channel existed since Apr 15)
Did the OMC DC signal (DARM error signal) have glitches or saturation?
- Check K1:OMC-TRANS_DC_{A,B}_IN1_DQ
Was POP90I buildup (the sideband buildup within the power-recycling cavity, PRC) degrading before lockloss?
- K1:LSC-POP_PDA2_RF90_I_NORM_DQ
Which arm did start degrading first?
- IR X buildup: K1:LSC-TR_X_NORM_OUT_DQ
- IR Y buildup: K1:LSC-TR_Y_NORM_OUT_DQ
- GR X buildup: K1:AOS-TMSX_GR_PDA1_OUT_DQ
- GR Y buildup: K1:AOS-TMSY_GR_PDA1_OUT_DQ

KAGRA/Subgroups/DET/DataQuality/DQshift200407_20 (last edited 2020-04-21 22:47:26 by KeikoKokeyama)

-  ⇤ ← Revision 1 as of 2020-04-15 22:02:24 → 
  Size: 3577
  Editor: KeikoKokeyama
  Comment:
+   ← Revision 12 as of 2020-04-16 18:05:19 → ⇥
  Size: 2735
  Editor: KeikoKokeyama
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-= Shift tasks related with DetChar =
+= DQ Shift checklist (2020 Apr 7-20) =
 Line 8:
-||4. || Check Lockloss data                              || See https://gwdet.icrr.u-tokyo.ac.jp/~controls/summary/today/ <<BR>>We can get the GPS time list at lockloss (GPS end)||
||5. || DetChar Reports during ER1 || [[http://klog.icrr.u-tokyo.ac.jp/osl/?r=12282 | klog12282]], [[http://klog.icrr.u-tokyo.ac.jp/osl/?r=12275 | klog12275]], [[http://klog.icrr.u-tokyo.ac.jp/osl/?r=12264 | klog12264]], [[http://klog.icrr.u-tokyo.ac.jp/osl/?r=12257 | klog12257]], [[http://klog.icrr.u-tokyo.ac.jp/osl/?r=12205 | klog12205]]||
+||4. || Check Lockloss data                              || See https://gwdet.icrr.u-tokyo.ac.jp/~controls/summary/today/ <<BR>>We can get the GPS time list at lockloss (GPS end). See below for more challenging characterization.||
||5. || Check the input power|| The EPICS channel showing the input power is K1:LAS-POW_IMC_DC_OUT_DQ||
||6. || DQ shift Reports || Post the findings on klog, for example, [[http://klog.icrr.u-tokyo.ac.jp/osl/?r=12282 | klog12282]]||
-Line 11:
+Line 12:
-=== Additional trial ===
  * '''Check Sensitivity & Binary range transition'''
    Let's investigate the noise source which caused such a transition.
    Open sitemap and access [sitemap] -> [DetChar] -> [Bruco] (See [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=9081|JGW-G1809081]])
  * '''Check Spectral line noise'''
    Let's investigate the frequency, stability with more fine frequency resolution.
    Open sitemap and access [sitemap] -> [DetChar] -> [Mnitors] -> [DARM lines]
  * '''Check Lockloss data'''
    Let's investigate the localsss causes.
    Open sitemap and access [sitemap] -> [DetChar] -> [Lockloss]
+=== Additional DQ challenge: Lockloss investigation ===
 If you have an access to the control room machines or main data server, please try to find the cause of lockloss by checking the following important channels! Many of the listed channels can be found in SummaryPages, however it might be difficult to look closer only with it.
-Line 23:
+Line 15:
-=== New suggestions for Detchar shift ===

You should change the interferometer state from ‘Locked’ to ‘Observing’ before checking the below details:

  * Summary

 * Has the average range changed significantly?

 * Is the number and character of the range drop events, significantly differ? 
     (To check how each range drop event behaves)

    * Are there any significant changes in the glitchgram?

 * Is any new or unexpected noise visible in the h(t) spectrogram?

 * Are there any anomalies in the glitch rate for loud glitches?


  * Lock/Sensitivity/glitches

 * Is there anything unusual in the hourly glitchgrams?


  * Lock/Sensitivity/strain

 * Is there anything unusual in the hourly h(t) spectrograms?


  * SEI/Ground/BLRMS_overview

 * Do any seismic gestures (earthquakes, anthrogrogenic etc..) appear to correlate with noise in h(t)?

 * PEM - all but especially seismic and acoustic

            * Are there any significant changes, especially new features, in the PEM channels?

 * Hveto

   * Hveto finds correlations between the h(t) glitches and glitches in other channels. Classes of glitches that might have the same cause are thus identified. “Significance” measures the strength of a correlation. Are any of the most significant channels different from those of the previous days or shifts? 

 * Fscan
  Check for a new or disappeared lines, note down line information such as frequency, transition time
+ * Did any suspensions move drastically?
  * Check the following oplev channels:
   * K1:VIS-{PRM, PR2, PR3, BS, SR3, SR2, SRM, ITMX, ITMY, ETMX, ETMY}_TM_OPLEV_{PIT, YAW}_DIAG_DQ (urad) for large suspensions.
   * K1:VIS-{MCI, MCO, MCE, IMMT1, IMMT2, OMMT1, OMMT2, OSTM}_TM_OPLEV_{PIT, YAW}_OUT_DQ (not calibrated in urad except MCI, MCE, MCO) for type-C suspensions.
 * Did any error signals have obvious glitch or saturation?
   * Error signal channels are K1:LSC-{DARM, MICH, PRCL, MCL}_IN1_DQ. (This DQ channel existed since Apr 15)
 * Did the OMC DC signal (DARM error signal) have glitches or saturation?
   * Check K1:OMC-TRANS_DC_{A,B}_IN1_DQ
 * Was POP90I buildup (the sideband buildup within the power-recycling cavity, PRC) degrading before lockloss?
   * K1:LSC-POP_PDA2_RF90_I_NORM_DQ 
 * Which arm did start degrading first?
   * IR X buildup: K1:LSC-TR_X_NORM_OUT_DQ
   * IR Y buildup: K1:LSC-TR_Y_NORM_OUT_DQ
   * GR X buildup: K1:AOS-TMSX_GR_PDA1_OUT_DQ
   * GR Y buildup: K1:AOS-TMSY_GR_PDA1_OUT_DQ