9987
Comment:
|
14084
|
Deletions are marked like this. | Additions are marked like this. |
Line 11: | Line 11: |
=== 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 * 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. * Update of summary page * Trouble of Omicron trigger generation * [[https://klog.icrr.u-tokyo.ac.jp/osl/?r=20328|klog#20328]] * 120Hz glitches investigation during O3GK * 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 * 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. ----- |
|
Line 13: | Line 55: |
* announcement | * Announcement |
Line 15: | Line 57: |
* 120Hz glitches investigation during O3GK * unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012] * DQ flags for O4 * DQR update * Tcam image analysis to identify mirror location and center (Aoyama Gakuin univ.) * Confirmation of task list for O4 |
* 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 |
Line 69: | Line 131: |
* Minutes | * Minutes (Yuzurihara) |
Meetings
- Meeting time: 13:00-13:30 JST/KST on every Monday
- Meeting room: Zoom
Contents
Agenda & Minutes
20220404 (Mon.)
- Agenda
- Announcement
DQR design document, put comments on git issue
- Workshop 2022/04/15
- 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
- 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.
- Update of summary page
- Trouble of Omicron trigger generation
- 120Hz glitches investigation during O3GK
- Announcement
- 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
- 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.
- Installation of IGWN was done on k1detfs.
- Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
20220328 (Mon.)
- Agenda
- Announcement
DQR design document, put comments on git issue
Workshop 2022/04/15 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
- Announcement
- 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
- Unify conda environment in Kamioka detchar computers, k1sum[01] and k1det[012]
20220307 (Mon.)
- Agenda
- 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.
- 120Hz glitches investigation during O3GK
20220307 (Mon.)
- Agenda
- 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 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
- 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