Attached are plots of dust counts requested from 4 PM August 5 to 4 PM August 6.
CP5 filled Constantly high dust counts in all three OSB optics labs Jim B. updated the control room CDS workstation GDS tools 09:06 Ace Portable Toilets on site 10:16 spike in dust counts at end Y, possibly coincident with Hugh R. flushing HEPI air lines Hugh R. reported he could not control medm screens from end Y, had me update HEPI pump control settings from control room 10:21 - 10:30 Cyrus R. reconfiguring and rebooting the mechanical room vacuum VME crate, MR INST AIR went invalid for a short period 10:34 Paradise water delivery 11:13 Hugo P. updating HAM ISI master model 11:49 Hugo P. restarting HAM ISI models, DAQ restarted
(Josh Smith, Stefan Ballmer) We estimated the IMC transmitted frequency noise due to the PSL intensity noise. The intensity noise explains the IMC frequency noise below 80Hz (the light discrepancy is likely due to me using ISS data from today). Interestingly, this noise also explains the HIFO-Y green readout noise between ~6Hz and ~50Hz (alog entry 7216). At the time of data taking (7/25/2013, 06:23:53 UTC) the ISS was off, i.e. the MC RIN was high (plot 2). Conversion: IMC_trans_freq_noise = f0/L*PWR*(2+1+1)/c/mMC2/(2*pi*f)^2 * RIN where f0=2.818e14 Hz (red frequency) L=16.4736 m (IMC length, one way) PWR=164 Watt (Power in the IMC, = 1 Watt * Finesse/pi, Finesse=516) mMC2=2.9kg (Mass of MC2 mirror, same as for MC1 and MC2) (2+1+1) (effect of MC2 at 0deg, MC1 at 45deg, MC3 at 45deg) f (Audio frequency)
I installed the latest {master model/Medm/scripts} update from Stanford, on the HAM-ISIs (Details, ECR E1300548)
This new version features the replacement of local biases with Cartesian Biases for the ISIs. Doing so allows removing the DC value of the CPS readouts of the error signal (biases use) while still keeping information regarding the platform position, and alignment, in the cartesian basis (which we could not do with the local biases).
Master models, MEDM screens and scripts were updated for the HAM-ISI. Every H1 HAM-ISI model was recomplied and restarted.
Safe.snap files were updated for HAM2 and HAM3 so the local biases are left off when the model is restarted. Snap files are commited under the SVN (r5268)
the DAQ was restarted.
Everything work as expected. Isolation loops are turned back ON on both HAM2 and HAM3 ISIs. ![]()
Details about svn updates can be found in the attached log.
Work was performed under WP4082, which is now closed.
Updates are ready for installation on BSC-ISI as well.
We added fluid to the main line piping today and the fluid is flowing under servo control at 40psi.
I talked with Richard at Craftsman Flooring today. It appears from the file at Craftsman that we ordered enough material to cover the balance of the VEA floor around the chambers. Bubba knows where at least a partial roll of flooring is (Y-End by emergency exit). So I asked Craftsman to schedule flooring install ASAP, which will be next week. They will call me if they can get here sooner.
It seems that the ISS has been preventing the FSS from locking since yesterday (see alog 7340).
I turned off the ISS autolocker for the moment so that we can go ahead with the IMC locking which is one of the main activities recently.
For the linux-x86_64 workstation, the gds tools have been changed to branch gds-2.16.5 to be consistent with the LHO control room.
The gds tools have been updated to branch 2.16.5. The gds tools include diag, diaggui, chndump, foton, awggui, ezcaread, ezcawrite, ezcaswitch, ezcademod, ezcaservo, ezcastep, and some other utilites. Here's a list of more significant changes: GUI programs (diaggui, foton, awggui): Expand channel field width in fields and menus that display channel names. Ability to generate .png files for plots (bugzilla 420) Update to allow more than 128 tp and awg responses from front ends Release notes viewable from Help menu (if installed) For foton: Modify to report in much better detail errors that are encountered when reading a filter file. Errors reading a file are indicated by changing the File... button to a red color. When mouse clicking the red File... button, errors are displayed in a popup dialog box. (see image 1) Use caution if the File... button is red. This indicates that saving the filter file will most likely result in some (defective) filters not being saved. Change matlab merge batch mode to not display any ROOT graphics. Batch mode foton returns 0 for successful operation or -1 (255) for failure. Errors will be written to stdout if any are encountered. Filters with output ramp set with 0 ramp time will be converted to immediate switching with a warning issued to the user. Foton preserves filters that consist of only gain(1). For ezcademod, expanded the number of channels it can read to 200,000. This is inadequate, and is a stop-gap measure which will have a more permanent fix implemented.
The Mac OS X gds tools have also been updated.
Everything is within spec so we are moving on to the ERMx.
This is the last step of the alignment that is done with laser beam outside of the chamber. Once in chamber, we'll have to fine tune it using the real ALS beam.
Tomorrow we will:
Started M1 to M1 transfer functions overnight for PR2 (HAM3). HAM-ISI is damped.
I started a measurement on HEPI-HAM2 for the night (on 'opsws0'). Should be done tomorrow morning around 8am.
The DAMPED->ISOLATED transit script has been updated. What it does:
1. switch the blend filter installed into the first bank (blend_start)
2. turn on the lvl1 isolation loops
3. switch the blend filter installed in bank#4 (blend_low_frequency).
The location of the blend filters could be change later.
The recover scripts for SAFE and READY have also been updated. We'll try them tomorrow.
I ran a Local static test on HAM6-ISI to make sure sensor/actuator wiring is correct throughout the chain.
Results are attached. We drove 1000 counts on each actuator, and looked at the cross-couplings. Main cross-couplings (red) show that V2 actuator needs to have its cable flipped. This is a quick fix that will be performed tomorrow.
It also seem like the responses are not as consistant between corners as we would like them to. Rubbing cable(s) could be the reason.
Starting ETMX spectra at 4:25 pm to check health of suspension after Betsy and Travis made some adjustments.
Damping Off: 1059780891
Damping On: 1059780354
The summary plots have data for L1ITMX (blue), L1ETMX (green), and H1ETMX of 7/31 (red) and today (8/5). Since 7/31, the L1 and L2 OSEMs have been adjusted so the data for them is now valid. Nothing looks to be touching.
J. Kissel, H. Paris, A. Pele, B. Shapiro After spending all afternoon getting all the chambers up into their best (local) performance, I've used Stefan's instructions to lock the Y ARM on Red. So easy -- even I could do it! Thanks to all of those who've written scripts to automate the ALS and IMC :-). Interestingly, and I forgot to ask about it, but there's no need to run any down script when the lock is lost. One just runs the two scripts again (assuming your Beam Splitter alignment remains good). OK, I wrote the aLOG too soon. There have been several lock stretches, and the ISI-BS has tripped. I detailed time line is written below, for as long as I stayed here. Here's the configuration of the SEI/SUS during these stretched: Cavity Lock: Chamber HEPI ISI SUS HAM1 Locked n/a n/a HAM2 Floating, Alignment Offsets Only Level 2 Isolated MC1, MC3, PRM damped Level 1.5; PR3 damped Level 1.0 HAM3 Floating, Alignment Offsets Only Level 2 Isolated (eLIGO Blends) MC2, PR2 damped Level 1.5 BS Level 2 Isolated (Position Locked) Level 3 Isolated* BS damped Level 2.0 ITMY Locked Level 3 Isolated ITMY damped Level 2.1 ETMY Level 2 Isolated (Position Locked) Level 3 Isolated ETMY damped Level 2.1, TMSY damped Level 2.0 * I noticed ISI-BS had tripped around 2:53 UTC, but it may have been down for some time. I didn't bother bringing it back up, 'cause I didn't want to blow the cavity lock. Or another three hours. All Optical Levers are well centered. All BSC-ISIs have been brought up to the configuration outlined in LHO aLOG 7226, but just for posterity, this means: Level 3 Isolation Filters Blends at ST1 "T250mHz" and ST2 "250mHz" GND to ST1 STS2 Sensor Correction is ON (The corner station ISIs are both using the beer-garden STS2) ST1 to ST2 T240 Sensor Correction is ON ST0 to ST1 HEPI L4C Feed-Forward is ON (with "FF01_2" filters) The Input Gains for the L4Cs and GS13s are OFF (I *think* this means they're in low -gain mode). They're ON for the T240s. ---------- Time Line (all times UTC, Jul 25 2013) 2:27 Locked on Red 2:46 Lost Red Lock 2:47 Regained Red Lock 2:50 Glitch in CARM_IN1! 2:53 Noticed ISI-BS had tripped. All other ISIs are still fully operational 2:57 Glitch in CARM_IN1! 3:00 Lost Red Lock 3:06 Regained Red Lock 3:11:23 Glitch in CARM_IN1! 3:24:47 Glitch in CARM_IN1! 3:27 We begin to ignore the IFO and go home, be cause there's enough data in the can to get a 0.01 [Hz] measurement in the past (assuming those glitches don't spoil the spectra)... but may the lock last through the night!
Josh Smith, Chris Pankow Hi HIFO-Y folks, Stefan asked us to look into coherence around the time of the HIFO-Y tests of the past two days. Here we're comparing the data from the 25th in alog 7220 with the one from the 26th in this alog. The most noticeable difference between the two times is that the CARM noise is significantly lower, and nearly the whole effect comes from engaging the PSL ISS. Attached plots are: 1) CARM noise from 25th compared to CARM noise from 26th. 2) PSL ISS PDA and PDB for 25th - ISS OFF (sorry for not having this in RIN, will try to update with that info.) 3) PSL ISS PDA and PDB for the 26th - ISS ON 4) Coherence between ISS and CARM for 25th (very high) 5) Coherence between ISS and CARM for 26th (almost none) Note: o find the clean times we looked at ALS-Y_REFL_B_LF_OUT_DQ and LSC-CARM_IN1_DQ to make sure it was locked and had not glitches. Stefan mentioned that this could be from Intensity noise coupling to length/frequency noise in the IMC via radiation pressure. This should not be hard to calculate with the RIN of the PSL, the length and geometry of the MC, and the mirror masses. Is it already in the noise budget? We will continue for looking for other systems that have coherence during the quieter time on the 26th.
For the lower-noise HIFO-Y time from the 26th in the comment above, the PSL table/periscope accelerometer channels are somewhat coherent with the ratty noise from 100-400Hz (see attached PDF). This is not quite a strong as the coherence with the green laser HIFO-Y signal reported by Robert and co on 7150. In addition to that, the HAM3 GS13s show coherence at 0.4, 1, 3, and 4.2Hz (see second attachment). I also checked MICs, MAGs, TILTs, and L4Cs and didn't find anything to write home about.
Lock happens on Jul 26 2013 (UTC) 2:27 Locked on Red 2:46 Lost Red Lock
(Jeff, Kiwamu, Stefan) With the H1:LSC-REFLAIR_A_RF9_I calibrated in Hz, and the open loop transfer function measured, here is the noise it sees: Input Mode Cleaner transmitted frequency noise. Also plotted is dark noise (shutter closed). We do not know yet what the ugly noise ~1/f^3 noise is.
The loop transfer functions are attached: Open loop gains: CARM_OLG_RED.txt CARM_OLG_GREEN.txt Closed loop gains: CARM_CLG_RED.txt CARM_CLG_GREEN.txt Inverse closed loop gains CARM_iCLG_RED.txt CARM_iCLG_GREEN.txt Inverse closed loop gain with a factor of 1/2 gor Green Hz to Red Hz conversion: CARM_iCLG_RED_g2r_special.txt
S. Ballmer, J. Kissel We had made an estimate for the coil driver noise in low-noise mode (State 3, ACQ off, LP ON), and ruled it out. However, I've checked the state of the Binary IO switches, and MC2 is running in State 2, ACQ ON, LP OFF, and and MC1 and MC3 are running in State 1, ACQ OFF, LP OFF. We'll try for this measurement again, with the coil drivers in their lowest-noise mode.
I've plotted the above-attached, red and green, open loop gain transfer functions (see *_full.pdf attachment). Through trial and error, I figured out that the text file columns are (freq [Hz], magnitude [dB], phase [deg]). And remember these are IN1/IN2 measurements, so it's a measurement of - G, not G (which is why the phase margin is between the data and 0 [deg], not -180 [deg]). Also, because the data points around the UGF were so sparse, I interpolated a 50 point fit around the UGF to get a more precise estimate of the unity crossing and phase margin. See _zoom.pdf for a comparison of the two estimates. I get the following numbers (rounded to the nearest integer) for the raw estimate and the fit estimate: The raw CARM UGF is: 136 [Hz], with a phase margin of: 33 [deg] The Fit CARM UGF is: 146 [Hz], with a phase margin of: 30 [deg] The raw CARM UGF is: 169 [Hz], with a phase margin of: 35 [deg] The Fit CARM UGF is: 170 [Hz], with a phase margin of: 34 [deg]