4pm readings (Torr)

PT-243: 1.08e-9
PT-244: 1.42e-9
PT-210: 1.42e-9

John, Kyle, Chandra

Testing a three day cycle on CP3 overfill. We will *not* fill CP3 today and instead monitor pressures overnight, and fill tomorrow, Friday. 

Chandra time (local): 16:00, 20:00, 00:00, 4:00
Kyle time (local):  18:00, 22:00, 2:00, 6:00

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.

[Fil, Jenne]

We've measured the distances from each Newtonian array sensor location (marked on the LVEA floor with green electrical tape) to the racks we'll use for signal concentration, so that we can order our cables soon. 

The new Met One dust monitors have been installed in:
The LVEA at HAM6 and in the Beer Garden, in the Optics Lab,End-X, and End-Y. They are and sampling for 60 seconds every 10 minutes. 

There are still a few minor issues being resolved, which do not effect the operation of the units or the particle counts. 

Attached is a quick operators guide to the new monitor. Fuller documentation will follow.    

John, Chandra

Pressures at IPs IP-7 & IP-8 on diagonal were ~10 Torr. Pumped out volumes with aux cart and opened gate valves to main diagonal volume. Connected HV cables, but did not activate IPs yet. Current diagonal pressure = 7e-7 Torr.

IP-8 still needs cable strain relief.

h1fw1 froze up last night at 22:41 PDT with a kernel panic. It was restarted at 10:16 PDT today (I pressed the front panel reset button)

last part of the console error message was:

VFS: Close: file count is 0

Kernel panic - not syncing: CRED: put_cred_rcu() sees xxxxxxxxxxxxxx with usage -1

where xxxxxx is a large hex number.

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.

I have updated the documentation in the DCC here,

https://dcc.ligo.org/LIGO-T1500502

about hoft generation for ER8/O1 to include information about C02 hoft.

In particular, these caveats are included:

* For the exact versions of filter files, code, and command lines used to generate C01 and C02 hoft see: https://wiki.ligo.org/Calibration/GDSCalibrationConfigurationsO1

* Users should check with their working group about which vetoes and which veto-definer files to use with each type of data before producing final results.

Michael, Krishna, Hugh, Jeff

This morning, we took out the piezo stacks from under the BRS-2 platform. We then turned on the ion pump. The current initially went up to 20 mA and slowly dropped down to ~300 microamps in ~1 hr. We then disconnected the Pump station. When we checkd it later after about 4 hrs, the pump current was ~200 microamps (P ~ 1e-6 torr) and steadily dropping.

Michael and I then hooked up the rest of the electronics, wrapped the vacuum can in several sheets of foam, and finally set up the thick-foam-box around the instrument.

Hugh had set up the EY_GND medm screen showing the BRS-2 data coming into the ISI frontends (similar to EX_GND). After correcting a cable connection mistake, we are now getting the BRS-2 angle data into CDS. Currently we are getting the following channels in to ISI AA Chasis:

ADC0, channel 27: Raw Tilt Signal : Calibration - to be worked out soon. This is a high-passed value of the raw angle measured by the autocollimator, high pass: 2 pole at ~0.5 mHz.

ADC0, channel 28: Drift Signal : Calibration: 58.33 nrad/ct. This is a scaled down version of the raw angle signal.

ADC0, channel 29: Ref Signal : Calibration: - to be worked out soon. This is the angle of the reference mirror. It is useful as a measure of the autocollimator noise. Unlike BRS-1, this signal has a higher noise floor and is useful only at very low frequencies, below ~ 5 mHz.

ADC0, channel 30: Status Signal : This is currently zero. The plan is to use this as an indication of the health of BRS-2.

The Tilt channel is currently noisy and we will investigate further tomorrow.

