model restarts logged for Thu 02/Oct/2014
2014_10_02 09:29 h1isibs
2014_10_02 09:33 h1hpiitmx
2014_10_02 09:33 h1hpiitmy
2014_10_02 09:35 h1isiitmy
2014_10_02 09:36 h1isiitmx
2014_10_02 09:42 h1hpibs
2014_10_02 09:44 h1isibs
2014_10_02 09:46 h1hpibs
2014_10_02 10:03 h1hpiham6
2014_10_02 10:03 h1isiham6
2014_10_02 10:10 h1hpiham1
2014_10_02 10:14 h1hpiham5
2014_10_02 10:14 h1isiham5
2014_10_02 10:16 h1hpiham2
2014_10_02 10:18 h1isiham2
2014_10_02 10:20 h1hpiham4
2014_10_02 10:20 h1isiham4
2014_10_02 10:27 h1isiham3
2014_10_02 10:29 h1hpiham3
2014_10_02 10:43 h1dc0
2014_10_02 10:45 h1broadcast0
2014_10_02 10:45 h1fw0
2014_10_02 10:45 h1fw1
2014_10_02 10:45 h1nds0
2014_10_02 10:45 h1nds1
2014_10_02 10:48 h1hpiham1
2014_10_02 11:53 h1ioppemmy
2014_10_02 11:53 h1pemmy
2014_10_02 11:53 h1sushtts
2014_10_02 16:38 h1pslfss
2014_10_02 16:55 h1psliss
2014_10_02 16:59 h1broadcast0
2014_10_02 16:59 h1dc0
2014_10_02 16:59 h1fw0
2014_10_02 16:59 h1fw1
2014_10_02 16:59 h1nds0
2014_10_02 16:59 h1nds1
2014_10_02 17:02 h1psliss

no unexpected restarts. Seismic and PSL model changes, with associated DAQ restarts. Recovery of h1pemmy after IO Chassis power supply swap.

SEI Status:

- Motion measured on ITMY (ISI and optical lever) using the LLO configuration was good again last night, so we duplicated this configuration to all the BSC-ISI units

- As we re-started the units, Jim found an oscilation in ITMX. He fixed it. It is not correlated with the new blend configuration. More details on that to follow.

- Hugh worked on the Guardian. It is now fully updated to account for the new config (decribed below). Thanks a lot to Jamie for the remote support. The Guardian is now fully updated and running.

- All the units are up and running. We leave the sensor correction OFF for the night.

Configuration in use:

- LLO blends installed everywhere (excact same filters copied/pasted from the filter text file)

- Stage 1 RZ off on all units

- Only Stage 1 X and Y isolated on Stage 2 (all units except the BS)

- Stage 2 damped only on the BS

- Sensor correction is off for the night

• DRMI locks at 10 watts using refl air.  (input matrix shown in the screen shot).
• we have used OM1 for a DC centering servo for the AS WFS, and we have phased them using the free swinging michelson. 

Other than this we have been disrupted by ITMX this evening. 

Jenne, Alexa, Sheila

Since the asc had IPC senders for signals to OM1 and OM2, but the only revciever in the h1sushtts model were from the OMC model, we added new recievers.  Anamaria told us where to find the livingston model, and confirmed that it was up to date, so we copied what they had done there, just summing the inputs from the OMC model and ASC. 

Complied, installed, seems to be working, and we can now use the DC signals from our AS WFS for a centering servo.

Peter K, Gabriele

In brief, we finally managed to close the ISS second loop. The attached plot compares the intensity noise measured on the second loop photodiodes in different configurations: second loop open (green and maroon), loop closed withe the additional integrator (red and blue), loop closed with the additional boost (cyan and magenta).

Clearly, the boost doesn't do a very good job. With the integrator on, we get a loop bandwidth of the order of 200 Hz, and a gain at 10 Hz of something like 10-15.  We don't have enough gain to cope with our present large power noise after the IMC.

Procedure to engage the second ISS loop

