Keita, Kiwamu,

We updated the lists of the sceice frame channels on the LSC, OMC and ASCIMC models. This means that we edited the following master blocks:

• asc/common/models/ASCIMC_MASTER.adl
• lsc/common/models/lsc.mdl
• lsc/common/models/lscimc.mdl
• omc/common/models/omc.mdl
• omc/common/models/omclsc.mdl

Then we recompiled, reinstalled and restarted the three models. Additionally, burtrestored them back to 10:10 PT of this morning. After we double-checked the ini files to make sure that the right channels were selected, we checked in the above common blocks to the SV

Additionally, we added commissioning frame for the EOM driver signals such as LSC-MOD_RF9_AM_ERR and etc

The followings are lists of the science frame channels after the update. Note that we did not edit ALSEX or ALSEY but they are listed for completeness:

kiwamu.izumi@opsws5:/opt/rtcds/lho/h1/chans/daq$ grep -B 1 "^acquire=3" H1LSC.ini | grep DQ
[H1:IMC-F_OUT_DQ]
[H1:IMC-I_OUT_DQ]
[H1:IMC-L_OUT_DQ]
[H1:IMC-REFL_DC_OUT_DQ]
[H1:IMC-TRANS_OUT_DQ]
[H1:LSC-ASAIR_B_RF90_I_ERR_DQ]
[H1:LSC-MCL_IN1_DQ]
[H1:LSC-MCL_OUT_DQ]
[H1:LSC-MICH_IN1_DQ]
[H1:LSC-MICH_OUT_DQ]
[H1:LSC-ODC_CHANNEL_OUT_DQ]
[H1:LSC-POPAIR_B_RF18_I_ERR_DQ]
[H1:LSC-POPAIR_B_RF90_I_ERR_DQ]
[H1:LSC-POP_A_LF_OUT_DQ]
[H1:LSC-POP_A_RF45_I_ERR_DQ]
[H1:LSC-POP_A_RF45_Q_ERR_DQ]
[H1:LSC-POP_A_RF9_I_ERR_DQ]
[H1:LSC-POP_A_RF9_Q_ERR_DQ]
[H1:LSC-PRCL_IN1_DQ]
[H1:LSC-PRCL_OUT_DQ]
[H1:LSC-REFL_A_LF_OUT_DQ]
[H1:LSC-REFL_A_RF45_I_ERR_DQ]
[H1:LSC-REFL_A_RF45_Q_ERR_DQ]
[H1:LSC-REFL_A_RF9_I_ERR_DQ]
[H1:LSC-REFL_A_RF9_Q_ERR_DQ]
[H1:LSC-REFL_SERVO_ERR_OUT_DQ]
[H1:LSC-REFL_SERVO_SLOW_OUT_DQ]
[H1:LSC-SRCL_IN1_DQ]
[H1:LSC-SRCL_OUT_DQ]
 

kiwamu.izumi@opsws5:/opt/rtcds/lho/h1/chans/daq$ grep -B 1 "^acquire=3" H1OMC.ini | grep DQ
[H1:LSC-DARM_IN1_DQ]
[H1:LSC-DARM_OUT_DQ]
[H1:LSC-REFL_SERVO_CTRL_OUT_DQ]
[H1:OMC-ASC_ANG_X_OUT_DQ]
[H1:OMC-ASC_ANG_Y_OUT_DQ]
[H1:OMC-ASC_P1_I_OUT_DQ]
[H1:OMC-ASC_P2_I_OUT_DQ]
[H1:OMC-ASC_POS_X_OUT_DQ]
[H1:OMC-ASC_POS_Y_OUT_DQ]
[H1:OMC-ASC_Y1_I_OUT_DQ]
[H1:OMC-ASC_Y2_I_OUT_DQ]
[H1:OMC-DCPD_A_OUT_DQ]
[H1:OMC-DCPD_B_OUT_DQ]
[H1:OMC-DCPD_NULL_OUT_DQ]
[H1:OMC-DCPD_SUM_OUT_DQ]
[H1:OMC-LSC_DITHER_OUT_DQ]
[H1:OMC-LSC_I_OUT_DQ]
[H1:OMC-LSC_SERVO_OUT_DQ]
[H1:OMC-ODC_CHANNEL_OUT_DQ]
[H1:OMC-PZT1_MON_AC_OUT_DQ]
[H1:OMC-PZT1_MON_DC_OUT_DQ]
[H1:OMC-PZT2_MON_AC_OUT_DQ]
[H1:OMC-PZT2_MON_DC_OUT_DQ]
 

