= Shift tasks related with DetChar =
||<#AAFFC3 style="text-align:center; "> '''Task No.''' ||<#AAFFC3 style="text-align:center; "> '''Theme''' ||<#AAFFC3 style="text-align:center; "> '''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 [[http://klog.icrr.u-tokyo.ac.jp/osl/|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 [[http://klog.icrr.u-tokyo.ac.jp/osl/|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)||
||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]]||
=== 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]
=== 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