LVK Detchar Meeting
ligo.org Teamspeak Detchar channel Teamspeak
- June 11th 8.00am PT / 11.00am ET / 5.00pm CET / June 12th 12am JST
Topic |
Presenter |
Duaration |
File |
|
Short commissioning update |
Taka-aki Yokozawa |
5min |
||
Detchar status |
||||
KAGRA DQ update |
Takahiro Yamamoto |
5min |
||
Glitch study update |
Chihiro Kozakai |
5min |
||
Glitch dataset archiving |
Pil-Joing Jung |
5min |
||
Line and other tool |
Shoichi Oshino |
5min |
||
PEM update |
Tatsuki Washimi |
5min |
||
Summary Pages update |
Keiko Kokeyama |
2min |
||
- Discussion (~20min)
- LV detchar Status during O3
- What to prepare before the observation
- Event trigger database at KAGRA?
- How do KAGRA share the detchar info (flags, triggers, etc) with L-V?
- How are L-V sharing?
- Could we do detchar-engineering run with L-V?
- Anything else?
Quick minutes
Takahiro's questions:Data category criteria? DQ report?
Jess, Nicolas: Segment database, graceDB - we could plug to the LV one, it should be simple. VIRGO does this way. VIRGO does local detchar checks on EGO machines independently, then upload results to graceDB and so on. We'll discuss over emails. Contact Ryan Fisher.
LV ERs and Observations have
DQ shifts (LIGO-L1500110, LIGO DetChar Rotas)
- Weekly DQ shift
- tool results integrate to summary pages
- they have been working as good training for junior colleagues
- Rapid response team; experts team for particular events, They are on call (run manager, from all the teams including instruments, data analysts and EM)
Nicolas suggestion: focus on main milestones such as securing tool reliability and so on.
Jess pointed the DQ Report (DQR) documentation