Displaying report 1-1 of 1.
Reports until 22:20, Monday 27 January 2014
H1 IOO
paul.fulda@LIGO.ORG - posted 22:20, Monday 27 January 2014 - last comment - 19:27, Tuesday 28 January 2014(9586)
IMC calibrated length / frequency path housekeeping

[Jeff, Paul]

I had a look through the calibrated length and frequency paths for the IMC (IMC-X and IMC-F respectively) to check that the calibration is still in order. A description of all the filters in the IMC-X and IMC-F paths can be found in Giacomo's entry 5945.

In fact, some things were amiss in the IMC_X path:

IMC-X_M1 path:

Filters that were engaged: to_m

Filters that are now engaged: dc_cal, wresg1, wresg2, to_m

MC2 M1 feedback is not currently engaged, so this may not matter right now. However, I've engaged the filters that calibrate the IMC-X_M1 signal to M3 motion. wresg1 and wresg2 model the suspension TF from M1 actuation to M3 actuation with the resg damping filters engaged (as they are currently). If and when M1 stage feedback is applied, the corresponding IMC-X channel should be calibrated now.

IMC-X_M2 path:

Filters that were engaged: dc_cal, white, sus_d1, sus_d2, to_m

Filters that are now engaged: dc_cal, wresg, to_m

The sus_d1 and sus_d2 filters are used to model the suspension TF without the resg filter in the M1 L damping path turned on. Because we are now using the resg damping I have switched the sus_d1 and sus_d2 filters off and engaged the wresg filter, which is used to model the suspension TF with the resg filter in the M1 L damping path. The white filter is a filter which was implemented in L1 in an attempt to avoid digitization noise above 50Hz (since the signal is so small there). I don't think we want to have this filter engaged, since it has to be accounted for later in data analysis, and I think we can ignore IMC_X so far above the L to F crossover. I've therefore disengaged this filter. This isn't the first time this one has come back to haunt us: see e.g 5311 or 5452.

IMC-X_M3 path:

Filters that were engaged: dc_cal, white, sus_d, to_m

Filters that are now engaged: dc_cal, wresg, to_m

Same story as for the M2 path.

I took a snapshot of all IMC-X filter banks.

IMC-F path:

Filters that were engaged: cts2V, InvGenFilt, VCO, FtoL

Filters that are now engaged: cts2V, InvGenFilt, VCO, FtoL

The only filter that changed since Giacomo's entry 5945 is the FtoL filter being engaged now instead of the tokHz filter. This means that the IMC_F signal is now calibrated in meters, presumably for ease of comparison with IMC_X. I checked the VCO gain filter: it is still the 536,604 Hz/V value, agreeing with Kiwamu's number from entry 5556 after accounting for the double pass of the AOM.

Comments related to this report
laura.nuttall@LIGO.ORG - 17:59, Tuesday 28 January 2014 (9616)
I had at four separate times (first plot) after these changes were made to see how H1:IMC-X_DQ looked after it didn't appear comparable to LLO last week (see alog 9373). I've also attached a more recent plot of the same channel at LLO (second plot). The same channel still looks quite different between sites and H1:IMC-X_DQ still seems quite featureless in comparison to LLO. A rather naive question...are they meant to look similar?
Images attached to this comment
paul.fulda@LIGO.ORG - 19:27, Tuesday 28 January 2014 (9618)

As Laura pointed out, the calibrations for L1 and H1 data for these two paths were quite different. I've now gone ahead and changed the H1 calibration path to match the L1 settings.

IMC-X

M1 filters: dc_cal, white, wresg1, wresg2, to_um

M2 filters: dc_cal, white, wresg, to_um

M3 filters: dc_cal, white, wresg, to_um

This means that the IMC-X path is now calibrated in micrometers and it does have the whitening filter engaged. This means the whitening filter (two zeros at 0.2Hz and two poles at 1kHz) should be accounted for in post-processing.

IMC-F

Filters: cts2V, InvGenFilt, VCO, tokHz

This means that the IMC-F path is now calibrated in kHz.

I've saved a snapshot of all 4 filter bank states.

Displaying report 1-1 of 1.