found that h1iopsush56 was incorrectly built against RCG2.6.1, we rebuilt against 2.6.2 and restarted. This fixed the bogus ADC bit error in the STATE_WORD.
We noticed h1susmc2 was built Tuesday against a modified RCG2.6.2 and should be rebuilt and restarted at some time.
While scouring the PR SUS screens and EPICs values to be sure they're up-to-date, I noticed that both the HLTS and HSTS overview screens (SUS_CUST_HSTS_OVERVIEW.adl and SUS_CUST_HLTS_OVERVIEW.adl) were still pointing to an old SUS_CUST_HXTS_M3_WD.adl screen which has some preliminary design of the optical lever portion of watchdog and was buggy in its parsing of the status bitword for PR3. Only PR3 has an optical lever, none of the HSTSs have one. I've now updated both overview screens to point to respective HLTS and HSTS M3 WD screens, SUS_CUST_HLTS_M3_WD.adl and SUS_CUST_HSTS_M3_WD.adl respectively. Their screen shots are attached. The updated and new screens have been committed to the userapps repository, under /opt/rtcds/userapps/release/sus/common/medm/hxts/ (Note I've also logged in and svn up'ed this directory, therefore updating the LLO screens for them since it's an noninvasive change, they also have no PR3 or SR3 optical lever yet, and haven't started using the lower stages of their HLTSs). In addition, because the optical lever on PR3 doesn't exist yet, and the band-limiting filter bank on the RMS path wasn't visible/accessible/linked from the previous WD screens, they had remained empty until now. Similar to the OSEM Band-limiting filters (), I've filled in FM1 in the SUM bank ($(IFO):SUS-$(OPTIC)_M3_WD_OPLEV_BANDLIM_SUM) with the 10 Hz low pass, dcBandLim = zpk([],[10],1,"n") (foton design string) and the P and Y paths ($(IFO):SUS-$(OPTIC)_M3_WD_OPLEV_BANDLIM_$(DOF)) with the 0.1 - 10 Hz band pass. acBandLim = zpk([0;8192;-8192],[0.1;10;10],10.1002,"n") (foton design string) Finally, for lack of experience, I've set the minimum SUM threshold to 5000 [ct] (based on half the typical light sum seen on the test mass optical lever), and the maximum RMS threshold also to 5000. (These filters still need to be installed on LLOs HLTSs).
Sanity check:
An overnight accumulation yielded the same results for the Y2 module. Conclusion - We can get reasonable results with a 4 hour accumulation. Temperature overnight 29F.
The bump in pressure at ~3:00 AM(11:00 utc) is not explained - maybe just a gauge artifact.
The h1ecatc1 Beckhoff computer just crashed about 10 minutes ago. Logging in shows a dialog box saying that 'Windows has recovered from an unexpected shutdown'. I will leave it for the night. This means the PSL environment channels are down again.
I ran the powershell script to start just the last set of IOCs (opcThird.ps1). These include the PSL environment channels.
Attached are plots of dust counts > .3 microns and > .5 microns in particles per cubic foot requested from 5 PM March 5 to 5 PM March 6. Also attached are plots of the modes to show when they were running/acquiring data. Data was taken from h1nds1. T0=13-03-06-01-00-00; Length=86400 (s) 420 seconds worth of data was unavailable on this server 1440.0 minutes of trend displayed
Guido M, Joe G, Deepak K
We restored the IMC mirror positions inside their suspension systems based on the Pitch and Yaw OSEM readings to their best lock values (02/10/13 22:20:00). The Pitch/Yaw readings and the Alignment Offsets of the three mirrors are:
MC1:
Alignment Offsets -
Pitch : 355 ct (665.661 urad)
Yaw : 497 ct (1332.258 urad)
Mirror OSEM Value -
Pitch : -2615 urad
Yaw : 46 urad
Length : 80 um
MC2:
Alignment Offsets -
Pitch : 65 ct (121.9 urad)
Yaw : 137 ct (367.8 urad)
Mirror OSEM Value -
Pitch : -21 urad
Yaw : 137 urad
Length : 5 um
MC3:
Alignment Offsets -
Pitch : 543 ct (1018.2 urad)
Yaw : 170 ct (455.7 urad)
Mirror OSEM Value -
Pitch : -855 urad
Yaw : -376 urad
Length : 66 um
I've updated the h1susmc*_safe.snap files this morning with these numbers. In addition, Arnaud noticed yesterday that the MC1 M1 (top stage) open light current compensation OFFSETs and GAINs in the OSEMINF banks were actually the *old* assembly area values instead of the values taken with production electronics from LHO aLOG 4067. I've updated the compensation to use the production electronics numbers, so this is captured in the h1susmc1_safe.snap as well. All three .snaps have been committed to the userapps repository.
Following aLOG 5671, I have started to restore the HEPI at EY this afternoon. Here are the few tasks performed:
- Large offsets were visible in corner 3. (Source of the shift (Feb 25th,2013) is unknown at the moment). I applied offset drives in the local basis to bring back the IPS within 3000 counts.
- I cancelled out IPS offsets in the Cartesian basis
- Few weeks ago, I modified the commissioning scripts such that the minus sign of the feedback loops is introduced in the isolation filters. Before the modification, I temporary put the minus signs in the Output filter bank to be able to use the "ramp up" script. I removed the minus sign from the output filters bank.
- Ramp up isolation filters
- Applied the yaw offset (-737800 counts)
STS-2 (ground instrument) looks currently off centered and signals are pretty flat. Centering the seismometer was unsuccessful.
STS-2s can be re centered either using by pushing the AZ button (front panel of the interface chassis) or using binary outputs. At this point, binary outputs are only controlled by the ISI models (the feature is not implemented in the HEPI models). I noticed that the STS-2 centering bit (at EY) was high whereas it should not (The ISI output word is right). I left the binary output cable (from BO chassis to STS2 chassis) disconnected.
The curtains closest to BSC2 were removed and rolled up for temporary. All extraneous CPStat was removed from the beam tube close to HAM3. Tomorrow, we will rig the HAM3 cleanroom and move it into place as close to BSC2 as possible using the crane.
I restarted the DAQ after the vacuum work was completed today. This added the new IOP models for h1sush56, h1susauxh56, h1seih45 to the DAQ. This closes WP3736.
I extended the H1CDS_STATE_WORD_CUSTOM.adl medm screen to include place holders for MY and EX systems and add a summary of the DAQ systems.
The Perl environment setup scripts have been modified for control room workstations to add a LIGOTOOLSBIN path, which should point to /ligo/apps/${EPICS_HOST_ARCH}/ligotools/bin/
No issues to report here. We had only 5 Apollo crew. Cleanroom was lowering at 8am and the Cartridge was TDC at 1155. Crane full payload was 9560, Cartridge weight 9130lbs (less the 430lb 3point lifter). Apollo took 30 minute lunch and back to raising the cleanroom. Landed and bolted to Support tubes and all torqued, closed up, & exited at 1445.
Thanks to Jodi for lots of prep work as well as Jim Greg & Mitchell and Apollo: Randy, Mark, Mick, Scott & Ed. Thanks to MichaelL for logistical & moral guidance.
I'm sure Dale will provide to images soon.
Results are posted here as well as earlier with the H1 accumulation. The Y2 module appears be be significantly better than Y1 - perhaps 6 times better.
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=5666
9:00 LVEA laser safe
10:00 Start moving the BS quad suspention
14:00 EY in laser hazard (Corey and Kiwamu)
14:15 Pooling water sample
14:20 Student at the control room and around (Dale)
14:30 Fire alarm at the Warehouse triggered by open an oven (contac Justin for more details)
14:45 BS in BSC2 completed
15:00 Safety meeting
Fire alarm activation was a result of dense steam cloud being released from an extended cycle of the Large Parts Washer---this machine is not typically used in this capacity but we will be doing similar procedures for the next few days to clean storage structures for HXTS suspensions. It is possible that the alarm may activate again.
Alarm ack by VPW crew per instructions from Richard M---no contact with HFD.
We took TFs and Power Spectra data for HSTS I1-MC1. All files have been committed to the SVN repository. The data files are attached below for review by Stuart A. and Jeff K.
My only minor concern is what appears to be a roll mode ever so slightly coupling into longitudinal + transverse DOFs. Although, damping appears to suppress this coupling on I1-MC1. After discussing this with Jeff B over the phone, he and his assembly team will check flag alignments.
Under close inspection, MC1 looks to exhibit similar R-T cross-coupling as has been seen on the L1 SRM suspension (see LLO aLog entry 6451), although shifted in frequency consistent with the shift in the roll mode. However, the MC1 R-T coupling is significantly weaker than for SRM, and having raised this with both Norna R and Jeff K, we feel that this minor feature should be noted, and that MC1 can be approved through Phase 1b.
J. Kissel We'd chased our tails for a few days because we were comparing uncalibrated alignment data mode cleaner mirror against calibrated data (see LHO aLOG 5660). We believe the calibration was not present over these past few days (maybe weeks) because the safe.snap was out-of-date. So, I've taken the time to give them a thorough, expert's thrice-over, ensuring all parameters are in the correct configuration, and have captured new safe.snaps. Details below. Items that I've confirmed: - OSEM open light current compensation is in place (OSEMINF OFFSETs and GAINs) - MC1 - M1 from LHO aLOG 4067, - M2 & M3 from LHO aLOG 3409 - MC2 - M1, M2, & M3 from LHO aLOG 3505, - MC3 - M2 & M3 from LHO aLOG 4624. - Sensor calibration is ON (see LLO aLOG 4291 for derivation) - OSEMINF FM5 "to_um" filter is engaged for all stages (see LLO aLOG 4555 for original implementation) - DAMP FM5 "norm*" filter is engaged for M1 stage (see LLO aLOG 5388 for original implementation) - DAMP damping loops are set with up-to-date filters and gains: - L: FM3 [resg], FM5 [normL] G = -1.55 - T: FM1 [0:25,25], FM10 [ellip50], G = -2.0 - V: FM1 [0:20,20], FM10 [ellip50], G = -3.0 - R: FM1 [0:20,20], FM10 [ellip50], G = -0.2 - P: FM1 [0:25,25], FM10 [ellip50], G = -2.0 - Y: FM1 [0:20,20], FM10 [ellip50], G = -1.0 Note, the exact frequencies at which the velocity damping filter (FM1) in T,V,R,P,and Y differ from LLO, but this doesn't really affect the performance -- they're crappy whether they're all at 25 Hz as in LLO or at 25 +/- 5 Hz as they are here (and isn't captured by the BURT snapshot anyways). They will be replaced soon, so for now the discrepancy is not worth fixing. - ISIWIT Path is installed, on and engaged (originally from LHO aLOG 4553, but I couldn't find a log indicating when things were specifically installed for the MC mirrors.) - OPTICALIGN M1 alignment offset drive calibration is installed (from LHO aLOG 4763) - Alignment offsets from a prior good IMC lock are installed (from LHO aLOG 5663) - All stages of inner-most watchdog parameters are set, and the 'dogs are cleared and armed - OSEM DC Threshold set to +/- 30000 [cts] (based off of a ~few thousand count buffer of the full ADC range) - OSEM AC Threshold set to 8000 [cts RMS] (based off of empirical experience of "what it rarely goes over during normal use) - ACT AC Threshold set to 25000 [cts RMS] (based off of empirical experience of "what it rarely goes over during normal use) - All Bandlimiting filters are engaged - Coil Driver BIO states set to 1 (see T1100507) - Low Pass filter OFF for TTOP driver - Low Pass and Acquire filters OFF for TACQ driver - [MC2 Only] Locking Filter paths are as described from a prior good IMC lock (from LHO aLOG 5452) And naturally, for the safe.snap capture, I've turned OFF all requested drive to the DAC, so - OPTICALIGN alignment offsets are turned off (at the OFFSET button level) - DAMP damping loops are turned off (at the OUTPUT button level) - MASTERSWITCH is OFF -------- Though Mark has written a nice utility for capturing safe.snaps (see LHO aLOG 5202), I needed to get this done fast, hadn't used it before, and saw a few things I didn't like (which we've since corrected), so I captured the files "by hand" (which is quickest for me), hence: (1) Turned off all requested DAC drive, i.e. "natural" steps listed above by hand. (2) Captured each suspension's safe.snap, saving over what is in the userapps repository, e.g. controls@opsws0:burtfiles 0$ pwd /opt/rtcds/userapps/release/sus/h1/burtfiles controls@opsws0:burtfiles 0$ burtrb -f /opt/rtcds/lho/h1/target/h1susmc1/h1susmc1epics/autoBurt.req > /opt/rtcds/userapps/release/sus/h1/burtfiles/mc1/h1susmc1_safe.snap (3) Ensured that the link to target directory (which is where the front end *actually* looks during reboot) was in place, e.g. controls@opsws0:burt 0$ pwd /opt/rtcds/lho/h1/target/h1susmc1/h1susmc1epics/burt/ controls@opsws0:burt 0$ ls -l safe.snap lrwxrwxrwx 1 controls controls 63 2013-01-17 12:46 safe.snap -> /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susmc1_safe.snap (4) committed the new safe.snap to the userapps repository,
J. Kissel, C. Vorvick
Since I'm not nearly as much of an expert on the HAUX, I asked Cheryl to set up the IMs as she liked them, with appropriately good alignment offsets and captured a new h1susim_safe.snap as well.
Two things of note:
- The alignment offsets are installed in the TEST filter bank, because the fields built for alignment offsets (i.e. ${IFO}:SUS-${OPTIC}_M1_OFFSET_${DOF}) have not been converted from simple EPICs values to a full filter bank as was done for all of the multi-stage suspensions back in October to take advantage of the ramping features (see T1200478). It would be aesthetically good to change the alignment offset infrastructure to be the same as the rest of the suspensions, but it's not necessary. (though it's scary to have a place to mistakenly add non-working vestigial alignment offsets...)
- All watchdog values are set to +/- 100000 [ct] or 100000 [ct RMS], which is well outside of range that would actually protect the suspension. Cheryl says "they've been intentionally set to ridiculous numbers such that we can work in chamber without having to reset the watchdog all the time." Hence once the chamber is closed up an settled, we should set these values back to reasonable, protective, values, and recapture the safe.snap.
Kyle valved out the Y1 Module for a few hours today. Tomorrow we will valve out the Y2 module.
Attached is the rate of rise for the two end vacuum gauges.
If I have done the math correctly this translates to a very low outgassing rate with no significant leaks : 1.3 e-6 tl/sec for the 2km module. If it is all H2 this yields ~2e-14 tl/s/cm2
Rai reminded me that the gauge factor for H2 is about twice that for N2. So the outgassing rate stated above should be ~2x higher. Rai reports a number of 4e-14 for the H2 outgassing rate when measured 15 years ago.
An accumulation on Y2 was performed today. See the attached plot.
The results are 2.4 e-7 tl/s for the module which translates to an H2 outgassing rate of ~6.6 tl/s/cm^2 (using a gauge correction of 2 for H2)
This is significantly better than Y1.
Also attached is a plot of the two accumulations plotted on the same time scale.
Correction: the number above should be 6.6 e-15 tl/s/cm^2 for the H2 outgassing.