FranciscoL

After one week of having the inner beam centered on the Rx sensor (LHO:78810), on July 09, we moved the beam from center to the right.

This movement was done to double check the changes seen after our move on May 14 (LHO:77840). LHO_XY_Comparison_dataVmodel_1399180506-1404571480.pdf shows the full cycle and nominal results of our series of pcal beam movements, which ended on 24-07-09 @ 08:00 PT. The plot legend shows the value given by the weighted mean of each week using the mean value of each observing stretch for the distribution. The *raw* data for each observing stretch is plotted in gray but, for scaling purposes, some of that data is outside the range of the plot. The black line is what we expected the X/Y comparison to yield from the beam movements that we made. EDITORS NOTE: The vertical axis on the plot is in HOPs (Hundreth of a percent). Although some changes are unexpected, these are not concerning or significant changes that will affect LHO calibration. It is also an ongonig investigation, we are learning as we go.

The movement done in May 14 is seen on the first step of the plot, a week after having both beams centered, where the weighted mean yields a value of 0.99747 – a change of -25 HOPs from the previous week. However, as seen in the model, we expected the line to change by +19.2 HOPs. The rest of the movements *agree* with our model. Further analysis and diagnostics are pending but the main takeaway is that the data does not match the model for this one move, which motivates repeating the measurement.

During this procedure, we used keithley DVM (KVM) 1424277 instead of the FLUKE handheld DVM.

EndStationLog.pdf lists the voltage values after each significant step of procedure T2400163. The steps represent writing down a voltage value after a particular change to the beam position. Some highlights from the recorded values.

• (Both beams) We gained a digit by using the KVM but it fluctuates by ±0.0002V.
• (Target off) Finalized beam movement and recorded the voltage from the Rx sensor with the inner beam only. See InnerBeamAfter.jpg for visual proof of the movement. Voltage of 1.6820V is 10 HOPs lower to previous position (1.6836V). Fine adjustments to pitch and yaw did not improve the amplitude of the signal.
• (Both beams) The measurement was recorded after removing beam block on outer beam and removing the target. See BothBeamsAfter.jpg for the final state of the pcal beams incident on the input port of the Rx sensor. The measurement of 3.3832V is lower by 4 HOPs from the initial measurement (3.3847V).

The KVM was calibrated using a Martel voltage/current calibrator (Martel) after the procedure. The KVM was configured to a range of 10V and a resolution of 6.5 "FAST digits ("FAST" is referred to the time it takes for the ADC on the KVM to integrate; a 6.5 FAST resolution corresponds to an integration time of 16s) . The following table lists the voltages provided by the Martel and the corresponding readings displayed on KVM 1424277.

In summary, (1) using a KVM increased the resolution of our measurements for the beam movement procedure. (2) The 'Initial' measurement changed by 8 HOPs from the last voltage measurement from the previous movement (3.382V), done on July 02 (LHO:78810). (3) The initial and final voltage measurement during today procedure changed by 4 HOPs.

Lockloss @ 07/10 03:37

Lockloss @ 07/10 01:20UTC

07/10 00:29 UTC I took us out of Observing to tune the squeezer since we have now been locked for over three hours.

TITLE: 07/09 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Relock after maintenance day was fairly straight forward, aside from needing to run the baffle align scripts to get light in the xarm. This was maybe expected since EX tripped during DAC card work. Once the IFO was up, there was some excess noise ~25-60Hz, but things are now starting to improve in that area. Our range is still lower than usual, but it's still increasing.

Lock acquisition notes:

• No green light in X arm when starting initial alignment
  • TMSX Test offsets found on, cleared manually. Also found excitations on in that same bank. Odd.
  • Ran baffle align scripts. The end result didn't yield light, but I saw that when dithering ETMX there was a brief bit of light seen. So I only had to scan with ETMX to find it and got locked quickly.
• The rest was fully auto.

LOG:

• 1508 Lock loss to start maintenance
• 2150 Observing                                                                                                                                                                                               

FAMIS 21007

Work done in the enclosure today and last week (including PMC swap and adjustments needed as a result) all show up clearly on this week's trends.

I still see a very slight increase in PMC REFL since last week's PMC swap, which we also saw with the old PMC and informed us about its increasing cavity loss, but now that we've made things a bit more stable, we'll keep an eye on it. PMC REFL was able to get at least a few watts lower than before the PMC swap, so that's promising.

Relevant alogs: 78813, 78839, 78814, and 78979

TITLE: 07/09 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 5mph 5min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY:

Detector Observing at 147Mpc and has been locked for almost 2 hours.

J. Oberling, R. Short

Today we worked to better optimize the PSL's stabilization systems (PMC, FSS, ISS) after last week's PMC swap.

