I updated the iscmodeling tools on the workstations in the control room by checking out them from MIT's cvs server. Jim secretly installed the cvs command only on opsws4 for me. So if one wants to update them in some future, he or she should run the cvs command on opsws4.
(Alexa, Sheila)
We began by misaligning ITMX. At which point our starting RF AM signal was -47dBm at 24.41MHz. We inserted a PBS before the EOM to ensure that we had optimized s-pol into the EOM. Then we adjustd the EOM stage such that the RF AM signal dropped to -60dBm. The Imon signal then had an RF AM offset of 2mV, with a peak-to-peak of 4mV at 500Hz (in comparison to alog 9434). The Qmon signal had an RF AM offset of 1mV with a peak-to-peak of 3mV.
We then examined the noise out of Imon with the cavity misaligned, and only saw a factor of 2 decrease at 100Hz compared to the previous measurement (alog 9436). This reduction could have also come from the improved modulation depth we achieved today. There is still too much noise...
Occasional unexpected CP1 level fluctuations previously shown to be the result of the filling of the portable LN2 dewars. Attached is the latest example. Only noteworthy when fluctuations reach alarm levels (~1/2 the time)
The h1dmt0 and h1dmt1 computers are in the process of being upgraded to Ubuntu 12.04. This will take a couple of hours.
The upgrade process has finished. John Z. will need to update the DMT software on both computers to finish the job.
Hugh, Sebastien
Position loops (UUG 5Hz) have been installed on HEPI-ITMX.
The design of those loops can be find in the SVN at:
/ligo/svncommon/SeiSVN/seismic/HEPI/H1/ITMX/Scripts/Control_Scripts/Version_5/GET_H1_ITMX_Controller.m
The function GET_H1_ITMX_Controller stores the zpk filters into a structure called FILTER_OUTPUT. This structure is used by the HEPI scripts steps 6&7 to generate the plots and saved the filters into the good format.
Sebastian and I looked at trends back during the day to set the Target positions for HEPI. We left the Pringle modes out of the loop for a while because they were generating large drives to the actuators. After a couple hours we saw the trends of the pringles not going anywhere fast so we set those targets and engaged those loops.
When I looked at longer term trends to make this log I see that the HEPI Location values were zero until Hugo and I worked on the position loops on the 16th and the input matrices were populated. The trends look very flat/stable until ~8pm 21 Jan. The ISC crew reports suddenly experiencing a sudden misalignment. They traced it to ITMx HEPI. Some confusion about whether or not they attempted to engage the uncommissioned HEPI loops but the point is, HEPI moved and stayed. They realigned the SUS and continued. So HEPI will stay here.
Attached is the current Cart_Bias for the Target positions. If you see the HP or VP numbers far from the Targets, know that these are AC coupled.
Done.
From ~ 2:00 - 2:10 PM
Done
Mark B.
The previous best HTTS model (20130723TipTilt) had two issues: (i) the MOI values from P1100090-v5 were obviously wrong and had had to be arbitrarily increased by about an order of magnitude to match the observed frequencies, and (ii) there was no allowance for built-in ECD. Bram supplied some new MOI/mass values which were more up-to-date and didn't have the divide-by-10 typo. And I added ECD support to the underlying Matlab.
The result is a new parameter set, 20140123HTTSdamp (Mathematica) or httsopt_damp.m r6162 (Matlab). See
https://awiki.ligo-wa.caltech.edu/aLIGO/Suspensions/OpsManual/HTTS/Models/20140123HTTSdamp and ^/trunk/Common/MatlabTools/SingleModel_Production/httsopt_damp.m.
The mass and MOIs are now as-built and the damping parameters have been chosen to roughly reproduce the observed peakiness in TF data from H1:RM1 on 12/20/13 (see attached plots for L, P and Y). The match to the mode frequency is now very good without any fudging.
Done
For WP 4409
Work done, VEA transitioned back to laser SAFE.
[Jeff K, Stefan B, + detchar] The bitmask defining the summary bit for the Input Mode Cleaner state-vector (ODC) has been trimmed to respond to only those bits recording the ASC WFS switch (bit 1), and the relative power indicators (bits 11 and 12). In this mode glitches in the WFS alignment will be recorded by the relevant bits 2-9 but won't affect the summary bit, and a low-power mode will still result in summary=GOOD. This was tested first at LLO and logged here. This hasn't been set in the safe.snap, but will be monitored and coordinated over the next few days.
We confirmed that when the WFS alignment (mainly DOF2 Pitch and DOF1 Yaw) strays outside of the thresholds set, it does not have a noticeable affect on the calibrated length of the cavity. Attached are ASDs for both LHO and LLO of IMC_X_DQ. Plotted are two nominal times (red/blue lines) when everything is aligned (all the ODC bits are green) and two times (yellow/green) when the WFS are reporting poor alignment (the y-axis is not in counts/rtHz but the units of the channel - m/rtHz (?)). There is no noticeable difference between the four traces on a given plot. For the time being, we feel ok in removing the WFS alignments from the summary bit (as reported) however we plan to do long term studies of what the thresholds for each DOF should be and maybe then they can be re-added to the summary bit. Question for whoever can answer this - why is LHO so featureless (compared to LLO) and why are the scales (y-axis) so different between sites? Thanks
