Reports 1-1 of 1 Clear search Modify search
DetChar (General)
hirotaka.yuzurihara - 22:12 Saturday 22 October 2022 (22627) Print this report
Noise budget mode is available on Pastavi

I developed the tool to make noise budget by Pastavi. (I added the button for noise budget mode. See the attached figure)

Note that this is the early access, so there are bugs (due to development for 6 days)! Helpful comment/suggestion/bug report are welcome!

 

Usage 

Mainly the usage is two-step.

  • Compute noise budget data set (see figure)
    • visit the Pastavi page
    • select the date to compute ASD by date or gps time
    • select the transfer function data (xml data from diaggui) from table
      • If you measured the transfer function by diaggui at workstation, put the xml data at `/kagra/Dropbox/Measurements/NoiseBudget/TFs`
      • XML files will appear in this list automatically via Dropbox. If not appear, push the reload button
    • push the button `Fill form` in the right side of table
      • channel A and channel B, xml channsl for ASD will be filled.
      • Usually channel B should be DARM channel.
      • If you want to use other channel for ASD estimation, you can edit the channel for ASD
    • (option) select the legend name for plot. If the form is empty, the channel name will be used for plot.
    • (option) add memo to share the information about the condition, date, who. This information will be shown in the buttom table.
    • push the button of `Make plot` 
      • inside the code, we read the data and estimate ASD.
      • we read the transfer function from xml file and interpolate with fixed frequency (0.01Hz).
      • we compute `TF * ASD * calibration filter` as noise budget data.
      • the resulted spectrum is stored as numpy binary file (in future I will add the download button in the table), and they are listed up in the buttom table.
    • repeat these steps untill you finish generating all the noise budget data set
  • Make a noise budget plot (see figure)
    • Select single or multiple noise budget data from table by checking the checkbox
      • `for reference` :  just shown in the plot as reference data
      •  `for noise budget` : shown as noise budget data and also the square root of sum
    • (option) you can set x/y-range
    • (option) you can set the scal for the plot
      • default setting is log-log scale

