|
Size: 776
Comment:
|
Size: 1118
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| * The web server to share the DQR result is {{{gwdet.icrr.u-tokyo.ac.jp}}}? * Computational power is enough? (k1det1, k1det2) * Evaluate the load of NDS server * Check number of channel + sampling rate * In rough estimate by DQR, 5 event/day (including false alarm events) * DQR during KAGRA commissioning, DQR during LV ER |
|
| Line 10: | Line 16: |
| * For stationarity monitor, less than 1 min. (48 sec) | * For stationarity monitor, less than 1 min. (40~48 sec) |
Remained taks
- (Although this will finish just before O4,) fix the channel list for DQR
- Investigate how to run other tools.
- Finalize design document
The web server to share the DQR result is gwdet.icrr.u-tokyo.ac.jp?
- Computational power is enough? (k1det1, k1det2)
- Evaluate the load of NDS server
- Check number of channel + sampling rate
- In rough estimate by DQR, 5 event/day (including false alarm events)
- DQR during KAGRA commissioning, DQR during LV ER
Done
- Measure the computational time for one channel
- Investigate the availability of how many channels we can use for DQR by our computers
- For stationarity monitor, less than 1 min. (40~48 sec)
- For omega scan (2 channel), less than 1 min. (55 sec)
- Try to use other tool
For example, user's manual for {dqr-stationarity}
- finished preparing the init file for stationarity monitor
- Investigate typical data duration for DQR
- It depends on sensor type or data itself.
- Typically more than 64 seconds.