Differences between revisions 347 and 1579 (spanning 1232 versions)
⇤ ← Revision 347 as of 2022-03-02 15:40:29 →
Size: 5312
Editor: HirotakaYuzurihara
Comment:
← Revision 1579 as of 2025-01-08 10:59:12 → ⇥
Size: 3259
Editor: HirotakaYuzurihara
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
  * Meeting time: 13:00-13:30 JST/KST on every Monday
  * Meeting room: Zoom		   * Meeting time: 11:00-11:30 JST/KST on every Wednesday
  * Meeting room: Zoom3
Line 8: Line 8:
== Agenda & Minutes ==

-----
=== 20220228 (Mon.) ===
  * Agenda
    * announcement
     * RRT plan during O4 [[https://dcc.ligo.org/LIGO-G2102323|slide]]
    * 120Hz glitches investigation during O3GK
    * conda environment for Kamioka detchar computers, k1sum[01] and k1det[012] (YamaT)
    * 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 [[https://wiki.ligo.org/LSC/Meeting/LVKMeetingMarch2022|wiki]] [[https://cgca.uwm.edu/events/2021lvk|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
       * [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=19913|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 [[https://git.ligo.org/detchar/dqrtasks/-/issues/8|issue]]
    * lock loss study of GreenX
     * [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=19906|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
      * [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=19847|klog#19847]]
    * Proposal new tool to see past data by NDS (Darkhan)

-----
=== 20220207 (Mon.) ===
  * Agenda
    * 120Hz glitches
    * Report from [[https://wiki.ligo.org/DetChar/JanFeb2022DetCharF2F|LIGO Detchar F2F Meeting]]
    * DQ flags for O4
    * progress of DQR
  * Minutes
    * 120Hz glitches
      * No updates
    * DQ flags for O4
      * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=13851|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
      * [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=19671|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
      * [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=19212|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
      * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=13721|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.		 === 20250108 (Wed.) ===
 * Agenda
   * Announcement
    * O4b schedule:
     * '''O4b''': O4b will now end 9 June 2025.
     * [[https://observing.docs.ligo.org/plan/|Run plan(12/15 updated)]] [[https://wiki.ligo.org/Operations/Agenda241219|operation (12/19)]]
    * Scheduled conference
     * LVK meeting: 2024/03/24-27 @Albert Park, Melbourne, Australia
      * Early bird registration will close at 2025/01/16.
     * Open Data Workshop 2024/05/12-14
     * GWADW 2025: 2024/05/18~5/23 @the Hilton Cocoa Beach (Florida) Oceanfront
     * Amaldi & GR: 2024/07/14-18 @Scottish Exhibition Centre, Glasgow, UK [[https://iop.eventsair.com/gr24-amaldi16/|web]]
     * ICRC 2025: 2024/07/15-24 @Geneva (Switzerland) [[https://indico.cern.ch/e/icrc2025|web]]
    * KAGRA site report [[https://gwdoc.icrr.u-tokyo.ac.jp/DocDB/0162/L2416243/001/KAGRAReport_20241211.pdf|12/11]]
     * For the summary during holidays, see Miyoki-san's mail.
    * Evaluation of effort for KAGRA authorship 2024 is underway.
    * Several visiter at KAGRA site during January
    * Next meeting: 2025/01/15
   * Progress reports
     * Upgrade DetChar computers (YamaT)
     * DQR update (Yuzurihara)
     * lock loss study in the commissioning (YamaT, Yuzurihara) [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/misc/html/lockloss_o4b_break.html|web]]
     * Update contents of summary page (Oshino)
     * Related to segment files (Uchikata, Narikawa)
     * pyCBC trigger list for O4a data (Narikawa and Uchikata)
     * provide the CAT1 veto-definer file for IPC glitch (Uchikata)
 * Minutes
     * Commissioning support
      * Summarize the lockloss count labeled by the SYS_LOCKLOSS guardian [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=32170|klog]] [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=16404|table]]
      * Categorization by the behavior of POP90 before the lockloss [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=32167|klog]]
     * Segment file
      * The segment of `K1-GRD_PEM_EARTHQUAKE` is already available on DQSEGDB. For other new segments will be available at DQSEGDB. ([[https://git.ligo.org/computing/helpdesk/-/issues/6176#note_1245022|git issue]])
      * Name convention issue came up. Plan: `K1-DAQ-IPC_ERROR` --> `K1-DAQ_IPC_ERROR`. Before releasing this segment, we have a chance to change the name.
      * We need to update other scripts if we change the segment name. Developers or maintainers, please check your code.
     * It's better to keep the code in the [[https://github.com/gw-detchar/tools|GitHub repository]] up-to-date. Remember to push the code after you modified it or confirmed it's stable.
     * The line monitor is working well during the holidays. [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/LineMonitor/day/today/|web]]
Line 134: Line 47:
  * [[KAGRA/Subgroups/DET/Meeting/2024|2024]]
  * [[KAGRA/Subgroups/DET/Meeting/2023|2023]]
  * [[KAGRA/Subgroups/DET/Meeting/2022|2022]]

Meetings

  • Meeting time: 11:00-11:30 JST/KST on every Wednesday
  • Meeting room: Zoom3

Contents

  1. Meetings
      1. 20250108 (Wed.)
      2. Past meeting

20250108 (Wed.)

  • Agenda
    • Announcement
      • O4b schedule:
      • Scheduled conference
        • LVK meeting: 2024/03/24-27 @Albert Park, Melbourne, Australia
          • Early bird registration will close at 2025/01/16.
        • Open Data Workshop 2024/05/12-14
        • GWADW 2025: 2024/05/18~5/23 @the Hilton Cocoa Beach (Florida) Oceanfront

        • Amaldi & GR: 2024/07/14-18 @Scottish Exhibition Centre, Glasgow, UK web

        • ICRC 2025: 2024/07/15-24 @Geneva (Switzerland) web

      • KAGRA site report 12/11

        • For the summary during holidays, see Miyoki-san's mail.
      • Evaluation of effort for KAGRA authorship 2024 is underway.
      • Several visiter at KAGRA site during January
      • Next meeting: 2025/01/15
    • Progress reports

      • Upgrade DetChar computers (YamaT)

      • DQR update (Yuzurihara)

      • lock loss study in the commissioning (YamaT, Yuzurihara) web

      • Update contents of summary page (Oshino)
      • Related to segment files (Uchikata, Narikawa)
      • pyCBC trigger list for O4a data (Narikawa and Uchikata)
      • provide the CAT1 veto-definer file for IPC glitch (Uchikata)
  • Minutes
    • Commissioning support

      • Summarize the lockloss count labeled by the SYS_LOCKLOSS guardian klog table

      • Categorization by the behavior of POP90 before the lockloss klog

    • Segment file

      • The segment of K1-GRD_PEM_EARTHQUAKE is already available on DQSEGDB. For other new segments will be available at DQSEGDB. (git issue)

      • Name convention issue came up. Plan: K1-DAQ-IPC_ERROR --> K1-DAQ_IPC_ERROR. Before releasing this segment, we have a chance to change the name.

      • We need to update other scripts if we change the segment name. Developers or maintainers, please check your code.

    • It's better to keep the code in the GitHub repository up-to-date. Remember to push the code after you modified it or confirmed it's stable.

    • The line monitor is working well during the holidays. web

Past meeting

KAGRA/Subgroups/DET/Meeting (last edited 2025-01-08 14:17:09 by HirotakaYuzurihara)