kiwamu.izumi@opsws5:/opt/rtcds/lho/h1/chans/daq$ grep -B 1 "^acquire=3" H1ASCIMC.ini | grep DQ
[H1:IMC-DOF_1_P_IN1_DQ]
[H1:IMC-DOF_1_Y_IN1_DQ]
[H1:IMC-DOF_2_P_IN1_DQ]
[H1:IMC-DOF_2_Y_IN1_DQ]
[H1:IMC-DOF_3_P_IN1_DQ]
[H1:IMC-DOF_3_Y_IN1_DQ]
[H1:IMC-DOF_4_P_IN1_DQ]
[H1:IMC-DOF_4_Y_IN1_DQ]
[H1:IMC-DOF_5_P_IN1_DQ]
[H1:IMC-DOF_5_Y_IN1_DQ]
[H1:IMC-IM4_TRANS_PIT_OUT_DQ]
[H1:IMC-IM4_TRANS_SUM_OUT_DQ]
[H1:IMC-IM4_TRANS_YAW_OUT_DQ]
[H1:IMC-ISS_QPD_PIT_OUT_DQ]
[H1:IMC-ISS_QPD_SUM_IN1_DQ]
[H1:IMC-ISS_QPD_SUM_OUT_DQ]
[H1:IMC-ISS_QPD_YAW_OUT_DQ]
[H1:IMC-MC1_PIT_OUT_DQ]
[H1:IMC-MC1_YAW_OUT_DQ]
[H1:IMC-MC2_PIT_OUT_DQ]
[H1:IMC-MC2_TRANS_PIT_OUT_DQ]
[H1:IMC-MC2_TRANS_SUM_OUT_DQ]
[H1:IMC-MC2_TRANS_YAW_OUT_DQ]
[H1:IMC-MC2_YAW_OUT_DQ]
[H1:IMC-MC3_PIT_OUT_DQ]
[H1:IMC-MC3_YAW_OUT_DQ]
[H1:IMC-ODC_CHANNEL_OUT_DQ]
[H1:IMC-PWR_IN_OUT_DQ]
[H1:IMC-PZT_PIT_OUT_DQ]
[H1:IMC-PZT_YAW_OUT_DQ]
[H1:IMC-WFS_A_DC_PIT_OUT_DQ]
[H1:IMC-WFS_A_DC_SUM_OUT_DQ]
[H1:IMC-WFS_A_DC_YAW_OUT_DQ]
[H1:IMC-WFS_A_I_PIT_OUT_DQ]
[H1:IMC-WFS_A_I_YAW_OUT_DQ]
[H1:IMC-WFS_A_Q_PIT_OUT_DQ]
[H1:IMC-WFS_A_Q_YAW_OUT_DQ]
[H1:IMC-WFS_B_DC_PIT_OUT_DQ]
[H1:IMC-WFS_B_DC_SUM_OUT_DQ]
[H1:IMC-WFS_B_DC_YAW_OUT_DQ]
[H1:IMC-WFS_B_I_PIT_OUT_DQ]
[H1:IMC-WFS_B_I_YAW_OUT_DQ]
[H1:IMC-WFS_B_Q_PIT_OUT_DQ]
[H1:IMC-WFS_B_Q_YAW_OUT_DQ]
 

kiwamu.izumi@opsws5:/opt/rtcds/lho/h1/chans/daq$ grep -B 1 "^acquire=3" H1ALSEX.ini | grep DQ
[H1:ALS-X_ODC_CHANNEL_OUT_DQ]
[H1:LSC-X_ARM_OUT_DQ]
[H1:LSC-X_TIDAL_OUT_DQ]
 

kiwamu.izumi@opsws5:/opt/rtcds/lho/h1/chans/daq$ grep -B 1 "^acquire=3" H1ALSEY.ini | grep DQ
[H1:ALS-Y_ODC_CHANNEL_OUT_DQ]
[H1:LSC-Y_ARM_OUT_DQ]
[H1:LSC-Y_TIDAL_OUT_DQ]
 

