Michael, Krishna

Today, we changed some parameters which correct for pixel-level non-linearities in the CCD. This improved the noise in the BRS-2 output.

We also improved several error-handling features of the code and created the Status signal (the 4th channel going in to SEI), which is set to have the following states: Good (5V), Damping On (2V) and Bad (0V). In the near future, there will be several other more detailed states on the BRS model screen indicating the specific problem, if it is in a bad state, which will help debug the problem. Detailed documentation on this will be prepared soon. We also filled out some of the filter banks for processing the BRS-2 data and for tilt-subtraction. More on that in the future.

The first attachment shows the BRS-2-rX signal in comparison to the STS2-Y seismometer on the ground close to it. The data is converted in to displacement units and was measured with low wind speeds on the order of 2-3 mph. The next page shows the coherence between the sensors. The instrument is still drifting and settling, so the low-frequency noise will improve over time.

We noticed that there may have been some excess noise in BRS-2, especially at higher frequencies, due to aliasing from the high frequency spikes (30, 80 Hz). Therefore we lowered the software low-pass corner frequency from ~50 Hz to 10 Hz. This does introduce phase-loss at ~few Hz but since this sensor is primarily used at ~10-500 mHz, this shouldn't be a problem.

The second attachment shows the output of BRS-2 after the improved low-pass.

6:00 pm reading (torr) 

PT243 - 1.11 x 10-9 
PT244 - 1.45 x 10-9 
PT210 - 1.45 x 10-9

We have an oscillation in H1 that has been with us for a long time, is not understood, and can be mitigated by moving alignment offsets, and gets worse at high power.  All the information in this alog is elsewhere in the log, this is just a summary.

For about 6 months we didn't change our soft loop offsets because when we did we would get the oscillation, this is how we stayed stable through O1.  The main symptom is that the pitch optical levers move at frequencies around 0.45 Hz, all in phase with each other, and if you look at the relative sign of the optical levers it looks like CSOFT motion. the POP and arm transmitted powers also oscillate. Now that our soft loops are working again, we are probably in a position to again tune the soft loop offsets to be stable at 20 Watts, but it seems like this won't be a great solution as we try to increase the power even further. 

There have been many alogs about this, but I wanted to summarize some of the recent things we have looked at. 

It seems like the torque that moves the test masses isn't coming from any of the arm ASC loops, or the optical lever damping.  The first screenshot shows this, this is from Tuesday night when we powered up several times in slightly different configurations and repeatedly saw the same size of oscillation.    The solid lines here show what was our normal configuration before Tuesday, with ITM optical lever damping on and ETM optical lever damping off.  The dashed lines show the test configuration, where we added notches to the soft loops that reduce the actuation by about a factor of 100 at the oscillation frequency, and lowered the CHARD gains by a factor of 10. You can see that in the test configuration we also have about 5 and a half times less DHARD drive in the test configuration than in the normal one.  Since all of these ASC drives are smaller in the test configuration but the oscillation is about the same, it seems like the force that moves the test masses must not be from these control signals. 

It seems like the fluctuating radiation pressure due to changes in circulating power alone can't provide enough torque.

In the attached matlab script I estimated the miscentering we would need on each optic so that the approx 900 W changes in circulating power we see during the oscillation could provide the radiation pressure torque.  These are way too large, ranging from 8-33 cm on the different optics.  As a sanity check I also assumed that the alignment shift we see powering up before the soft loops get a changce to correct is due to radiation pressure (which it may not be).  From that I estimate miscenterings ranging from 0.5-3 cm. I used the moment of interias from Evan Hall's alog , which he tells me are slightly wrong but not enough to matter.

The oscillation frequency does seem to depend on circulating power

The evidence for this may be a little shaky since it is hard to get enough cycles of the oscillation to get a spectrum with nice resolution, but the second attached screen shot shows a spectrum of ETMX optical lever pit for 3 different circulating powers.  These circulating powers are based on Dan Hoak's calibration and the TR XB QPD.  The frequency of the lower two powers is the same within the resolution of my spectra. This may not hang together perfectly because I have included a little bit of time when we were powering up or down in the spectrum.

Other ideas?

We have also tried putting a resonant gain the DARM loop(no impact), changing A2L feedforward (no impact), and centering on the ETMs (improvement).  One possible test we could try to understand this better would be to drive the laser intensity and see if we can produce angular motion.  

State of H1: locking and making it to DC Readout

Site Activities:

• John and Chandra to LVEA vertex - vacuum
• Bubba to MX, MY, EY chiller yard - vent prep and chiller work
• Richard and Ed - EY and EX - electronics survey
• Fil - LVEA - vent prep
• Betsy and Travis - OSB optics lab
• Karen and Chris to MY and MX - cleaning