Introducing the new LASER_PWR Guardian node! Use it to change the power by selecting one of the three requestable powers (2W, 10W, 22W) or open the "ALL" screen to select any 'POWER_#W'. I attached a shot of the graph if you're curious. This node is nominally manged by ISC_LOCK and then ALIGN_IFO during initial alignment (though this has created some usermsg issues that I am trying to work around, more on that later).

I have also changed around some of the management for initial alignment. If the user wants to run initial alignment:

1. From READY in ISC_LOCK, go to manual and select INITIAL_ALIGNMENT

2. Wait for ALIGN_IFO to run through its DOWN state. This will temporarily take control of the ALS's, LASER_PWR, and IMC_LOCK nodes.

3. Run the green alignment from ALIGN_IFO instead of each of the ALS nodes. Offload the green WFS at the same ti.

4. Continue as usual, during SRC the LASER_PWR node will bring the power up to 10W and then back down after.

6. When done with initial alignment, make sure to go to INIT on ISC_LOCK to take back control of the nodes. then continue as usual.

I added the LASER_PWR, as well as the SR3_CAGE_SERVO nodes to the Guardian Overview screen (shot attached).

I also slightly changed the ISC_GUARDIANS medm to show who the managers are of each node and placed the new node on the bottom. (shot also attached).

As I mentioned above, there are some user messages that will pop up on ALIGN_IFO and ISC_LOCK about the nodes being stolen by one another. This isn't a big deal for ISC_LOCK to report this whie we are in the middle of initial alignment, but it isn't good for ALIGN_IFO to be continuously notifying during normal locking. I have something that I want to try next opportunity I get, hopefully tomorrow. And if that doesn't work, Jamie seemed to have an idea of how to solve these types of situations that will be in the next Guardian release. Until then we can not manage the nodes during initial alignment just as before.

(Tasked by Aidan)

We were curious of how the HWS sled power decrease over time so we know when to swap them out. Below I've attached plots of HWSX and HWSY sled power (corrected for gains) and input current. The start time is when we replaced the SLED (April 26, 2015 for YSLED and March 1, 2016 for XSLED). I only plotted the time when the SLEDs were turned on (displays in number of days). XSLED shows deteroration of ~2% per day and YSLED shows deterioration of ~1% per day (given 7mW to be 100%, I don't think we are shooting 7mW out though but the trend looks reasonable). YSLED power decreased slightly faster when the input current = 94 mA.

XSLED data can be found here and YSLED data can be found here. The column goes Time|Power (mW)|Current(mA). The script to fetch and plot data can be found in the same directory.

The fast decay in the beginning is a known problem.

WP 5799 FR 4694 (PKA II 1193)

Continuing the offload of SUS calculating the SUSPOINT motion from ISI GS13 cartesian motion, this has ISI doing the calculating.  We'll stop the SUS doing the calcs as soon as we confirm that DetChar is happy with the ISI numbers.

All the HAM models were rebuilt & installed and FrontEnds restarted.  safe and OBSERVE.snaps were checked and updated (lots of new channels.)

No issues with HAM ISIs reisolating.

Medm editing is ongoing for the SUSPOINT.  Each medm is custom for the number of suspensions.  HAM6 and HAM2 still need to be built.

Along these lines, the BSC Models were adjusted to put the SUSPOINT on IPC and at ENDY, the BRS was added as at ETMX.

SVN COMMITS:

hugh.radkins@opsws1:models 0$ svn commit -m "HAM SUSPOINT calcs moved to ISI and BSC SUSPOINT calcs added to IPC and BRS at ETMY"
Sending        models/h1isibs.mdl
Sending        models/h1isietmx.mdl
Sending        models/h1isietmy.mdl
Sending        models/h1isiham2.mdl
Sending        models/h1isiham3.mdl
Sending        models/h1isiham4.mdl
Sending        models/h1isiham5.mdl
Sending        models/h1isiham6.mdl
Sending        models/h1isiitmx.mdl
Sending        models/h1isiitmy.mdl
Transmitting file data ..........
Committed revision 12961.
hugh.radkins@opsws1:models 0$ pwd
/opt/rtcds/userapps/release/isi/h1/models

