Yesterday I modified the end station cal models to add the FPGA duotone signal to the commissioning frame. When analysing the data, I noticed that the non-filtered loop back duotone signal  has a low amplitude. In the attachment below, the red plot is the FPGA duotone signal zoomed at the zero crossing point. This signal has a maximum amplitude of 4000 counts over the whole second. The green plot is the IOP loop-backed duotone, again zoomed in. This plot has a max amplitude of 250 counts, so at the zero crossing the bit noise is apparent. The reduction of the amplitude is due to the difference in the voltage range and bit range of the DAC compared to the ADC (ADC is 16bit, +/- 20V, DAC is 18bit +/- 10V). There is a missing factor of 2, perhaps the differential signal is converted to single ended in the loop-back circuit?

Rick thinks we dont need to do anything for O1 to boost the non-filt amplitude. One solution would be to use additional DAC and ADC channel and perform the loop-back external to the IO Chassis, sending the signal out through a gain to compensate for the amplitude loss.

Ryan F., Duncan M.

Today we have updated the EPICs settings for ODC channel configurations that affect the following channels:

ODC-MASTER
ODC-X
ODC-Y

These changes follow the changes described in the ECR 1500289.

We accepted the changed in the SDF system, and svn committed the change to the safe.snap for ODC-MASTER.

The h1iscex and ey _safe.snap files were backed up prior to the modifications, modified, but not committed.

We also changed the ODC-MASTER EPICs to complete the configuration for the INJection bit reporting.

The Tuesday maintenance day was a bit rough but successful.
CDS will be working on PEM wiring
DtEng commissioning work:
PSL – TTFSS testing and commissioning
           PD power budget
           ISS Outer Loop electronics 

PCAL – End-X clipping investigation

ALS – Diff calibration measurements

PEM – Cabling work on the roof
             Railed sensor at Mid-X


Safety Meeting: 
   John asked the GSA cars be kept available especially during the Tuesday maintenance window for onsite work. All car use must be entered in the log, and the keys returned to the key box when finished with the car. It was stressed NOT to eat or leave food and drinks in the cars, as this attracts rodents to the cars, with rather unpleasant and expensive repairs.      

h1susey BIOS change

Mike Thomas, Dave, Jim:

Mike took detailed photographs of l1susey's BIOS screens. After reviewing them and those of the slower front end computers Jim had some changes to try on h1susey. These were installed and it looks like we have not seen an EY IOP glitch since then.

RCG 2.9.6 upgrade

Rolf, Jeff, Betsy, Jim, Dave:

All front ends were upgraded to RCG 2.9.6. The IPC file was created from scratch. All front end models were restarted. Detailed alog on its way.

PCAL duotone channel to DAQ

Rick, Dave:

the models h1calex and h1caley were modified to write the FPGA duotone channel to the DAQ commissioning frame.

Cosmic Ray Channel to DAQ

Richard, Dave:

h1pemcs was modified to write the TRIG channel from the cosmic ray detector to the science frame.

OBSERVATORY MODE install

Vern, Dave, Stefan:

h1odcmaster was modified to add the H1:ODC-OBSERVATORY_MODE EPICS channel. The associated MEDM screen was added to the SITEMAP under the OPS tag.

ISC IOP model settings

Dave:

The PCAL models at the end stations require the DUOTONE loop back path to allways be engaged. I modified the safe.snap for the models h1iopisce[x,y] to ensure this is so. SDF will altert if they are turned off.

New SUS PI models and DAQ configuration:

Matt, Sheila, Joe B, Dave:

Installed Monday, DAQ configued Tuesday. New h1susetm[x,y]pi models were started in the end station SUS front ends. To avoid the "DAQ too small" error two channels were added at full rate but filled with zeros to minimize impact on commissioning frame size. DEMOD channels were added to DAQ at 4kHz rate.

Other New user models

Hugh, Jeff, Kiwamu, Daniel:

Many user model changes other than those detailed above went in: New ISI models from HAMS and BSC, new ASCIMC model, some SUS models showed a DAQ change (investigation needed), PSL PMC finally applied its 32kHz to 16kHz DAQ channel transition.

DAQ Restart:

Jim, Dave:

The DAQ was restarted to support the above changes. Both frame writers continue to be completely stable.

Restart Log:

The models restart log is attached, due to the RCG upgrade it is lengthy.

Reset the following CDS errors:
H1SUSETMY TIM, ADC
H1SUSETMY TIM
H1SUSTMSY IPC

H1IOPSEIEY IPC
H1ISIETMY  IPC

H1ALSEY IPC
H1ISCEY IPC

H1IOPSUSEX ADC
H1IOPSEIEX IPC

H1ALSEX IPC
H1ISCEX IPC 

Evan, Stefan, Sheila, Matt, Lisa

