Differences between revisions 283 and 478 (spanning 195 versions)
⇤ ← Revision 283 as of 2021-11-22 12:18:16 →
Size: 40156
Editor: TakahiroYamamoto
Comment:
← Revision 478 as of 2022-05-12 10:55:45 → ⇥
Size: 22996
Editor: HirotakaYuzurihara
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
  * Meeting time: 14:00-15:00 JST/KST on every Thursday   * Meeting time: 13:00-13:30 JST/KST on every Monday
Line 9: Line 9:
=== 20211122 (Mon.) ===
  * Agenda
    * Investigation about 120Hz glitches
    * Segments for Open data
    * Progress of DQR
    * Site commissioning
    * Report from LVK DAC telecon

=== 20211115 (Mon.) ===
  * Agenda
    * O3GK Glitch investigation
    * Segment information for open data
    * Progress of DQR
    * Site commissioning
-----
=== 20220509 (Mon.) ===
 * Agenda
   * Announcement
    * Vigo DetChar paper [[https://arxiv.org/abs/2205.01555|arXiv]]
    * GWADW2022 [[https://indico.icrr.u-tokyo.ac.jp/event/255/|web]]
    * The 9th KAGRA International Workshop (KIW) [[https://indico.itp.ac.cn/event/123/|web]]
    * The GRAvitational - wave Science&technology Symposia (GRASS 2022) [[https://agenda.infn.it/event/30681/|web]]
   * KAGRA commissioning reports
   * Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
    * call for volunteers from remote site, to test hveto and FScan. Please let us (Yuzuriahra or YamaT) know.
   * DQR update (Yuzurihara)
   * Update contents of summary page? (Oshino)
   * Combine DET computer resources into one DET cluster at Kamioka site
   * Report of new tool development? (Darkhan)
   * Glitch subtraction survey for O4
    * see mail from Davis Derek (2022 May 3)
    * deadline : May 16
    * The glitch subtraction activities are managed under DET. I would like to ask regular report in DET meeting.

 * Minuts
   * Announcement
   * KAGRA commissioning reports
    * ADC noise measurement [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20658|klog#20658]]
    * In-air health check for Yarm suspensions (ITMY and ETMY) is on-going.
     * If no problem, review will be done next week and pumping down will start on week of May 23
   * DQR update (Yuzurihara)
    * no update
   * Report of new tool development? (Darkhan)
    * add channel list?

-----
=== 20220502 (Mon.) ===
 * Agenda
   * Announcement
   * KAGRA commissioning reports
    * PRM cause the glitch in IMMT1 OPLEV signal and POP forword QPD signal [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20539|klog#20539]]
    * In-air health check for suspensions (ITMY, ETMY) is on-going by Ushiba [[ https://klog.icrr.u-tokyo.ac.jp/osl/?r=20631|klog#20631]] [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20632|klog#20632]]
   * Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
    * call for volunteers from remote site, to test hveto and FScan. Please let us (Yuzuriahra or YamaT) know.
   * DQR update (Yuzurihara)
   * Update contents of summary page? (Oshino)
   * Combine DET computer resources into one DET cluster at Kamioka site
   * Report of new tool development? (Darkhan)
   * Data Quality flag for O4a
    * We are asking the concrete requirement for DAC members (CBC, burst, Stochastic)
    * This is related to discuss the ER period and time
   * Analysis of TCam photos of ITMY and ETMY with the metal scale by Tcam
 * Minutes
   * Announcement
    * GWADW2022 [[https://indico.icrr.u-tokyo.ac.jp/event/255/|web]]
    * The 9th KAGRA International Workshop (KIW) [[https://indico.itp.ac.cn/event/123/|web]]
    * The GRAvitational - wave Science&technology Symposia (GRASS 2022) [[https://agenda.infn.it/event/30681/|web]]
   * DQR update (Yuzurihara)
    * no update.
   * Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
    * no update
   * Update contents of summary page? (Oshino)
    * [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20634|klog#20634]]
   * Analysis of TCam photos of ITMY and ETMY with the metal scale by Tcam [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20574|klog#20574]]
    * analysis is on-going by Aogaku students. Report will appear soon.

-----
=== 20220425 (Mon.) ===
 * canceld
-----
=== 20220418 (Mon.) ===
 * Agenda
   * Announcement
    * monthly maintenance for JGWDoc + JGW wiki + klog on April 18 13:00-16:00 JST.
   * Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
    * call for volunteers from remote site, to test hveto and FScan. Please let us (Yuzuriahra or YamaT) know.
   * DQR update (Yuzurihara)
   * Update contents of summary page? (Oshino)
   * Combine DET computer resources into one DET cluster at Kamioka site
   * Report of new tool development? (Darkhan)
 * Minutes
   * Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
     * No updates in last week.
     * Some volunteers for testing of hveto, fscan are sitll wanted.
     * We should start to test also iDQ from now on for future observing runs (O5, O6...)
   * DQR update (Yuzurihara)
    * operation test for tools is on-going without error and trouble
   * Update contents of summary page? (Oshino)
    * no update
   * Combine DET computer resources into one DET cluster at Kamioka site
    * no update
   * Report of new tool development? (Darkhan)
    * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=14032|slide]]
   * 120Hz glitches investigation during O3GK
    * [[https://github.com/gw-detchar/tools/tree/master/Hveto/etc|configuration file]]
-----
=== 20220411 (Mon.) ===
 * Agenda
   * Announcement
    * Workshop 2022/04/15 [[https://indico.in2p3.fr/event/26414/program|web page]]
     * DetChar talk is planed by Yokozawa. When he circulates slide, put comments on slide.
   * Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
    * call for volunteers from remote site, to test hveto and FScan. Please let us (Yuzuriahra or YamaT) know.
   * Exchange of opinions between DET members(YamaT, Sawada(OPS), Yuzurihara) and DMG members(Kanda, Oohara)
   * DQR update (Yuzurihara)
   * Update contents of summary page? (Oshino)
   * Combine DET computer resources into one DET cluster at Kamioka site
    * (Oshino) explain idea, goal, and timeline
   * Report of new tool development? (Darkhan)
   * Follow-up report of remote contribution from Aoyama Gakuin univ.
 * Minutes
   * Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
     * no volunteer yet (Test of hveto and FScan).
       * Coding kagradata.py for the new version of Bruco is ongoing.
       * We need to decide KAGRA common rule about NDS2 and DATAFIND for fixing codes.
     * NAPT test was started for the purpose of saving number of IP address in DGS network.
       * DET gateway (copy of k1gate is enough for the test) will be connected to DGS network.
         * Other nodes will be under DET gateway.
       * It may be better to construct the gateway as Deb10. (Copy of k1gate is Rocky8)
         * TY have no experience of constructing NAPT on Debian.
       * NDS(k1nds[012]), NFS(k1nfs0) services must be available from under DET gateway.
       * How should we do k1det2 which is used for Bruco running from CDS workstation.
   * Exchange of opinions between DET members(YamaT, Sawada(OPS), Yuzurihara) and DMG members(Kanda, Oohara)
    * related to conda environment and DQR tasks
    * in Kashiwa server and Kamioka computers, we should have common rule fo NDS2 and DATAFIND, which YamaT already mentioned.
   * DQR update (Yuzurihara)
    * the application to connect between igwn-alert and Task Manager was developped by Joe
    * DQRAlert [[https://git.ligo.org/o4-dqr/dqralert|git repo]]
    * I tried to run this tool in Kamioka computer and it is working well.
    * need to prepare the document of how to use this tool on wiki page.
    * [[https://git.ligo.org/o4-dqr/dqralert/-/blob/trunk/docs/source/overview.rst|DQR workflow]]
   * Update contents of summary page?
    * no update
   * Combine DET computer resources into one DET cluster at Kamioka site
    * goal : prepare job management server and can submit job to k1det[012]
    * timeline : before O4
    * there might be conflict between this cluster and NAPT test. Oshino and YamaT will discuss.
   * Follow-up report of remote contribution from Aoyama Gakuin univ.
    * (Yokozawa, Oshino, Yuzurihara) we started the discussion of task list and how to contribute from remote site.
-----
=== 20220404 (Mon.) ===
  * Agenda
    * Announcement
     * DQR design document, put comments on [[https://git.ligo.org/detchar/o4-data-quality-report-design-document/-/issues?label_name%5B%5D=Second+circulation|git issue]]
     * Workshop 2022/04/15
      * [[https://indico.in2p3.fr/event/26414/program|Workshop on the development of innovative tools for new collaborations within gravitational wave detection experiments]]
     * KAGRA's authorship submission. For details, see [kagra 05009]. Deadline April 8 17:00 JST
    * Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
    * DQR update
    * Update of summary page
    * Trouble of Omicron trigger generation
    * 120Hz glitches investigation during O3GK
Line 24: Line 159:
    * O3GK Glitch investigation => Skipped.
    * Segment information for open data
      * Data reproduction with correct segments were finished.
      * We need to check about error estimation of 4kHz downsampled data. => TY
      * Data will be release at the same time with O3GK paper.
    * Progress of DQR
      * LValert was update as python3 in LIGO.
      * We also need to move new version for O4.
      * Software test will be conducted on k1det0,1 => HY
    * Site commissioning
      * PSL room is now in working mode for future works.
        * PMC, PLL, IMC signals are affected by sound noise.
      * Glitches on MC OpLevs were decreased by wind shields.
        * [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/summary/day/20211101/detchar/mce_yaw/|before]] -> [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/summary/day/20211103/detchar/mce_yaw/|after]]
        * Noise floor level was also improved. ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=18756|klog#18756]])
        * Alignment jump by seismic disturbance in high frequency (1Hz~) still remains.
          * We need to take care about K1:VIS-MC{I,E,O}_TM_WIT_{P,Y} and K1:IMC-IMMT1_TARNS_QPDA1_DC_{PIT,YAW}_OUT
        * Plot range should be changed on SummaryPages. => SO
-----
=== 20211108 (Mon.) ===
  * Agenda
    * O3GK Glitch investigation
    * Segment information for open data
    * Progress of DQR
     * Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
      * Installation of IGWN was done on k1detfs.
        * Too slow HDD response? (~150KB/s via NFS)
      * Works well
        * SummaryPages as GPS-select mode
          * ini-file grammar is slightly changed from the old version.
        * Omicron
          * No special hack
        * Omega-scan
          * needs temporal code hack
        * Bruco
          * needs preparation for reading kagra data (kagradata.py)
          * No {{{--include}}} option in original one.
      * Not yet
        * SummaryPages as Daily mode (This will be done by Kamioka people)
        * hveto
        * FScan
          * Not included in IGWN environment?
      * Problem
        * No global NDS2, DataFind servers or equivalent way.
          * SSH port forwarding is not enough because port number is different depending on person.
          * So I cannot do the code hack on IGWN software in the system region.
        * KAGRA env may not be able to be included in IGWN until O4.
          * If so, we shouldn't use IGWN in officially for O4.
     * (Lupin) igwn-py38? or py39?
     * YamaT asked status of FScan
     * In future, we need to prepare similar environment on Kashiwa cluster. The environment is not completely same as Kamioka computers.
     * We need volunteers from remote site, to test hveto and FScan. Please let us (Yuzuriahra or YamaT) know.
    * DQR update (Yuzurihara)
     * Operation test for new version of Task Manager is on-going on k1det1.
     * I found that code of stationary task uses `datafind` to read gwf data, which we don't have.
     * I need to consider how to read data for DQR tasks.
      * (Darkhan) Is there any way to get the latest list of channels?
      * (Yuzurihara) If you can specify the name of frame data, there is a function on gwpy.
    * Update of summary page (Oshino)
     * no update
    * Trouble of Omicron trigger generation (Oshino)
     * [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20328|klog#20328]]
     * replaced the local SSD on k1sum1. The Omicron triggers are stored in different disk.
    * 120Hz glitches investigation during O3GK
     * no update
     * Kihyun can't join for a while. This project will be postponed.
    * Report of new tool development (Darkhan)
     * showed demonstration
     * this tool can take a ratio between channels and will be able to apply time-domain filter (band pass/highpass/lowpass) in future.
-----
=== 20220328 (Mon.) ===
  * Agenda
    * Announcement
     * DQR design document, put comments on [[https://git.ligo.org/detchar/o4-data-quality-report-design-document/-/issues?label_name%5B%5D=Second+circulation|git issue]]
     * Workshop 2022/04/15 [[https://indico.in2p3.fr/event/26414/program|Workshop on the development of innovative tools for new collaborations within gravitational wave detection experiments]]
    * Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
    * Activity report by students from Aoyama Gakuin univ.
     * glitch investigation related to IMMT1 oplev (Aoyama Gakuin univ.)
     * Tcam image analysis to identify mirror location and center (Aoyama Gakuin univ.)
    * DQR update
    * Update of summary page
    * 120Hz glitches investigation during O3GK

 * Minutes
  * Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
   * YamaT constructed the test environment in local computer
   * Although YamaT is copying the environment to DetChar computers, it is very slow. (speed ~ 250KB/s)
   * After copying, YamaT will work on modification of codes to fit KAGRA data, such as nds2.py
   * For testing the tools (Omicron, Hveto...), we need volunteers, especially remote site!
  * Activity report by students from Aoyama Gakuin univ.
   * five students and two staff members from Aoyama Gakuin univ. stayed Kamioka site during last three weeks.
   * They helped commissioning work both in tunnel [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20124|klog#20124]] [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20155|klog#20155]] and in control room.
   * several code developments to understand glitch cause have been done. [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20026|klog#20026]] [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20027|klog#20027]]
   * code development to identify mirror center of ITMX have been done by using image analysis. [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=14003|slide(Japanese)]] [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20036|klog#20036]] [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20198|klog20198]] [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20203|klog#20203]]
  * DQR update
   * Joe updated Task Manager. Yuzurihara will install new version and test it.
  * Update of summary page
   * no update
  * 120Hz glitches investigation during O3GK
   * no update

-----
=== 20220307 (Mon.) ===
  * Agenda
    * announcement
     * LVK meeting March 2022 [[https://wiki.ligo.org/LSC/Meeting/LVKMeetingMarch2022|wiki]] [[https://cgca.uwm.edu/events/2021lvk|web]]
      * registration is available
    * 120Hz glitches investigation during O3GK
    * unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
    * DQ flags for O4
    * DQR update
    * glitch investigation related to IMMT1 oplev
 * Minutes
    * 120Hz glitches investigation during O3GK
     * no update
    * unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
     * YamaT is working on this project at test-server.
     * Test of new conda environment will start from next week (after JPS meeting)
    * DQ flags for O4
     * no update
    * DQR update
     * Joe is developing the code to connect between igwn-alert and TaskManager. It will be available soon.
     * Schedule for review
      * Review of Task Manager will be done before review of each task.
      * High priority task needs to complete before Aug. 2022
      * Low priority task needs to complete before Nov. 2022
    * glitch investigation related to IMMT1 oplev
     * From March 8, students from Aoyama Gakuin univ. stayed at Kamioka
     * They worked on the investigation of glitch. [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20026|klog#20026]][[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20027|klog#20027]]
     * They checked IMMT1 QPD signals and PRM suspension signals at the time of glitch.
    * NDS2 tool development (Darkhan)
     * no major update.
    * GPS accuracy monitor (Oshino)
     * is available on [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/summary/day/20220313/detchar/gps/|summary page]]
     * Current difference is acceptable and reasonable.
    * No meeting on March 21 due to Japanese holiday. Next meeting is planed on March 28.

-----
=== 20220307 (Mon.) ===
  * Agenda
    * announcement
     * RRT plan during O4 [[https://dcc.ligo.org/G2200220|slide]]
     * LVK meeting March 2022 [[https://wiki.ligo.org/LSC/Meeting/LVKMeetingMarch2022|wiki]] [[https://cgca.uwm.edu/events/2021lvk|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
Line 50: Line 284:
    * O3GK Glitch investigation (Kihyun)
     * Kihyun checked the omega-scan at the time of glitch. [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=13383|slide (see the last three slides)]]
     * There is no glitches in these channels at the same time of the glitch.
    * Segment information for open data (Uchikata)
     * They checked which data segments were used for GRB analysis. The correct DQ segment was used for GRB analysis.
     * For some reason, the wrong segment information was used for open data.
     * The reproduction of open data is on-going. The data set needs the review again.
    * Progress of DQR (Yuzurihara)
     * Recently the new feature to archive the parallel process was added in [[https://o4-dqr.docs.ligo.org/o4-dqr-configuration/#how-to-specify-directory-of-a-task|TaskManager]].
     * Yuzurihara is testing this feature to apply KAGRA data.

=== 20211101 (Mon.) ===
  * Agenda
    * O3GK noise budget paper [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=13405|JGW-P2113405-v1]]
    * hveto, O3GK glitches
    * Info. for open data
    * Progress of DQR		    * 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
    * In last PEM meeting, Yuzurihara presented the current status and received the helpful comments. [slide](https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=13970)
    * We will change our plan to construct the data quality flag and will compute the BLRMS of gwpy to set the threshold.
    * The review is necessary before O4. (probably very close to O4, because we need ER)
   * DQR update
    * no update
   * Commissioning of GreenX
    * In the last weekend, the commissioner tried continuous GreenX. During that trials, they found many short term lock loss (~10 ms). 10 ms is too short to follow the suspension motion, so it is likely that there are some causes of the lock loss except for the suspension motion.
    * The commissioner needs helps DetChar members to identify the cause or give a hint of the cause.
    * For details, 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]]
    * main channel K1:TMS-X_GR_PDA1_OUT_DQ
    * time : 2022 Mar 06 23:37:50 UTC = 2022 Mar 07 8:37:50 JST = GPS time 1330645088


-----
=== 20220228 (Mon.) ===
  * Agenda
    * 120Hz glitches
    * DQ flags for O4
    * progress of DQR
    * lock loss study of GreenX

  * Minutes (Yuzurihara)
    * 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
Line 68: Line 357:
    * Info. for open data
      * We should refer segments on [[https://segments-web.ligo.org|DQSEGDB]]
      * For GW searches: K1-SCIENCE_MODE, DET_FOR_GRB200415A
      * We need to check [1270965983, 1270976372) and [1270976435, 1270976783).


=== 20211025 (Mon.) ===
  * Agenda
    * Omicron glitches (40?, 120Hz)
    * DQR [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=13381|slide]]		     * 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
Line 79: Line 373:
    * Omicron glitches
      * ALS channels has some coincidence.
        * Cavity and suspensions are shared GR and IR lasers.
        * It's not identified the cause (GR laser or suspensions) yet from current results.
      * Chamber ACC at EXC has also same glitches.
        * hveto cannot detect coincidence on EYC and other ACC channels.
        * These channels also checked by Omega-scan once => Kihyun.


=== 20211011 (Mon.) ===
  * Agenda
    * site commissioning
    * omicron/hveto analysis
    * DQR		     * 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
Line 94: Line 401:
    * site commissioning
      * MC OpLev glitches ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=18518|klog#18518]])
      * PLL resonance ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=18466|klog#18466]])
      * IX MN glitches vanished(?) ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17876|klog#17876]])
    *

=== 20210927 (Mon.) ===
  * Agenda
    * hveto analysis
    * O4 commissioning
    * progress of DQR [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=13326|slide]]
  * Minutes
    * hveto
      * glitch rate was computed for O3GK paper [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=13311|JGW-D2113311]]
      * Clustering (with 0.1s window) was performed on gwpy function
    * O4 commissioning
      * Commissioning is now pending and suspension health check is ongoing.

=== 20210906 (Mon.) ===
  * Agenda
    * hveto analysis
    * O4 commissioning
    * JPS meeting
  * Minutes
    * O4 commissioning
     * Turn on the clustering option of Omicron ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=18070|k-log#18070]])
     * periodic glitches are happening in ITMX ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17876|klog#17876]])
      * These glitches seems to be correlated to IXV temperature ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17912|#17912]])
      * To find the source of ITMX glitches, there is a investigation ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17980|#17980]])
      * Update of summary page : Added ITMX signals for glitch pipeline ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=18112|k-log#18112]])
     * Implementation of GAS DC control for ITMX ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=18153|k-log#18153]])

=== 20210830 (Mon.) ===
  * Agenda
    * hveto analysis
    * O4 commissioning
    * O4 readiness
  * Minutes
    * hveto analysis
      * veto segment list will be shared. => Kihyun
    * O4 commissioning
      * PLL noise ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=18014|klog#18014]])
      * periodic glitches are happening in ITMX ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17876|klog#17876]])
       * These glitches seems to be correlated to IXV temperature ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17912|#17912]])
       * To find the source of ITMX glitches, there is a investigation ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17980|#17980]])
      * MCi and MCo pitch strange behavior ([[https://klog.icrr.u-tokyo.ac.jp/osl/index.php?r=18027|k-log#18027]])
      * Glitch investigation by Omicron
        * If there are many sources of glitches, information about small change in glitch rate is helpful to noise hunting.
        * ITMX PS should be added on SummaryPages => Oshino
        * And also we should set 0.1s clustering option as the first test for Omicron process.
        * In pyomicron, 0.1s clustering is default settings and pyomicron is available in igwn.
    * O4 readiness
      * #15 [Cont'd] State Vector Definition
        * Responsible: '''T. Yamamoto -> T. Yamamoto'''
      * #16 + #20 Segment production with short latency
        * Responsible: '''K. Kokeyama -> S. Oshino, T. Yamamoto'''
      * #17 [Cont'd ] Status web pages (summary pages, [[https://monitor.ligo.org/gwstatus|gw status]], [[https://ldas-jobs.ligo.caltech.edu/~gwistat/gwistat/gwistat_p.html|gw istat]])
        * Responsible: '''S. Oshino -> S. Oshino'''
      * #18 [Cont'd] DQ event validation
        * Responsible: '''C. Kozakai -> K. Ueno, T. Yamamoto'''
      * #19 [Cont'd] GraceDB
        * Responsible: '''H. Tagoshi -> H. Tegoshi(?)'''
      * #21 [New] Data Category (at least CAT1) production
        * Responsible: '''N. Uchikata(?)'''
      * #22 [New] RRT contribution
        * Responsible: '''H. Yuzurihara'''
    * Taks list of DetChar
      * We need to set concrete task list for authorship issue. (within 1 month?) => Yamamoto
      * Time line of each tasks also should be decided => Yamamoto & each responsible person
      * After creating the draft version of task list and time line, they will be shared on DET telecon.


=== 20210823 (Mon.) ===
  * Agenda
    * hveto analysis
    * O4 commissioning & preparation
    * f2f meeting
  * Minutes
    * hveto analysis
      * O3GK 2 weeks data was analyzed with new configuration.
      * Blip, LF burst were found in many times.
      * All vetoed segments will be shared soon.
    * O4 commissioning
      * IMC commissioning is on-going
       * beam shape of transmitted beam at MCE is not clear circle. It looks like ellipse.
       * Now Kenta Tanaka and I are investigating the cause. If the cause is happening outside of mode cleaner, we can do something to remove the cause.
       * From the last week investigate, we are doubting it is ghost beam. [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17930|k-log]] [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17903|k-log]] [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17883|k-log]]
      * VIS commissioning
       * VIS team is working the implementation of dumping filter, which is called local dumpling. Now they are discussing about the evaluation of the requirement value for dumpling.
       * Many glitches in the feedback signal were observed. [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17974|k-log]]
    * f2f meeting
      * Status talk of DAC/DET (28th Sat. 9:00~?)
        * => Yamamoto
      * Contribution talks
        * Pastavi development (poster) => Yuzurihara
        * Gaussianity search (poster) => Morisue

=== 20210816 (Mon.) ===
  * Agenda
    * hveto analysis
    * O4 commissioning
    * KAGRA readiness
    * f2f meeting
  * Minutes
    * hveto analysis
      * various clustering
        * ([[https://gwdet.icrr.u-tokyo.ac.jp/~controls/hveto/manual/2020-04-15cl0.1/|0.1]], [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/hveto/manual/2020-04-15cl0.2/|0.2]], [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/hveto/manual/2020-04-15cl0.3/|0.3]], [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/hveto/manual/2020-04-15cl0.4/|0.4]], [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/hveto/manual/2020-04-15cl0.5/|0.5]], [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/hveto/manual/2020-04-15cl0.6/|0.6]], [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/hveto/manual/2020-04-15cl0.7/|0.7]], [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/hveto/manual/2020-04-15cl0.8/|0.8]], [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/hveto/manual/2020-04-15cl0.9/|0.9]], [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/hveto/manual/2020-04-15cl1.0/|1.0]])
      * old results
        * ([[https://gwdet.icrr.u-tokyo.ac.jp/~controls/hveto/manual/2020-04-15_cl0_1v2/|0.1]], [[https://gwdet.icrr.u-tokyo.ac.jp/~controls/hveto/manual/2020-04-15_cl0_2/|0.2]])
    * O4 commissioning
      * FNC instability ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17748|klog#17748]], [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17865|klog#17865]])
        * We are not investigating the cause of instability of Michelson fringes of FNC (green laser)
        * Fiber coupling at PSL room is the most reasonable candidate.
        * We need to investigate temperature environment around green laser more detailed.
      * MN Photo sensor noise ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17876|klog#17876]])
        * It doesn't seem to be not a real ground motion because upper stage isn't shaked.
        * We doubt the electrical noise now.
        * O4 readiness
    * O4 readiness
      * #15 [Cont'd] State Vector Definition
        * Responsible: '''T. Yamamoto -> T. Yamamoto'''
      * #16 + #20 Segment production with short latency
        * Responsible: '''K. Kokeyama -> S. Oshino, T. Yamamoto'''
      * #17 [Cont'd ] Status web pages (summary pages, [[https://monitor.ligo.org/gwstatus|gw status]], [[https://ldas-jobs.ligo.caltech.edu/~gwistat/gwistat/gwistat_p.html|gw istat]])
        * Responsible: '''S. Oshino -> S. Oshino'''
      * #18 [Cont'd] DQ event validation
        * Responsible: '''C. Kozakai -> K. Ueno, T. Yamamoto'''
      * #19 [Cont'd] GraceDB
        * Responsible: '''H. Tagoshi -> H. Tegoshi(?)'''
      * #21 [New] Data Category (at least CAT1) production
        * Responsible: '''!!!!!'''
      * #22 [New] RRT contribution
        * Responsible: '''H. Yuzurihara'''

=== 20210802 (Mon.) ===
  * Agenda:
    * hveto analysis
    * O4 commissioning and preparation
    * Hardware injection plan during O4
    * KAGRA O4 readiness
    * Proposal of O3GK DetChar paper [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=13149|slide]]
  * Minutes:
    * hveto analysis
      * clustering test
        * Round winer doesn't change by clustering option.
        * Some kind of clustering is necessary but best parameter is not clear yet.
        * Kihyun will share the event time of clustered events.
        * We should check each event by spectrogram, Omega-scan, etc.
        * hveto with clustering will be also performed for 2 weeks day.
    * O4 commissioning
      * Omega-scan on Kashiwa has some error now. And
    * Hardware injection plan during O4
      * KAGRA CAL group is now gathering the plan of HWI during observations.
      * In LIGO case, in order to do HWI during obs., they need special and reasonable reasons.
      * KAGRA CAL also plan to adopt same procedures of the HWI management as LIGO.
      * If you have any HWI plan related to DET activities pls. share in DET telecons once.
      * We would like to discuss that the requested plans should be conducted during ER or obs.
    * O4 readiness
      * #15 [Cont'd] State Vector Definition
        * Responsible: '''T. Yamamoto -> T. Yamamoto'''
      * #16 + #20 Segment production with short latency
        * Responsible: '''K. Kokeyama -> S. Oshino, T. Yamamoto'''
      * #17 [Cont'd ] Status web pages (summary pages, [[https://monitor.ligo.org/gwstatus|gw status]], [[https://ldas-jobs.ligo.caltech.edu/~gwistat/gwistat/gwistat_p.html|gw istat]])
        * Responsible: '''S. Oshino -> S. Oshino'''
      * #18 [Cont'd] DQ event validation
        * Responsible: '''C. Kozakai -> T. Yamamoto'''
      * #19 [Cont'd] GraceDB
        * Responsible: '''H. Tagoshi -> H. Tegoshi(?)'''
      * #21 [New] Data Category (at least CAT1) production
        * Responsible: '''!!!!!'''
      * #22 [New] RRT contribution
        * Responsible: '''H. Yuzurihara'''

=== 20210726 (Mon.) ===
  * Agenda:
    * hveto analysis
    * O4 commissioning
    * O4 readiness
  * Minutes:
    * hveto analysis
      * Analyses with various clustering parameter are in progress. Kihyun will report in next telecon.
    * O4 commissioning
      * no updates
        * SummaryPages
        * lvalert
        * DET cluster
    * O4 readiness
      * It is preferable that the same person does not become multiple responsible person
      * As WP2021, DET tasks which is taken into account an effort follows readiness issues.

      * #15 [Cont'd] State Vector Definition
        * Responsible: '''T. Yamamoto -> T. Yamamoto'''
      * #16 + #20 Segment production with short latency
        * Responsible: '''K. Kokeyama -> S. Oshino, T. Yamamoto'''
      * #17 [Cont'd ] Status web pages (summary pages, [[https://monitor.ligo.org/gwstatus|gw status]], [[https://ldas-jobs.ligo.caltech.edu/~gwistat/gwistat/gwistat_p.html|gw istat]])
        * Responsible: '''S. Oshino -> S. Oshino'''
      * #18 [Cont'd] DQ event validation
        * Responsible: '''C. Kozakai -> !!!!!'''
      * #19 [Cont'd] GraceDB
        * Responsible: '''H. Tagoshi -> H. Tegoshi(?)'''
      * #21 [New] Data Category (at least CAT1) production
        * Responsible: '''!!!!!'''
      * #22 [New] RRT contribution
        * Responsible: '''H. Yuzurihara'''

=== 20210719 (Mon.) ===
  * Agenda:
    * hveto analysis
    * O4 commissioning
    * O4 readiness
  * Minutes
    * O4 commissioning
      * IMC-XARM commissioning
        * FNC control saturation [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17464|klog17464]]
        * MC Oplev glitches and 120Hz line still exist (K1:VIS-MC{I,E,O}_TM_WIT_{P,Y})
        * Unstational noise excess on Green laser above 100Hz still exists (K1:ALS-
    * O4 readiness
      * #15 [Cont'd] State Vector Definition
        * Responsible: '''T. Yamamoto -> T. Yamamoto(?)'''
      * #16 + #20 Segment production with short latency
        * Responsible: '''K. Kokeyama -> S. Oshino, T. Yamamoto'''
      * #17 [Cont'd ] Status web pages (summary pages, [[https://monitor.ligo.org/gwstatus|gw status]], [[https://ldas-jobs.ligo.caltech.edu/~gwistat/gwistat/gwistat_p.html|gw istat]])
        * Responsible: '''S. Oshino -> S. Oshino(?)'''
      * #18 [Cont'd] DQ event validation
        * Responsible: '''C. Kozakai -> '''
      * #19 [Cont'd] GraceDB
        * Responsible: '''H. Tagoshi -> H. Tegoshi(?)'''
      * #21 [New] Data Category (at least CAT1) production
        * Responsible:
      * #22 [New] RRT contribution
        * Responsible: '''H. Yuzurihara(?)'''

=== 20210705 (Mon.) ===
  * Agenda: 		    * 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
Line 329: Line 415:
    * white paper
    * O4 commissioning
  * Minutes:
    * O3GK paper
      * Hveto was rerun with various parameters.
      * But there is no improvement in the veto efficiency.
    * white paper
      * Final version was released.
      * There was no additional comments from LV
      * [[https://git.ligo.org/operations/operations-white-paper-2021|LIGO Git]]
    * O4 commissioning
      * no report

-----
=== 20210628 (Mon.) ===
  * Agenda
    * O3GK paper
    * white paper
    * O4 commissioning & preparation
  * Minutes
    * O3GK paper
      * Uchikata-san and Narikawa-san got a consistent results with Kozakai-san's one.
      * hveto was performed with 0.1 duration.
      * There is no efficient channel/sensor for glitch veto.
        * Some parameters comes from LIGO's one.
        * So we need to find better parameters for KAGRA's data.
        * We also need prepare the more efficient sensors for O4 observing run
      * Kihyun is also performing the crosscheck. (1 or 2 weeks later he can report.)
    * white paper
      * [[https://git.ligo.org/operations/operations-white-paper-2021|Draft on LIGO Git]]
      * TY will be added a description about CAGMon until LVK DET call.
      * WP will be fixed at Ops call on 6/30 (?)
    * O4 commissioning & preparation
      * IMC commissioning
        * [Ongoing] Glitches on OpLev
          * Because of too many glitches, it's difficult to investigate one by one.
          * K1:VIS-MC{I,E,O}_TM_WIT_{P,Y} (MC Oplevs)
        * [Fixed] PLL noise coming from broken circuit [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17188|klog17188]]
        * [Ongoing] PLL also has glitches (maybe) due to electrostatic discharge. [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17239|klog17239]]
          * K1:ALS-{X,Y}_BEAT_ERR_OUT_DQ (error signal)
          * K1:ALS-{X,Y}_PLL_SLOW_DAQ_OUT_DQ (feedback signal)
        * [Ongoing] non-stational correlation between IMC/PLL and Microphone
          * K1:CAL-CS_PROC_IMC_FREQUENCY_DQ (calibrated frequency noise)
          * K1:IMC-SERVO_SLOW_DAQ_OUT_DQ (feedback signal of IMC)
          * K1:ALS-{X,Y}_PLL_SLOW_DAQ_OUT_DQ (feedback signal of PLL)
        * [Ongoing] station correlation between PMC and Microphone
          * Investigation about significance of coherence is ongoing.
-----
=== 20210621 (Mon.) ===
  * Agenda
    * O3GK paper
    * O4 whitepaper
    * O4 commissioning & preparation
  * Minutes
    * O4 white paper
      * The 1st version of the draft was submitted on June 17th.
        * [[https://git.ligo.org/operations/operations-white-paper-2021|LIGO Git]]
        * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=12985|JGW-T-2112985]]
      * Final deadline is June 30th.
        * We can still do the miner fix.
    * O4 commissioning & preparation
      * IMC Commissioning
        * Omicron trigger searches for MC Oplevs were resumed ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=17150|klog#17150]]).
          * K1:VIS-MC{I,E,O}_TM_WIT_{P,Y} (oplev signals)
          * K1:VIS-IMMT{1,2}_TM_WIT_{P,Y} (as a reference of circuit noise)
        * SummaryPages
          * Glitch trigger tabs are added.
          * Loudest glitches can be seen on Pastavi (only internal ICRR network)
=== 20210614 (Mon.) ===
  * Agenda
    * O3GK paper
    * O4 whitepaper
    * O4 commissioning & preparation
  * Minutes
    * O3GK paper
      * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=13009|plot]]
    * O4 white paper
      * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=12985|draft]]
      * It's better to include PEM plans in commissions support section if exits.
    * O4 commissioning & preparation
      * IMC Commissioning
        * We have now four frequency noise signal (IMC, PMC, PLL-X, PLL-Y)
          * K1:CAL-CS_PROC_IMC_FREQUENCY_DQ (calibrated IMC as MHz)
          * K1:PSL-PMC_PZT_HV_MON_OUT_DQ (calibrated PMC as Volt at PZT amp.)
          * K1:ALS-X_PLL_SLOW_DAQ_OUT_DQ (calibrated Green-X as Volt at PZT)
          * K1:ALS-X_PLL_SLOW_DAQ_OUT_DQ (calibrated Green-Y as Volt at PZT)
        * PMC (always) and others (sometimes) have correlation with microphone signal
          * K1:PEM-MIC_PSL_TABLE_PSL1_Z_OUT_DQ (calibrated as Pascal)
        * OpLev signals have some glitches and are investigated now.
          * K1:VIS-MC{I,E,O}_TM_WIT_{P,Y}
          * Real SUS motion?, electrical glitches?, scattered light? etc.
      * SummaryPages
        * Updated PSL, PEM tabs.
          * PLL signals are available.

-----

=== 20210607 (Mon.) ===
  * Agenda
    * O3GK paper
    * O4 whitepaper
    * O4 commissioning & preparation
  * Minutes
    * O3GK paper
      * Preparing some plots about histgram and glitch rate of both KAGRA and GEO
    * O4 whitepaper
      * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=12985|draft]]
    * O4 commissioning & preparation
      * CAGMon development
        * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=12986|slide]]
          * Found correlation between wind power and BNS ranges
          * OMMT1 doesn't (maybe) have Oplev. It's better to confirm what kind of sensors were coneected.
          * BNS range channel has ~2min latency. It may become better results by considering the latency in BNS range calculation.
      * IMC commissioning
        * Noise investigation ([[https://klog.icrr.u-tokyo.ac.jp/osl/?r=16928|klog]])
        * Correlation between IMC and MIC sometimes increase in spite of no change in microphone spectra.
        * Coupling coefficients may be changed in time.
      * Cross check of hveto results.
        * Kihyun's (KISTI) and Chihiro's (Kamioka) results were confirmed as consistent each other.
        * For O4 observing run, Kashiwa environment is also important for increasing machine power.
        * Requirement of machine power should be estimated soon (but it's strongly depends on the situation of O4 joining)
        * We plan to use 100-200 aux. channels and it's very helpful to analyze them at the same time for each pipeline.
      * lvalert
        * no report
      * SummaryPage
        * no report
      * DetChar cluster
        * no report


-----
=== 20210531 (Mon.) ===
  * Agenda
    * O3GK paper
    * O4 readiness
    * O4 commissioning & preparation
  * Minutes
    * O3GK paper
      * Comparison with Uchikata-san's and GEO people's results is ongoing.
      * Kihyun is performing validation check of his results => He will report in next or 2 weeks later telecon.
    * O4 readiness
      * #15 [Cont'd] State Vector Definition
        * Responsible: '''T. Yamamoto -> T. Yamamoto(?)'''
      * #16 + #20 Segment production with short latency
        * Responsible: '''K. Kokeyama -> '''
      * #17 [Cont'd ] Status web pages (summary pages, [[https://monitor.ligo.org/gwstatus|gw status]], [[https://ldas-jobs.ligo.caltech.edu/~gwistat/gwistat/gwistat_p.html|gw istat]])
        * Responsible: '''S. Oshino -> S. Oshino(?)'''
      * #18 [Cont'd] DQ event validation
        * Responsible: '''C. Kozakai -> '''
      * #19 [Cont'd] GraceDB
        * Responsible: '''H. Tagoshi -> H. Tegoshi(?)'''
      * #21 [New] Data Category (at least CAT1) production
        * Responsible:
      * #22 [New] RRT contribution
        * Responsible: '''H. Yuzurihara(?)'''
    * white paper 2021
      * No progress in draft.
      * Task list will be based on O4 readiness.
        * If there is another task plan, please let TY know (maybe CAGMon, ICA, pastavi development etc.).
    * O4 commissioning & preparation
      * LVAlert
        * no report
      * SummaryPages update
        * no report
      * DET cluster
        * no report
      * CAGMon development
        * no report

-----
=== 20210524 (Mon.) ===
  * Agenda
    * O3GK paper
    * O4 commissioning & preparation
    * O4 readiness
  * Minutes
    * O3GK paper
      * Discussion with GEO people is ongoing
    * O4 commissioning & preparation
      * MC circuit noise hunting
        * Current spectrum is too clean 1/f noise.
          * Frequency noise should shows 1/f spectrum.
          * But we haven't checked it's a real frequency noise (circuit noise etc.).
          * Nakano-kun said current spectrum is consistent with past measurements.
      * sound correlation
        * Investigating sound correlation with three microphones. [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=12937|slide]]
      * lvalert test
        * no report
      * DET cluster
        * no report
      * SummaryPages
        * added for some IMC signals and it work well.
    * White paper 2021
      * [[https://git.ligo.org/operations/operations-white-paper-2021|2021]]
      * [[https://git.ligo.org/operations/operations-white-paper-2020|2020]]

=== 20210517 (Mon.) ===
  * Agenda
    * KAGRA O4 readiness
    * LVK white paper 2021
    * O3GK paper
    * IMC commissioning
  * Minutes
    * KAGRA O4 readiness
      * #15 [Cont'd] State Vector Definition
        * Responsible: '''T. Yamamoto -> '''
      * #16 [Cont'd] DQSEGDB capability
        * Responsible: '''K. Kokeyama -> '''
      * #17 [Cont'd ] Status web pages (summary pages, [[https://monitor.ligo.org/gwstatus|gw status]], [[https://ldas-jobs.ligo.caltech.edu/~gwistat/gwistat/gwistat_p.html|gw istat]])
        * Responsible: '''S. Oshino -> '''
      * #18 [Cont'd] DQ event validation
        * Responsible: '''C. Kozakai -> '''
      * #19 [Cont'd] GraceDB
        * Responsible: '''H. Tagoshi -> '''
      * #20 [New] Segment production (merged with #16?)
        * Responsible:
      * #21 [New] Data Category (at least CAT1) production
        * Responsible:
      * #22 [New] RRT contribution
    * LVK white paper
      * Responsible:
      * What TY thought
        * All activities which are submitted as 2021 DET effort should be described on this documents.
        * It will be based on white paper 2020 and KAGRA O4 readiness.
        * Should clarify who will do each item (though personal name itself is not described on this documents).
        * Should show the rough timeline for R&D tasks.
    * O3GK paper
      * We need to continue to discuss with GEO people about GEO data analysis.
    * IMC Commissioning
      * Current IMC control signals on DGS are contaminated by circuit noise.
      * Important thing is that contamination is occurred only on DGS signals or also on real analog signals
      * Important channels
        * K1:IMC-SERVO_{MIXER,FAST,SLOW}_DAQ_OUT_DQ
        * K1:IMC-SERVO_NPRO_TEMP_BIAS_OUT_DQ
        * => These channels will be added to SummaryPages
    * O4 preparation
      * CAGMon development
        * no report
      * lvalert test
        * no report
      * DET cluster
        * no report

=== 20210510 (Mon.) ===
  * Agenda
    * KIW
    * O3GK paper
    * IMC Commissioning
    * O4 preparation
  * Minutes
    * KIW
    {{{
- Status of KAGRA DET (20 min) => T. Yamamoto
- Status of LIGO Detchar (20 min)
- Status of Virgo Detchar (20 min)
- Contributed Talk 1 - one slot from KAGRA (15 min) => H. Yuzurihara
- Contributed Talk 2 - CAGMon tools (15 min)
- Contributed Talk 3 - KISTI's data transfer and computing (15 min)
    }}}
    * O3GK paper
      * hveto process for GEO600 was done.
    * IMC Commissioning
      * [PMC] Acoustic coherence (20-200Hz)
      * [IMC] Oscillation? (13-15MHz)
    * O4 preparation
      * SummaryPages
        * no report
      * lvalert
        * no report
      * DET cluster
        * no report

=== 20210426 (Mon.) ===
  * Agenda
    * O3GK analysis
    * O4 preparation
    * IMC Commissioning
  * Minutes
    * O3GK analysis
      * Omicron analysis of GEO was finished.
      * Checking results is ongoing.
      * We need to convert segment information on DQSEGDB to xml format.
      * After checking omicron results, hveto analysis can be started.
    * CAG Mon development
      * CAG Mon was able to detect some correlation in O3GK data
      * Prioritize is not done yet.
        * prioritize can be decided by correlation coefficient value or total duration of correlation appearing
      * We need more time to develop CAGMon (before we move to review process.).
    * IMC Commissioning
      * Microphone self noise is evaluating now.
      * They will be installed in PSL room
    * Paper writing person(s) from DET
      * TY takes over from Kozakai-san.
    * summary of lvalert test for LVK DET telecon

-----
=== 20210419 (Mon.) ===
  * Agenda
    * O3GK analysis
    * O4 preparation (LV alert, SummaryPages, CAGMon)
    * PMC/IMC noise hunting
  * Minutes
    * O3GK analysis
      * GEO data analysis is started.
      * Channel list is prepared by GEO people.
    * PMC/IMC noise hunting
      * Sound noise
        * Frequency noise has coherence with microphone signal.
        * Sound noise affected to DARM sensitivity during O3GK.
        * Noise source and injection injection route should be investigated.
      * Electrical noise(?)
        * Accelerometer channel has coherence with frequency noise when PEM sensor turned OFF.
        * Circuit noise level is small, but some electrical coherence may exist.

=== 20210408 (Thu.) ===
  * Agenda
    * O3GK analysis
    * SummaryPage
    * LV alert [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=12760|slide]]
    * NDS2
    * IMC Commissioning
  * Minutes
    * O3GK analysis
      * hveto re-analysis for a part of data was done.
        * round winner is same
        * significant is slightly difference, (using same conf. triggers, version, etc)
        * Next step is to check consistency of veto segment
      * GEO data
        * Analysis itself will be performed by KAGRA people
        * Understanding results will be performed by GEO (+KAGRA) people
        
-----
=== 20210401 (Thu.) ===
  * Agenda
    * Progress of hveto analysis
    * DetChar cluster
    * lvalert
    * SummaryPages
    * RRT for O4
  * Minutes
    * Announcement
      * New slot of DET meeting.
        * => Pending because TY cannot know free time slot yet. (7 doodle poll is running...).
      * hveto
        * Omicron test analysis is successful.
        * hveto doesn't run on m31 yet.
        * We need to KISTI environment.
      * lvalert
        * Waiting response from LV people.
        * We need realistic json format of GW alert.
        * Only for the purpose of launching pipelines, dummy format is also used.
      * SummaryPages
        * The 1st version of VIS tab is already available (Only Type-A and guardians).
        * Importing PSL tab from LIGO is already done.
        * But there is many difference of channel name convention.
        

-----
=== 20210325 (Thu.) ===
  * Agenda
    * Progress of hveto analysis
    * GEO data analysis
    * SummaryPage construction
    * lvalert test
    * PMC/IMC commissioning
    * Meeting time in the next FY
  * Minutes
    * Progress of hveto analysis
      * Consistency check still remains and it is solved yet.
    * GEO data analysis
      * Basic takeover is finished.
      * Uchikata-san and Narikawa-san can start to use Omicron and hveto.
      * But some error occurs on hveto@m31.
      * We should fixed environmental problem.
    * SummaryPage construction
      * The 1st version is already constructed on test directory.
      * We can apply it for product environment because current SummaryPage is not valid.
    * lvalert test
      * lvalert itself works well.
      * Next step is receiving alert.
      * We need to ask LIGO people about alert format etc.
    * PMC/IMC commissioning
      * Due to a lot of troubles, we haven't achieved IMC locked yet.
      * We may start some kind of commissioning from Mid or Late of April.
    * Meeting time in the next FY
      * TY will circulate doodle poll.

=== 20210317 (Thu.) ===
  * O3GK paper
    * hveto cross-check
      * Checking Omicron parameter remains.
      * Required re-run for whole two weeks.
    * veto segment production
      * Merging short segments is not required.
    * GEO data analysis
      * It can be done by someone form Tagoshi-san's group.
  * O4 preparation
    * Kamioka cluster
      * It's pending due to the recovery work of power outage.
    * Takeover about Omicron, hveto, GlitchPlot
      * Takeover itself is done.
      * TY is finding candidate person of each pipelines toward O4.
    * Omega-scan test
      * Installing on Kashiwa
    * lvalert test
      * It's works well on k1det1
    * SummaryPage update
      * The 1st version of VIS page is constructed.
      * It's being checked by Miyo-kun.
    * IMC commissioning
      * It is not locked yet because of some troubles.

=== 20210225 (Thu.) ===
  * Agenda
    * Progress of O3GK paper
    * O4 preparation
  * Minutes
    * Progress of O3GK paper
      * Chihiro re-analysis with proper science segment for omicron triggers.
      * A part of Kihyun's analysis is done.
      * Cross-check can be done. But not start yet.
    * DetChar cluster in Kamioka
      * http://klog.icrr.u-tokyo.ac.jp/osl/?r=16082
      * OS installation for master node was done.
    * Omega-scan test
      * Installation for Kashiwa cluster was done.
      * Error is occurred on gwdatafind.
    * SummaryPages
    * LVAlert

-----
=== 20210218 (Thu.) ===
  * Agenda
    * Progress of O3GK paper
    * O3 data replay
    * O4 preparation
  * Minutes
    * Progress of O3GK paper
      * hveto conf is same
      * segment is used as latest same science segments
      * definition of cutting end of segments is difference.
      * Channel list is used as on github's one.
      * Next step -> unifying cutting definition.
        * Kihyun will re-run omicron with new segment cutting definition
      * We need to merge veto segment from a lot of short ones to continuous one.
    * O3 data replay
      * Main purpose of O3 data replay is performing end-2-end test of low-latency pipelines (CAL, DET, DAS, etc).
      * LV will use real O3 data.
      * KAGRA provides simulated data (~80Mpc for BNS) because of too poor sensitivity of O3GK data.
      * We may need to inject GWs on software with consistency with LV's real events.
      * Frame work of software injection is already available.
    * SummaryPage
      * Updating VIS page.
      * It will be closed to LIGO's one.
    * LVAlert
      * k1det1 can be used for test.
      * Need personal account because we use personal DCC account for accessing GraceDB.
        * Ask LV people how to get common account on next LVK DET meeting.
    

-----

=== 20210204 (Thu.) ===
  * Agenda
    * Progress of O3GK paper
    * O3 data replay
    * O4 requirement
  * Minutes
    * Progress of O3GK paper
      * Omicron trigger transfer: Kamioka -> KISTI, it is postponed.
        * Young-Min asked KISTI administrator.
      * GW-search triggers have not been served yet.
    * O3 data replay
      * K1:OPS-SIM_GAUSS1_IN1 (simulated error signal)
      * K1:OPS-SIM_GAUSS1_OUT (simulated h(t) )
        * gaussian noise as floor level
        * Some spectral lines (cal lines, violin mode, power lines)
        * Simulated glitches.
      * K1:OPS-SIM_GAUSS3_OUT (simulated auxiliary channel)
    * O4 requirement
      * DQ state vector (Yamamoto)
        * Providing on real-time model.
      * Data Quality Report (Yuzurihara)
        * First step is to use lvalert in order to receive GW alert from GraceDB.
      * Transient Event validation (Kozakai)
        * Basic idea is omicron+hveto (same as O3GK)
        * Takeover should be done from Kozakai-san.
      * Category veto (Yamamoto)
        * At least CAT1 should be provided.
        * We need to convert to veto-definer file format.
      * Spectral lines investigation (Yokozawa)
        * Listing of VIS-derived peak frequencies.
-----
=== 20210128 (Thu.) ===
  * Agenda
    * Report from Burst search
    * Binary range evaluation with C20 offline h(t)
    * Progress of O3GK paper
  * Minutes
    * Report from Burst search
      *
    * Binary range evaluation with C20 offline h(t)
      * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=12499|slide]]
      * Multi-taper and Welch show similar results
      * Bayesline result is slightly different from results by other two methods.
      * Estimated values are enough for O3GK (search) paper.
      * LVK review of this work is necessary for publishing results.
    * Progress of O3GK paper
      *


=== 20210121 (Thu.) ===
  * Agenda
    * Announcement
      * LVK DetChar call will be held (Jan. 25 19:00 JST, KST)
    * Progress of O3GK paper
    * CAGMon results
    * O3 Data replay
  * Minutes
    * Progress of O3GK paper
      * Some difference between Kihyun's and Chihiro's results.
      * hveto setting should be tuned on conf file and re-run again.
      * GW search results will be provided 1-2 months later (?).
    * CAGMon results
      * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=12481|slide]]
    * O3 data replay
      * LV requested the simulated data instead of O3GK data as KAGRA's data.
      * Auxiliary channels which has realistic coherence, coincidence etc are not available.
      * All multi-channel analyses cannot work well in such situation.
      * We need more discussion how do we join O3 data replay.


=== 20210107 (Thu.) ===
  * Agenda
    * Progress of O3GK analysis
    * O4 preparation
  * Minutes
    * Progress of O3GK analysis
      * Analysis itself was finished.
      * Results by Chihiro and Kihyun are now comparing.
        * => Some conf. is still difference.
      * At least after finishing paper work, omicron triggers should be shared on Kashiwa cluster for remote site people.
    * O4 preparation
      * Model update will be finished soon.
        * => After model update, suspension commissioning will be started.
      * SummaryPages seems to be stopped.
        * => Because of the channel name update by VIS model changes.
        * => Current situation of real-time model is slightly complicated. ITMY: Old model, others: new model etc.
        * => After finishing CRY measurements, all suspension models are unified.
       * 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.

-----
Line 880: Line 421:
  * [[KAGRA/Subgroups/DET/Meeting/2021|2021]]

Meetings

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

Contents

  1. Meetings
    1. Agenda & Minutes
      1. 20220509 (Mon.)
      2. 20220502 (Mon.)
      3. 20220425 (Mon.)
      4. 20220418 (Mon.)
      5. 20220411 (Mon.)
      6. 20220404 (Mon.)
      7. 20220328 (Mon.)
      8. 20220307 (Mon.)
      9. 20220307 (Mon.)
      10. 20220228 (Mon.)
      11. 20220221 (Mon.)
      12. 20220207 (Mon.)
      13. 20220131 (Mon.)
      14. 20220117 (Mon.)
      15. Past meeting

Agenda & Minutes

20220509 (Mon.)

  • Agenda
    • Announcement

      • Vigo DetChar paper arXiv

      • GWADW2022 web

      • The 9th KAGRA International Workshop (KIW) web

      • The GRAvitational - wave Science&technology Symposia (GRASS 2022) web

    • KAGRA commissioning reports
    • Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
      • call for volunteers from remote site, to test hveto and FScan. Please let us (Yuzuriahra or YamaT) know.
    • DQR update (Yuzurihara)
    • Update contents of summary page? (Oshino)
    • Combine DET computer resources into one DET cluster at Kamioka site
    • Report of new tool development? (Darkhan)
    • Glitch subtraction survey for O4
      • see mail from Davis Derek (2022 May 3)
      • deadline : May 16
      • The glitch subtraction activities are managed under DET. I would like to ask regular report in DET meeting.
  • Minuts
    • Announcement
    • KAGRA commissioning reports

      • ADC noise measurement klog#20658

      • In-air health check for Yarm suspensions (ITMY and ETMY) is on-going.
        • If no problem, review will be done next week and pumping down will start on week of May 23
    • DQR update (Yuzurihara)
      • no update
    • Report of new tool development? (Darkhan)
      • add channel list?

20220502 (Mon.)

  • Agenda
    • Announcement
    • KAGRA commissioning reports

      • PRM cause the glitch in IMMT1 OPLEV signal and POP forword QPD signal klog#20539

      • In-air health check for suspensions (ITMY, ETMY) is on-going by Ushiba klog#20631 klog#20632

    • Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
      • call for volunteers from remote site, to test hveto and FScan. Please let us (Yuzuriahra or YamaT) know.
    • DQR update (Yuzurihara)
    • Update contents of summary page? (Oshino)
    • Combine DET computer resources into one DET cluster at Kamioka site
    • Report of new tool development? (Darkhan)
    • Data Quality flag for O4a
      • We are asking the concrete requirement for DAC members (CBC, burst, Stochastic)
      • This is related to discuss the ER period and time
    • Analysis of TCam photos of ITMY and ETMY with the metal scale by Tcam
  • Minutes
    • Announcement

      • GWADW2022 web

      • The 9th KAGRA International Workshop (KIW) web

      • The GRAvitational - wave Science&technology Symposia (GRASS 2022) web

    • DQR update (Yuzurihara)
      • no update.
    • Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
      • no update
    • Update contents of summary page? (Oshino)

    • Analysis of TCam photos of ITMY and ETMY with the metal scale by Tcam klog#20574

      • analysis is on-going by Aogaku students. Report will appear soon.

20220425 (Mon.)

  • canceld

20220418 (Mon.)

  • Agenda
    • Announcement
      • monthly maintenance for JGWDoc + JGW wiki + klog on April 18 13:00-16:00 JST.
    • Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
      • call for volunteers from remote site, to test hveto and FScan. Please let us (Yuzuriahra or YamaT) know.
    • DQR update (Yuzurihara)
    • Update contents of summary page? (Oshino)
    • Combine DET computer resources into one DET cluster at Kamioka site
    • Report of new tool development? (Darkhan)
  • Minutes
    • Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
      • No updates in last week.
      • Some volunteers for testing of hveto, fscan are sitll wanted.
      • We should start to test also iDQ from now on for future observing runs (O5, O6...)
    • DQR update (Yuzurihara)
      • operation test for tools is on-going without error and trouble
    • Update contents of summary page? (Oshino)
      • no update
    • Combine DET computer resources into one DET cluster at Kamioka site
      • no update
    • Report of new tool development? (Darkhan)
    • 120Hz glitches investigation during O3GK

20220411 (Mon.)

  • Agenda
    • Announcement

      • Workshop 2022/04/15 web page

        • DetChar talk is planed by Yokozawa. When he circulates slide, put comments on slide.

    • Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
      • call for volunteers from remote site, to test hveto and FScan. Please let us (Yuzuriahra or YamaT) know.
    • Exchange of opinions between DET members(YamaT, Sawada(OPS), Yuzurihara) and DMG members(Kanda, Oohara)
    • DQR update (Yuzurihara)
    • Update contents of summary page? (Oshino)
    • Combine DET computer resources into one DET cluster at Kamioka site
      • (Oshino) explain idea, goal, and timeline
    • Report of new tool development? (Darkhan)
    • Follow-up report of remote contribution from Aoyama Gakuin univ.
  • Minutes
    • Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
      • no volunteer yet (Test of hveto and FScan).
        • Coding kagradata.py for the new version of Bruco is ongoing.
        • We need to decide KAGRA common rule about NDS2 and DATAFIND for fixing codes.
      • NAPT test was started for the purpose of saving number of IP address in DGS network.
        • DET gateway (copy of k1gate is enough for the test) will be connected to DGS network.
          • Other nodes will be under DET gateway.
        • It may be better to construct the gateway as Deb10. (Copy of k1gate is Rocky8)
          • TY have no experience of constructing NAPT on Debian.
        • NDS(k1nds[012]), NFS(k1nfs0) services must be available from under DET gateway.
        • How should we do k1det2 which is used for Bruco running from CDS workstation.
    • Exchange of opinions between DET members(YamaT, Sawada(OPS), Yuzurihara) and DMG members(Kanda, Oohara)
      • related to conda environment and DQR tasks
      • in Kashiwa server and Kamioka computers, we should have common rule fo NDS2 and DATAFIND, which YamaT already mentioned.
    • DQR update (Yuzurihara)
      • the application to connect between igwn-alert and Task Manager was developped by Joe

      • DQRAlert git repo

      • I tried to run this tool in Kamioka computer and it is working well.
      • need to prepare the document of how to use this tool on wiki page.

      • DQR workflow

    • Update contents of summary page?
      • no update
    • Combine DET computer resources into one DET cluster at Kamioka site
      • goal : prepare job management server and can submit job to k1det[012]
      • timeline : before O4
      • there might be conflict between this cluster and NAPT test. Oshino and YamaT will discuss.
    • Follow-up report of remote contribution from Aoyama Gakuin univ.
      • (Yokozawa, Oshino, Yuzurihara) we started the discussion of task list and how to contribute from remote site.

20220404 (Mon.)

  • Agenda
  • Minutes
    • Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
      • Installation of IGWN was done on k1detfs.
        • Too slow HDD response? (~150KB/s via NFS)
      • Works well

        • SummaryPages as GPS-select mode

          • ini-file grammar is slightly changed from the old version.
        • Omicron
          • No special hack
        • Omega-scan
          • needs temporal code hack
        • Bruco
          • needs preparation for reading kagra data (kagradata.py)

          • No --include option in original one.

      • Not yet

        • SummaryPages as Daily mode (This will be done by Kamioka people)

        • hveto
        • FScan
          • Not included in IGWN environment?
      • Problem

        • No global NDS2, DataFind servers or equivalent way.

          • SSH port forwarding is not enough because port number is different depending on person.
          • So I cannot do the code hack on IGWN software in the system region.
        • KAGRA env may not be able to be included in IGWN until O4.
          • If so, we shouldn't use IGWN in officially for O4.
      • (Lupin) igwn-py38? or py39?
      • YamaT asked status of FScan
      • In future, we need to prepare similar environment on Kashiwa cluster. The environment is not completely same as Kamioka computers.
      • We need volunteers from remote site, to test hveto and FScan. Please let us (Yuzuriahra or YamaT) know.
    • DQR update (Yuzurihara)
      • Operation test for new version of Task Manager is on-going on k1det1.

      • I found that code of stationary task uses datafind to read gwf data, which we don't have.

      • I need to consider how to read data for DQR tasks.
        • (Darkhan) Is there any way to get the latest list of channels?
        • (Yuzurihara) If you can specify the name of frame data, there is a function on gwpy.
    • Update of summary page (Oshino)
      • no update
    • Trouble of Omicron trigger generation (Oshino)

      • klog#20328

      • replaced the local SSD on k1sum1. The Omicron triggers are stored in different disk.
    • 120Hz glitches investigation during O3GK
      • no update
      • Kihyun can't join for a while. This project will be postponed.
    • Report of new tool development (Darkhan)
      • showed demonstration
      • this tool can take a ratio between channels and will be able to apply time-domain filter (band pass/highpass/lowpass) in future.

20220328 (Mon.)

  • Minutes
    • Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
      • YamaT constructed the test environment in local computer

      • Although YamaT is copying the environment to DetChar computers, it is very slow. (speed ~ 250KB/s)

      • After copying, YamaT will work on modification of codes to fit KAGRA data, such as nds2.py
      • For testing the tools (Omicron, Hveto...), we need volunteers, especially remote site!
    • Activity report by students from Aoyama Gakuin univ.
      • five students and two staff members from Aoyama Gakuin univ. stayed Kamioka site during last three weeks.

      • They helped commissioning work both in tunnel klog#20124 klog#20155 and in control room.

      • several code developments to understand glitch cause have been done. klog#20026 klog#20027

      • code development to identify mirror center of ITMX have been done by using image analysis. slide(Japanese) klog#20036 klog20198 klog#20203

    • DQR update
      • Joe updated Task Manager. Yuzurihara will install new version and test it.
    • Update of summary page
      • no update
    • 120Hz glitches investigation during O3GK
      • no update

20220307 (Mon.)

  • Agenda
    • announcement

      • 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]
    • DQ flags for O4
    • DQR update
    • glitch investigation related to IMMT1 oplev
  • Minutes
    • 120Hz glitches investigation during O3GK
      • no update
    • unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
      • YamaT is working on this project at test-server.
      • Test of new conda environment will start from next week (after JPS meeting)
    • DQ flags for O4
      • no update
    • DQR update

      • Joe is developing the code to connect between igwn-alert and TaskManager. It will be available soon.

      • Schedule for review
        • Review of Task Manager will be done before review of each task.
        • High priority task needs to complete before Aug. 2022
        • Low priority task needs to complete before Nov. 2022
    • glitch investigation related to IMMT1 oplev
      • From March 8, students from Aoyama Gakuin univ. stayed at Kamioka

      • They worked on the investigation of glitch. klog#20026klog#20027

      • They checked IMMT1 QPD signals and PRM suspension signals at the time of glitch.
    • NDS2 tool development (Darkhan)
      • no major update.
    • GPS accuracy monitor (Oshino)

      • is available on summary page

      • Current difference is acceptable and reasonable.
    • No meeting on March 21 due to Japanese holiday. Next meeting is planed on March 28.

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 (Yuzurihara)
    • 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, they found many short term lock loss (~10 ms). 10 ms is too short to follow the suspension motion, so it is likely that there are some causes of the lock loss except for the suspension motion.

      • The commissioner needs helps DetChar members to identify the cause or give a hint of the cause.

      • For details, see klog#19963 klog#19983

      • main channel K1:TMS-X_GR_PDA1_OUT_DQ
      • time : 2022 Mar 06 23:37:50 UTC = 2022 Mar 07 8:37:50 JST = GPS time 1330645088

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-11-05 14:02:03 by HirotakaYuzurihara)