PMC

We found PMC Refl at ~21 W this morning, when we had left it ~23 W at then end of maintenance last week.  The drop is due to the enclosure settling after having the environmental controls on for almost 7 hours (this is normal behavior).  PMC Refl had been drifting between 20 W and 21 W since settling down after our incursion, and we did not see a sharp increase over the last week as we had been seeing with the previous PMC.  This is good news, but we will continue to monitor this as the slow increase in PMC Refl took place over many weeks.

We began by adjusting the operating currents of the PSL pump diodes, as these have a large affect on the output beam quality; this work was done with the ISS OFF.  We had adjusted these while PMC Refl for the old PMC was increasing, so it made sense that they would be off with the new PMC.  We found that this PMC really likes Amp1 to be pumped less and Amp2 to be pumped more.  In the end we had PMC Trans at ~108 W and PMC Refl at ~17.8 W.  The pump diode currents are shown in the first picture and given here:

• I1: 9.0 A
• I2: 8.8 A
• I3: 9.0 A
• I4: 9.0 A

With these pump diode currents Amp1 is outputting ~65.5 W and Amp2 is outputting ~138.0 W (Amp1 output down a little while Amp2 is unchanged).  Interesting note, lowering the pump diode currents for Amp1 (and therefore lowering its output power) did not have a large affect on the output power of Amp2, and increasing the pump diode currents for Amp2 did not have a large affect on its output power but did have a large affect on PMC Refl (0.1 A changes resulted in PMC Refl changes of 1.0 W or more).

We then went to the LVEA and took a TF of the PMC, results shown in the 2nd picture.  UGF is ~1.15 kHz and phase margin is 54.4 degrees.  Also, with the enclosure environmental controls OFF the TF is much smoother than the first one we took after the swap (with the environmental controls still ON).  Good to see things looking better here.  This done we went into the enclosure to tune the ISS and FSS.  In discussion with Jenne we decided to wait on tweaking the mode matching lenses until we have done a PMC sweep to see what our mode content looks like.

ISS

We opened up the ISS box to tweak the power on the two ISS PDs.  The ISS likes the PDs to output 10 VDC, so the ISS box's internal half-wave plate was adjusted until PDB (which usually reads a little higher) was outputting roughly 10 V.  The alignment on each PD was tweaked; PDB was well aligned but PDA was a little off.  After tweaking the alignment both PDs read closer to the same value than they have in a while (the BS that splits the light to both ISS PDs isn't an absolutely perfect 50/50), so that's a nice improvement.  The final PD voltage values are:

• PDA: 9.93 V
• PDB: 9.98 V

This done, we shut the ISS box and moved on to the FSS.

FSS

The FSS tune up was done with the ISS ON and diffracting ~3% (RefSignal set to -1.99 V); this is done to keep measured power levels stable and helps to speed up the alignment (hard to align an AOM when the power is jumping around).  As usual we began by taking a power budget of the FSS beam path, using our 3W-capable Ophir stick head:

• FSS In: 285.6 mW
• AOM In: 283.4 mW
• AOM Out, SP: 194.0 mW
  • SP Diffraction Efficiency: 68.5%
• AOM Out, DP: 133.5 mW
  • DP Diffraction Efficiency: 68.8%
• EOM Out: 131.7 mW

We then set about tweaking the beam alignment to increase both the single- and double-pass diffraction efficiencies, as these are both regularly above 70%.  There was a change in power state between the initial power budget and our adjustments.  We tweaked the HWP WP05, which controls the input polarization of the FSS (WP05 is used in combo with PBS01 to set horizontal polarization w.r.t. the table), and upon re-checking the FSS input power it had "increased" to 292.8 mW.  We've seen this with these little Ophir stick heads before.  Their small size is very convenient for fitting into tight spaces, like found in the FSS beam path, but they come with drawbacks.  They aren't the most stable in the world, and they are VERY angle of incidence dependent; we usually have to spend some time aligning the stick head to the beam to ensure it is as perpendicular as we can get.  My guess is this is what happened here, we thought we had it perpendicular when we did not.  We confirmed our FSS In and AOM in powers made sense and moved on with the alignment.  We tweaked the AOM alignment to increase the single-pass diffraction efficiency, tweaked mirror M21 to improve the double-pass diffraction efficiency, and ensure we were not clipping on the FSS EOM (provides the 21.5 MHz PDH sidebands for locking the RefCav).  Our final power budget:

• FSS In: 292.8 mW
• AOM In: 290.3 mW
• AOM Out, SP: 210.8 mW
  • SP Diffraction Efficiency: 72.6%
• AOM Out, DP: 148.1 mW
  • DP Diffraction Efficiency: 70.3%