JimW, HughR

We took all the SEIs down with guardian.  Ran foton -c foton hepifile and then loaded the modified file.  Re-isolated all platforms.

Leo, Jeff
Some charge measurements was done on both ETMs.
We found ETMX ESD driver non functional, Betsy fixed it (see 20203)
Measurements results are in attachments. For most quadrants we have the same trend as discussed in 20067

The guardian core and cdsutils packages were upgraded today:

• guardian: r1485
• cdsutils: r494

After a couple of small issues were ironed out, the guardian machine was rebooted and all nodes are up and running with the new versions:

Notable fixes/features in the new version:

guardian:

• fix handling of jumps in MANUAL mode: jumps are ignored and treated as if the state had returned True (does not leave state)
• managers: add STATUS and STALLED node channels; Node.done property returns True if state is "DONE"
• import mechanism was fixed so that all code imports are properly registered and committed to the archive
• removed MANAGED button from main overview screen (was determined that it wasn't used and was more confusing than not.  It's still available from the STATES screen.)
• "guardlog -x" will open a standard guardlog xterm window
• NOMINAL states are no longer required to be requestable
• better exception handling for connection errors: NDS connection errors should produce CERROR, which should clear up on their own after the server comes back.

cdsutils:

• ezca, nds, better connection exception handling
• gpstime: add "parse" classmethod that can parse arbitrary time/date specifications
• added gpstime cli that can return local, UTC, and GPS times for arbitrary time/date specification

FRS3410. Jenne, Jim, Carlos, Dave

Jenne found that certain digital cameras were not snapshotting correctly. After power cycling the digital video servers and the ITMX spool camera, we tracked the problem down to the "Frame Type" setting in the digital video configuration file. The cameras which fail their tiff snapshotting have this setting set to "Mono12", those which work have "Mono8"

In fact the majority of cameras are set to "Mono8", listing is below.

Question to the digital video experts, what does this setting mean and what have we broken by reverting back to "Mono8"?

THIS TIME, the fix that is suggested by Richard as a comment lower in the alog 19487 worked:

"powered the unit off, removed the DAC cable, powered the unit on, reattached the DAC cable and all seems to be working.

J. Oberling, P. King

Today we measured the OLTF of the ISS inner loop and the PMC.  This was done in response to LLO's recent measurement of the same documented here.  Peter has all the TF data and will post it as a comment to this report.  For the ISS inner loop, the gain was changed from 6dB to 16dB in the last couple of days, so we measured the TF at 6dB and at 16dB of gain to see how the increased gain changed things.  For the PMC we ended up increasing the gain to 22dB (up from 18dB).  This brought the UGF to ~7.5 kHz, closer to what we expect from E1200385.

I also had a chance to turn off the ISS without disturbing anything else and calibrate the 2 PDs discussed in alog 20043, and therefore complete the work in WP 5391.  The new gain values for the these PDs are as follows:

• PD_AMP: 0.00349223
• PMC_TRANS: 0.0103

Jim Batch, Carlos Perez

The newer faster h1susey computer has been replaced with the more stable original h1susey computer.  The h1susetmy model is still running within the 60uS window, but not by much.  We will be watching this to see if there are problems that arise over the next week.  Also, the h1susetmypi models runs well within it's maximum time, so no problems are anticipated with that model.

I've added the rest of the SUSes to the SUS guardian overview screen such that it is easier to quickly see the state of each SUS guardian (very useful for Tuesdays).

Recall that this screen is found via the GRD drop down from the site map.

(Jenne, Fil)

The slow controls interface for the EOM drivers is now up and running. The attached screen shot shows the remote controls screen. RF power can be adjusted between 4dBm and 27dBm in 0.2dB steps. On the unit the remote switch must be set to External, the excitation switch be set Off and the RF power switch to On. 

Fast channels are available under H1:LSC-MOD_RF9/45_AM with filter modules ERR, CTRL (in loop), AC and DC (out of loop).

Cables have been pulled to the PSL, but the unit we have is not connected yet.

Timing monitors for the 1 PPS signals have been added. Each signal channel has a nominal and tolerance field as well as an out-of-range flag. A screen shot is attached.

