Summary:

Filter configuration for ISS 1st loop to generate RIN channels (H1:PSL-ISS_PDA_REL_OUTPUT and PDB) doesn't look good. It seems as though we're somehow chosen to use inferior of the two filters in place both for  "CALI_AC" and "CALI_DC", assuming that D1001998-V2 (PD circuit diagram) and D1001985-V2 (ISS circuit diagram) are correct.

I made somewhat better filter for "CALI_AC". For "Cali_DC" probably it's good enough to use the one we're not using. I loaded the coefficients for the new file for H1PSLISS from H1PSLISS_GDS_TP MEDM screen.

This doesn't affect the loop because these channels are not in the feedback loop, but making these filters right makes it easier for different RIN channels to be compared.

Details:

Reading D1001998-V2, D1001985-V2, T0900630, analog part of the monitor output for PSL-ISS_PDA and PSL-ISS_PDB ADC have analog z, p and k of [0.0723;2700;0.0707] Hz, [3.3607;130;3.12;2300] Hz, and 0.2, they're all in the PD box (ISS box is just the pass through as far as these outputs are concerned). These are DC coupled.

After they are received in the front end model, the signal is first converted to volts but not dewhitened by PSL-ISS_PDA, and then distributed to PSL-ISS_PDA_CALI_DC and PSL-ISS_PDA_CALI_AC. In DC the signal is low-passed, and in AC it's dewhitened and high-passed, and AC is devided by DC to give RIN (first attachment).

In CALI_DC path, there are two filters FM1 and FM2, only FM1 is used (second attachment left). I also plotted the inverse of the analog whitening transfer function including the DC gain in the same attachment. FM1 looks like a strange  dewhite, nothing wrong with that, but I don't see any reason to prefer FM1 over FM2. Just use FM2.

In CALI_AC path, there are also two filters FM3 and FM4 (second attachment right). Compared with the inverse of the analog, it seems like the one in use (FM3) underestimates the RIN by 18dB at 1kHz. FM4 looks better but it's DC coupled. I made a new filter (green) and put it in FM5.

It's kind of odd that we're keeping DC gain factor in two different parts (CALI_DC and CAL_AC) instead of upstream. However, moving this gain into upstream affects PDASTAT thing (see the first attachment again), so I'll not fix this.

Changed the web view of vacuum MEDM screens to use the new Beckhoff MEDM screen for Mid Y in place of the old screen.

Laser Status:
SysStat is good
Front End power is 30.32 W (should be around 30 W)
Frontend Watch is GREEN
HPO Watch is GREEN

PMC:
It has been locked 1.0 day(s) 21.0 hour(s) and 31.0 minute(s) (should be days/weeks)
Reflected power is 15.98 W and PowerSum is 120.3 W

FSS:
It has been locked 0.0 day(s) 2.0 hour(s) and 13.0 minute(s) (should be days/weeks)
TPD[V] = 3.935 V (minimum 0.9 V)

ISS:
The diffracted power is around 29.4% (should be 5-9%)
Last saturation event was 0.0 day(s) 2.0 hour(s) and 14.0 minute(s) ago (should be days/weeks)

15:05 UTC Jeff B. to cleaning area to put away garb
15:11 UTC Jeff B. done
15:14 UTC Film crew on site
15:49 UTC Starting initial alignment
16:03 UTC Kyle to HAM 11 and HAM 12 to look at pumps
~16:30 UTC Richard and Filiberto starting Beckhoff vacuum upgrade at mid Y
Finished initial alignment
17:16 UTC Restarted video2 (MEDM screens updating very infrequently)
17:26 UTC Kyle back
18:02 UTC Richard and Filiberto done with Beckhoff vacuum upgrade at mid Y
Nutsinee turning on HWS X,Y
19:07 UTC DAQ restart for mid Y Beckhoff vacuum channels
19:35 UTC Received phone call for Hanford monthly alert test
19:47 UTC Film crew driving down an arm to record footage
20:18 UTC Sheila restarting ASC model (WP 5840)
20:27 UTC DAQ restart for SUSETMXPI and ASC model changes
20:36 UTC Travis and Betsy to LVEA to retrieve equipment
20:47 UTC Travis and Betsy back
20:51 UTC Film crew done recording beam tube footage
20:57 UTC Guardian node testing (WP 5841)
21:21 UTC Film crew to roof
21:22 UTC Gerardo to CP3 to overfill
21:51 UTC Gerardo done

TITLE: 04/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    Wind: 14mph Gusts, 7mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.31 μm/s
QUICK SUMMARY: Commissioners hard at work.

 

1/2 open LLCV bypass valve, and the exhaust bypass valve fully open.
Flow was noted after 57 seconds, closed LLCV valve, and 3 minutes later the exhaust bypass valve was closed.

Added 150mL H2O to the H1 PSL crystal chiller.

Kyle 

HAM11/12

Gerardo and I had improved things Friday but the rate of rise is still too high when the pump carts get valved-out today -> Using large forces applied at great distances, I encouraged all (160) ea, 7/8-9 obstinate door bolts that, in fact, more clamping was possible (~ 11/160 were very loose although at random not necessarily adjacent to each other - Friday Gerardo and I had done only the non-door bolts connecting the HAMs to each other and to the OMC spool - time ran out)

