Morning Meeting Notes - from Corey

Work Permits

ETMx

HEPI:  Actuators attached (but galled bolt yesterday slowed things), see a little bit of a tilt

--look at level (Doug or Hugh)

Have Thomas do ACB checks, and then do ETMx alignment

After alignment, unlock ISI & run TFs

ITMx

Payload last night & need to check lockers

Dropping cables down

AOS (Cryopump Baffle)

parts staged

ready to assemble this morning(Mitch/Gerardo/Thomas)

Apollo

BSC3 feed-thrus

Notes from the rest of the day: Cheryl

Facilities:

X arm insulation removal

Rollup doors - EY and MY

Roofing continues

LVEA general work:

ACB assembly continues

Control Room:

ITMX model restart

DAC restart

EX restart

Many more restarts - testing code - Rolf and Dave/CDS

- code tested today will be backed out tonight starting around 4PM

- Dave's estimate is that it will take an hour to load and restart code

EX:

 - Thomas is back, no others there to my knowledge

A TCS general status has been requested. This report will focus on TCS in-vac readiness. BSCs 1, 2, and 3 will be populated with steering mirrors. BSCs 1 and 3 are populated with D1101013 assemblies. BSC 2 is populated with D1101851 assemblies. 

Both D1101013 assemblies are mostly complete. The wedge parts that attach to the chamber are kitted and ready for install. The mirrors and their sub-assembly mount D1102029 remain to be kitted. The mirrors themselves are waiting for two FTIR results to return. Most of them passed, however, two failed (E1300748) and were recleaned by Joe DeRenzis and myself. 

Both D1101851 assemblies are installed in BSC 2. They are mostly complete, the only thing needed is to install the SM2 steering mirrors and related hardware. 

Hopefully the mirror sub-assemblies can be kitted soon and TCS in-vac install will be dependent on FTIR results / door removal.

We are currently testing RCG2.8 on the front end systems which send their DAQ data to the second 10GE port on h1dc0. The full list of computers is:

h1oaf0, h1lsc0, h1asc0, h1pemmx, h1susauxey, h1iscey, h1susey, h1seiey, h1susauxex, h1iscex, h1susex, h1seiex.

All models running on these FEs were recompiled against the latest RCG trunk (the branch2.8 is a few days old, so we elected to compile against the trunk for this test). The exceptions are the SUSTMSX and SUSTMSY whose models are being worked on and did not compile, these were left at their 2.7.2 version.

The LVEA test stand was also left at 2.7.2 even though they are part of the block of FEs writing to this h1dc0 port.

The DAQ was reconfigured to remove the EDCU ini files associated with the upgraded models.

The front ends were restarted, no problems were observed.

We tested various slow (16Hz) channels which are now being transmitted along with the fast data over the DAQ network and not being acquired by the EDCU via the FrontEnd network, no problems have been observed.

The sus team are damping ETMX with the new version of h1susetmx with no problems being observed.

The ODC team checked their slow channels with no problems being seen.

As a demonstration of the synchronisity of the new 16Hz slow channels, the attachment shows 1 second of full data for a DuoTone slow channel for 2.8 (left plot) and 2.7.2 (right plot), showing true aliasing of the 960Hz Sine Wave signal with the new system.

We monitored the network bandwidth used by the second 10GE port, as measured by the switch, increased by 10% (200Mbps to 220Mbps).

The frame size did not increase beyond the noise level.

Since SEI/IAS/ACB people were still sorting alignment issues with the ETMx cartridge, we hopped into BSC3 to make some progress on ITMx.  SEI still needs to finish payload and balance but we suspended the masses in prep for controls testing and future alignment.  We added the witness plate to the suspension and removed all temp payload EQ stop bars.  Payload is correct for SEI balance.

With Arnaud, we reset all 12 top stage BOSEM offsets and gains (to compare with test stand values) and then set the OSEMs to 50% OLV.  We attempted damping, but both chains had watchdog trips within seconds of enabling the DOFs.  We have rechecked that we do not (think) we have mechanical rubbing so will revisit the software/EE guys for further assistance.

I just now turned on the horizontal draw fan that I have parked in the cleanroom wall near the chamber door. I would expect to see some higher than normal particle counts on unit #3 as the turbulent flow moves particulate out of the room likely from under the chamber, etc.

Today, I went to the LSB lab to put the SR03-02 optic in the oven and found water all over the floor in the lab.  A quick call to SKi who came down and repaired a fitting leak he generated yesterday - followed by a good mopping up of water and floor cleaning.  A small amount of water leaked into the fiber lab, but did not disturb anything on the floor.

SO, the labs are clean.  And as of tomorrow, the SR03 will be ready to be suspended.

