SEI - Data mining;  HEPI pump investigation ongoing; performance measurements with DRMI locked.

SUS - Jamie will be coming to update Guardian infrastructure and work on SDF; TJ adding HAMAUX and TT to Guradian Overview; Thomas working on Drift Monitor

ISC/Commish - 10:00AM commissioning schedule; moving forward in a positive direction.

3IFO - BSC5 testing done; still has CPS issue; Will be moving from staging building into LVEA (TBA); 1 of 4 dessicant cabinets have arrivedand going into highbay.

Daniel, Filiburto, Dave:

The h1tcscs ADC signals were discovered today to have changed around 1pm Tuesday 27 Jan PST. We found that the DC power strip feeding the non-PEM AA and the 16bit DAC AI chassis for h1oaf0 to be powered down. We reconnected the DC power strip's cable and these systems are now operational.

K. Venkateswara

BRS was turned off just before the vent at EX (15711). I restarted the code in the BRS laptop and noticed that the DC position of the balance had changed owing to the 2 deg C temperature change in the XVEA. The balance is just out of the nominal range but still working correctly, as far as I can tell. If it proves to be noisier, I may adjust the set point in hardware on Tuesday, since it will take a couple of hours to get right. For now, I adjusted the DC offset in the code appropriately and it all seems to be working as usual (see image). The wind-speed is barely a few mph.

The sensor correction is now using the tilt-subtracted ground super-sensor. This should make no difference to the platform, at the moment, as the sensor correction is using the "0.43-Hz only" filter.

Rana and Travis updated a newer version of the drift monitor and added it to the sitemap at LHO, and I made some further changes:

I have fixed bugs in the MEDM screen (/opt/rtcds/userapps/release/sus/common/medm/SUS_DRIFT_MONITOR.adl), and now the buttons for updating individual suspensions work again. LLO, if you svn update the MEDM screen, please be aware that instances of "H1" in the code will need to be changed to "L1" to prevent horrible, epic failure. 

I've added a set of dictionaries to the drift monitor update script (/opt/rtcds/userapps/release/sus/common/script/driftmon_update.py) that allow for setting fixed threshold values by editing the code itself (example below). The current values are somewhat arbitrary guesses, so they require tuning. The changes have been committed to svn, and the code should be LLO-friendly without any modification. 

Example: To set fixed thresholds, open driftmon_update.py, and scroll down until you find the following (at line 115 at the time of this post):

########## TUNE THRESHOLDS HERE ###########
# yellow thresholds = mean +- yellow_factor * BOUND value
# red thresholds = mean +- red_factor * BOUND value


yellow_factor = 1
red_factor = 2

BOUND_MC1 = {'P' : 50, 'V' : 10, 'Y' : 15}
BOUND_MC2 = {'P' : 50, 'V' : 10, 'Y' : 5}
BOUND_MC3 = {'P' : 50, 'V' : 15 , 'Y' : 20}
.
.
.
and so on.... and edit the values corresponding to the suspensions and degrees of freedom you wish you tune. For instance, with the code above, if the script updates MC1 pitch and sets, say, 10uRad as the nominal value, then the code above will make the yellow alarm trip at <-40uRad and >60uRad (mean +- 50uRad), and the red alarm trip at <-90uRad and >110uRad (mean +- 2*50uRad).

 

I updated the GUARD_OVERVIEW and the IM/TT medm screens to contain micro/mini Guardians for IM1, IM2, IM3, IM4, RM1, RM2, OM1, OM2, OM3. The scripts were already made available by Stuart Aston and Jameson Rollins at LLO see https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=15772 and also https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=15585. The Guardian Nodes were not yet created though so I had to create those and figure out that they also had to be started.

Currently RM1, RM2, OM1, OM2, OM3 do not have any offset.snap files saved to them in userapps/sus/h1/burtfiles/ (hence the red border on the Guardian Minis in the overview screen shot).

Attached are the before and after of the GUARD_OVERVIEW.adl screens along with the new HAUX and one of the new HSSS IM screens.

ISS arrays are ready to be containerized. The bases for the cans needed a slight modification so they are currently at a machine shop. Once they are back and out of the air bake, work can continue for storage and shipping. I have attached a brief report with pictures for the next soul that works on this so things can be located easily.

Also attached is a spreadsheet of which items are associated with which ISS and a report of progress.

There is a problem with the signal from the ITMY OSEM, it was verry noisy durring the lock losses last night and it is still noisy now, this seems to be always this way. 

The attached screen shots show the signals up the chain on each quad.

Dan, Richard, Daniel, Rich

We loaded the updated Beckhoff code today to enable the full functionality of the newly installed Fast Shutter Driver.  The system is now operating properly.  There are a couple of things worthy of note:

