Reports 1-1 of 1 Clear search Modify search
DetChar (General)
takahiro.yamamoto - 12:29 Wednesday 19 March 2025 (33033) Print this report
Comment to Range estimation on SummaryPages (32817)
[Yuzurihara, YamaT]

Finally, we found both online and SummaryPages estimation has bias as opposite direction.

SummaryPages estimation over-estimated as ~10-12% due to the ripple issues (see also klog#32817).

Online estimation under-estimated as ~14-16%. Depending on the situation of enhanced resonant peaks such as 7Hz, 18Hz, etc. the configuration of PSD estimation during O4a is no longer suitable for current noise.

I modified online estimation code for current noise situation and will deploy it on next maintenance day.

-----
For some consistency with various web-site of LVK, ranges was estimated by using STRAIN channel during observing run. On the other, only DISPLACEMENT channel is well-managed during commissioning test (mainly due to human resource issue). So I had to revert used channel after leaving from O4a. But I forgot it. As the mitigation way of such kind of issue, I'm now planning to prepare new EPICS records on dedicated IOC@k1script1 to save estimated ranges by using both strain and displacement for an easy cross-check. In order to avoid confusing, only one range will probably be DAQ-ed. So another one will be prepared as an volatile records only for an quick cross-check.
Search Help
×

Warning

×