• EOM Out: 148.1 mW

We did have to move the EOM a little to re-center its input and output apertures on the beam.  We then adjusted mirrors M23 and M47 (these are our picomotor equipped mirrors) to align the beam to the RefCav using our alignment iris (use M23 to the front of the iris, M47 to the back) and locked the RefCav.  The picomotors were used to tweak up the beam alignment into the RefCav; we started with an initial TPD of ~0.63 V and ended with a TPD of 0.793 V.  The beam alignment on the RefCav RFPD was then checked and tweaked, and we took locked and unlocked voltages for a visibility measurement:

• Unlocked: 1.185 V
• Locked: 0.272 V
• Visibility: 77.0%

The visiblity here is a little lower than its norm, which generally hangs out in the lower-80% range (last couple of FSS tune ups had visibility around 83%).  Best guess here is a combo of mode matching changes (some evidence of the output mode of this PMC being slightly different from the old) and not quite tweaked up alignment (hard to get the alignment really good while in the enclosure with environmental controls on).  Seems there may be some room for mode matching improvement to the RefCav, as both the visibility and TPD are lower than we've usually see after a tune up.  Power in the FSS beam is also a little lower than usual (generally around 300 mW, as seen above it's closer to 290 mW now), which also contributes to this.  This being the best we could do with what we currently have in the time alloted, we left the enclosure.  We'll probably have to do some remote alignment tweaks to both the PMC and RefCav at a later date, once the enclosure is at a better thermal equilibrium.  We left the enclosure ACs running for ~15 minutes to bring the enclosure temperature down to its usual ~71.4 degF temperature (as measured by the Table South temperature sensor), and then put everything in Science mode and left the LVEA.

Once back in the control room we turned the ISS back ON.  It was already diffracting close to 2.5% so we left the RefSignal alone.  Watchdogs were re-enabled and Ryan performed a rotation stage calibration, and we handed things off to TJ for IFO recovery.  This closes WP 11947.

We will continue to monitor PMC Refl with this new PMC over the coming weeks.

Following our work in the PSL enclosure this morning (alog from Jason soon to come), I calibrated the PSL rotation stage since the output of the new PMC had again changed slightly.

The process this time had just a couple of hiccups (steps taken listed in alog74597). For starters, the MoveRotationStage.py script had somehow had its contents deleted last week and was robo-committed to svn that way, so I needed to revert it to the previous revision. Also, I'm not sure how I haven't noticed this before, but Jason pointed out while the rotation stage was stepping through each angle, the maximum power out did not line up exactly with one of the preset angles on the stage, so the maximum power stated by the script is not accurate. I'll think about how to rework thse scripts to produce a more accurate calibration curve.

J. Kissel
WP 11969

The attached screenshot shows the MEDM screen interface for the new routing of the h1iopomc0's ADC0 signals reading out copies of the OMC DCPD A and B ADC voltage at 524 kHz (see discussion of front-end -model implementation in LHO:78956). 
From the sitemap, pull down the "OMC" menu (circled in neon green) and select a new screen link "DCPD TEST" (arrow-ed in magenta)
That opens up the black overview screen which shows the ADC input matrix and the link to the filterbanks (circled in light blue).
That link opens up the screen on the far right of screenshot which displays
    - read only versions of the primary DCPD A0 and B0 524 kHz banks.
    - read only version of the PI DOWNCONV SIG filter 524 kHz bank.
    - The new A1, B1, and A2, B2 filter banks.

You can see these screens are already populated in the configuration I want to test first. These settings are all initialized, monitored, and accepted in the SDF settings.

Maintenance completed just after noon. Ryan and Jason then ran a calibration with the PSL rotation stage and then I started an initial alignment.

We are moving onto DC readout now.

WP 11971

The following cables were disconnected at the feedthrough:

1. H1:ISC-X9-82 (EX)
2. H1:ISC-X10-82 (EY)

Cables are for the in-vacuum picomotors. Picomotors are not used. A shortening plug was installed on the each flange (all pins tied to backshell, backshell tied to chamber ground via mounting screws). Will monitor DARM, PEM ESD VMON,and FScan for improvements.