H1 Activities:

• TJ worked on new Initial Alignment Guardian code in the morning
• Initial alignment was done
• Locking went well with a pause in DRMI and Engage ASC part2
• At the end of the shift, H1 was in DC readout and in the hands of the Commissioners

Possible Activities for tomorrow:

• Filiberto - End Station - work on hardware for parametric instability - will effect QPDs, so will prevent locking
• Vent prep continues

4pm readings (Torr)

PT-243: 1.08e-9
PT-244: 1.42e-9
PT-210: 1.42e-9

John, Kyle, Chandra

Testing a three day cycle on CP3 overfill. We will *not* fill CP3 today and instead monitor pressures overnight, and fill tomorrow, Friday. 

Chandra time (local): 16:00, 20:00, 00:00, 4:00
Kyle time (local):  18:00, 22:00, 2:00, 6:00

The HAM ISI model updates Tuesday, alog 26321, allow the suspension motion calculation to be done by the ISI.  The filters and matrices to convert from ISI GS13 cartesian basis to the optic euler basis are now filled.

The BSC ISIs were updated for this earlier in the month.  Alogs: original model updates-25913, ISI vs SUS calibration filter- 25993, mods for multi sus plarforms- 26117, library part cleanup/corrections- 26128, BSC filters & matrices populated- 26132, svn commits- 26143.

DetChar can now start pointing to these ISI computations.  Look at channels: H1:ISI-{isi platform}_SUSPOINT_{suspension}_EUL_{euler dof}MON.

euler dof is L, T, V, R, P, orY

isi platform is HAM2, 3,..6, ETMY, ETMX,..,BS

suspensions available are ETMY, TMSY, ETMX, TMSX, ITMY, ITMX, BS, MC1, MC2, MC3, PRM, PR2, PR3, IM1, IM2, IM3, IM4, SRM, SR2, SR3, OMC.  Of course you have to get the suspension on the correct isi platform.

Attached is a snapshot of the medms: the GS13 filter bank and available suspension calcs are accessed from the ISI Chamber overview; the transformation matrices are accessed from the calc screen.

[Fil, Jenne]

We've measured the distances from each Newtonian array sensor location (marked on the LVEA floor with green electrical tape) to the racks we'll use for signal concentration, so that we can order our cables soon. 

The new Met One dust monitors have been installed in:
The LVEA at HAM6 and in the Beer Garden, in the Optics Lab,End-X, and End-Y. They are and sampling for 60 seconds every 10 minutes. 

There are still a few minor issues being resolved, which do not effect the operation of the units or the particle counts. 

Attached is a quick operators guide to the new monitor. Fuller documentation will follow.    

John, Chandra

Pressures at IPs IP-7 & IP-8 on diagonal were ~10 Torr. Pumped out volumes with aux cart and opened gate valves to main diagonal volume. Connected HV cables, but did not activate IPs yet. Current diagonal pressure = 7e-7 Torr.

IP-8 still needs cable strain relief.

h1fw1 froze up last night at 22:41 PDT with a kernel panic. It was restarted at 10:16 PDT today (I pressed the front panel reset button)

last part of the console error message was:

VFS: Close: file count is 0

Kernel panic - not syncing: CRED: put_cred_rcu() sees xxxxxxxxxxxxxx with usage -1

where xxxxxx is a large hex number.

We've had much more success tonight with the non-broken Xarm Trans QPD.  We once again re-centered the spots on the ETMs, although they didn't need much moving.  We are able to sit at 10W and 12W just fine now.  Now, we're running into regular ol' loop oscillations, so we've been measuring loops at different powers, and trying to re-tune them. 

CHARD Y seemed the most egregious, so we created a new control and boost filter combo, which live in FMs 4 and 5.  Unfortunately, these filters are totally unuseable at 2W, although they improve our stability at 10W, so right now the guardian still only engages the old loop shape filters.  We'll have to re-think the 2W filter situation to make sure we can transition between these filters.  Right now, we were by-hand turning off the CHARDY loop, changing the filters, then re-engaging the loop.  Attached is an open loop gain for the new loop.

PRC2 pitch we've decided is kind of okay if we use a factor of 2 less gain.

Now, we're seeing oscillations that also show up in AS 90, so we suspect either the MICH or SRC angular loops.  Unfortunately, there's something going on with NDS/the lockloss plotter/something, such that I can't get data from the last ~5 locklosses.  The ones before that, I can still get and plot, but it can't find data for the last several even if it's been an hour since that lockloss. 