This morning, Travis finished swapping the incorrect blade tip EQ stops on the SRM top mass with the correct ones and then reset the BOSEMs to 50% OLV.  This supsension is ready for Phase 2b testing.  Note, we skipped Phase 2a testing since the "optic" used for this round of the SRM installation is a dummy 2" optic in a metal dummy mass.

J. Kissel

In order to grab a few necessary parts for the SUS model/MEDM screen upgrades, I've updated a few ISC and CDS corners of the cds_user_apps repo. I checked before I updated to be sure there were no local modifications that would be in conflict with the updates, as well as making sure I didn't receive anything that I didn't expect to. This is done with an 
svn st -u
in the folders of interest. The "-u" tells you what you will get upon update (with a " * " indicating you will receive an update, and if the revision number is next to the " * ", it indicates you'll get an update to an already existing file.)

Here're the results of what was updated:
/opt/rtcds/userapps/release/lsc/common/medm
A    LSC_CUST_UGF.adl
U    LSC_CUST_OUT_MTRX.adl
A    LSC_CUST_LOCKIN_DEMOD.adl
A    LSC_TRIG_TEST_OVERVIEW.adl
U    LSC_CUST_POW_NORM.adl
A    LSC_CUST_LOCKIN_DEMOD_MTRX.adl
U    LSC_RFPD_DEMOD.adl
A    LSC_TRIG_TEST.adl
U    LSC_CUST_LOCKIN.adl

/opt/rtcds/userapps/release/asc/l1/medm
A    LSC_POW_NORM_P.adl
A    L1ASC_CUST_POW_NORM.adl
A    L1ASC_QPD_MTRX.adl
U    L1ASC_INMAT_Y.adl
U    L1ASC_OUTMAT_Y.adl
A    LSC_POW_NORM_Y.adl
U    L1ASC_OVERVIEW.adl
A    L1ASC_WFS_INMATRIX_QUADRATURE.adl

/opt/rtcds/userapps/release/cds/common/med
U    CUST_CAMERA.adl
U    L1ASC_TRANS_POP_QPD.adl
A    L1ASC_SPARE_QPD.adl
U    L1ASC_WFS_SETTINGS.adl
U    L1ASC_AS_REFL_QPD.adl
A    L1ASC_QPD_SEG.adl
U    L1ASC_WFS_QUADRATURE_FILTERS.adl
A    L1ASC_QPD.adl
A    L1ASC_LKIN_INMAT.adl
A    L1ASC_CUST_LOCKIN_DEMOD.adl
U    L1ASC_INMAT_P.adl
U    L1ASC_OUTMAT_P.adl
A    IMC_WFS_DC_QPD_MTRX.adl

These folders are all now updated to version 6036.

J. Kissel, R. Bork, D. Barker, J. Batch

After installing and completing all of the changes to the front-end simulink model for the QUAD, it took a while before it would successfully compile, due to my own misunderstandings of how tags and (separately) cdsBinIns work. Unfortunately both bugs result in a bunch of red-herring errors being thrown. Many thanks to Rolf, Jim, and Dave for their help resolving these issues*.  Once I got that up and running, the rest of the day was spent updating the QUAD OVERVIEW screen to match the new infrastructure. This is almost entirely complete, but I have not made any of the necessary changes to the sub screens. Tomorrow is another day.

For the record, CDS would like to begin updating to RCG 2.8 tomorrow. I consider all of the QUAD models ready for this upgrade, though it would be nice to see the remaining QUADs (see below) installed against RCG 2.7.2, before going forward. The remaining suspension types are *not* ready, and should be left alone.

I have left the QUADs as follows:
ETMY -- compiled, installed, restarted, restored (but the safe.snap will need to be retaken because of all the new bits).
ETMX -- compiled, but not installed
ITMY -- compiled, but not installed
ITMX -- compiled, but not installed
Robert and Arnaud are taking measurements on the other three tonight, and need a good DAQ status, so I have refrained from installing new stuff.

Note -- the good news is that with the removal of the ISI OFFLOAD path and reduction of the DRIVEALIGN matrix, the QUAD models now finish all computation in 37 [usec] as opposed to 45 [usec] of their 61 [usec] clock cycle.
Note -- Stefan's new dependency script is also awesome (see LHO aLOG 8213).
Note -- The compilation process only spits out he last 10 errors or so. To get a full list of errors, look at ${BuildLocation}/${modelname}.log on the build machine. At LHO, for the ETMY, that's /opt/rtcds/lho/h1/release/h1susetmy.log
Note -- For a complete and utter gorl details of what the parser spits out -- and therefore a detailed list of every part's inputs and outputs, look at ${BuildLocation}/src/epics/util/diags.txt after a compile. It's daunting, but if you have one channel or two that's problematic, you can just search for it and investigate it's connections to see if they make sense.
Note -- cdsBinIns MUST have their input grounded. Otherwise, the RCG claims that everything connected to them -- all the way out to the top-level model -- is disconnected, instead of telling you what's really wrong. Rolf says this bug is on the list of things to be fixed when he goes through all parts and makes sure certain ones don't require things attached to them for the model to compile.
Note -- Within a given sub-system level, you cannot pipe an input into a sender tag, then stick the output of the receiver tag directly into a sub-sub-system. To the RCG, this is like "skipping a level," because nothing happens to the signal at the sub-system level, so connections are lost. Similarly, when you do this, the RCG throws errors on *everything* connected to this path, but not tell you what's really wrong.

The new list of things that I've done to the front end code:
- Add SVN $Id$ to all models and library parts, to better track version control
- Moving the DRIVEALIGN matrix out of the DAMP/TEST/OPTICALIGN paths on the main chain, such that it only operates on the LOCK path for each stage (and therefore reducing the size of the M0 / M1 version)
- Adding output switches after the internal SUS offloading, so -- in the "offloaded" hierarchy scheme -- one can send alignment signals straight to the top without zeroing out diagonal DRIVEALIGN matrix elements
- Removing the wasteful, unnecessary DRIVEALIGN path on reaction chain's TOP mass.
- Making both DAMP and LOCK filter banks use cdsCtrlFilt, such that they produce a status bit word for ODC consumption during lock acquisition
- Defining the list of channels that shall stay in the science frames, to be stored for all time
- Removing obsolete L1 and L2 (lower stage) damping from the QUADs which had been needed for very early H2OAT operation before ISIs were turned on
- Removing the explicit definition of 2048 from the stored ODC DAQ channel, such that it is by default sored at the model's native rate as designed
- Adding a length-driven, (optical lever/OSEM) angle response lock-in for force-to-angle decoupling and tuning.

The remaining to-do list for the QUAD screens:
- Find the generic ISC Lock-In screen. They must have one.
- Add "GOOD"/"BAD" states to DAMP and LOCK screens
- Remove DRIVEALIGN from RO screen
- Create LKIN2OSEM matrix screens
- Add PUM Analog WD to OVERVIEW screen.
- Add Coil Driver BIO status information to the OVERVIEW screen.

Here's the outstanding userapps SVN status on files that are pertaining to my work:

?       common/medm/quad/SUS_CUST_QUAD_L1_LKIN2OSEM.adl
?       common/medm/quad/SUS_CUST_QUAD_M0_CENTERING_TEST.adl
?       common/medm/quad/SUS_CUST_QUAD_M0_LKIN2OSEM.adl
?       common/medm/quad/EDITME.adl
?       common/medm/quad/SUS_CUST_QUAD_L2_LKIN2OSEM.adl
?       common/medm/quad/SUS_CUST_QUAD_L3_LKIN2ESD.adl
M       common/medm/quad/SUS_CUST_QUAD_OVERVIEW.adl
MM      common/models/HAUX_MASTER.mdl
MM      common/models/HLTS_MASTER.mdl
MM      common/models/SIXOSEM_F_STAGE_MASTER.mdl
MM      common/models/BSFM_MASTER.mdl
MM      common/models/MC_MASTER.mdl
M       common/models/OMCS_MASTER.mdl
MM      common/models/HSTS_MASTER.mdl
MM      common/models/FOUROSEM_STAGE_MASTER.mdl
MM      common/models/TMTS_MASTER.mdl
MM      common/models/QUAD_MASTER.mdl
M       h1/medm/h1mcall.adl
M       h1/models/h1sustmsx.mdl
M       h1/models/h1sustmsy.mdl
M       h1/models/h1susprm.mdl
M       h1/models/h1sussrm.mdl
M       h1/models/h1suspr2.mdl
M       h1/models/h1susbs.mdl
M       h1/models/h1suspr3.mdl
M       h1/models/h1sussr2.mdl
M       h1/models/h1sussr3.mdl
M       h1/models/h1susetmx.mdl
M       h1/models/h1susomc.mdl
M       h1/models/h1susetmy.mdl
M       h1/models/h1susmc1.mdl
M       h1/models/h1susitmx.mdl
M       h1/models/h1susmc2.mdl
M       h1/models/h1susmc3.mdl
M       h1/models/h1susitmy.mdl

(The double "MM" status means that I've modified the model itself, AND the svn properties to make sure the SVN $Id$ is recognized.)

Both horizontal and vertical HEPI actuators are attached on BSC 9.

Values after IAS positing, pre actuator attachment:

After actuator attachment:

Change

Corner 4's big vertical change was possibly from a tripod with some bend in it.

Attached are screen shots of the new MEDM screens for new h1odcmaster, h1odcx and h1odcy.

The bitmask for the corner was set.

Patrick, Daniel, Cyrus, Alexa, Dave, Sheila

Around 3:30 this afternoon Alexa tried to test the whitening filter controls at end x.  The PLC was not running, and was asking the user to choose a run time system.  In the meantime I tried to remote login from the control room, which only worked using the IP adress, not using the server name.   After looking into this Cryus changed the network type to work (before it was public, and the windows firewall settings would not allow dave to ping the machine). 

The computer had a blue screen and rebooted. It did not start the twinCAT stuff on automatically as it should.  I tried going through the instal scripts.  There was no communication between ISC common and the End 2 beckhoff chassis.  Cryus gave Alexa and I a replacement cable.  After swapping the cable some of the modules were in the OP stae, some were PREOP with an INIT error. 

Patrick put the system manager into config mode and back to run mode all the modules are in the OP state.  We logged in and ran the PLCs, and restarted the epics database a few times.  There seems to be no communication with EPICs, the power shell says:

target machine not found, Cause: Missing ADS routes

Stefan has installed ODC MASTER (running on h1oaf0), ODC X (running on h1iscex) and ODC Y (running on h1iscey) for H1.  The MASTER will be used to summarize the ODC information from the corner station ODC channels.  The X will be used for the X end, and the Y for the Y end.  

Stefan has also generated MEDM screens that are available under the sitemap by following: ASC > ODC site overview.  The output channels are displayed at this level, and further details may be seen by digging into the yellow buttons labeled MASTER,Y or X.  

We are filling out the bit labels and setting up the bitmasks needed to compute the summary information, once IPC connections are added.  For now, we also have EPICs parts in place to simulate the signals that would be sent from the subsystem ODCs.  

We added the h1odcx and h1odcy models to the end station ISC front ends (h1iscex and h1iscey). These were added to rtsystab and the DAQ master file. The DAQ was restarted, which also took the new h1susetmx ini files following Jeff's new h1susetmx mode install.

It appeared to have reset back to the default settings. I changed it back to location 15 from 1, to automatic from manual, and from a hold time of 1 sec to 1 minute.

Gains and offsets to center and normalize the signal of the osem between -15000 and 15000 counts have been calculated and are summed up in the summary table above.
Numbers have been entered in the medm and a new safe snapshot has been commited to the svn.
The excel chart E1200343 has been updated as well

After Karen and I cleaned inside the PSL this morning I had a look at the ref cav alignment.  When I started the tpd had 0.5 V, after adjusting mostly pitch it is at 1.18V.  Since this is back to just above what it was 4 weeks ago, I set the resonant threshold back to 0.9V. 

There is currently 8.9mW headed towards the fiber.  I used a fiber feedthrough to conect the two ends of the fiber that go to the ALS fiber distributuion box, and sent the light back into the PSL. Initaly there was 1.9mW coming out of the fiber, I would have expected more of a power increase from friday http:// https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=8193 because of the increase in the ref cav transmission.

I adjusted the alignment of the ALS fiber path and moved the ROC=100mm lens forward by about 1 cm to get 6.2mW out of the fiber, 70 % coupling efficiency. 

The fiber launch PD reading has increased to 0.73 mW, from 0.19 mW, so we should get about 3.8 times more power at the end station than what we measured friday, almost 100 uW.

Since phase 3a ETMX reaction chain transfer functions from thursday night didn't look good, Travis and Betsy went back in chamber on friday and moved back one of the top mass earthquake stop (one blocking the vertical direction). New series of transfer functions have been ran over the week end and are plotted in the attachments.

They now show a good match with the model and LLO measurements and moving the EQ stop definitely improved the results. Although, transverse still doesn't have any coherence with the drive, see second page of 2013-10-18[...].pdf attached

I checked the voltage at the output of the coil driver during the drive of transverse and the signal is clearly there, see image attached.

The attached results are described below :

(1) 2013-10-18[...] = Plot comparing R0 undamped TF phase 3a and the model

(2) allquads_[...] = Comparison between LHO R0 undamped TF phase 3a on friday night (2013-10-18), LHO R0 undamped TF phase 3a on thursday night (2013-10-18)

(3) Image = Screenshot of the drive signal of side osem at gps = 1066192865 (during transverse excitation) at (in red) the excitation test point, and (in blue) the coil driver output. Signals are coherent, meaning the chain between the dac and the coil driver is not broken