J. Kissel

I'm slowly working my way through the 14 suspensions that need chamber close-out testing after last week's furiously awesome effort to get doors on before the Thanksgiving week. It's going slower than expected because, for some of the SUS, I'm taking "Official SUS-style" TFs for the first time at LHO, so I've gotta tweak the measurements, make sure the SUS are set up correctly, and also because -- even on a Saturday! -- I'm interrupted with people calling me ask work questions ( THANKS JANEEN, GOSH (-; ). Anyways, enough whining. So far, I've seen no signs of badness -- excellent! Details below, and plots proving the goodness to come later.

----

I've now got and exported the (DTT) data for all degrees of freedom of M1 to M1 TFs
TMSX, RM1, and RM2
and they've been committed to the SVN. I'll process the data later when I find out from my colleagues in what the state of the matlab analysis software lies for these orphaned SUS types that we're now re-adopting into the family.

I still need to get M1 to M1 TFs of
IM1, IM2, IM3, IM4, MC1, MC2, MC3, PRM, PR2, PR3
and both M0 to M0 and R0 to R0 TFs for
ITMX

I've created new directories in the SUS repo for the HTTS, which hadn't been created yet for LHO because no one had taken any data on them.
The templates for the data I've taken are here:

/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/RM1/SAGM1/Data/
2013-11-23_2120_H1ASCRM1_M1_WhiteNoise_L_0p1to50Hz.xml
2013-11-23_2120_H1ASCRM1_M1_WhiteNoise_P_0p1to50Hz.xml
2013-11-23_2120_H1ASCRM1_M1_WhiteNoise_Y_0p1to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/RM1/SAGM1/Data/
2013-11-23_2214_H1ASCRM2_M1_WhiteNoise_L_0p1to50Hz.xml
2013-11-23_2214_H1ASCRM2_M1_WhiteNoise_P_0p1to50Hz.xml
2013-11-23_2214_H1ASCRM2_M1_WhiteNoise_Y_0p1to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/TMTS/H1/TMSX/SAGM1/Data/
2013-11-23_2045_H1SUSTMSX_M1_WhiteNoise_L_0p1to50Hz.xml
2013-11-23_2045_H1SUSTMSX_M1_WhiteNoise_P_0p1to50Hz.xml
2013-11-23_2045_H1SUSTMSX_M1_WhiteNoise_R_0p1to50Hz.xml
2013-11-23_2045_H1SUSTMSX_M1_WhiteNoise_T_0p1to50Hz.xml
2013-11-23_2045_H1SUSTMSX_M1_WhiteNoise_V_0p1to50Hz.xml
2013-11-23_2045_H1SUSTMSX_M1_WhiteNoise_Y_0p1to50Hz.xml

For each, I've exported both as .pdf and .txt with the same name (_tf tag for transfer function, _coh for coherence) for use later.

The triples and QUAD should go much quicker since there are already many measurements of them with known good DTT templates, so it's just a matter of opening them up and hitting go. Why DTT, and not the automated Matlab software that you can just set and forget, you ask? Because over the course of 6 hours, there're too many things that can fail with the automated system at this point, and you don't know of a failure until you've wasted the six hours. I'd rather mindlessly click buttons for six hours with DTT, constantly confirming that things are going well, and listen to some good tunes on a Saturday afternoon.