4501
Comment:
|
7233
|
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 <<TableOfContents(3)>> |
Line 6: | Line 8: |
=== 20190606 (Thu.) === | == Agenda & Minutes == ----- === 20220307 (Mon.) === |
Line 8: | Line 13: |
* Urgent task for ER with X-arm cavity * Omicron update (Yamamoto) ... Done. * DQ Vector update (Yamamoto). * Glitch visualization (Kozakai) * SummaryPage update (Yokozawa) * Segment file update (Oshino) * Fscan update (Oshino, Yamamoto) === 20190530 (Thu.) === * Agenda * [[http://gwwiki.icrr.u-tokyo.ac.jp/JGWwiki/KAGRA/Subgroups/DET/Task/O3|Task list for O3 run and Engineering Run on 8th Jun]] * [[http://gwwiki.icrr.u-tokyo.ac.jp/JGWwiki/KAGRA/Subgroups/DET/DataQuality|Data Quality Flags]] * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=10289|Glitch plot]] === 20190523 (Thu.) === * Agenda * Task list for Engineering Run on 8th Jun. * Trigger based plotting tool [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=10253|ckozakai]] === 20190516 (Thu.) === * Agenda * Comment of JRPC meeting and PAB review. * * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=xxxx|Minutes]] === 20190509 (Thu.) === * Skipped due to the PAB review. === 20190502 (Thu.) === * Skipped due to the Japanese holiday. === 20190425 (Thu.) === * Agenda * SDF preparation * DQ flags for data analysis * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=10147|Minutes]] === 20190418 === * Skipped due to the F2F meeting === 20190411 (Thu.) === * Agenda * SDF flags preparation [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=9228|slide]] * Fscan on SummaryPage * DetChar computers * Tool development [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=10044}|slide]] === 20190404 (Thu.) === * Agenda * IMC run (3/29-3/31, 4/3-4/4) * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=10024|yamat]] * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=10029|ckozakai]] * Progress of Kamioka works * hveto * There are some bugs on the latest version of hveto. * Old version of hveto was installed in k1sumX and will be installed in k1det0. * Fscan * Automation of the Scan is already succeeded. * We found a bug in our cache generation system and start to fix this bug. === 20190328 (Thu.) === * Agenda * Progress of Kamioka works * Fscan run on test computer by manually. * For automating and integrating to SummaryPage, we need to generate Segment file in automatically. * We need to consider how to pick up line information and list up it from FScan results. * Automation of hveto on KISTI is succeeded with PMC error signal and PEM channels. * We start to install hveto on hveto@k1sumX. === 20190322 (Fri.) === * --(Zoom3)-- -> Zoom2 (https://zoom.us/j/6676627462) * Agenda * f2f talk * 1 slot (Status talk -> T. Yamamoto) * DAC satellite [?] * Task list in next week * Sharing the current situation of SummaryPage * Preparing k1det0/1 * Managing SDF for VIS * Installing LIGO's tools and KGWG's tools * Task list of engineering run * Providing glitch information: (t, f, SNR) * Providing line information: (f, df, Amplitude, noise source) * Preparing the information server * hveto and glitch identification (Pil-Jong & Kokeyama) * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=9984|PMC important channel list]] * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=9258|Glitch analysis presented in JPS]] |
* 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 * 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 96: | Line 44: |
=== 20190314 === * Skipped due to the JPS meeting |
----- === 20220228 (Mon.) === * Agenda * 120Hz glitches * DQ flags for O4 * progress of DQR * lock loss study of GreenX |
Line 99: | Line 52: |
=== 20190307 === | * 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.) === |
Line 101: | Line 88: |
* Task list of engineering run on May * Tools and results from KGWG * Summary Page isseus * f2f talk |
* 120Hz glitches * DQ flags for O4 * progress of DQR |
Line 106: | Line 92: |
=== 20190228 === * Meeting room * Zoom3 (https://zoom.us/j/5045179604) |
* 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 110: | Line 104: |
* Magnetic coupling proposal with LV (Jishnu) * Enhancement of SummaryPage * Data sharing between Kamioka, Kashiwa, and KISTI * Young-Min's trip * Slide * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=9903|yamat]] |
* 120Hz glitches * Report from [[https://wiki.ligo.org/DetChar/JanFeb2022DetCharF2F|LIGO Detchar F2F Meeting]] * DQ flags for O4 * progress of DQR * Minutes * 120Hz glitches * No updates * DQ flags for O4 * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=13851|slide]] * (Yuzurihara) read BLRMS data and made the several plots with 1% and 99% percentile. * When KAGRA will be locked as observation mode? * hopefully after july, there will be lock trial for two monthes(?) * When you set the 1% criteria, always you throw away the 1% data? * We might need to consider the better procedure to care that point. * progress of DQR * [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=19671|klog#19671]] ----- === 20220131 (Mon.) === * Agenda * 120Hz glitches * Report from DQR hackathon * DQ flags for O4 * Master thesis (Morisue-san) ----- === 20220117 (Mon.) === * Agenda * 120Hz glitches * ITMX glitches * DQR progress * DQ flags for O4 * Minutes * 120Hz glitches * No updates * Next step is coincidence search with signals around ETMY including local control sensors. * ITMX glitches * [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=19212|klog#19212]] * K1:VIS-ITMX_F3_LVDTINF_GAS_{IN1,OUT} have glitches. * It seems to occur around AA chassis. (AA and cable replacement didn't help to improve situation). * We will try to find glitches on other channels on the same ADC board. * This channel should be added to Omicron search on SummaryPages. * DQR progress * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=13721|JGW-G2213721]] * DQ flags for O4 * No updates * O3GK paper * Threshold used for computing a glitch rate was changed as SNR=6.5. * It's a same criterion with LIGO, and Virgo. * Both GEO and KAGRA's results are now computed and draft was also updated. ----- === Past meeting === * [[KAGRA/Subgroups/DET/Meeting/2021|2021]] * [[KAGRA/Subgroups/DET/Meeting/2020|2020]] * [[KAGRA/Subgroups/DET/Meeting/2019|2019]] |
Meetings
- Meeting time: 13:00-13:30 JST/KST on every Monday
- Meeting room: Zoom
Contents
Agenda & Minutes
20220307 (Mon.)
- Agenda
- Minutes
- 120Hz glitches investigation during O3GK
- no update
- unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012] (YamaT)
- There are many computers/workstations in Kamioka site or Kamioka control room.
- Workstations (k1ctr*) use common conda environment by mounting the file server.
In DetChar computers k1{sum,det}[01], conda environment should be unified all DetChar resources, similar to workstations.
To prevent the trouble that DetChar experts might break the environment, the conda environments will be set as read-only permission.
Installation will be done by Kamioka members. After that, we need volunteers to test the DetChar tools on new conda environment.
- what is the time line?
- Installation will finished before the end of March. From April, the test will start. Volunteers are helpful.
- DQ flags for O4
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 : klog#19963 klog#19983
- 120Hz glitches investigation during O3GK
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
- 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.
- accouncement
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)
- 120Hz glitches
20220207 (Mon.)
- Agenda
- 120Hz glitches
Report from LIGO Detchar F2F Meeting
- DQ flags for O4
- progress of DQR
- Minutes
- 120Hz glitches
- No updates
- DQ flags for O4
- (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
- 120Hz glitches
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
- 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.
- 120Hz glitches