So, next up:  Measure the MICH and SRC loops at 10W to see if they're close to unstable.  Measure again at 15W, and then think about going from there.

Introducing the new LASER_PWR Guardian node! Use it to change the power by selecting one of the three requestable powers (2W, 10W, 22W) or open the "ALL" screen to select any 'POWER_#W'. I attached a shot of the graph if you're curious. This node is nominally manged by ISC_LOCK and then ALIGN_IFO during initial alignment (though this has created some usermsg issues that I am trying to work around, more on that later).

I have also changed around some of the management for initial alignment. If the user wants to run initial alignment:

1. From READY in ISC_LOCK, go to manual and select INITIAL_ALIGNMENT

2. Wait for ALIGN_IFO to run through its DOWN state. This will temporarily take control of the ALS's, LASER_PWR, and IMC_LOCK nodes.

3. Run the green alignment from ALIGN_IFO instead of each of the ALS nodes. Offload the green WFS at the same ti.

4. Continue as usual, during SRC the LASER_PWR node will bring the power up to 10W and then back down after.

6. When done with initial alignment, make sure to go to INIT on ISC_LOCK to take back control of the nodes. then continue as usual.

I added the LASER_PWR, as well as the SR3_CAGE_SERVO nodes to the Guardian Overview screen (shot attached).

I also slightly changed the ISC_GUARDIANS medm to show who the managers are of each node and placed the new node on the bottom. (shot also attached).

As I mentioned above, there are some user messages that will pop up on ALIGN_IFO and ISC_LOCK about the nodes being stolen by one another. This isn't a big deal for ISC_LOCK to report this whie we are in the middle of initial alignment, but it isn't good for ALIGN_IFO to be continuously notifying during normal locking. I have something that I want to try next opportunity I get, hopefully tomorrow. And if that doesn't work, Jamie seemed to have an idea of how to solve these types of situations that will be in the next Guardian release. Until then we can not manage the nodes during initial alignment just as before.

(Tasked by Aidan)

We were curious of how the HWS sled power decrease over time so we know when to swap them out. Below I've attached plots of HWSX and HWSY sled power (corrected for gains) and input current. The start time is when we replaced the SLED (April 26, 2015 for YSLED and March 1, 2016 for XSLED). I only plotted the time when the SLEDs were turned on (displays in number of days). XSLED shows deteroration of ~2% per day and YSLED shows deterioration of ~1% per day (given 7mW to be 100%, I don't think we are shooting 7mW out though but the trend looks reasonable). YSLED power decreased slightly faster when the input current = 94 mA.

XSLED data can be found here and YSLED data can be found here. The column goes Time|Power (mW)|Current(mA). The script to fetch and plot data can be found in the same directory.

The fast decay in the beginning is a known problem.

J. Kissel, B. Weaver, H. Radkins, D. Barker, J. Batch

Here's a list of all of the upgrades we were involved in today. There will be more details of the upgrade, more debugging, associated MEDM screen changes, svn commits, and other clean up tomorrow as we continue to explore what we've installed and debug. Bear with us, and thanks for your patience.

1) Fixed UIM coil driver path's automatic compensation bug by updating CD_STATE_MACHINE.c. See Int. Issue 1178.
2) Installed ISI GS13's projection to SUSPOINT Euler basis projection into the SEI models. See ECR E1600028.
3) Sent the Euler Basis Longitudinal DOF for each SUS involved in a cavity over various IPC (PCIE and RFM) and models (ISI, End-station PEM, H1OAF) to be collected in OAF. See ECR E1600028.
8) Removed the excess RFM channels from End-Station ALS models (noteably *not* the excess channels in the ISC models). This made room for 3). See LHO aLOG 25216
4) Added various rotational sensor correction paths to the BSC ISIs (GND BRS to ST1, and ST1 to ST2). (Prototyping, this stuff, no ECRs just yet)
5) Removed the L4C sensor correction path. See SEI aLOG 666
6) Added new infrastructure for the EY BRS. (Most Copied from EX, covered by ECR E1500246)
7) Reverted the BSC SUS's coil driver monitors to store the NOISEMON in the frames (and pushed the FASTIMON to the commissioning frames). Also, we put filter modules in front of the NOISEMONs (like was done for the FASTIMONs the last time we touched this) in case we ever wish to calibrate them. See ECR E1600033 and LHO aLOG 26313

Because we haven't built MEDM screens and actually *used* any of these paths yet, there's still potential for bugs and we haven't explored and/or fixed all of the collateral damage. Stay tuned as we continue to work on all of these updates tomorrow.