hugh.radkins@opsws1:hamisi 0$ svn commit -m "Added suspension OPTICs for medm generation"
Sending        hamisi/H1_isiham2_overview_macro.txt
Sending        hamisi/H1_isiham3_overview_macro.txt
Sending        hamisi/H1_isiham4_overview_macro.txt
Sending        hamisi/H1_isiham5_overview_macro.txt
Sending        hamisi/H1_isiham6_overview_macro.txt
Transmitting file data .....
Committed revision 12962.
hugh.radkins@opsws1:hamisi 0$ pwd
/opt/rtcds/userapps/release/isi/h1/medm/hamisi

hugh.radkins@opsws1:burtfiles 0$ svn commit -m "Update snaps for SUSPOINT & commissioning"
Sending        burtfiles/h1isibs_down.snap
Sending        burtfiles/h1isibs_safe.snap
Sending        burtfiles/h1isietmx_safe.snap
Sending        burtfiles/h1isietmy_OBSERVE.snap
Sending        burtfiles/h1isietmy_safe.snap
Sending        burtfiles/h1isiham2_safe.snap
Sending        burtfiles/h1isiham3_safe.snap
Sending        burtfiles/h1isiham4_OBSERVE.snap
Sending        burtfiles/h1isiham4_safe.snap
Sending        burtfiles/h1isiham5_OBSERVE.snap
Sending        burtfiles/h1isiham5_safe.snap
Sending        burtfiles/h1isiham6_safe.snap
Sending        burtfiles/h1isiitmx_safe.snap
Sending        burtfiles/h1isiitmy_OBSERVE.snap
Sending        burtfiles/h1isiitmy_safe.snap
Transmitting file data ...............
Committed revision 12963.
hugh.radkins@opsws1:burtfiles 0$ pwd
/opt/rtcds/userapps/release/isi/h1/burtfiles
 

I'll commit the medm adls once I'm finished with them.

J. Kissel, B. Weaver, H. Radkins, D. Barker, J. Batch

Here's a list of all of the upgrades we were involved in today. There will be more details of the upgrade, more debugging, associated MEDM screen changes, svn commits, and other clean up tomorrow as we continue to explore what we've installed and debug. Bear with us, and thanks for your patience.

1) Fixed UIM coil driver path's automatic compensation bug by updating CD_STATE_MACHINE.c. See Int. Issue 1178.
2) Installed ISI GS13's projection to SUSPOINT Euler basis projection into the SEI models. See ECR E1600028.
3) Sent the Euler Basis Longitudinal DOF for each SUS involved in a cavity over various IPC (PCIE and RFM) and models (ISI, End-station PEM, H1OAF) to be collected in OAF. See ECR E1600028.
8) Removed the excess RFM channels from End-Station ALS models (noteably *not* the excess channels in the ISC models). This made room for 3). See LHO aLOG 25216
4) Added various rotational sensor correction paths to the BSC ISIs (GND BRS to ST1, and ST1 to ST2). (Prototyping, this stuff, no ECRs just yet)
5) Removed the L4C sensor correction path. See SEI aLOG 666
6) Added new infrastructure for the EY BRS. (Most Copied from EX, covered by ECR E1500246)
7) Reverted the BSC SUS's coil driver monitors to store the NOISEMON in the frames (and pushed the FASTIMON to the commissioning frames). Also, we put filter modules in front of the NOISEMONs (like was done for the FASTIMONs the last time we touched this) in case we ever wish to calibrate them. See ECR E1600033 and LHO aLOG 26313

Because we haven't built MEDM screens and actually *used* any of these paths yet, there's still potential for bugs and we haven't explored and/or fixed all of the collateral damage. Stay tuned as we continue to work on all of these updates tomorrow.