1.  The ISI watchdogs trip in HAM6 whenever the fast shutter fires at full speed AND whenever the fast shutter is actuated in the slow mode either up or down.  Reason for this sensitivity as compared to the apparently less sensitive response at LLO is not yet understood.
2.  If the high voltage is not enabled (HV ready) on the front panel of the shutter driver, the shutter Beckhoff code defaults to a blocking shutter state (closed) and will not allow you to unblock the shutter.  This is a code feature, and is not actually precluded in hardware.
3.  We verified that the logic is correct on all signals including: shutter controller output, LV OMC Length shutter input, Fast Shutter input, all readbacks.  All are correct.

When I came in this morning, DRMI was still locked and I had the place to myself, so I decided to try turning on the BSC RZ loops with a high blend. I was using SRCL, PRCL and MICH as witnesses. I was mostly able to turn the loops on without losing lock if I turned the loops on slowly, but the BS broke DRMI and Ed has been having a hard time getting DRMI back. I tried ITMX first, then added ITMY, then tried the BS. Attached plots show the cavity spectra for the baseline (in red), ITMX  RZ on(blue) and both ITM's RZ on in green. Not much change at low frequency, although SRCL and PRCL both improve some. But between 1 and 4 hz the RZ loops make things worse. I've returned the BSCs to their standard configuration.

model restarts logged for Thu 29/Jan/2015
2015_01_29 01:42 h1fw0
2015_01_29 05:43 h1fw0

both unexpected restarts. Conlog frequently changing channels report attached.

Reconfigured and restarted the corner EtherCAT system to link the slow channels for the fast shutter.

The attached plot shows the uptime of the 3 EtherCAT chassis. The y-axis shows the elapsed time, since the last restart/reboot. This can be due to a hardware problem, or just a normal software update. The record starts around 11/11. For the corner there was a restart on 12/9 and then it was up for more than 50 days. (The fact that the trace wraps around from +24 days to -24 days is due to a programming error.) EY also looks good with one additional restart around January 9th. However, EX clearly has a problem with a forced reboot every other Tuesday.

Evan, Alexa, Elli, Kiwamu, Rana, Keita, Sheila

We are getting closer.

Today it has been much more reliable and robust for us to get to the state where DARM is controlled on RF.  Differences from yesterday that have probably helped with this:

• We have added a new state to the ALS ARM guardian that puts the tidal for the X arm in the transition state once ALS DIFF is locked. 
• We realized with remote help from jamie, that we cannot instanstiate a cds utils servo until we are ready to start using it. As soon as we intsansitate it, it will start to integrate.  We found this problem using the lock loss tool, and have fixed the ISC_LOCK guardian to do this.
• We are carefully adjusting the ETM alignment by hand in the CHECK_IR state.
• We have addded a 200 Hz low pass to DARM, and we are turning off the 80 Hz low pass after the transition to RF DARM, and removing the 60Hz notch. 

The ISC_LOCK guardian takes us to an offset in TR CARM of 20.  There we have been trying to transition to REFL9 I/TRY. We lowered the whitening gain of REFL9I which was saturating the ADC, we now have 0dB whitening gain and no whitening filters.  The steps that we have been doing that are not yet in guardian are:

• move CARM TR offset to -25, with ramp time of tens of seconds.  At about 2/3 of the way through this ramp we reduced the DARM gain (in the input matrix) from 30 to 20.  
• We have often turned of the DHARD WFS at this point, although its not clear that was necessary. 
• when we arrive at -25, we adjust the offset in REFL_TR to match the input. 
• We add TR_REFL to the input matrix with a gain of -20, and ramp TR CARM down to  0.5.  We have been able to go to TR CARM gains of 0.25 stably. 
• We noticed at this point that TR CARM still seems to be in charge at DC, so we added a high pass in that path with a zero at 0.1 HZ and a pole at 1 Hz.  
• After engaging the high pass we were able to reduce the offset in TR REFL to -6 or so, and to reduce the gain the TR CARM path further. 

At this point, some kind of oscillation has been starting which eventually blows the lock.  Some example times are 2:47:06 UTC and 3:13:01 UTC.  The attached striptool shows both of these events.  You can see the oscillation in POP18, AS 90, AS DC, and REFL DC.  As I've been writing I've been letting the guardian try to lock on its own, it has lost the lock twice in the REDUCE_CARM_OFFSET_MORE state, I think this is because the DIFF offset wasn't adjusted well.  I've extended the time that the servo runs before this step.  

I've left DRMI locked, with the arms misaligned for seismic people.  

 We have noticed that it is sometimes taking a verry long time for guardian to calculate paths (the ISC_LOCK guardian).  

We also just saw something more strange.  It seems that the ALS COMM guardian, which was managed by the ISC_LOCK guardian, became executed, although we are pretty sure no one in the control room did this. screen shot of the log is attached. 

