no restarts reported.
conlog frequently changing channel log attached
Kiwamu, Stefan, Matt, Lisa Since Valera called us to announce the LLO 50 Mpc and kindly encouraged us to catch up, we didn't want to let him down, and we decided to keep going. Details are in the previous entry , here are a couple of plots with the latest CARM offset reduction and power build up (TR_Y_QPD is 1 for single arm). REFL DC is going down and REFL 9I is going up as they should (first plot). BS control becomes unhappy in the latest step of the CARM offset reduction (see second plot). We were greedy (and sleepy) and we didn't measure anything on our way up, some loop measurements are the next thing in the list. Getting close..tomorrow there could be even more to be thankful for. P.S.: We still need to check our power and offset calibration.
Kiwamu, Lisa, Matt, Stefan - First we verified that the CARM to transmitted light transition still works today (arm power 0.32*single arm). - Next we repeated the transition to AS_45_Q, and turned on the gain scaling (arm power 2.0*single arm). - We also immediately turn on AS_45_Q gain scaling with TR_X (arm power 2.0*single arm). - Then we turned on the DHARD WFS (arm power 2.0*single arm): whitening gain of 9dB: H1:ASC-AS_B_RF45_WHITEN_GAIN 3 H1:ASC-AS_B_RF45_Q_PIT_GAIN and H1:ASC-AS_B_RF45_Q_YAW_GAIN gain to 0.1 input matrix AS_B_RF49Q to DHARD H1:ASC-INMATRIX_P_8_6 1e-4, same for yaw H1:ASC-DHARD_P_GAIN 0.3 , same for yaw control filter modules FM1 (integrator) and FM5 (Low pass LP0.2) output matrix: H1:ASC-OUTMATRIX_P_7_8 = 1 , H1:ASC-OUTMATRIX_P_8_8 = -1 , H1:ASC-OUTMATRIX_Y_7_8 = 1 , H1:ASC-OUTMATRIX_Y_8_8 = 1 - Then we went to a hgher arm power (arm power 32*single arm). - We noticed that TR_X starts saturating right around there, so we intended to switch to the QPDS, but had an unreasonable amount of trouble for this simple operation. - Still trying... Attached is a plot of the CARM transfer function. It also includes a transmitted power ratio of the QPD's and the LSC PD's.
The message is that we increased the build up in the arms up to ~30 times the single arm power (CARM offset ~ 40pm). The first plot shows a trend of the arm power transmission. In the first (incredibly stable!) lock we made several attempts to reduce the CARM offset further, but the IFO started to become unstable, so Stefan was quickly going back to a larger offset to prevent unlocking. It turned out that the problem was a saturation in the X TR diode (clearly visible in the second attachment). The following locking attempts were killed by the (in principle) straightforward task of switching to the in-vac TR QPDs. The problem turned out to be that the signals that we were carefully matching were one before power normalization, and the other one afterwards..
Later, we reduced the CARM offset further down to approximately 20 pm at which point the arm build up was 100 times higher than that of the single arm.
As reported in Stefan's previous log, we were having a difficulty in switching the TR sensor from TR_X(Y)_A to ASC_QPD_Bs. Keeping using TR_A actually introduced a broad noise peak at around 70 Hz which showed up all the LSC loops. Stefan then carefully adjusted their relative gains and therefore the transiotion went very smooth. We did not see an obvious transient in any of the LSC signals during the transition of the TR sensors. Then we further reduced the TR_CARM offset to -15 counts without a problem. We did not see a gain peaking or any sign of significant change in the optical gain of DARM. So we did not have to chage the DARM gain. At this point we saw REFL_DC almost going down as low as 50% and also POP_DC increasing significantly. We kept running the DHARD ASC loops.
We stayed at this point for a while, but then it seemed that the DRMI dropped the lock. Before the lock loss, RMS of the SRCL control signal slowly kept increasing. It could be a coupling from CARM which was contaminating the SRCL control. We may want to decrease the SRCL UGF in order to prevent the SRM suspension from saturating.
Nice going, you are almost there. (The old grouch (for Lisa's benefit)
The ALS_COMM and ALS_DIFF FIND_IR algorithms have not been working over the last few days, but they have been taking a lot of time to fail.
This evening we rewrote them both. ALS_DIFF has a nice algorithm which tries the known good locations quickly, and if that doesn't work it searches around those locations. Unfortunately, the search part has only been tested a few times, because the initial quick check of known locations usually works.
For ALS_COMM, we didn't bother with a search feature. The known good locations are checked, and if that fails (which is rare) it asks for help from the user. It would be good to better test the search functionality of ALS_DIFF, and then make ALS_COMM have something similar just to deal with the rare cases in which the known locations fail.
ALS_COMM is, in fact, not working too well. It may really need some search ability.
For initial alignment, and transmon pointing onto the baffle PDs in particular, we have a new script.
in /opt/rtcds/userapps/release/asc/h1/scripts there is
ditherAlign.py which has top level functions for TMSX and TMSY (and place holders for the ITMs) - this can be called from the command line e.g., ./ditherAlign.py TMSXbaffleAlign.py contains functions for aligning optics to baffle PDs - it includes a very coarse spiral search, a dither alignment, and higher level combinations of theseslowDemod.py contains ultility functions for dithering and demodulation using EPICS (yes, I know its bad, but what else? and it works for freqencies below 4Hz...)testDemod.py for testing slowDemod.pyWhen the TMSs are close to the correct position, the dither alignment takes less than 1 minute. When they are way off, it takes a few minutes.
This should be extended to the ITMs and ETMs to help find them when they are really lost. Once it is working well, we should move these into the IAS guardians.
There are some strange things, but in summary,
WFSA is more sensitive to the hard mode (arm axis rotation at around the center of the arm) than the soft (arm axis translation).
WFSB's sensitivity to the hard mode is smaller than WFSA by a factor of 5 or so. Also, WFSB is somewhat more sensitive to the soft than WFSA.
This means that we can use WFSB as the soft mode sensor and feed back to TMSX (because TMS causes the soft and the hard mode with comparable normalized amplitude at the same time), while using WFSA as the hard mode sensor to feed back to e.g. ITMX. Then we can use the ITMX camera image to slowly feed back to the ETMX to fix the beam position on ITMX. Or you can do fancier diagonalization but you get the idea.
In the attached, the right most plot shows the response of WFSA and WFSB against EX and IX PIT motion.
You can see that WFSA's response is much larger than WFSB. You also see that WFSA only goes down when you tilt EX, but that's not the case for IX (why?).
The middle plot shows you both PIT and YAW response. Again WFSA is much more sensitive than WFSB.
The left plot is the response against TMS in YAW (didn't have time to do PIT), and you see that the WFSB response is about twice as large as WFSA.
Both ETM and ITM causes mostly the hard mode motion because the cavity is close to concentric.
OTOH TMS causes both the hard and the soft mode motion at the same time.
So, all in all, these appear to mean that WFSA is more or less the hard mode sensor, and WFSB is the soft one.
SEI working on BSC2
Commissioning work on X-arm
Working happening over the break will require work permits
Apollo working on cabling outside and in the VPW
EE working in H2 building
9:30 Corey Craning in LVEA, done 13:30
10:00 Sudarshan to LVEA
10:45 Richard to LVEA
13:45 Corey back to LVEA
14:00 DaveB to CER, both Mids, back at 14:30
14:00 Richard and Vern to CER
Vern and Richard re-installed the TCS X rotation stage interface board with the protection diodes removed.
Dave Ottaway, Elli
For the X-end green WFS, we adjusted the WFS autocentering gain to match the Y-end WFS. The updated values are:
H1ALS-X_A_AUTOC_PIT_CTRL_GAIN: 200,000
H1ALS-X_A_AUTOC_YAW_CTRL_GAIN: -150,000
H1ALS-X_B_AUTOC_PIT_CTRL_GAIN: 70,000
H1ALS-X_B_AUTOC_YAW_CTRL_GAIN: 70,000
The unity gain frequency at the for the X-end WFS is:
WFS A PITCH: 15 Hz
WFS A YAW: 15 Hz
WFS B PITCH: 6 Hz
WFS B YAW: 7 Hz
And the unity gain frequency at the Y-end:
WFS A PITCH: 10 Hz
WFS A YAW: 10 Hz
WFS B PITCH: 7.5 Hz
WFS B YAW: 7 Hz
Ed, Keita, Jeff
So, a quick and nasty coherence check just to find possible dead monitor channels using a couple of frequencies reveals apparent bad channels:
ETMY M0: SD - voltmon, fastimon
R0: F1 - noisemon
L2: All Channels? - noisemon
ITMY L1: UR fastimon
All suspensions in Y-Arm from TMS back to ITM were tested. Any not specified here measured good.
The fact that ETMY L1 shows apparent DC offsets, in the -4300 ct range in all noisemon channels, UL voltmon and LR fastimon, is not revealed by this measurement.
The contractors will not be working on the new DCS addition during the Thanksgiving holiday, 11/27-11/30. They will return on 12/1.
The frontend laser watchdog was re-activated. For reasons unknown it was switched off around midnight on 11/11.
I'll go through and review to make sure nothing has been reverted or missed but this should be the last HEPI matrices to be corrected, at least those that really affect current operation and positional studies.
The rotation and pringle dofs had magnitude errors of x2 & x4 and the output (CART2ACT) matrix was all 1s. See the first attachment for the before (left) and correct (right) values.
The second attachment shows the times series as the platforms were taken down, the matrices corrected (shifting the Cartesian readings) and bringing things back up. No issues in that process: the ISI ST2 was already just damping, ST1 was brought down to damping and then the HEPI deisolated. Matrices updated, RZ Reference Location corrected, new filters loaded, HEPI and ISI reisolated. I tweaked the yaw position a few 100nrads to recover the exact OpLev output. Brough the system backdown to take a safe.snap and then reisolated. By the way, the Pitch & Yaw are correct.
The final two attachments are the before controllers and the new 4hz UGF generic controllers. The TF data going into these are from H2 ETMY but I still looked at them and with some phase margins in the lower 20degrees and some gain peaking near 3 using a 5hz UGF, I lowered the UGF to 4hz and now the phase margins are lowest in the upper 20s and the worst gain peaking is just over 2.
Updated safe.snap and new foton file committed to svn.
Daniel asked me to remove the search for home command from the ISC_DRMI guardian (this guardian had issued 61 search for home commands in the past 24 hours). I committed isc/h1/guardian/ISC_DRMI.py to SVN before making this change. I commented out the search for home line in the DOWN state's main section, and reloaded this node at 10:47PST.
Daniel was having problems with cam22 when executing a snapshot. The cam22 epics channels froze. Restarting the process via monit and manually did not recover the system, so I rebooted h1digivideo2. Daniel repeated his snapshot and it failed again. After the second reboot I successfully snapshotted cam22 and Daniel can no longer reproduce the error.
Initial attempts to take undamped TFs on ITMX & ITMY exhibited rung up P & R modes (see LHO aLOG entry 14653). For the next attempt, fine tuning of excitation amplitudes was necessary to avoid ringing up these modes. Phase 3b (in-vacuum) undamped TF measurements have been taken for ITMX & ITMY (QUAD) suspensions as follows:- - ITMX M0-M0 undamped results (2014-10-30_0700_H1SUSITMX_M0_ALL_TFs.pdf) - ITMX R0-R0 undamped results (2014-10-30_0700_H1SUSITMX_R0_ALL_TFs.pdf) - ITMY M0-M0 undamped results (2014-10-28_1200_H1SUSITMY_M0_ALL_TFs.pdf) - ITMY R0-R0 undamped results (2014-10-28_1200_H1SUSITMY_R0_ALL_TFs.pdf) ISI Status: ISI's damped and FULLY_ISOLATED via Guardian. ITMX & ITMY undamped TFs above have been compared with other similar QUADs at the same phase of testing (allquads_2014-10-30_AllQUADS_Doff_Phase3b_ALL_ZOOMED_TFs.pdf). The plot key is as follows:- Blue Trace = Model Prediction (fiber/thincp). Orange Trace = L1 ITMX (fiber 2013−09−04), Phase 3b. Black Trace = L1 ITMY (fiber 2013−09−05), Phase 3b. Magenta Trace = H1 ITMY (fiber 2014−10−28), Phase 3b. Cyan Trace = H1 ITMX (fiber 2014−10−30), Phase 3b. Summary: M0-M0, main chain TFs are a very good fit to the model, for all DOFs, with only some minor cross-couplings from P2V. R0-R0, reaction chain TFs agree with the model predictions and are consistent with similar QUADs. The largest deviation from the model can be seen with the ~1.45 Hz P mode, a consequence of the harness routing stiffening the suspension, seen before. Some minor cross-couplings are also present: from P2L, P2R, and P2V only for ITMY. Damped TFs should be taken to verify that damping loops suppress these cross-couplings. All data, scripts and plots have been committed to the sus svn as of this entry.
Power spectra had been taken and processed a while back, but not posted until now. These power spectra measurements have been compared to previous Phase 3 measurements for H1 ITMs (allquads_2014-11-26_Phase3_H1ITMX_ALL_Spectra_D*.pdf). The plot key is as follows:- Black Dashed Line = Expected Sensor Noise Blue Trace = H1SUSITMY 2013−07−19_1400, Phase 3b (in-vacuum) Green Trace = H1SUSITMX 2014−04−11_1600, Phase 3b (in-vacuum) Red Trace = H1SUSITMX 2014−07−07_1000, Phase 3a (in-air) Summary: Noise floors for recent ITMX measurements are consistent with previous measurements, but are much more noisy below 40 Hz due to air turbulence, clean rooms, purge air etc. Oddly, L1 and L2 OSEM DOFs appear to suffer from a scaling problem. However, scaling is correct for L1 & L2 EULER DOFs. n.b. the same discrepancy was also observed in the data taken before the optic was swapped. Thus, raising no concerns. All data, scripts and plots have been committed to the sus svn as of this entry.
Damped transfer functions can be found in LHO aLOG 15575.
