Differences between revisions 6 and 28 (spanning 22 versions)
Revision 6 as of 2019-06-10 19:16:42
Size: 1023
Comment:
Revision 28 as of 2019-06-13 10:37:47
Size: 2564
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * ligo.org Teamspeak Detchar channel  * ligo.org Teamspeak Detchar channel [[KAGRA/Subgroups/DGS/Meeting/LKAccess|Teamspeak]]
Line 7: Line 7:
|| Short commissioning update || Taka-aki Yokozawa || 5min || x|| || Short commissioning update || Taka-aki Yokozawa || 5min || [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/DocDB/ShowDocument?docid=10310|o]]||
Line 9: Line 9:
|| KAGRA DQ update || Takahiro Yamamoto || 5min || x||
|| Glitch study update || Chihiro Kozakai || 5min || x||
|| Glitch dataset archiving || Pil-Joing|| 5min || [[https://gwdoc.icrr.u-tokyo.ac.jp/DocDB/0103/G1910304/001/LVK_DetChar_meeting_20190611.pdf|o]]||
|| Line and other tool || Oshino || 5min || x||
|| PEM update || Washimi|| 5min || [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=10284|KIW6 slide]]||
|| Summary Pages update || ? || 5min || x ||
|| KAGRA DQ update || Takahiro Yamamoto || 5min || [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/DocDB/ShowDocument?docid=10314|o]]||
|| Glitch study update || Chihiro Kozakai || 5min || [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/DocDB/ShowDocument?docid=10315|o]] ||
|| Glitch dataset archiving || Pil-Joing Jung|| 5min || [[https://gwdoc.icrr.u-tokyo.ac.jp/DocDB/0103/G1910304/001/LVK_DetChar_meeting_20190611.pdf|o]]||
|| Line and other tool || Shoichi Oshino || 5min ||  [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/DocDB/ShowDocument?docid=10313|o]]||
|| PEM update || Tatsuki Washimi|| 5min || [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/DocDB/ShowDocument?docid=10284|KIW6 slide]]||
|| Summary Pages update || Keiko Kokeyama || 2min || [[attachment:LVKdetchar_kk.pdf]] ||
Line 17: Line 17:
   * LV detchar Status during O3
Line 18: Line 19:
   * Status of the detchar during O3
   * How do KAGRA share the detchar info (flags, triggers, etc) with L-V?
   * Could we do engineering run with L-V?
   * Anything else?
    * 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 ([[https://dcc.ligo.org/cgi-bin/DocDB/ShowDocument?.submit=Identifier&docid=L1500110&version=|LIGO-L1500110]], [[https://wiki.ligo.org/DetChar/Rotas|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 [[https://docs.ligo.org/detchar/data-quality-report/|DQ Report (DQR) documentation]]

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

o

Detchar status

KAGRA DQ update

Takahiro Yamamoto

5min

o

Glitch study update

Chihiro Kozakai

5min

o

Glitch dataset archiving

Pil-Joing Jung

5min

o

Line and other tool

Shoichi Oshino

5min

o

PEM update

Tatsuki Washimi

5min

KIW6 slide

Summary Pages update

Keiko Kokeyama

2min

LVKdetchar_kk.pdf

  • 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

KAGRA/Subgroups/DET/Meeting/LVK0612 (last edited 2019-06-13 10:37:47 by TakahiroYamamoto)