[Evan, Jenne, JimW]

We turned the ITM pitch oplev damping back on, set some QPD offsets for POP and transmons, and were able to go to 20W without trouble.  We have finally made it to nominal low noise for the first time in weeks!  Hooray!  Sadly, a 2.84Hz oscillation killed us after about 10 seconds.  Work continues, but I was excited enough to write an alog.

1555 -1635 hrs. local -> To and from Y-mid 

Recent conditions -> 60F - 75F days, Dewar ~40% full vapor pressure 14 psi, LLCV 18% open 

[Executed nominal procedure as was practiced for 48 hour over-fill intervals] 

LN2 at exhaust after 32 min 30 seconds with LLCV bypass 1/2 turn open and exhaust check valve bypass open 

Next scheduled over-fill to be Monday, April 4th before 4pm local.  

NOTE: Need to revisit agreement between Dewar's local mechanical level gauge and value indicated by CDS.  Also, recommend adopting new default for LLCV bypass X turns open for new 72 hour over-fill interval (something more open than previous default of 1/2 turn open).  

We're looking at replacing the HWS code which is compiled in MATLAB (and quite incompatible with newer versions on Ubuntu) with a more streamlined, Python-based version. The test bed for this is H1HWSEY.

So far, we have tested the following:

• Dave has succesfully installed Ubuntu 14.04 and the EDT (frame grabber card) drivers on the machine
• Once the EY HWS is turned on, I can log into H1HWSEY, run serial_cmd and succesfully connect to the internal menu system of the camera
• Can acquire an image from the camera and save it to file with the take command
• Downloaded python_code from HWS_SVN into /home/controls to test the running to the Python code on this in-situ machine
  • Final installation directory of python code still needs to be established

Need to install EPICS/ PYEPICS ancd CDS tools.

State of H1: unlocked for 3.5 hours due to an earthquake

Activities since mid-day update:

• 19:30 Kyle started a pump cart by HAM4/5
• 20:46 ITMY Hardware Watchdog Tripping verbal alarm
• --- FYI: ITMY Hardware Watchdog is NOT hooked up to ITMY, but the sensor is live and reading a signal real-time
• --- when I opened the MEDM, the sensor was red and then went green again - NOT it's expected behavior, so Dave's looking into it
• 21:09 Ed to LVEA - vent prep, out at 21:18
• 21:09 Kyle - out of LVEA
• 21:10 Keita-Jenne to LVEA - checking HAM6 racks - 21:33 done
• 21:30 Hugh - updating ISI models
• 22:33 final checks before restarting the DAC - Dave, Hugh, JeffK - DAC restart successful
• 22:50 Kyle to MY, CP3 fill
• 22:50 PSL ISS Diffracted power was low - around 6% - raised to 8%
• 22:50 Jenne starting an Initail Alignment, to assess where H1 alignment is at after being down for 3 hours due to an earthquake

Currently Activity: Jenne is looking at the alignment

See the attached for an incorrect syntax and the correct way to direct the front end to save the channels in the Science Frames.

The asterisk placed after the desired science frame rate makes the rate interpreted incorrectly.  Since it did not know what to do with 1024*, it was storing the channel in the commissioning frames at 4096 and not at all in the science frames.  The asterisk on the channel name is the correct way to go.  The directions are all there, I just failed to look closely.  I should have learned the necessity of doing so after all these years.

The modification was to a library part so the edits at least were not extensive.  The change is committed:

hugh.radkins@opsws1:models 0$ svn commit -m "Corrected syntax error in frame storage"
Sending        models/ISI_to_SUS_library.mdl
Transmitting file data .
Committed revision 13015.
hugh.radkins@opsws1:models 0$ pwd
/opt/rtcds/userapps/release/isi/common/models
 

After Jeff and Hugh made their fixes to all the ISI models and restarted them, I did a DAQ restart.

The restart was normal except that h1fw1 did not come back. It had tried to restart its daqd process, and then kernel panic'ed similar to Wednesday evening's crash (VFS count 0). I reset the machine by pressing the front panel RESET button, it all came back normally after that.

Remember that since the h1susex and h1susey computers were upgraded to faster models (but still running the 2.6 kernel and 2.9.6 RCG), the sus model timing error rate was reduced but no zero'ed.

I have trended 30 days of FEC-88 (SUS ETMX) and FEC-98 (SUS ETMY) STATE_WORD starting 31 days ago, to determine the rate or TIM (second bit) and ADC (third bit) errors.

h1susetmx had 36 TIM errors and 1 ADC error. 37 errors in 30 days = average of 1 error per 20 hours.

h1susetmy had 125 TIM errors and 1 ADC error. 126 errors in 30 days = average of 1 error per 5.8 hours.

The process to gather the data is to use the command line nds1 client to give the MAX channel minute trend. A python script then masks out the upper bits from the STATE_WORD, so the overflows and CFC bits are discarded.

[Keita, Jenne]

We have recorded the label of each cable connected to ISCT6.  Anyone may feel free to disconnect all of the cables at any time on Monday morning, to facilitate the moving of the table. 

Attached is the set of cable labels, and where they are.