Attached data is promising. 

BSC4 

BSC4 annulus has a "high gas load" as well -> After Gerardo had reminded me that the dome had been removed during the "gutting" of the 2K, I put a wrench on a few of the bolts that I was able to access from the ladder nearby -> most of the bolts were quite loose -> We will torque these tomorrow during maintenance day.

With the elevated intensity noise currently being injected into the interferometer, we can passively make an estimate of the CARM pole frequency.

The attachment shows the transfer functions that take interferometer input power to transmitted arm power (as measured by the four end-station QPD sums) with the interferometer locked at 22 W. There isn't good coherence around the CARM pole frequency itself. However, if we normalize each signal to RIN, this fixes the dc value of the transfer function at 1. Hence, the magnitude of the slope is sufficient to extract the CARM pole.

At 10 Hz, the transfer function is 0.0631, which implies a CARM pole of 0.63 Hz. There is about 1.5 % uncertainty from the spread in the values from the four transfer functions, and about 2 % uncertainty from the drifts in dc intensity for the four QPD sums during the measurement period. Together that makes 2.5 % uncertainty. There may also be additional uncertainty from the whitening and antiwhitening of the QPD signals.

If we assume an ETM transmissivity of 4 ppm, an ITM transmissivity of 1.45 %, a PRM transmissivity of 3.0 %, and 50 ppm of loss on each test mass, we expect a CARM pole of 0.64 Hz (see T1500325).

Obviously a superior method is to take a driven transfer function that has good coherence at and around the CARM pole frequency, and to use the phase information to make a true fit.

Dave, Nutsinee

The peak counts didn't make sense for both HWSX and HWSY when I first ran the code. Stream_image shows glitchy looking images on HWSY and no image at all on HWSX. Turning the camera and frame grabber on and off didn't help so we restarted the hwsmsr computer. That seems to have solved the issue.

Changed the setting for the high voltage, now at 5.0 KV.  Previous setting at 7.0 KV.

Crew from Japanese television station is filming on site today and tomorrow
Nicole is here to work on 3IFO and property management

SEI: BRS is on at both end stations and has run over the weekend. Personnel need to notify the operator if they are going to end X or end Y so that the BRS can be turned off beforehand.
PSL: PMC mode matching and ISS issues
VAC: Tapping and drilling holes at mid stations on Tuesday for scroll pumps. Gerardo pulling cables at vertex.
FAC: Landscapers on site
CDS: Beckhoff vacuum upgrade planned for today. Beckhoff vacuum upgrade at LX and LY planned for Tuesday. Workstations will be rebooted at 6 am remotely each Tuesday starting on May 2. You must send an email to Carlos beforehand if you do not want a particular station restarted.

I did a set of tests with the guardian node. The codebase is in a state that should be ready for Jamie and I to set it up tomorrow on the guardian script machine. Going forward things to do are:
 * Update docstrings
 * Install glue, gracedb, and grid credentials on guardian machine
 * Plan out how to run the gracedb process and get robot certificate
 * Do series of injections with guardian node on guardian machine - test full injection pathway, test killing active injection, test reloading schedule, test multiple injections in a row, etc.

Below I outline the tests I did.

How to do command line tests with guardian daemon

Can now do the following tests on the command line at a LHO workstation:
 * To test reading schedule and finding the next injection: guardian INJ WAIT_FOR_NEXT_INJECT
 * To test gracedb event creation: guardian INJ CREATE_GRACEDB_EVENT
 * To test awg and inject a signal from schedule into the detector: guardian INJ CREATE_AWG_STREAM INJECT_CBC_ACTIVE
 * To test schedule validation script: PYTHONPATH=/opt/rtcds/userapps/release/cal/common/guardian:${PYTHONPATH}; python guardian_inj_schedule_validation.py --ifo H1 --schedule /opt/rtcds/userapps/release/cal/common/guardian/schedule/schedule_1148558052.txt --min-cadence 300

NOTE: You will need glue and gracedb python packages to run some of these tests, and these packages are not system-installed on workstations in the control room. And for gracedb upload testing you need the grid credential tools which are not on LHO workstations. And for gracedb upload test you need to make sure dev_mode is False.

Test injections

Injections from last night are in aLog 26749.

Today I continued with some more development tests. Injections that are constant amplitude of 1e-26 for 1 second duration into H1:CAL-PINJX_TRANSIENT_EXC; start time of the injections are:
 * 1145554100
 * 1145555100
 * 1145555700
 * 1145560262

(i) Call to awg works and injection goes into INJ-PINJX_TRANSIENT_EXC.

(ii) Injections logged correctly and meta-data is propagating through infrastructure to inform the searches. Can see the hardware injection tests done with the guardian node on the detchar summary pages. The first three not logged with a injection type, eg. BURST, because in initial tests just wanted to correctly use the awg module. Can see thereafter the injections were flagged with a type in ODC and this propagates to the low-latency frames for the online searches and the segment database for the offline searches. Can see attached plots for ODC segments and segment database segments.