1. All switches should be low (H1:PSL-ISS_SECONDLOOP_CLOSED, H1:PSL-ISS_SECONDLOOP_SERVO_ON, H1:PSL-ISS_SECONDLOOP_BOOST_ON, H1:PSL-ISS_SECONDLOOP_INT_ON)
2. Move the second loop gain to the minimum (H1:PSL-ISS_SECONDLOOP_GAIN to 0)
3. Switch on the second loop (H1:PSL-ISS_SECONDLOOP_SERVO_ON to high)
4. Adjust the reference input H1:PSL-ISS_SECONDLOOP_REF_SIGNAL_ANA to move the output of the second loop as close as possible to zero (check H1:PSL-ISS_SECONDLOOP_SIGNAL_OUTMON)
5. Switch on the additive path in the ISS inner loop (H1:PSL-ISS_SECONDLOOP_CLOSED to high)
6. Increase the gain to maximum (H1:PSL-ISS_SECONDLOOP_GAIN to 40)
7. Engage the integrator (H1:PSL-ISS_SECONDLOOP_INT_ON to high)

Some details

The input signals to the second loop servo board (the two sums of photodiodes) were not behaving correclty: they appeared to be choppen at the zero level, meaning that only the positive (or negative) part of the signal was present. We traced dow the problem to the OP27 which is used in the output stage of the transimpedance box. This OP27 was used to create a single ended monitoring of the box output, which was sent to the front panel and not used. For some reason we don't understand yet, this opamp was creating the problem. We removed it from the two boards and the sum output is now good.

We also modified the ISS model to wire in the two additional switches ADD_GAIN and ADD_PD_58_SUM. We plan to modify  the additional gain module to get an additional factor of ten in the gain.

8:45 SEI bootfest of all CS ISI and HEPI

9:04 Aaron to EY to retreive AA chassis

9:19 Jodi to MY

9:22 Betsy and Corey to LVEA on 3IFO cable hunt

9:29 Jodi back from MY molesting tiltmeter

9:55 Peter King and Gabriele to PSL looking at ISS

9:55 McCarthy to LVEA looking for tools

10:05 McCarthy out of LVEA

10:24 Jeff and Andres to EX

10:34 JeffK to LVEA testing seismometers

10:43 Framebuilder restarted

10:48 Betsy, Kyle, Bubba to LVEA crane fest

10:50 Cris to EX

11:11 Karen to EY

12:20 Craning in LVEA complete

14:02 Jason to realign ITMy OpLev

14:28 Jason out of LVEA

15:00 Rick and Sudarshan to EX to mount PCal camera housing

16:20 Robert to BTE between MY and EY

Commisioners have reported excess pitch motion in ITMX for the past few nights. The plot attached shows the Optical lever motion (Top left is ASD, bottom left is RMS) , and the ground motion (Top right is ASD, bottom right is RMS). Measurement are taken every morning at 1am on Sunday (Red), Monday (Blue), Tuesday (Green), Wednesday (Brown) and Thursday (Magenta).

The numbers below show that the pitch motion has varied by as much as a factor of 5 from one night to another, but it is not necessarily directly correlated with the amplitude of the ground motion (worst pitch motion was yesterday though the mircro-seism was not higher than during the previous nights).

- Optical Lever RMS motion at 100 mHz, Sunday through Thursday at 1 am PT:

18 nRad / 44nRad / 63nRad / 42nRad / 100 Rad

- Ground instruments RMS motion at 100 mHz in nm/s (must check the units, but it's fair to compare the day to day relative motion), Sunday through Thursday at 1 am PT:

113  / 106 /  197 / 189 / 140

- Ratio in nRad/(nm/s):

0.16   0.41   0.32  0.22   0.71

Power supply for the PEM IO chassis was replaced. Unit powered up with no issues. Front end computer was also powered on.  

J. Kissel, J. Warner, H. Radkins

This completes the changes needed at LHO for the GND STS Kerfuffle, Integration Issue 942, and completes activity for Work Permit 4876. We can't yet close ECR E1400386, or the integration issue, because Ben needs to update the system wiring diagrams, but those should be very coming soon.

After moving all STS distribution chassis outputs into the now-pre-defined AA chassis spigots (see drawing in E1400386 for reference, for now, until the drawings get updated), then completing all model changes to include all three corner-station, sensor-correction, STSs in every HPI and ISI last night (see LHO aLOG 14264), Hugh, Jim, and I took on the task of installing the new code. We

- used guardian to ramp down each chamber, taking the manager to OFFLINE, where applicable, and where not, bringing each ISI and HPI to the READY state and turning OFF the master switch.
- turned OFF all HPI and ISI sensor correction filters by zeroing the MATCH filter bank gain and turning OFF the output switch.
- captured a new safe.snap, using
      ]$ makeSafeBackup ${subsystem} ${modelName}
  and committed to the appropriate "burtfiles" directory in the userapps repo