We cannot make a reasonable assessment of energy deposited in HAM6 when we had the pressure spikes (the spikes themselves are reported in alogs 78346, 78310 and 78323, Sheila's analysis is in alog 78432), or even during regular lock losses.

This is because all of the relevant sensors saturate badly, and the ASC-AS_C is the worst in this respect because of heavy whitening. This happens each and every time the lock is lost. This is our limitation in configuration. I made a temporary change to partly mitigate this in a hope that we might obtain useful knowledge for regular lock losses (but I'm not entirely hopeful), which will be explained later.

Anyway, look at the 1st attachment, which is the trend at around the pressure spike incident at 10W (other spikes were at 60W, so this is the mildest of all). You cannot see the pressure spike because it takes some time for the puffs of gass molecules to reach the pirani.

Important points to take:

• Marker shows when the Fast Shutter was actually fired, which is witnessed by GS13 (bottom left).
• ASC-AS_C cannot be relied on. It started saturating badly even before the FS fired (look at INMONs, 3rd from the top, left), and it kept saturating for a long time.
• OMC QPDs cannot be relied on. They started saturating at about the same time as AS_C though they seem to have stopped saturating earlier  (2nd from the bottom, left).
• AS_B and AS_C cannot be relied on. They're much better than AS_C and OMC QPDs, they started railing some milliseconds earlier than the FS, but they railed (right middle for SUM, one below that for INMONs).
  • But the beam was NOT clipped by the Fast Shutter after it closed as the power dropped to zero, we can see that after WFS stopped saturating.

This is understandable. Look at the second attachment for a very rough power budget and electronics description of all of these sensors. QPDs (AS_C  and OMC QPDs) have 1kOhm raw transimpedance, 0.4:40 whitening that is not switchable on top of two stages of 1:10 that are switchable. WFSs (AS_A and AS_B) have 0.5k transimpedance with a factor of 10 gain that is switchable, and they don't have whitening.

This happens with regular lock losses, and even  with 2W RF lock losses (third attachment), so it's hard to make a good assessment of the power deposited for anything. At the moment, we have to accept that we don't know.

We can use AS_B or AS_A data even though they're railed and make the lower bound of the power, thus energy. That's what I'll do later.

(Added later)

After TJ locked the IFO, we saw strange noise bump ffrom ~20 to ~80 or so Hz. Since nobody had any idea, and since my ASC SUM connection to the PEM rack is an analog connection from the ISC rack that also has the DCPD interface chassis, I ran to the LVEA and disconnected that.

Seems like that wasn't it (it didn't get any better right after the disconnection), but I'm leaving it disconnected for now. I'll connect it back when I can.

WP11970 h1susex 28AO32 DAC

Fil, Marc, Erik:

Fil connected the upper set of 16 DAC channels to the first 16 ADC channels and verified there were no bad channels in this block. At this point there were two bad channels; chan4 (5th chan) and chan11 (12th chan).

Later Marc and Erik powered the system down and replaced the interface card, its main ribbon cable back to the DAC and the first header plate including its ribbon to the interface card. What was not replaced was the DAC card itself and the top two header plates (Fil had shown the upper 16 channels had no issues). At this point there were no bad channels, showing the problem was most probably in the interface card.

No DAQ restart was required.

WP11969 h1iopomc0 addition of matrix and filters

Jeff, Erik, Dave:

We installed a new h1iopomc0 model on h1omc0. This added a mux matrix and filters to the model, which in turn added slow channels to the DAQ INI file. DAQ restart was required.

WP11972 HEPI HAM3

Jim, Dave:

A new h1hpiham3 model was installed. The new model wired up some ADC channels. No DAQ restart was required.

DAQ Restart

Erik, Jeff, Dave:

The DAQ was restarted soon after the new h1iopomc0 model was installed. We held off the DAQ restart until the new filters were populated to verify the IOP did not run out of processing time, which it didn't. It went from 9uS to 12uS.

The DAQ restart had several issues:

both GDS needed a second restart for channel configuration

FW1 spontaneously restarted itself after running for 9.5 minutes.

WP11965 DTS login machine OS upgrade

Erik:

Erik upgraded x1dtslogin. When it was back in operation the DTS environment channels were restored to CDS by restarting dts_tunnel.service and dts_env.service on cdsioc0.

Lockloss @ 07/09 01:46UTC after 8.5 hours locked

Bruco ran for last night's 159MPc range (instructions from Elenna), using command below. Results here.

python -m bruco --ifo=H1 --channel=GDS-CALIB_STRAIN_CLEAN --gpsb=1404222629 --length=1000 --outfs=4096 --fres=0.1 --dir=/home/camilla.compton/public_html/brucos/GDS_CLEAN_1404222629 --top=100 --webtop=20 --plot=html --nproc=20 --xlim=7:2000 --excluded=/home/elenna.capote/bruco-excluded/lho_DARM_excluded.txt

Can see:

• CHARD_P is bad 10-30Hz and CHARD_Y is very bad < 25Hz
• PRCL bad coherence 10-20Hz 
• SRCL looks good and MICH only has a little coherence 10-20Hz 
• OMC ASC signals dominate <16Hz, maybe this is expected....  
• HAM1 signals are high 10-30Hz, from PRCL coupling?