After looking at all the L4C plots, Krishna suggested we look at the IPS thinking that with the loops closed by the HEPI Platform servo which has lots of gain, it should suppress the IPS signal and the L4C coherence we are seeing was from something else...like the fluid moving the piping...  Seem reasonable although really?

However, see attached:  Same times as the L4C coherence I posted Tuesday.  I show HAM5 at the local position sensor (IPS.)   It is very clear the Horizontal IPS have great coherence from 0.5 down to .02 hz when the pressure sensor loop is closed.  The Vertical IPS coherence isn't nearly as strong but certainly present.  The output drive to the HAM5 Actuators is very small both horizontal and vertical.

I attach too the coherences from the End Stations.  The second attachment has ETMX in the left plots and the ETMY in the right plots.  Both pressure servo loops are closed but ETMX pressure signals do seem to be quieter (although not as quiet as I've seen the corner station's back before December) and the ETMX is servoing on the direct output pressure at the Pump Station.  Whereas, at the ETMY, we are servoing on the actual remote pressures at the BSC10 differenced in the epics database.  The signals at ETMY have always been very noisy and so when I switched ETMY to the differential mode, I added serious smoothing to the signals before differencing.

Looking at the the comparison of the ETMs there are distinctions but what causes what them is not clear.  The quieter EndX is evident in the amplitude and dispite the smoothing, the EndY has a much sharper and higher amplitude peak at 150mhz.  Don't ask me what's happening at 3.5hz...

The lower plots at interesting in that unlike at HAM5, there is no coherence with the vertical IPS on either platform but the horizontals are very coherent.  This coherence at ETMX is narrower in band though maybe somewhat more like the band at HAM5...related to the quieter pressure signal at ETMX or due the ETMY servoing on the difference rather than the direct supply pressure or the smoothing...?

Summary:

I was able to close the ISS Second Loop few times this morning. The loop performance was on-par with what we achieved when we locked it last time. The picomotor closed to the ISS PD array was also moved to optimize the light on the ISS PDs and the QPD

Details:

Noticing that the ISS QPD pitch and yaw were off, I moved the picomotor closer to the ISS array to optimize the light on the PDs and the QPD. This work improved the light on half of the PDs by about 10-20% . This also improved the beam position on the QPD. Before and after readings are listed:

I was able to close the loop without kicking the IMC out of lock. This was not robust and the previously used script wouldnot work because the second loop output fluctuation was much bigger than that we used as threshold in the script. Rather changing the script, I would want to investigate why we are not able to obtain the same robustness that we previously had. The loop performance is on par with what we have achieved in the past. With the loop closed and boost and integrator on, RIN was about 2E-8/sqrt(Hz) at 10 Hz . The attached plot shows the loop performance at different configurations.

Kiwamu, Elli, Alexa, Evan, Rana, Daniel, Sheila

Today we were able to reach CARM offsets around 30 pm.  

We transitioned DARM to AS45Q, at a CARM offset where sqrt(TRX+TRY) was -7, we then normalized the signal by sqrt(TRX) (with a factor of 0.23).  One important step in getting there was to implement the ezca servo that adjusts the ALS DIFF offset to bring AS45Q into the linear range.  We are now using that both at a CARM offset of 1 (in SQRT TRX+TRY), and after we transition to the QPDs.  We then change the DARM loww pass filter from a 33Hz low pass to a 80 Hz low pass, to get better phase margin since we are no longer saturating the ESD with ALS noise.  We did this transition several times sucessfully.  As Rana mentioned in alog 16334, we installed an ND1 filter on ASAIR A.  Since this we haven't transitioned to RF DARM again (for reasons that seem to be unrelated to the ND filter), so we will need to check the gain before we transition again. 

After making this transition, Elli, Kiwamu and Rana worked on the DHARD WFS, which we turned on to reduce the fuctuations in AS DC.  This allowed us to go to CARM offsets -25 in sqrt(TRX+TRY), which is about half of the total power we expect in the arms.  If you assume that the recyling gain is 30 (we don't really know) it is something like 30 pm.  In Refl DC we saw the power drop by about 20%.  We saw that the linearized REFL 9 I signal had turned over, and that without linearization the signal had reached the peak.  We made a few attempts to transition, and we were able to turn down the gain of the TR CARM signal to 50% of the nominal and turn the REFL 9 signal to what we think the nominal gain should be (-100 in the input matrix).  We lost the lock when we turned off the TR CARM signal.  Our next plan was to leave the TR CARM engaged with reduced gain, and keep reducing the CARM offset.  

However, we have been having a hard time locking in the last few hours.  We think that it might help to try transitioning to DARM to RF a little sooner, so that we could use WFS.  

The sequence that was working earlier this afternoon is in guardian up to the RF DARM transition, although this might need to be re-worked.  We have added but not tested a state for the DHARD WFS. 

Attached is a screenshot of our striptool durring the sequence, which was all handled by the guardian this time.