Differences between revisions 11 and 12
⇤ ← Revision 11 as of 2019-12-23 13:42:03 →
Size: 3242
Editor: HideyukiTagoshi
Comment:
← Revision 12 as of 2019-12-23 13:42:36 → ⇥
Size: 3258
Editor: HideyukiTagoshi
Comment:
Deletions are marked like this. Additions are marked like this.
Line 61: Line 61:
  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? 		     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?

Shift tasks related with DetChar

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)

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 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]

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

KAGRA/EngineeringRun/ER191217_24/DetChar (last edited 2019-12-25 13:21:27 by miyoki)