Meetings

• Meeting time: 13:00-13:30 JST/KST on every Monday
• Meeting room: Zoom

Agenda & Minutes

20220228 (Mon.)

• Agenda
  • 120Hz glitches
  • conda environment for Kamioka detchar computers(k1sum[01] and k1det[012])

  • RRT plan during O4 slide

  • DQ flags for O4
  • progress of DQR
  • lock loss study of GreenX

20220228 (Mon.)

• Agenda
  • 120Hz glitches
  • DQ flags for O4
  • progress of DQR
  • lock loss study of GreenX
• Minutes
  • accouncement

    • LVK meeting March 2022 wiki web

      • registration is available
      • Wed, 17 March 2021:
        • Plenary Session #1 (09:00-10:30 US/CDT) (=3/16 23:00 JST)
        • Paper Presentation Session #1
        • Plenary Session #2 (16:00-17:30 US/CDT) (=3/17 6:00 JST)
      • Thu, 18 March 2021:
        • Plenary Session #3 (09:00-10:30 US/CDT) (=3/17 23:00 JST)
        • Paper Presentation Session #2
        • Plenary Session #4 (16:00-17:30 US/CDT) (=3/18 6:00 JST)
    • Pastavi server will be unavailable tonight

      • klog#19913

  • 120Hz glitches
    • no update
  • DQ flags for O4
    • no update
  • progress of DQR
    • igwn-alert is running more than 9days and receiving the MDC alert

    • next step is to connect the MDC alert with the launch TaskManager.

    • remained task is to develop InspiralRange issue

  • lock loss study of GreenX

    • klog#19906

    • From the Hveto result, the channel (K1:IMC-SERVO_MIXER_DAQ_OUT_DQ) was the most coincident channel with the lock loss of GreenX.
  • unify the detchar computing environment (YamaT)
    • scattered codes and applications (Omicron, summary page, ) over Kamioka computers are troubling.
    • we plan to unify the environment by using igwn conda
    • detail will be reported in next meeting
    • (Darkhan) conda environment on k1ctr*. someone accidentally update someone's conda environment. administrator should prepare the conda environment?
    • (YamaT) k1ctr* share the environment. this activity is not related to k1ctr* but k1sum[01], k1det[012]. we should separate the user environment and the environment for the DET tools
    • (Darkhan) should avoid accidental mistake.

20220221 (Mon.)

• Agenda
  • 120Hz glitches
  • DQ flags for O4
  • progress of DQR
• Minutes
  • 120Hz glitches
    • No updates
  • DQ flags for O4
    • No updates
  • progress of DQR

    • klog#19847

  • Proposal new tool to see past data by NDS (Darkhan)

20220207 (Mon.)

• Agenda
  • 120Hz glitches

  • Report from LIGO Detchar F2F Meeting

  • DQ flags for O4
  • progress of DQR
• Minutes
  • 120Hz glitches
    • No updates
  • DQ flags for O4

    • slide

    • (Yuzurihara) read BLRMS data and made the several plots with 1% and 99% percentile.
    • When KAGRA will be locked as observation mode?
      • hopefully after july, there will be lock trial for two monthes(?)
    • When you set the 1% criteria, always you throw away the 1% data?
      • We might need to consider the better procedure to care that point.
  • progress of DQR

    • klog#19671

20220131 (Mon.)

• Agenda
  • 120Hz glitches
  • Report from DQR hackathon
  • DQ flags for O4
  • Master thesis (Morisue-san)

20220117 (Mon.)

• Agenda
  • 120Hz glitches
  • ITMX glitches
  • DQR progress
  • DQ flags for O4
• Minutes
  • 120Hz glitches
    • No updates
    • Next step is coincidence search with signals around ETMY including local control sensors.
  • ITMX glitches

    • klog#19212

    • K1:VIS-ITMX_F3_LVDTINF_GAS_{IN1,OUT} have glitches.
    • It seems to occur around AA chassis. (AA and cable replacement didn't help to improve situation).
    • We will try to find glitches on other channels on the same ADC board.

    • This channel should be added to Omicron search on SummaryPages.

  • DQR progress

    • JGW-G2213721

  • DQ flags for O4
    • No updates
  • O3GK paper
    • Threshold used for computing a glitch rate was changed as SNR=6.5.
    • It's a same criterion with LIGO, and Virgo.
    • Both GEO and KAGRA's results are now computed and draft was also updated.

Past meeting

• 2021

• 2020

• 2019