- *** Made sure all filter files are softlinks to the userapps repo, and repo versions were up-to-date and committed
      -- we found that the majority of the HPI and ISI filter files (both .txt and .fir) were NOT softlinks to the userapps repo. To fix, we
          - Copied any non-softlink files to the appropriate filterfiles directory in the userapps repo
          - Committed the files
          - removed the files from the chans directory
          - created the softlink in the chans directory to the userapps repo, e.g.
              ]$ cd /opt/rtcds/lho/h1/chans/
              ]$ ln -s /opt/rtcds/userapps/release/${subsystem}/h1/filterfiles/${filterfilename} ./${filterfilename}
- re-compiled and installed the new model code
- restarted the front-end code
- untripped all watchdogs
- cleared any IPC errors on HPI/ISI/SUS by hitting the "diag reset" button on everyone's GDS_TP screen.
- used guardian manager to bring up each chamber, takingthe manager to ISOLATED, where applicable, and where not HPI to ROBUST_ISOLATED and ISI to HIGH_ISOLATED
- Restarted the frame builder / data concentrator
    ]$ telnet h1dc0 8087
    daqd> shutdown
- Confirmed that every corner station HPI and ISI reads out the correct GND STS on the correct channel using dataviewer and me zydeco dancing in proximity to each sensor successively.


Note that *** may need some attention when loading in new filters. It's unclear yet what quack (the matlab method of installing new filters that really only the SEI team uses) will do when loading filters. It currently installs new filters into the /opt/rtcds/${site}/${ifo}/chans/ directory. Will it over write the soft-link? Will it follow the softlink? I think this has been checked that it won't break anything, but it's something we should pay attention to in the future. It's especially interesting to see if the .fir filters can handle it.

Laissez les Bon Temps Roulet!

Issue likely applies to other subsystems but SEI has a hierarchical guardian and this may be more a problem for these types of guardians.

Before restarting the front ends, the guardian was used to bring things down by moving the request from Isolated to offline. When the BS (and all other) guardian (Chamber Manager) was turned from OFFLINE to ISOLATED after the frontend restart, we had to RELOAD the guardian.  This was expected and maybe normal.

However on HAM4, the chamber manager reload was not sufficient.  The Chamber Manager reported "ERROR in state INIT; see log for more info; MODE=>RELOAD to reset"

The log file reported "NameError: name 'Connect' is not defined"