Sanity check

  • Tamaki-san made the noise budget for ETMY_MN [klog#22449]
  • I tried to make a noise budget by using new tool (see figure). The resul looks consistent.
    • In my noise budget, I didn't include AS DARK noise due to issue. It is a fiture task.
Images attached to this report
Comments to this report:
tomotada.akutsu - 23:28 Saturday 22 October 2022 (22632) Print this report

Nice! Seemingly useful!!

hirotaka.yuzurihara - 12:51 Monday 07 November 2022 (22814) Print this report

Related to klog#22811,

I finished implementation of the several features : 

  1. checkbox to tuen on/off the noise curves for `current best` and `O4a target (3Mpc)`
  2. category in the legend, such as `noise budget` and `reference data

I attach the updated example.

Images attached to this comment
hirotaka.yuzurihara - 20:59 Thursday 10 November 2022 (22876) Print this report

I finished the implementation of the arbitral color option to select the line colors.

See the attached image. Only if you want to change the line color, you should edit these list for line color.

I attach the example using the default color set.

Images attached to this comment
hirotaka.yuzurihara - 15:44 Wednesday 16 November 2022 (22929) Print this report

Here are recent new features.

  • When you set the `alpha` in color list, that noise budget data will not be appear on noise budget plot (actually alpha value will be set as zero). But, it will be included in `Summation of esto,ated noise`.
    • This is a option for plotting multiple kinds of noise curves.
    • see the attached screenshot
  • I added the checkbox to overplot `plot CLIO's best sensitivity`.
Images attached to this comment
hirotaka.yuzurihara - 18:52 Thursday 22 December 2022 (23327) Print this report

Due to the Dropbox issue (klog#23015), the noise budget mode was down this month. But, Tamaki-san needed to make the noise budget. So, I fixed the issue by very very very temporal way. (When Dropbox comes back online, I will edit my script to be back to the original way.)

Now you can ues the noise budget mode on Pastavi.

  • When you copy the xml file to Dropbox directory ( /kagra/Dropbox/Measurements/NoiseBudget/TFs ), please wait for 1 minutes to sppear the xml file on the table. If the xml file doesn't appear on the list, please remove the cache and the history of the web browser and try again. If that doesn't work, please contact Yuzurihara on slack.
  • Currently, the Pastavi server is mounting the Dropbox directory by `sshfs`. The connection is not stable. So, if something strange, the connection might be stopped. In that case, please contact Yuzurihara. I need to reconnect manually.... (I miss Dropbox.)
hirotaka.yuzurihara - 12:41 Sunday 25 December 2022 (23358) Print this report

I implemented the feature to record the summation of estimated noise curve.

By using this feature, you can compare several kinds of sum of noise budged, such as comparing the noise budget under strong seismic motion and mild seismic motion. Concrete example will be provided by Tamaki-san!

Usage  (see attached figure): 

  1. Check the option of `output sum of noise sources` and push `Make plot` as usual
    • legend name will be used on the plot as legend name
    • memo describes the situation and a personal memo in the below table. This will not be used for the plot.
  2. The result of sum will appear in the table
  3. Select several sum of noise budget and make plot of them as usual
Images attached to this comment
hirotaka.yuzurihara - 17:30 Wednesday 25 January 2023 (23695) Print this report

Based on Tamaki-san's request, I added options to overplot several target sensitivity during O4 and O5. There are check boxes above the table. (see attached image

Images attached to this comment
hirotaka.yuzurihara - 9:42 Wednesday 15 February 2023 (23966) Print this report

In the case of oplev, the data is recorded by 512 Hz sampling. But, the commissioner can sweep over the Nyquist frequenc (such 1000 Hz). This made the error.

I fixed the issue this morning. Now you can make a noise budget whose the transfer function is measured over the Nyquist frequency. Anyway, the user doesn't need to care the frequency band.

 

I also added the recent sensitivity curve on the bottom table. Check the data of `creation date = 2023-02-15 09:25:38 JST`.

hirotaka.yuzurihara - 15:23 Wednesday 15 February 2023 (23975) Print this report

Based on the chat with Tamaki-san, I updated the apperance of noise budget page to improve the usability. See the attached image.

Images attached to this comment
hirotaka.yuzurihara - 21:52 Tuesday 28 February 2023 (24206) Print this report

I updated the noise budget mode.

When you select the xml file and the date to compute ASD, the result will appear in the next page, with the following question : 

  • When you push `save this result`, the generated noise budet data will be added in the databse. So, you can make noise budget plot by using this data.
  • When you push `close window without save`, the generated noise budet data will NOT be added in the databse.

I hope this update will prevent the scatter a table of noise budget.

Images attached to this comment
hirotaka.yuzurihara - 0:59 Thursday 02 March 2023 (24223) Print this report

I updated the way to create the data set of DARM sensitivity. Previous way was complicated..

New procedure

  1. select checkbox of `compute DARM sensitivity` (see Fig)
    • xml is not necessary. so, form for xml will be empty
    • necesary channel names will be filled automatically
  2. select date and time as usual (see Fig)
  3. put the legend name and memo
  4. push `make plot`
  5. confirm the created sensitivity curve. If OK, push `save` button to add table.

Note that when you create the plot with overlapping noise budget and DARM sensitivity, please check `for reference` for DARM sensitivity and `for noise budget` for noise budget data.

Images attached to this comment
hirotaka.yuzurihara - 9:31 Wednesday 08 March 2023 (24303) Print this report

I added the feature to make a noise budget data from text data, instead on using the transfer function. See the instruction and gif.

For the stable operation, there are the requirements for the text file. (or you just mimic the example data.)

  • Add the header staring from #
    • #author: [name of responsible person of this data]
    • #date: 2023-03-06 12:00:00 JST
      • The data is when this text data was generated (= simulated or measured). Please follow the format to write date.
    • #channel: [channel name]
      • write down the channel name related to data. If no related channel, empty is OK.
    • #description: 
      • `description` is an explanation of data, including simulation or measurement. (sample) a simulated amplitude spectrum of thernal noise assuming laser power = 100 W....
    • #reference: https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=13253
      • `reference` is URL to refer the data set, such as klog or JGWdoc. In such page, I expect the user uploads the code to generate this data set.
  • The text file should be put under the specific directory of KAGRA Dropbox (/kagra/Dropbox/Measurements/NoiseBudget/txtdata/) and should have the header lines like this example data. If the text data doens't include these header, it will not appear on the table.
  • About the file name, there is no limitation.
  • The contents of text file must be frequency and ASD [m/sqrt(Hz)]. If ASD has the different unit, please convert to [m/sqrt(Hz)] by yourself.
  • The line starting from # will be ignored as comments.
  • In the Pastavi, the data will NOT be interpolated and it's convenient to prepare the data with 0.1 Hz frequency resolution (by yourself) to compute sum of noise budget.

I checked that we can make the plot from the text file. If you found the bug, please let me know.

Images attached to this comment
Search Help
×

Warning

×