maintence day recovery

Sheila, Patrick, Daniel, Alexa, Chris, Kiwamu, Evan

Before we started commissioning tonight, we had to recover from some maintenance day activities. 

• The timing system had some problems, which was difficult to diagnose at first because there were many erroneous error messages from the timing system.  Once we got rid of most of these (by going into the master visualizations in the PLC on the beckhoff machine, and clicking on the icons for each fanout that doesn't have anything connected) The remaining errors were for End Y VCXO control voltage (this has been this way for a year or so according to Daniel) and a missing communication for the End Y Fanout.  Daniel fixed this by restarting PLC1, it is not clear what caused the problem or why restarting the PLC would fix it.  It would probably make understanding/maintaining the timing system easier if we had some more complete medm screens for it.

• /sus/common/scripts/sustools.py was edited today, apparently in a way that made our save alignment script no longer work.  We reverted to the version in the SVN, which fixed that problem.  The SUS guardians also complained about invalid syntax on line 63.  the version which was edited today is saved as sustools_oct28.py

• the new version of cdsutils seems to have a nonfunctional avg function, or at least a version which has different usage than the old version, which we could not decipher from the help.  We also recovered from this by reverting to the old version.  (some of our guardians use this, so if the usage is changing we need to be aware ahead of time).

• Apparently after the quad model changes the value of L3_LOCK_INBIAS was set to 0 (it should be 9.5) and the filter which was previously loaded in FM1 (a calibration into volts) disappeared.

• The pop shutter was closed, this might not be related to maintenance.

peek at PR2 baffle

Alexa, Kiwamu,

In response to Keita's alog about the PR2 baffle, we took a peek at the PR2 baffle by opening some of the viewports on HAM3 and HAM2 spool.

Conclusions:

• The aperture hole on the baffle looks centered.
• The baffle in front of PR2 looks the right one.

 

(PR2 baffle check out)

We opened up a viewport on the East side of HAM3 which the leftmost one with an illuminator attached on. This was the only available viewport to open up. We removed the illuminator and looked at the baffle through the viewport. We confirmed that there was no cross bar structure on the side of the baffle unit as shown in the DCC document (D1000328). We could not see the top part of the baffle where it supposed to have a cross bar structure. We took some pictures and I attach them to this entry.

(Peek at the aperture position)

Then we tried a different zooming in the PR2 digital camera in order to have a better view so that we can determine if the aperture hole is in the middle of the baffle unit or not. With a help of flash light illuminating the PR2 baffle from the HAM2 East side viewport, we could clearly see the edge on both right and left sides of the unit as well as the edge of the aperture. It looked like the hole is centered with respect to the right and left edges of the unit. We took several pictures of it via the digital camera so that one can evaluate the position later if necessary.

(MC2 scraper baffle check out)

Then we opened up another viewport on the West side of HAM3 in order to see both MC2 and PR2 baffles. Though, the MC2 baffle was completely occulting the PR2 baffle and therefore we could not see it. We could still confirm that the MC2 baffle has a cross bar structure on the side as shown in the design document (D1000327).

HAM-ISI & HEPI MEDM Overview Screens Updated

Similar to what was rolled-out earlier today for the Suspensions (see LHO aLOG entry 14657), I've now svn'd up the latest HAM-ISI & HEPI MEDM Overview screens, which includes the embedded Guardian mini control-panel providing access to requestable states, as was developed at LLO (see LLO aLOG entry 15010).

The following MEDM screens were updated:-

/opt/rtcds/userapps/release/isi/common/medm/hamisi/
U        ISI_CUST_CHAMBER_OVERVIEW_LARGE.adl
U        ISI_CUST_CHAMBER_OVERVIEW.adl

/opt/rtcds/userapps/release/hpi/common/medm/hepitemplate/
U    HPI_CUST_CHAMBER_OVERVIEW.adl

Screen-shots of the updated HAM-ISI & HEPI MEDM Overview screens are attached below.

updated conlog channel list

added 802 channels
removed 524 channels

RHX test scheduled to run at

I've scheduled a RH-X test to run from around 2:45AM for 5 hours. 

Coherence and transfer functions between ISI, Sus top mass and Optical levers (BSC chambers)

We reported last week that the pitch RMS motions of the bottom masses was dominated by 0.5 Hz features on all BSC units.  We are looking at the coherence between ISI, Suspension top mass and optical levers to find out how to reduce the bottom masses angular motion.

 

Plots:

The first figure attached shows coherence plots, the second figure shows transfer functions plots:

- in the top left, from "ISI longitudinal" to "SUS top mass longitudinal"

- in the top right, from "ISI longitudinal" to "SUS top mass pitch"

- in the bottom left, from "SUS top mass longitudinal" to "Optical Lever pitch"

- in the bottom right, from "SUS top mass pitch" to "Optical lever pitch"

 

Comments:

At 0.5 Hz,

- the coherence between ISI longitudinal and SUS top mass motion is not very high. We'll add more ISI channels to see how they contribute to the suspension point motion.

- the coherence betwen the suspension top mass and the optical levers is above 0.9 (above .99 in some instances). The BS longitudinal to pitch transfer functions show a Q around 20. The pitch to pitch transfer functions show similar Qs for all units. We can compare this to damping models.

 

Corrections:

- I used one hour of data starting on Monday Oct 27, 3 am PT.

- I fixed the axis labels and plots titles

CDS maintenance summary

SUS and LSC model changes. Jeff K

many sus models and LSC were changed. New IPC added between them. susaux models at end stations also changed.

HEPI Pump Controller. Hugh R

new EPICS databases started on EX and EY HEPI pump controllers. MEDM changed accordingly.

DAQ FW1 file system increase. Jim, Dave, Dan

h1ldasgw1 file system grown to use two raids.

Patch and Restart Workstations. Cyrus

All CDS workstations patched and restarted

Beckhoff changes. Patrick

Beckhoff systems for C1 (PLC1,3) X1 (PLC3) and Y1 (PLC3) modified.

DAQ reconfigured. Dave

DAQ reconfigured for Beckhoff and HEPI pump controller and susaux(ex,ey) changes. Restarted twice, needed start_streamers on various frontend after second restart.

Installing SUS DRIFTMON. Jim, Dave

Installing a test version of driftmon which doesn't require additional EPICS records. Testing NDS2 data collection parameters.

HWSX and HWSY are now running. But we're getting leakage from HWSY into HWSX.

Aidan. Alastair

Following a successful install of the HWSY correction, we realigned the HWSX optical system to accomodate a change in the green leakage field from four weeks ago (probably due to changes in alignment of the BS and SR3). We coarsely matched the ALS and 800nm optical axes through the irises. We fine-tuned the centering of the probe beam to the ITM by observing the location of the center of the intensity relative to the center of the shadow from the BS and tweaking the alignment of the upper periscope mirror to get the intensity distribution concentric with the shadow.

We will run RH tests in the morning to try to ascertain the exact location of the centers of the ITMs in the HWS coordinates.

However: when I turned on the HWS-Y SLED, the HWS-X sensor started going haywire. By reviewing the camera stream from HWS-X itself, it became clear that some of the HWS-Y probe beam is making it into the HWS-X camera. We haven't yet figured out what this leakage path is. We can still run the sensors one at a time as diagnostics. Only HWS-X is currently running.

And: we're seeing glitches in the frames from HWS-X that have been seen before. They manifest as part of the image being transpose with another part of the image. This is clearly a digital issue (probably access of the framegrabber). It has really only been observed when we try to access both cameras from the framegrabber.

Images of the HWS-X camera stream, with and without the HWS-Y probe beam turned on, are attached.

File system for h1fw1 doubled in size

WP 4916

Dan Moraru

The file system for writing frames on h1fw1 has been expanded by attaching a second SATABOY raid similar to h1fw0. This will provide a look back capability similar to h1fw0 as data is written over the coming weeks. The current look back capability of h1fw0 is:

Data	Hours
Commisioning frames	356
Science Frames	74
Minute Trends	106
Second Trends	851

Shift Summary Oct 28th, 2014

8:15 Jodi and guest to LVEA
8:15 RichardM to LVEA to check ITMX HEPI L4C
9:00 Mitch to LVEA
9:15 Hugh to EX/EY hooking up HEPI Pressure sensors, back at 11:00
10:15 Betsy to LVEA
11:00 Karen to EY
13:30 Betsy back out to LVEA
14:30 JeffB and Andres to LVEA, moving 3IFO sus
15:00 Kyle to EY work wit Rai, back 16:00

Guardian still not working for HAM2 ISI

I have tried to use the Guardian to isolate HAM2 ISI seven times today and it has never succeeded.  Three times early ~8am, twice at 1250, and twice at 1500.  Everytime I use the command script it succeeds.  Another thing I've noticed the Guardian does differently from the old Command script: The Guardian loads the reference location at the intermediate points whereas the command script does all 6 dofs at the end.

Attached is the GS-13 Spectra after switching to the 100mHz Blends on X Y & Z.  Again, it doesn't appear to be a better controller.

ITMY RH on at 4W

The ITMY RH is on at 4W for beam location of the HWS beam.

Changed default NDS server

The default NDS server has been restored to h1nds1.  This applies to all new logins, shells, or processes that use NDS, all currently running processes are unaffected and will continue to use h1nds0.

more Beckhoff work

Work under permit 4919 and possible missed stuff from 4917:

corner station

quit IOC
C:/SlowControls: svn update
H1ECATC1: PLC3: 'Update from source'
C:/SlowControls/Target/H1ECATC1/H1ECATC1.tsm: PLC1 rescan project, PLC3 rescan project; Actions -> Generate mappings, Check configuration; Save
Copy C:/SlowControls/Target/H1ECATC1/H1ECATC1.tsm to C:/SlowControls/Scripts/Configuration/H1ECATC1/SYS/H1ECatC1.tsm. svn commit
C:/SlowControls/Target/H1ECATC1/PLC3/PLC3.pro: rebuild all, save
Copy C:/SlowControls/Target/H1ECATC1/PLC3/PLC3.pro to C:/SlowControls/TwinCAT/Source/Interferometer/Corner/Plc3.pro
C:/SlowControls/TwinCAT/Source/Current/Interferometer/Corner/Plc3.pro: Export EXP. svn commit Plc3.pro and Plc3.exp.
C:/SlowControls/Target/H1ECATC1/H1ECATC1.tsm: PLC3 rescan project; Actions -> Generate mappings, Check configuration; Save.
Copy C:/SlowControls/Target/H1ECATC1/H1ECATC1.tsm to C:/SlowControls/Scripts/Configuration/H1ECATC1/SYS/H1ECatC1.tsm. svn commit
H1ECATC1: SYS, PLC1, PLC3: 'Stop', 'Update from source', 'Compile': Compile failed.
C:/SlowControls: svn update
H1ECATC1: SYS, PLC1, PLC3: 'Stop', 'Update from source', 'Compile', 'Activate and run': TwinCAT PLC Control has stopped working
Restart computer
quit IOC
H1ECATC1: SYS, PLC1. PLC3: 'Stop', 'Update from source', 'Compile': TwinCAT PLC Control has stopped working
H1ECATC1: SYS, PLC1. PLC2. PLC3: 'Stop', 'Update from source', 'Compile': TwinCAT PLC Control has stopped working, 'Activate and run': TwinCAT PLC Control has stopped working

At this point I don't know what is going on. Going into deeper investigation...

I got the corner station back, now end X is down...'mystery errors' in IOC.

All appear to be back. Burtrestores done to 6:10 am for all PLCs for the corner station, end X and end Y.

Calibration of HWSY magnification via injection into ITMY YAW

I'm currently injecting a 50mHz, 2 micro-radian ampltiude sinusoid into ITMY YAW (via the top stage). HWSY is now within a few mm of the conjugate plane of ITMY. The HWS code is running and will measure the apparent tilt at the HWS from the injection oscillation. I will use this to calibrate the magnificiation of the HWSY optical system.

guardian/cdsutils upgrades

I upgraded the guardian core and cdsutils (python ezca) installs:

• guardian r1095: better error handling, minor bug fixes
• cdsutils r359: NDS interface improvements (handle channels without IFO prefix), fix avg function, add filter module decoding utility (cdsutils sfm)

I restarted most of the nodes, except for the following:

jameson.rollins@opsws2:~/src/cdsutils/trunk 0$ guardctrl list | grep -v 1095
node         s k m vers  state                                    message
----         - - - ----  -----                                    -------
ALS_COMM     o - -    -  -                                        -
H1ECATC1PLC2 *   E 1076  INIT                                     
H1ECATX1PLC2 *   E 1076  INIT                                     
H1ECATY1PLC2 *   E 1076  INIT                                     
H1ISCEX      *   E 1076  INIT                                     
H1ISCEY      *   E 1076  INIT                                     
H1LSC        *   E 1076  INIT                                     
H1LSCAUX     *   E 1076  INIT                                     
HPI_HAM2     * * M 1083  ROBUST_ISOLATED                          
IAS_INPUT    o - -    -  -                                        -
IAS_MICH     o - -    -  -                                        -
IAS_PRC      o - -    -  -                                        -
IAS_SRC      o - -    -  -                                        -
IAS_TEST     o - -    -  -                                        -
IAS_XARM     o - -    -  -                                        -
IAS_YARM     o - -    -  -                                        -
IFO_ALIGN    o - -    -  -                                        -
ISC_LOCK     o - -    -  -                                        -                            
ISI_HAM2     *   P 1083  WATCHDOG_TRIPPED_FULL_SHUTDOWN           WATCHDOG TRIP: FULL_SHUTDOWN (4)                       
LSC          *   E 1076  INIT                                     
LSC_PRMI_VAR_FINESSE *   E 1083  DOWN                                     MISALIGN PRM
LSC_PRX      *   P 1083  FAULT                                    check LSC input matrix, ITMY not MISALIGNED
LSC_PRY      *   P 1080  FAULT                                    PRM not ALIGNED, ITMX not MISALIGNED
SEI_HAM2     *   P 1083  ISOLATED                                   
SUS_MC1      * * E 1080  ALIGNED                                  
SUS_MC3      * * E 1080  ALIGNED                                  
SUS_PR3      * * E 1080  ALIGNED                                  
SUS_PRM      * * M 1083  ALIGNED  

The non-running nodes (s='o') had various errors on restart, so I shut them down until they can be fixed.  I shut down all the IAS nodes since I was told they're not in use.  The HAM2 nodes were not restarted because Hugh was in the middle of doing some SEI work on HAM2.  The nodes starting with "H1" are the "CSDEF" nodes (not sure what the status of those is).  I'll restart these nodes when I'm sure it's ok.

I noticed that there are a couple of "hidden" nodes, that are not listed in the Guardian overview screen:

H1ECATC1PLC2 *   E 1076  INIT                                     
H1ECATX1PLC2 *   E 1076  INIT                                     
H1ECATY1PLC2 *   E 1076  INIT                                     
H1ISCEX      *   E 1076  INIT                                     
H1ISCEY      *   E 1076  INIT                                     
H1LSC        *   E 1076  INIT                                     
H1LSCAUX     *   E 1076  INIT   LSC          *   E 1076  INIT                                     
LSC_PRMI_VAR_FINESSE *   E 1083  DOWN                                     MISALIGN PRM
LSC_PRX      *   P 1083  FAULT                                    check LSC input matrix, ITMY not MISALIGNED
LSC_PRY      *   P 1080  FAULT                                    PRM not ALIGNED, ITMX not MISALIGNED

We should be very careful about these.  If they're being used, they should be on the overview.  If they're not being used, they should be shut down.  Do not leave running nodes off of the overview screen

DRMI 3F

Alexa, Sheila, Rana, Evan, Dan, Kiwamu

Today we worked on getting DRMI locked on 3F.  It took us a while to get through the inital alingment sequence for various reasons, but once we did, and sorted out the WFS DC centering (Evan and Rana made some improvements to the AS A centering loop, Dan pointed out that the output matrix was mixed up), we were able to use the ASC to bring the DRMI to a reasonable build up (POP18 at 200 cnts). 

We then looked at the demod phase of our 3F sensors.  We tuned both 135 and 27 to miniminize the Q signal, first exciting PRM then SRM.

The best demod phases in degrees:

	PRM	SRM
27	85.5	101.8
135	-25	65

We left 27 at 85.8 (we started at 84.8) and 135 at 65 (we started at 63).  We thendouble checked the relative gain between 3F and 1F signals, they are the same as previously, and we were able to transition to 3F.  (durring all of this DRMI was nice and stable, locking for up to an hour before we knocked it out with an excitation of some sort).

Since this we have made a few attempts to bring the arms in, we redid our entire inital alingment process, and after that realingned the DIFF and COMM beat notes (they haven't been realingned since the pico motor in HAM3 was moved last week).  We got about 3dBm in both beatnotes. 

Once we had the arms (off resonance by 1 kHz in green), we were able to lock DRMI quickly, but the build up was low.  When the ASC came on, it did improve the build up but as the build up got better, we started to mode hop.  This was repeated a few times.  By offsetting SRCL by -800 counts, we were able to avoid this mode hopping. 

We have now rung up the roll mode at 13 Hz on ETMY.