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.
Note, a trend shows this railed negative at almost 1am last night (Aug 4, 07:47 UTC)
I don't remember the exact time but sometime before ~midnight last night, Sheila and I had found the ETMX ESD driver railed negative, and drove to the end station to fix it. All we did was power cycle the box - no cable plug/unplugging, and it came back for us.
Sorry we didn't log this last night. We left around 12:30am, so the railing that Betsy mentions happened when no one was on site, although we left the guardian request somewhere in a fully-locked state (probably Nom. Low Noise).
We don't see button pushing which would have lead to the rail in the middle of the night last night... see attached 24 hour plot.
In talking to Sheila, she fesses up to having an ETMx ESD neg rail earlier at ~11pm (shown on the plot if you look closely), which they caught and went down to Ex to clear in the same manner as above. They left just before it railed neg again - hence the no-auto-locking from then on.
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:
Attached is the measured pre-modecleaner OLTF. Two values of gain slider were used. The initial one, 18 dB was where it was set to when we started the measurements. To increase the UGF we increased the gain to 22 dB. With the gain slider at 18 dB, the UGF is ~3.56 kHz with a phase margin of 70 deg. With the gain slider at 22 dB, the UGF is 7.7 kHz with a phase margin of 75 deg. We could push the gain a bit higher but that comes at the cost of robustness.
Attached is the first loop OLTF. It should be noted that this measurement was performed whilst Robert and Cheryl were working inside the PSL Enclosure and so the HEPA fans were on (ditto for the PMC measurement). Plots are for the old value of gain slider and for the current value. Currently the UGF is about ~65 kHz with a phase margin of ~25 deg. The measurements are consistent with those taken around the time installation was completed and more recent measurements done by Kiwamu and Sudarshan. We took a high frequency measurement but unfortunately the results don't seem right.
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.
Attached are the plots for the temperature and RH data for the Dry Box storage containers #1 & #4 (Box 2 & 3 are empty) from July. Data shows both cabinets functioning as expected. There was no data from the desiccant cabinet in the LVEA due to a sensor programming error. This problem has been corrected.
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.
Test stand also stopped: Aug 4 07:54:43 conlog-test-master conlogd: ../database.cpp: 661: insert_dbr_string_value_execute: Error executing m_p_insert_dbr_string_value_prep_stmt. Parameters: H1:SYS-MOTION_C_PICO_F_MOTOR_1_NAME, 1438700082050871034, 0, รณ#001, 0, 0. Aug 4 07:54:43 conlog-test-master conlogd: ../conlog.cpp: 314: process_cac_messages: MySQL Exception: Error: Incorrect string value: 'xF3x01' for column 'value' at row 1: Error code: 1366: SQLState: HY000: Exiting.
Restarted
I found the IFO struggling to keep the IMC locked through ALS lock acquisition. It appears as through the ISS and FSS are struggling this morning; attached are screen shots of the FSS and ISS screens before I took the IMC to DOWN, one can see the ISS diffracted power suddenly jump to ~10%. Not sure what's going on there. But good to know that we are having troubles with the ISS *before* we're going into the PSL, so we don't blame the team going in for causing the problems during recovery! Beginning maintenance day prep at 14:10 UTC (7:09 PDT) by bring ISC_LOCK to DOWN. Because the ISC_LOCK guardian was still transitioning, as opposed to in NOMINAL_LOW_NOISE, (and maybe because DOWN has become a goto again? LHO aLOG 20134 leaves it unclear if LHO aLOG 20125's changing the DOWN state to a goto has been reverted. The current ISC_LOCK graph shows that it *has* been reverted.) Also, I ran the OFFLOAD WFS script before bringing the IMC to OFFLINE. Strangely, the IMC lost lock during this process and it took ~1.5 minutes of flashing before it recovered. However, the IFO align screen has been captured with the IMC locked and well aligned, and the ISC_LOCK guardian is down,
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.
We removed the the 9MHz RIN setup, but left the (cleaner) 45MHz one in place. We also verified that the RIN is bad right out of the frequency multiplier. Is that unit simply broken? if so - can we just get a spare?
For reference, the harmonics generator is specked to have an amplitude noise of −150 dBc/Hz at 100 Hz: https://awiki.ligo-wa.caltech.edu/aLIGO/HarmonicGenerator
The ISS at the output of the IMC won't see RF AM, since it is fundamentally phase modulation. It will change the ratio between carrier and RF sideband strength. However, once the RF sidebands are stripped off by the OMC, we are left with just the fluctuations on the carrier. We can calculate the RIN of the carrier in the presence of RF AM with:
A few months ago, Kiwamu and I set some of the images to mono12, because 12 bit images have a slightly better SNR than the 8 bit images. We can switch them all back to mono8, except for the green ITM cameras, which we use for beam position refercences. It might be better if we didn't change those settings (ie keep the ITM green cameras set to mono 12.)
Fewer programs will open the 12 bit images than 8 bit images, but you can open them in python or matlab. Attached is a matlab script for opening the mono12 images, for them what don't want to write their own.