(iii) Destroying a node with an open stream that has trasmitted data to the front end does not perform the injection.

(iv) The gracedb upload functions have already been tested. Today I re-checked the functions and here is an example gracedb event that was uploaded T235981. Adding messages to the event log on gracedb was also tested again, notice the "This is a test." message on the T235981 gracedb page.

(v) Schedule validation script updated and tested.

Codebase developments

Some more changes:
 * There is now a dev_mode in the code to run the tests mentioned in the section above. At the moment this does two things (i) ignores to check if the detector is locked, (ii) ignores gracedb for now until we get the robot certificate sorted out, and (ii) waits in the INJECT_CBC_ACTIVE state instead of the AWG_STREAM_OPEN_PREINJECT state because we need to avoid jump transitions for the command line test above.
 * Schedule validation script works again (https://redoubt.ligo-wa.caltech.edu/svn/cds_user_apps/trunk/cal/common/scripts/guardian_inj_schedule_validation.py).

One thing of note is that guardian does not allow subprocesses to be created by states so the subprocess managment that I had written will not work with guardian. So right now once the injection starts the code will wait for the injection to finish, this is just the implementation in the awg package (see awg.ArbitraryStream.close); it can only be killed by stopping the node.

Chris B., Jamie R.

This aLog is documenting the work that has been done so far to get the guardian hardware injection node running at LHO. Documenting the work over the next few days could ease the installation at LLO, after we have sorted out everything at LHO.

It also includes some tidbits about the development that's been done, since several members of the hardware injection subgroup wanted to be kept in the loop.

Installations

There are only a few things we need on the guardian script machines that were not there are already. Things we have done:
 (1) Updated userapps SVN at /opt/rtcds/userapps/release/cal/common/guardian
 (2) Checked that we can instantiated guardian node with: guardctrl create INJ
 (3) Installed awg on the guardian script machine

Things we have yet to install on the guardian machine:
 * glue
 * ligo-gracedb
 * grid credentials

Codebase Development

This afternoon was mostly spent implementing several new things in the codebase. I have attached a new graph of the node to this aLog since there a number of new states, eg. new failure states, renamed the active injection states (formerly called CBC, BURST, etc.), renamed the IDLE state, and the renamed GraceDB state. And as always, the code lives in the SVN here: https://redoubt.ligo-wa.caltech.edu/svn/cds_user_apps/trunk/cal/common/guardian/

Some changes of note:
 * Changed jump transitions in successful injection pathway to edges. This changes how the node should be run. The model now is that the requested state should be INJECT_SUCCESS while running the node.
 * The modules (eg. inj_det, inj_types, etc.) have been moved to a new injtools subpackage.
 * Added success/failure messages for GraceDB events after injection is complete.
 * Added guardian decorators for a few tasks that are often repeated, eg. checking for external alerts.
 * Process managing for the awg call.

These changes have made the schedule validation script (https://redoubt.ligo-wa.caltech.edu/svn/cds_user_apps/trunk/cal/common/scripts/guardian_inj_schedule_validation.py) out-of-date, and that will need to be updated.

Also the GraceDB portions of the code have been commented out for now, since we're holding off on that for now until we have the grid credentials/how we will run the guardian process sorted out.

Tests

As I was developing I did a couple tests with the guardian node today. I did three hardware injections of constant amplitude (1e-26) into H1:CAL-PINJX_TRANSIENT_EXC. Each injection has a duration of 1 second. GPS start times are:
 * 1145497100
 * 1145497850
 * 1145500600

These tests were mostly to check that the call to awg was working properly.

The PINJX_HARDWARE filterbank has already been turned off (aLog 26748) so the signal will only appear in the PINJX_TRANSIENT and PINJX_HARDWARE channels.

In the attached plot below I shows the injection at 1145500600.

Matt, Sheila

We locked and saw that we have 3 orders of mognitude or so to much noise at DC readout.  It seems this is related to PSL problems, the atached screenshot shows coherence between the ISS second loop PDs and DARM up to 100 Hz, as well as coherence between frequency noise and DARM.  The pink trace shows the coherence between intensity and frequency noise.  With this noise, we were able to power up to 10 Watts, but saturated the DC PDs.  

We looked a little but at impementing a dither loop for SRM control.  The alingment dither system currently would allow us to demodulate POP18, but POP90 has much better signal, as you would expect.  The IPC for adding this is already in the models, so I've just added it to the matrix but didn't do the model restart yet (WP5840).  

We then gave up on locking and went to the PSL racks to look at some signals at high frequencies.  We saw a glitch that happens at a repetition rate of 37 kHz, and has frequency content of nearly a MHz, which shows up in the laser intensity noise.  Matt has a picture of this in the ISS PD and the ref cav transmission.  If we turn off the ISS this is still there (as expected since its above the bandwidth), but it is harder to see on top of low frequency intensity noise.  

When the ISS is off, the ISS PDs wander from rail to rail, and oscillate only when they are near the upper rail.