I have more-or-less finished a rough first draft of the automatic gyro noise budget MATLAB code. The rough architecture is:

1. An M-file that obtains and saves the current gyro noise, by:
   1. Downloading a recent time series via NDS from the ATF frames
   2. Using pwelch to take the spectrum
   3. Saving the data and frequency vector as ASCII
2. A "data" directory containing the above spectrum as well as ASCII spectra of all independently measurable noise contributions, such as:
   • PDH box output noises (V)
   • PD dark noises (V)
   • Displacement noise measurements for fundamental mechanical noise coupling estimates
   • Phase noise measurements
   • CCW and CW OLTFs
   • etc (this data library will be updated and amended as we go along)
3. An M-file that calibrates all the data in (2), plots it along with (1), and generates a PDF. The current date and time are printed in the plot title. This file contains many adjustable parameters such as:
   • PDH box gain settings
   • AOM VCO deviation setting
   • Gyro signal -> ADC preamp gain
   • etc

In addition to this, there are two functions named "pdh1437" and "pdh2215" which contain analytical expressions for the two respective filters. They take as arguments 1) a frequency vector and 2) the appropriate box's gain setting and return a vector of the transfer function sampled at these frequencies. These are used wherever a spectrum needs to be multiplied or divided by the PDH gain.

The file in (2) takes the OLTF in each direction and divides by the correctly sampled PDH gain and actuator gain to obtain the optical response in V/Hz. This is used to calibrate voltage spectra into (rad/s)/rHz.

(1) is separate so that we can choose whether to pull the gyro noise from the frames or upload our own (e.g. an analog measurement), and there will be a single file that runs everything in one fell swoop.

Below is a sample output. In this case, I have used our analog measurement of the gyro noise from last week as I am still working out the kinks in the NDS method (for some reason, they don't come out quite the same). Obviously, this is still somewhat barebones and we will need to add in more noise sources as they come to us. The good thing is that---at long last---we will be able to simply press a button every time we want an up-to-date noise budget. If we make a change to the setup, it is simply a matter of dropping the new data into the "data" directory and re-running.