The official goal of tonight was to make measurements for the ultimate noise budget plot that Evan is about to produce (work still in progress).

The unofficial goal was to improve the sensitivity between 50 - 100 Hz, and investigate  the noise that is obsessing Stefan these days . 

More details will follow tomorrow, but after Tuesday maintenance, three earthquakes and some in principle innocuous but effectively disruptive measurements, we finally managed to relock robustly and make a couple of (alleged) improvements (1/1.5 in Valera's scale of awesomeness):

- despite some recent MICH feed-forward tuning, MICH still had some residual coherence (< 0.3) with DARM between 50 and 100 Hz. We saw room for improving the current cut-off, so Matt added another filter to the LSC-MICH filter bank (FM9, EBS50) which only loses a few degrees of phase at 10 Hz, but provides about 10 dB of attenuation between 50 and 100 Hz. The coherence is now reduced < 0.1 above 50 Hz;

- starting by staring at some recent Bruco reports which showed some suspicious (even if small) coherence with the ASC AS DC signals below 100 Hz, we ended up (re)discovering that the current WFS centering loops ASC_AS_A / AS_AS_B --> OM1 / OM2 have a simple cut-off at 100 Hz (CLP100 in H1ASC-DC4/DC3 P/Y). The existing LP8 filter was not stable, so now there is a new cut-off at 20 Hz (ELF20).

Both these filters have been tested a couple of times during the entire locking sequence, so we leave them on.

We leave the interferometer locked undisturbed ~ 2:15 AM (July 29 9:15 UTC). 

P.S.: For the morning crew, as Sheila reported , the locking sequence doesn't currently work automatically to low noise because the ETMX ESDs are not turning off.

The OM dither lines (around 1.7kHz) are not being used, so I turned them down by a factor of 10.

H1:OMC-ASC_P1_CLOCK_GAIN = 0.1

I'll leave them on to make sure that we don't run into DAC bit-noise problems (e.g., no HF signal gathers the DAC noise around DC, which is not fun).

Occasionally, we ring up the BS butterfly mode (2.5kHz), the BS violins (300 Hz) and something at 41Hz.  What is that thing at 41Hz (which is always present, though usually not so big), and how are we exciting the other BS modes?

We noticed that we can't really turn off the ETMX ESD.  We aren't sure why.  

This causes the guardian to hang, in the state LOWNOISE_ESD_ETMY because it checks that the ESD is off. This can be worked around using manual, but the operator has to be carefull not to skip steps if we force the gaurdian to move on.

[Jenne, StefanB, Cheryl]

We were having some trouble getting the IMC WFS to converge (WFS came on, looked okay for a while, then started dragging the MC transmitted power down), so we implemented and tested the new global burt restore state, accessible from the ISC_LOCK guardian. 

In the end, the specific problem with the IMC WFS was that the ISC input filters on the M3 stage of the MC mirrors (definitely MC1, maybe others) had gain of zero, so the WFS signals weren't getting through to the optics' outputs. 

The solution we created, which should solve all kinds of problems, is a guardian state that does a global burt restore to a recent set of autoburt snapshots. This state has a date and time hard-coded in the guardian script, although it is easily change-able if we find a more preferable time.  Currently, it is restoring to the autoburts of 28 July 2015, 07:10.  To select this state, you need to go to "manual", since there are no edges to get there from any other state.  When it has finished the restores, it will immediately go to and run the Down state. 

The list of snapshots that are restored is:

• lsc
• asc
• omc
• alsex
• alsey
• iscex
• iscey
• pslfss
• psliss
• pslpmc
• ascimc
• susbs
• susetmx
• susetmy
• susitmx
• susitmy
• suspr3
• suspr2
• susprm
• sussr3
• sussr2
• sussrm
• susim
• susmc1
• susmc2
• susmc3
• sustmsx
• sustmsy
• ecatc1plc1
• ecatc1plc2
• ecatc1plc3
• ecatx1plc1
• ecatx1plc2
• ecatx1plc3
• ecaty1plc1
• ecaty1plc2
• ecaty1plc3

Perhaps though, we should just restore *every* snapshot that is captured by autoburt?

For Maintenance this morning I needed to break the IFO lock, so recorded the steps used today.

• ISC_LOCK  - setting ISC_LOCK to DOWN did not break the IFO lock
• requested IMC_LOCK to OFFLINE, but while IMC_LOCK is managed by ISC_LOCK, ISC_LOCK continues to relock the IMC
• setting ISC_LOCK to PAUSE allowed the change of IMC_LOCK to OFFLINE
• IMC_LOCK in EXC was still trying to put MC2 to MISALIGNED, instead of the requested state of SAFE, so was feeding signals to MC2 until IMC_LOCK was set to PAUSE

- Besty, Jeff, TJ, Cheryl