It is useful if the pastavi noise budgetting can

• select which noise contirbution curves will be included into a single summation curve
• become possible to display such summation curve"s", and
• select which DARM would be displayed, as commissioners sometimes want to compare some noise projection curves with the " current" DARM (or MICH or PRCL or...) to understand the noise landscape.

for the sake of commissioning. > Yuzurihara-dono

Can pastavi extract the DARM noise curves from a measured .xml file?

Akutsh-san, thank you for your comments!!

• > Can pastavi extract the DARM noise curves from a measured .xml file?
  • It is not implemented yet.
• > select which noise contirbution curves will be included into a single summation curve
  • There are two options in the bottom table. If you select `for reference`, that noise curve will not be included in the summation.
• > select which DARM would be displayed, as commissioners sometimes want to compare some noise projection curves with the " current" DARM (or MICH or PRCL or...) to understand the noise landscape.
  • I agree with that. In (near) future, the noise budget tool will be very important to judge the priority for the noise hunting activity and the improvement of inspiral range.
  • The current tequnical issue for your suggestion is to implement the (whitening and de-whitening) filters which are used in diaggui and foton.
  • In the current Pastavi, the latest whitening filter for DARM is implmeneted by hardcoded. But, to extend the tool for MICH, PRCL, and so on, the tool need to be able to treat any filter on foton.

Tamaki-san,

thank you for using the noise budget tool and also helpful feedback.

About the issue that one noise curve is hidden by summation curve, you can handle this issue by selecting `for reference` checkbox instead of `for noise budget`.

If you select `for reference`, the summation will not appear on the result plot.

> For now, it seems current DARM sensitivity can't be shown at least from Pastavi web page (navy blue line is current best, so it is not same as the DARM line in klog22513). 

I think if you specify the date and the proper channel name, you can overplot the current sensitivity. The procedure is as follows: 

• In the upper page of Pastavi, please select the date when FPMI was locked. To check such date, summary page is convenient. There is a button to check the lock segment by the summary page.
• Write down the channel name is `K1:CAL-CS_PROC_C00_STRAIN_DBL_DQ` in the form of `channel for ASD`. 
• Select the option `no transfer function + with filter (require : only channel for ASD)` in the top of table. If this checkbox is on, you don't neet xml file. And the generated noise curve is just sensitivity curve with multiplying the proper filter.

(I'm sorry for requesting the complitcated procedure. When I got the good idea, I can implement that more conveniently.)

I correct my post.

• The channel name was incorrect. Please use `K1:CAL-CS_PROC_DARM_DISPLACEMENT_DQ`. I attach the example of noise budget  including the current sensitivity.

Future work memo

• Implement the checkbox to tuen on/off the noise curves for `current best` and `O4a target (3Mpc)`.
• Implement the arbitral color options (to keep robustness, the usage will be not so simple)
• Implement the category (group?) appearance in the legend. There are two categories in the legend : refernce and noise budget. By using indent, it might be possible to implement.