Differences between revisions 364 and 365
Revision 364 as of 2022-03-07 13:39:06
Size: 7242
Comment:
Revision 365 as of 2022-03-07 13:39:51
Size: 7276
Comment:
Deletions are marked like this. Additions are marked like this.
Line 41: Line 41:
    * For the date, see [[https://klog.icrr.u-tokyo.ac.jp/osl/index.php?r=19963|klog#19963]] [[https://klog.icrr.u-tokyo.ac.jp/osl/index.php?r=19983|klog#19983]]     * For the available data (channel name and time), see [[https://klog.icrr.u-tokyo.ac.jp/osl/index.php?r=19963|klog#19963]] [[https://klog.icrr.u-tokyo.ac.jp/osl/index.php?r=19983|klog#19983]]

Meetings

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


Agenda & Minutes


20220307 (Mon.)

  • Agenda
    • announcement
      • RRT plan during O4 slide

      • LVK meeting March 2022 wiki web

        • registration is available
    • 120Hz glitches investigation during O3GK
    • unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012] (YamaT)
    • DQ flags for O4
    • DQR update
  • Minutes
    • 120Hz glitches investigation during O3GK
      • no update
    • unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012] (YamaT)
      • There are many computers/workstations in Kamioka site or Kamioka control room.
      • Workstations (k1ctr*) use common conda environment by mounting the file server.
      • In DetChar computers k1{sum,det}[01], conda environment should be unified all DetChar resources, similar to workstations.

      • To prevent the trouble that DetChar experts might break the environment, the conda environments will be set as read-only permission.

      • Installation will be done by Kamioka members. After that, we need volunteers to test the DetChar tools on new conda environment.

      • what is the time line?
        • Installation will finished before the end of March. From April, the test will start. Volunteers are helpful.
    • DQ flags for O4
    • DQR update
      • no update
    • Commissioning of GreenX
      • In the last weekend, the commissioner tried continuous GreenX. During that trials, the sudden lock losses were observed.
      • The commissioner needs helps DetChar members to identify the cause or give a hint of the cause.

      • For the available data (channel name and time), see klog#19963 klog#19983


20220228 (Mon.)

  • Agenda
    • 120Hz glitches
    • DQ flags for O4
    • progress of DQR
    • lock loss study of GreenX
  • Minutes (Yuzurihara)
    • 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
    • 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
    • Proposal new tool to see past data by NDS (Darkhan)


20220207 (Mon.)

  • Agenda
  • 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


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
    • 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

KAGRA/Subgroups/DET/Meeting (last edited 2024-03-27 11:26:27 by TakahiroYamamoto)