I measured the spot position on PRM by using the usual angular dither technique (see for example LLO alog 5010) with PRY locked. It turned out to be pretty good.
(some settings):
(results)
See the plot below.
(some notes)
In 2017, Koji corrected his coil balancing calculations from 40m elog 2863 Now,instead of
, where
is the ratio of moment of inertia and optic mass,
is the coil force imbalance factor, and
is the distance between coils. Corrected alpha to mm for HSTS optics: 39.28 mm / alpha For HLTS optics, see alog 42600.
Please don't disturb the Matlab session. -Hugh
WHAM4 only has level 1 robust controllers and we should build Level 2 & 3 controllers as well. Now that the system is really complete and we only have in-air TFs, it makes sense to run new TFs. We need to do this just about everywhere.
See the two attached plots to see the new CPS TF completed Wednesday, the response is nicely smooth (in vacuum) compared to the In-Air TFs with HEPI locked on May 23. Notice the large dip in H3 as well as the shift down and smoothing of peaks between 10 and 50 hz. Not sure what this means for controller development but it seems important. I drove with DTT and these seem to still be present. These features DO NOT appear in the GS13 signals but we do have good coherence here for the GS13.
Running down some funny business.
8:41 Safety audit committee to LVEA for tour
8:51 Jeff B to LVEA to shutdown dust monitors (2,3,4,5,13)
8:53 Filiberto to MidY on AOS parts hunt
9:31 Richard to MidY
9:34 Safety audit committee tour complete
9:36 Jeff B done with dust monitor work
9:41 Greg to EY
9:51 Christina to EX and EY for magnetometer install
10:00 Kyle to soft-close GV7
10:05 Richard back from MY
11:00 Betsy to west bay on laser barrier hunt
12:00 Greg transitioning EY to laser hazard
12:06 Jim B to LVEA with security review tour
12:33 Jim B out of LVEA
12:44 Greg Mendell to roof with security review committee
12:57 Karen to EY
12:58 Jim to ITMx investigating issues with ISI
13:11 Karen done at EY
13:49 Gerardo to EX, replacing valve on purge air system
13:53 Bubba to LVEA to crane zamboni out
14:55 Jason realigned ITMy OpLev
15:10 Gerardo back from EX
15:10 Gerardo to LVEA west bay CR to FC ITM optic for charging measurements
Soft-closed GV7 (this valve will be opened again in a few weeks and we seek to minimize hard closures) -> Added scroll backing pumps to YBM and XBM turbos (in parallel to QDP80 pumps and independently isolatable) -> Valved-in aux. pump carts to HAM5/6 and HAM4 annulus' -> Valved-in YBM and XBM turbos backed only by scroll pumps -> Shut down QDP80s -> Valved out IP1, IP2 and IP6 The pressure at the X-end is OK to leave open to BT (saves a cycle of GV20)
Removed and replaced the check valve for compressor No. 4.
Also, about 1 month ago the relief valve for this compressor was replaced.
I've been digging into why my new loops for ITMX won't run and I've found I have a bad CPS (St1-H3). Not really terrible, and probably not responsible for my difficulties. See plot, which was made with the H3 and V3 in-air cables switched, but the original way looked the same, indicating a likely bad board, not the cabling.
Now that most of the installation work is complete and the over chamber cleanrooms are turned off, I have shutdown and removed the dust monitors from the HAM2, HAM3, HAM4, HAM5, and the X-Arm spool areas. We are currently monitoring the general air in the LVEA via dust monitors in the Beer Garden and the HAM6 end of the tube. While removing the above mentioned dust monitors I found several that had been unplugged from A/C power. The extension cords unplugged from these dust monitors had other things plugged into them. These dust monitors were plugged into A/C power because their batteries are failing (and cannot be replaced). By unplugging these dust monitors they were taken off line and not monitoring the cleanroom environment. Please do not unplug dust monitors from A/C power without talking to Jeff B. first.
model restarts logged for Wed 03/Sep/2014
2014_09_03 09:03 h1fw1
unexpected restart of h1fw1
Attached is a plot of the reference cavity transmission and pre-modecleaner reflection signals. Both have drifted slightly since the re-alignment on Tuesday.
Now that the ISS is back working after re-aligning into the pre-modecleaner, it makes sense to do a measurement. The measurement looks better than the one performed on August 12th in that the hump out beyond 1 kHz is cleaner now than before. The low frequency relative power noise appears to be a little better from 1-3 Hz. One difference to note is that the diffracted light level is ~2% higher than before. Also the first loop gain is lower at 8 dB versus 17 dB (old). With the improved alignment, the power on the photodetector is ~10V versus ~8.6V.
Jameson, Nicolas
We spent some time today porting the L1 OMC Autolocker/Guardian to H1.
We changed the way it handles grabbing lock, it used to sweep the PZT with the loop open looking for a 00 resonance, we've changed it to sweep with the loop turned on, waiting for the transmission to trigger the loop. This makes the locking quite robust and fast.
We are currently skipping the fancy GigE camera 00 mode identifier, but this should be re-commissioned and used. Also, we can't test the violin mode detection because we don't have the full IFO.
So right now it is basically an automated way to get the single bounce beam resonating with the dither alignment loops on (or lower states if those are desired).
Kiwamu, Nic, Jamie, Lisa After peeking down the X arm and fixing the ITMX isolation loops , the plan for tonight was: 1) re-establish the corner alignment after the X arm was locked and aligned today; 2) make sure that with this new alignment we have a POP beam; 3) re-lock PRMI on the carrier; 4) evaluate effectiveness of new BS baffles; 5) lock DRMI on sidebands Status ------ 1) DONE 2) DONE 3) Not quite - With the new alignment, locking the PRMI on carrier was not as easy as it was last Friday. The power in POP is higher than before and POPAIR_B, currently used for PRCL normalization, was saturating (see plot attached, every time POP AIR saturates there is a glitch in the control signals). Kiwamu reduced the BBPD electronic gain by a factor of 10, but then the normalized signal became too noisy. So the current plan is to bring back to life the POPAIR_A diode, which, according to Kiwamu, is currently blocked by a camera. Notable event: * 6.15 UTC, Sep 4 - Earthquake - SEI and SUS didn't trip, but the corner optics moved like crazy for ~20 minutes
Sheila, Kiwamu,
We locked the infrared main laser to the X arm this evening in order to improve the alignment of the input poointing.
Here are some settings we used for future reference:
Jamie, Kiwamu
We tried engaging isolation loops in the stage 1 of ITMX ISI, but kept failing for some reason. In both robust- and high- isolation cases, we saw L4Cs ringing up at 10 Hz at the end of the auto-isolation processes and tripping the watchdog.
Checking each step of the guardian isolation process, we finally found that the instability was due to the X isolation loop. In particular, every time when it engages the 3rd boost, this makes the system unstable. Even though, we don't really know what the loop shape is for the X direction, we tried different gains in order to find a OK-stable gain. We ended up with a gain factor of 2. This seems to give us a OK-ish ISI performance in ITMX ISI. We did not try engaging the stage 2 isolation loops.
At the request of local commissioners, I have modified the SUS guardian code to go back to handling the setting of alignment offset values for the ALIGNED state, and have re-introduced the MISALIGNED state which sets the alignment offset to saved misaligned values. This all was originally in the SUS guardian code, but was removed at LLO due to precieved problems with the SUS guardians handling the offsets. The LHO commissioners, on the other hand, prefer the SUS guardians to have separate ALIGNED and MISALIGNED states.
SUS guardians have not been restarted yet. Only SR2 for testing. We're waiting until after the arm alignment tests are done.
NOTE: ALIGNED and MISALIGNED offset values MUST BE SAVED in order for the SUS guardians to restore to them! This is the big change by going back to this configuration. When the SUS guardians were not touching the offsets, there was no worry that they would accidentally be reset. Now that they are being set by guardian, we have to remember to always save the offsets appropriately after tweaking them. Forgetting to save them could result in the current alignment being lost if the suspension trips or the alignment state is cycled.
As a bonus, the SUS guardians will use the notification USERMSG to notify you if the alignment has been changed and not saved.
Here's the current SUS state graph:
This is all just a stop-gap until we get a better comprehensive solution to the alignment offset problem. This will likely be discussed in the next SYS meeting, on 9/9/2014.
All the SUS guardians have now been restarted
When Kiwamu locked PR-X (CH16), POP_A (CH1-7) saw some decent beam, about right in PIT and off in YAW.
POP_B (CH9-15) also saw something, it's not clear if it was the real beam or some ghost, the power is about a factor of 10 smaller than POP_A, and mostly in seg1 and 2.
Anyway, the important thing is that the POP_A already see the beam and POP_B is close.
Don't use pico to center these, though, as POP sled might be a good initial alignment reference.
We should first align the IFO to the POP sled and see if it makes things better. POP sled was aligned perfectly in the last days of HIFO-X/Y. Though a beam splitter was inserted after the vent, the insertion procedure was written such that the sled centering is preserved.
The above entry is simply wrong.
When I centered these QPDs before vent, with 45dB whitening gain and with a straight-shot beam, DC sum of QPDA was something like 56 counts with a bogus calibration factor of 0.0056 that is in QPD segment filters (screen shot from before the vent, May 30).
Since then we installed 90:10 to attenuate the light by a factor of 10, but increased the PSL power by a factor of 5, so when the beam hits the QPD I expect something like 28 counts, but we got 0.4 at most, it's a factor of 70 smaller than expected.