Differences between revisions 182 and 362 (spanning 180 versions)
Revision 182 as of 2021-04-08 15:17:11
Size: 9451
Comment:
Revision 362 as of 2022-03-07 13:36:41
Size: 7246
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 room: Zoom3 (https://zoom.us/j/5045179604)
  * Meeting time: 13:00-13:30 JST/KST on every Monday
  * Meeting room: Zoom
Line 9: Line 9:
=== 20210408 (Thu.) ===
  * Agenda
    * O3GK analysis
    * SummaryPage
    * LV alert
    * 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.
        
Line 53: Line 11:
=== 20210325 (Thu.) === === 20220307 (Mon.) ===
Line 55: Line 13:
    * 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.
    * 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
  * 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
    * 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 continuous GreenX trial was done by commissioner.
    * The sudden lock losses were observed. The commissioner needs helps DetChar members to identify the cause or give a hint of the cause.
    * Related k-log : [[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]]
Line 82: Line 43:
=== 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
Line 126: Line 45:
=== 20210218 (Thu.) === === 20220228 (Mon.) ===
Line 128: Line 47:
    * 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.
    
    * 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.
Line 156: Line 86:
=== 20220221 (Mon.) ===
  * Agenda
    * 120Hz glitches
    * DQ flags for O4
    * progress of DQR
Line 157: Line 92:
=== 20210204 (Thu.) ===   * 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.) ===
Line 159: Line 104:
    * Progress of O3GK paper
    * O3 data replay
    * O4 requirement
    * 120Hz glitches
    * Report from [[https://wiki.ligo.org/DetChar/JanFeb2022DetCharF2F|LIGO Detchar F2F Meeting]]
    * DQ flags for O4
    * progress of DQR
Line 163: Line 109:
    * 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.
    * 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]]
Line 188: Line 122:
=== 20210128 (Thu.) === === 20220131 (Mon.) ===
Line 190: Line 124:
    * Report from Burst search
    * Binary range evaluation with C20 offline h(t)
    * Progress of O3GK paper
    * 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 194: Line 137:
    * 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
      *
    * 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.
Line 205: Line 155:

=== 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.
-----
Line 246: Line 157:
  * [[KAGRA/Subgroups/DET/Meeting/2021|2021]]

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 (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 continuous GreenX trial was done by commissioner.
      • The sudden lock losses were observed. The commissioner needs helps DetChar members to identify the cause or give a hint of the cause.

      • Related k-log : 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-11-06 09:16:17 by HirotakaYuzurihara)