As per alog 20169 all the ISI models were restarted with the new WD saturation updates.

J. Kissel, B. Weaver

We've restarted all SUS models to install the changes described in LHO aLOG 20177. Betsy is going through the IFO_ALIGN screen cap found in LHO aLOG 20187 and restoring alignment offsets.

Aug  4 07:54:42 h1conlog1-master conlog: ../conlog.cpp: 301: process_cac_messages: MySQL Exception: Error: Incorrect string value: 'xFBxFFxFF@' for column 'value' at row 1: Error code: 1366: SQLState: HY000: Exiting.

Jenne, Nergis, Stefan


We hooked up monitoring points for measuring the 9MHz and 45MHz RIN going into the interferometer.

Here is the rig:
9MHz:
 - We inserted a 10dB coupler into the 9MHz cable feeding the EOM. This dropped the drive signal from 4.7Vpkk to 4.5Vpkk - small enough the interferometer didn't care.
 - It's output we directed into a two-way splitter, and fed both signals into a level 1 mixer.
 - The output was low-passed through a 10MHz low pass.
 - This gave us a DC level of 0.195V, and a noise of ~4.9nV/rtHz, resulting into a RIN of 2.5e-8.
 - We hooked it up to an SR560 (Gain=1e4, AC coupled, band-passed with poles at 300Hz and 30kHz), and stuck it into LSC-EXTRA_AI_1 (IOP-LSC0_MADC2_TP_CH8)
 - the ADC gain is 16384cts/10V

45MHz:
 - We used the two remaining spare spigots of the 45MHz distribution rack, and mixed them in a level 3 mixer.
 - Low-passed at 15MHz, we got a DC level of 0.57V, and a noise level of 120nV/rtHz...
 - ... resulting in an outrageous RIN of 2e-7/rtHZ
 - Again into an SR560 (Gain=1e3, AC coupled, band-passed with poles at 300Hz and 30kHz)
 - and into LSC-EXTRA_AI_2 (IOP-LSC0_MADC2_TP_CH9)

Plot 1 shows the RIN measured through the digital system
Calibration: LSC-EXTRA_AI_1 (IOP-LSC0_MADC2_TP_CH8): Gain=9.39e-5; p= 1, 728.178 65532    ; z= 300, 30000, 10062, 4973.6 9356.4, 33157, 426840 (dtt notation)
Calibration: LSC-EXTRA_AI_2 (IOP-LSC0_MADC2_TP_CH9): Gain=3.21e-4; p= 1, 728.178 65532    ; z= 300, 30000, 10062, 4973.6 9356.4, 33157, 426840 (dtt notation)

Note: the AA chasis itself has p= 728.178 65532    ; z= 10062, 4973.6 9356.4, 33157, 426840 (dtt notation)

Next Evan locked the interferometer, and we found a coherence of 0.9 between the 45MHz RIN (IOP-LSC0_MADC2_TP_CH9) and  ASC_AS_C (IOP-ASC0_MADC6_TP_CH11) - this was oue best monitor for mystery noise.... BINGO

We also calibrated OMC_DCPD_A (IOP-LSC0_MADC0_TP_CH12) in Amps (today the whitening filters were off):
Calibration:Gain=7.726e-7; p= 7.689, 7.689, 728.178 65532    ; z= 78.912, 90.642, 13700, 17800, 10062, 4973.6 9356.4, 33157, 426840  (dtt notation)

The noise level in OMC_DCPD_A was 7e-8mA/rtHz. Shot noise would be 5.7e-8mA/rtHz at 10mA.

Using the coherence between OMC_DCPD_A and RF45 RIN we estimated the ransfer function to be about 9e-5 A/RIN per photo diode. (Plot2)

This let's us estimate the RF45 RIN contribution: 9e-5 A/RIN * 2e-7RIN/rtHz = 1.8e-8mA/rtHz. Very close to the 1.4mA/rtHz estimated in alog 19856.

We are a bit puzzled by the fact that this doesn't seem enough the explain the full elevated noise in DCPD_A: sqrt(1.8^2 + 5.7^2) = 6.0 < 7  (everything x1e-8mA/rtHz). (Plot3)

Plot 4 shows the coherence (ignore below 300Hz - the interferometer wasn't completely in low noise mode.