Until I reloaded the ISI and HPI subordinate guardians (can't tell if just one or actually both needed to be reloaded), reloading the Chamber guardian was insufficient.

After reloading the subordiantes, reloading the Manager brought things back as usual.

Jeff enlisted Hugh and I to help with a mass snap, model compile, model restart -fest this morning in the corner station for all SEI platforms. The BSC's went fairly smoothly, but when I did HAM5, the watchdogs behaved strangely. I couldn't reset the DACkill or Rogue Exc WD's, but when I randomly tried turning on the master switch, I was then able to reset all WD's. The first couple tries, this immediately resulted in DACkill trips, but the 4th one stayed up. The chamber is now isolating again, but it sound like this should be investigated.

model restarts logged for Wed 01/Oct/2014
2014_10_01 10:33 h1broadcast0
2014_10_01 10:33 h1dc0
2014_10_01 10:33 h1fw0
2014_10_01 10:33 h1fw1
2014_10_01 10:33 h1nds0
2014_10_01 10:33 h1nds1
2014_10_01 10:33 h1psliss
2014_10_01 16:13 h1ioppemmy
2014_10_01 16:13 h1pemmy
2014_10_01 16:35 h1ioppemmy
2014_10_01 16:35 h1pemmy
2014_10_01 19:33 h1fw1
2014_10_01 23:13 h1fw1

unexpected restarts of h1fw1. New psliss model with associated DAQ restart. Recovery of h1pemmy after IO Chassis problem.

Alexa, Kiwamu, Sheila, Jenne

This is sheila, accidentally logged in as Jenne

We made some attempts tonight to transition DRMI to 3F.  We see that we don't have much signal in the 3F detectors at 1 Watt, so we have been transitioning manually to 10 Watts after lock is acquired.  We have transitioned PRCL successfully several times, with a gain of 1.5 in the input matrix, this is handled by guardian.  We have tried srcl, and used 60% of the 3F with 40% of the 1F.  Our next steps are to get some asc loops running, so that we don't spend as much time manually aligning DRMI, and also to try transitioning mich after prcl.  

The rotation stage has a lot of hysteresis, we will ultimately want some sort of servo to make sure that the input power is what we requested.

Kiwamu has measured the modulation depth: yesterday AS RF 90 was 33 counts, today (with the 19 dB RF amplifier and 6dB attenuator installed) it is 270.  This was consistent with the OMC scan which were the height of the 45 MHz sideband with DRMI locked was 0.3, today it was 3.  (These both mean that the modulation depth increased by roughly a factor of 3).  The gains in the guardian have been adjusted to take this into account.  

The good news is that we have locked DRMI many times tonight, it normally locks within a few minutes.  Also, the attached screen shot shows that DRMI was locked on 1F for about 10 hours last night.  

On ITMY, we are testing the blend configuration in use LLO (see 14210 for details). It should help reducing the Z to RZ couplings.  The document attached shows the coherence between the Optical Lever Yaw motion, and the degrees of freedom of Stage 1 ISI (measured by the T240s):

- Each page shows 5 hours of data taken between 1am and 6am PT

- The three plots on the left show time series. Top left is the optical lever, middle left is Stage 1 translations, bottom left is Stage 1 rotations.

- The six plots on the right show coherence as a function of time (5 hours on the x axis) and frequency (0.01 Hz to 1 Hz on the y axis). Red indicates a coherence of 1. Blue is a coherence of 0. Top right plot is coherence between Stage 1 X and optical lever Yaw, second from top is between ISI Y and optical lever Yaw... bottom right is coherence between Stage 1 RZ and optical lever Yaw.

Sunday morning: the ISI was controlled with the LHO configuration that has been in use lately (see 14210 for details). There is big coherence between Z, RZ and the optical lever at the microseism and at sub 0.1 Hz frequency. Optical lever RMS over ground motion RMS is about 16.5 rad/m/s.

Monday morning:  same configuration, same results and  comments. The Optical lever RMS over ground motion RMS is about 15.5 rad/m/s.

Tuesday morning:  the LLO configuration is ON. There is no more coherence between Z, RZ and the optical lever Yaw motion (except for some time around 4am PT, maybe the M4.4 at 3:44am in China?).  The Optical lever RMS over ground motion RMS is about  11 rad/m/s.

Wednesday morning: the guardian manager has been inadvertendly un-paused, re-engaging the Stage 1 RZ loop, and putting Stage 2 in dmaping only. The coherence is back and the motion ratio is 23 rad/m/s, but this is not a relevant configration.

We have re-put the ISI in the LLO configuration. If the data from the coming night is good again, we'll work on propagating this config to the other units, and updating the guardian parameters.

Dave, Sudarshan, Richard

LIGOCAM reported that three microphone at EY were disconnected.

I found last week that these microphone would work as normal when switched from their original channel position to some other channel on the AA chassis so, we restarted the  H1IOPISCEY yesterday to see if the problem was in the DAC. This was an unsuccessful attempt as mentioned in alog 14225.

Today, I injected 3Vpp signal on all the channels using a function generator and found out the following:

Channel 1-16 are working as normal (I happened to switch those microphones to one of these channels during my first attempt).

Channel 17-30 show nothing on the output end of medm screen monitor.

Summary: The problem is with the AA chassis board. Richard has been notified and this AA Chassis will be switched sometime next week.

For those interested in looking closer at QUAD model parameters, attached are plots comparing all of the QUAD Main Chains when suspended with wires and also when suspended with fibers.   Note, if QUAD data is missing for one of these configurations it's because there was no clean data available.  Between the 2 plotted configurations, all 12 (H1, L1, and 3IFO) QUADs are represented.  Note, I tried to chose data sets that had the same or similar environmental conditions, but it was difficult due to the fact that some QUADs were reworked on test stands and some were reworked in chamber.  In all cases they were mounted on Solid Stack Test Stands or Locked ISIs and in-air.

Data is committed to the svn and can be found at:

/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/Data/

There does not seem to be a pattern in the data of the 2nd pitch mode peak which are clustered by a specific type of suspension (ETM vs ITM, or wire segment hang vs wire loop hang).