Current (2:43pm local) pressures (Torr):

PT-243: 1.07e-9
PT-244: 1.40e-9
PT-210: 1.42e-9

~1230 hrs. local -> Started pump cart 
~1255 hrs. local -> Began pumping BSC4 annulus volume -> No change in PT140B resulted 

1 April 2016

Site Activities:

15:45 JeffB - LVEA - 3IFO

15:53 JeffB - out of LVEA

15:20 Kirshna, Michael - EY BRS-2

17:20 Chandra and Kyle - hook up pump cart to BSC4

17:56 Kyle-Chandra - craning pump cart to prime location (West crane, will restore crane parking)

19:30 all but Kyle out of the LVEA

H1 Activities:

15:20 Aiden, DaveB - EY Hartman testing code

17:25 COMM PLL red - not sure why, resolved after QPD offsets set

17:25 EX QPD offsets - Evan measuring Dark Offsets, since new hardware was installed

17:30 hartman EY epics not working - Dave and Aidan working on it

19:30 H1 attempting to lock DRMI, no known issues to prevent full lock

20:00 earthquake, 6.1, Papua New Guinea, guardian in Down

The PI AA/BP Chassis was reinstalled at EX this morning. No issues found with chassis, see alog 26351. Unit was left powered on, as not to pull down the TMS QPS's signals.

Unit installed in Rack SUS-C2, slot U21.

Using a power budget for IOT2L at input power to the IMC of 1W (alog 9331), which measured 12mW on REFL PD, and a modification to the IMC REFL path HWP (alog 9521) for IMC input power of 10W, which maintained the power on REFL PD of 12mW, I've calculated the power REFL PD saw in O1 at 22W IMC input, and will potentialy see in O2 at 50W.  Summary below.  Chart attached.

O1 numbers, 22W:

• REFL PD 27mW
• WFSA 13mW
• WFSB 11mW

Potential O2 numbers, 50W:

• REFL PD 61mW
• WFSA 30mW
• WFSB 26mW

Pressure profiles over 1 day and 60 day attached

Current pressures (Torr):

PT-243:  1.05e-9
PT-244:  1.35e-9
PT-210:  1.35e-9

The HAM ISI model updates Tuesday, alog 26321, allow the suspension motion calculation to be done by the ISI.  The filters and matrices to convert from ISI GS13 cartesian basis to the optic euler basis are now filled.

The BSC ISIs were updated for this earlier in the month.  Alogs: original model updates-25913, ISI vs SUS calibration filter- 25993, mods for multi sus plarforms- 26117, library part cleanup/corrections- 26128, BSC filters & matrices populated- 26132, svn commits- 26143.

DetChar can now start pointing to these ISI computations.  Look at channels: H1:ISI-{isi platform}_SUSPOINT_{suspension}_EUL_{euler dof}MON.

euler dof is L, T, V, R, P, orY

isi platform is HAM2, 3,..6, ETMY, ETMX,..,BS

suspensions available are ETMY, TMSY, ETMX, TMSX, ITMY, ITMX, BS, MC1, MC2, MC3, PRM, PR2, PR3, IM1, IM2, IM3, IM4, SRM, SR2, SR3, OMC.  Of course you have to get the suspension on the correct isi platform.

Attached is a snapshot of the medms: the GS13 filter bank and available suspension calcs are accessed from the ISI Chamber overview; the transformation matrices are accessed from the calc screen.

We've had much more success tonight with the non-broken Xarm Trans QPD.  We once again re-centered the spots on the ETMs, although they didn't need much moving.  We are able to sit at 10W and 12W just fine now.  Now, we're running into regular ol' loop oscillations, so we've been measuring loops at different powers, and trying to re-tune them. 

CHARD Y seemed the most egregious, so we created a new control and boost filter combo, which live in FMs 4 and 5.  Unfortunately, these filters are totally unuseable at 2W, although they improve our stability at 10W, so right now the guardian still only engages the old loop shape filters.  We'll have to re-think the 2W filter situation to make sure we can transition between these filters.  Right now, we were by-hand turning off the CHARDY loop, changing the filters, then re-engaging the loop.  Attached is an open loop gain for the new loop.

PRC2 pitch we've decided is kind of okay if we use a factor of 2 less gain.

Now, we're seeing oscillations that also show up in AS 90, so we suspect either the MICH or SRC angular loops.  Unfortunately, there's something going on with NDS/the lockloss plotter/something, such that I can't get data from the last ~5 locklosses.  The ones before that, I can still get and plot, but it can't find data for the last several even if it's been an hour since that lockloss. 

So, next up:  Measure the MICH and SRC loops at 10W to see if they're close to unstable.  Measure again at 15W, and then think about going from there.

Darkhan, Kiwamu,

We found that the optical follower servo (aka OFS) for the Pcal Y had stopped running. Pressing around some buttons on the medm screen, we could not make it back up running. We are suspecting some kind of hardware issue at the moment. According to trend data, it seems that it stopped running at around 18:30 UTC on Mar 18th for some reason. We will take a look at the hardware in the next Tuesday during the maintenance period.