aLIGO LHO Logbook

Displaying reports 67281-67300 of 85053.Go to page Start 3361 3362 3363 3364 3365 3366 3367 3368 3369 End

Reports until 16:03, Tuesday 05 May 2015

H1 TCS

Print this report.

nutsinee.kijbunchoo@LIGO.ORG - posted 16:03, Tuesday 05 May 2015 (18255)

ITMX HWS Optics alignment

Aidan suggested that I align the irises to the sled beam rather than alinging the sled beam to the irises so I went in and redid the alignment for the ITMX HWS optics. I blocked the green light, centered the sled beam to the mirrors/lenses and adjusted the irises accordingly. Then I let the green light through, fine tuned the irises positions and made sure the green and the sled beam are reasonably well overlapped if not right on top of each other (SRC aligned, BS aligned, ITMX aligned, TMSX alinged, ETMY misaligned at this point). The green beam is hitting the HWS. However, the streamed imagees don't show any decent return sled beam. Given that the incoming green light overlaps the outgoing sled beam whatever is causing the return sled beam to be off is likely in vaccum. Greg also noticed the green beam coming down the ITMY periscope changed position significantly compare to last week. So we agreed to not adjust the corner station HWS optics any further until we are sure that the SRC optics won't change the alignment again. The Hartmann waveplate is off at the moment for ITMX.

Images attached to this report

LHO VE

Print this report.

kyle.ryan@LIGO.ORG - posted 14:52, Tuesday 05 May 2015 (18254)

Switched IP12 controller at X-end to fixed voltage

John, Kyle

Don't want pressure to vary as the result of varying IP12 voltage output -> Wider community using X2 BT pressure as indication of possible leaks being introduced from BT cleaning activities on X2 -> Fixed voltage at 7000V (same voltage as Y-end)

LHO VE

Print this report.

john.worden@LIGO.ORG - posted 14:50, Tuesday 05 May 2015 (18253)

END X Pressure

The pressure at X END has been bouncing around due to the programmed voltage steps of the main ion pump controller. In order to stabilize this we have set the voltage to 7 KV. This is also the same setting as the Y END pump.

The immediate response has been an increase in pressure to ~2e-8 torr. We expect the pressure to fall back to the low e-9 range as the pump sputters and exposes fresh surfaces.

H1 GRD

Print this report.

jameson.rollins@LIGO.ORG - posted 14:10, Tuesday 05 May 2015 - last comment - 15:30, Wednesday 06 May 2015(18252)

minor guardian upgrade this morning

During maintenance this morning we pushed a fairly minor guardian upgrade. We are now running:

guardian r1447 (+2 minor MEDM screen changes from r1445 that is running right now)
cdsutils r474

Primary bugfixes or new features:

Improve SPM checking. This should get rid of the "SPM flickering" that was being reported at LHO.
MODE 'EXEC' is now called 'AUTO', to elliminate ambiguity with OP.
Fix node supervision logging to properly time stamp all logs.
Add TIME_INIT and TIME_UP channels that record when a node was initialized, and how long it's been up.

The last two are to help debug some of the intermittent issues we've been seeing with node processes hanging for unknown reasons.

The node status indicators on the main GUARD_OVERVIEW screen also now have a couple of extra indicators lights, for STALLED state of node, and if there are any SPM diffs:

Images attached to this report

Comments related to this report

jameson.rollins@LIGO.ORG - 15:30, Wednesday 06 May 2015 (18281)

Another new feature I forgot to mention is that guardian can now dump their internal setpoint table to a file.

This is triggered by writing a 1 ('True') to the SPM_SNAP channel for the node:

jameson.rollins@operator1:~ 0$ caput H1:GRD-SUS_ITMY_SPM_SNAP 1
Old : H1:GRD-SUS_ITMY_SPM_SNAP       False
New : H1:GRD-SUS_ITMY_SPM_SNAP       True
jameson.rollins@operator1:~ 0$ cat /ligo/cds/lho/h1/guardian/archive/SUS_ITMY/SUS_ITMY.spm
H1:SUS-ITMY_M0_TEST_P_SWSTAT IN,OT,DC
H1:SUS-ITMY_M0_TEST_Y_SWSTAT IN,OT,DC
H1:SUS-ITMY_R0_OPTICALIGN_Y_TRAMP 2.0
H1:SUS-ITMY_M0_OPTICALIGN_P_TRAMP 2.0
H1:SUS-ITMY_M0_TEST_P_TRAMP 2.0
H1:SUS-ITMY_M0_OPTICALIGN_Y_TRAMP 2.0
H1:SUS-ITMY_M0_TEST_Y_TRAMP 2.0
H1:SUS-ITMY_M0_OPTICALIGN_P_SWSTAT IN,OF,OT,DC
H1:SUS-ITMY_M0_OPTICALIGN_Y_SWSTAT IN,OF,OT,DC
H1:SUS-ITMY_R0_OPTICALIGN_P_TRAMP 2.0
jameson.rollins@operator1:~ 0$

A '.spm' file is written into the node archive directory (/ligo/cds/<site>/<ifo>/guardian/archive/<node>). The .spm file is a space-separated list of channel/setpoint pairs.

NOTE: the setpoints are accumulate over the running of the node. If the node has just been restarted (or the worker restarted after a STOP command has been issues) the setpoint table will be empty until the node passes through states where it actually writes to a channel. The full set of setpoints will only be fully known once the node runs through all system state code paths. Guardian has the ability to initialize the full set of setpoints for the node for a pre-defined set of channels, but we're not using that fascility yet.

The setpoint table is also written to the log when an SPM_SNAP is triggered, as is a full list of all PVs subscriptions currently active in the node:

2015-05-06T22:16:20.66686 SUS_ITMY W: PVs:
2015-05-06T22:16:20.66698 SUS_ITMY W:   H1:SUS-ITMY_DACKILL_STATE = 1.0
2015-05-06T22:16:20.66705 SUS_ITMY W:   H1:SUS-ITMY_L1_TEST_L_SW1R = 4.0
2015-05-06T22:16:20.66711 SUS_ITMY W:   H1:SUS-ITMY_L1_TEST_P_SW1R = 4.0
2015-05-06T22:16:20.66717 SUS_ITMY W:   H1:SUS-ITMY_L1_TEST_Y_SW1R = 4.0
2015-05-06T22:16:20.66723 SUS_ITMY W:   H1:SUS-ITMY_L1_WDMON_STATE = 1.0
2015-05-06T22:16:20.66728 SUS_ITMY W:   H1:SUS-ITMY_L2_TEST_L_SW1R = 4.0
2015-05-06T22:16:20.66734 SUS_ITMY W:   H1:SUS-ITMY_L2_TEST_P_SW1R = 4.0
2015-05-06T22:16:20.66740 SUS_ITMY W:   H1:SUS-ITMY_L2_TEST_Y_SW1R = 4.0
2015-05-06T22:16:20.66746 SUS_ITMY W:   H1:SUS-ITMY_L2_WDMON_STATE = 1.0
2015-05-06T22:16:20.66751 SUS_ITMY W:   H1:SUS-ITMY_L3_TEST_BIAS_SW1R = 4.0
2015-05-06T22:16:20.66757 SUS_ITMY W:   H1:SUS-ITMY_L3_TEST_L_SW1R = 4.0
2015-05-06T22:16:20.66763 SUS_ITMY W:   H1:SUS-ITMY_L3_TEST_P_SW1R = 4.0
2015-05-06T22:16:20.66768 SUS_ITMY W:   H1:SUS-ITMY_L3_TEST_Y_SW1R = 4.0
2015-05-06T22:16:20.66775 SUS_ITMY W:   H1:SUS-ITMY_M0_DAMP_L_SW2R = 1728.0
2015-05-06T22:16:20.66781 SUS_ITMY W:   H1:SUS-ITMY_M0_DAMP_P_SW2R = 1728.0
2015-05-06T22:16:20.66787 SUS_ITMY W:   H1:SUS-ITMY_M0_DAMP_R_SW2R = 1728.0
2015-05-06T22:16:20.66792 SUS_ITMY W:   H1:SUS-ITMY_M0_DAMP_T_SW2R = 1728.0
2015-05-06T22:16:20.66798 SUS_ITMY W:   H1:SUS-ITMY_M0_DAMP_V_SW2R = 1728.0
2015-05-06T22:16:20.66804 SUS_ITMY W:   H1:SUS-ITMY_M0_DAMP_Y_SW2R = 1728.0
2015-05-06T22:16:20.66810 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_P_SW1 = 0.0
2015-05-06T22:16:20.66816 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_P_SW1R = 12.0
2015-05-06T22:16:20.66821 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_P_SW2 = 0.0
2015-05-06T22:16:20.66827 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_P_SW2R = 1536.0
2015-05-06T22:16:20.66833 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_P_SWSTAT = 302080.0
2015-05-06T22:16:20.66839 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_P_TRAMP = 2.0
2015-05-06T22:16:20.66845 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_Y_SW1 = 0.0
2015-05-06T22:16:20.66850 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_Y_SW1R = 12.0
2015-05-06T22:16:20.66858 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_Y_SW2 = 0.0
2015-05-06T22:16:20.66870 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_Y_SW2R = 1536.0
2015-05-06T22:16:20.66880 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_Y_SWSTAT = 302080.0
2015-05-06T22:16:20.66891 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_Y_TRAMP = 2.0
2015-05-06T22:16:20.66903 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_L_SW1R = 4.0
2015-05-06T22:16:20.66913 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_P_SW1 = 0.0
2015-05-06T22:16:20.66923 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_P_SW1R = 4.0
2015-05-06T22:16:20.66933 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_P_SW2 = 0.0
2015-05-06T22:16:20.66940 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_P_SW2R = 1536.0
2015-05-06T22:16:20.66948 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_P_SWSTAT = 300032.0
2015-05-06T22:16:20.66955 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_P_TRAMP = 2.0
2015-05-06T22:16:20.66962 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_R_SW1R = 4.0
2015-05-06T22:16:20.66969 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_T_SW1R = 4.0
2015-05-06T22:16:20.66976 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_V_SW1R = 4.0
2015-05-06T22:16:20.66983 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_Y_SW1 = 0.0
2015-05-06T22:16:20.66995 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_Y_SW1R = 4.0
2015-05-06T22:16:20.66998 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_Y_SW2 = 0.0
2015-05-06T22:16:20.67005 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_Y_SW2R = 1536.0
2015-05-06T22:16:20.67013 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_Y_SWSTAT = 300032.0
2015-05-06T22:16:20.67023 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_Y_TRAMP = 2.0
2015-05-06T22:16:20.67027 SUS_ITMY W:   H1:SUS-ITMY_M0_WDMON_STATE = 1.0
2015-05-06T22:16:20.67037 SUS_ITMY W:   H1:SUS-ITMY_MASTERSWITCH = 1
2015-05-06T22:16:20.67044 SUS_ITMY W:   H1:SUS-ITMY_R0_DAMP_L_SW2R = 1728.0
2015-05-06T22:16:20.67048 SUS_ITMY W:   H1:SUS-ITMY_R0_DAMP_P_SW2R = 1728.0
2015-05-06T22:16:20.67055 SUS_ITMY W:   H1:SUS-ITMY_R0_DAMP_R_SW2R = 1728.0
2015-05-06T22:16:20.67062 SUS_ITMY W:   H1:SUS-ITMY_R0_DAMP_T_SW2R = 1728.0
2015-05-06T22:16:20.67070 SUS_ITMY W:   H1:SUS-ITMY_R0_DAMP_V_SW2R = 1728.0
2015-05-06T22:16:20.67077 SUS_ITMY W:   H1:SUS-ITMY_R0_DAMP_Y_SW2R = 1728.0
2015-05-06T22:16:20.67088 SUS_ITMY W:   H1:SUS-ITMY_R0_OPTICALIGN_P_SW1R = 12.0
2015-05-06T22:16:20.67172 SUS_ITMY W:   H1:SUS-ITMY_R0_OPTICALIGN_P_TRAMP = 2.0
2015-05-06T22:16:20.67187 SUS_ITMY W:   H1:SUS-ITMY_R0_OPTICALIGN_Y_SW1R = 12.0
2015-05-06T22:16:20.67198 SUS_ITMY W:   H1:SUS-ITMY_R0_OPTICALIGN_Y_TRAMP = 2.0
2015-05-06T22:16:20.67210 SUS_ITMY W:   H1:SUS-ITMY_R0_TEST_L_SW1R = 4.0
2015-05-06T22:16:20.67226 SUS_ITMY W:   H1:SUS-ITMY_R0_TEST_P_SW1R = 4.0
2015-05-06T22:16:20.67229 SUS_ITMY W:   H1:SUS-ITMY_R0_TEST_R_SW1R = 4.0
2015-05-06T22:16:20.67239 SUS_ITMY W:   H1:SUS-ITMY_R0_TEST_T_SW1R = 4.0
2015-05-06T22:16:20.67250 SUS_ITMY W:   H1:SUS-ITMY_R0_TEST_V_SW1R = 4.0
2015-05-06T22:16:20.67261 SUS_ITMY W:   H1:SUS-ITMY_R0_TEST_Y_SW1R = 4.0
2015-05-06T22:16:20.67275 SUS_ITMY W:   H1:SUS-ITMY_R0_WDMON_STATE = 1.0
2015-05-06T22:16:20.67287 SUS_ITMY W: SPMs:
2015-05-06T22:16:20.67316 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_P_SWSTAT = IN,OF,OT,DC
2015-05-06T22:16:20.67326 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_P_TRAMP = 2.0
2015-05-06T22:16:20.67353 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_Y_SWSTAT = IN,OF,OT,DC
2015-05-06T22:16:20.67363 SUS_ITMY W:   H1:SUS-ITMY_M0_OPTICALIGN_Y_TRAMP = 2.0
2015-05-06T22:16:20.67393 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_P_SWSTAT = IN,OT,DC
2015-05-06T22:16:20.67397 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_P_TRAMP = 2.0
2015-05-06T22:16:20.67424 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_Y_SWSTAT = IN,OT,DC
2015-05-06T22:16:20.67432 SUS_ITMY W:   H1:SUS-ITMY_M0_TEST_Y_TRAMP = 2.0
2015-05-06T22:16:20.67436 SUS_ITMY W:   H1:SUS-ITMY_R0_OPTICALIGN_P_TRAMP = 2.0
2015-05-06T22:16:20.67446 SUS_ITMY W:   H1:SUS-ITMY_R0_OPTICALIGN_Y_TRAMP = 2.0
2015-05-06T22:16:20.67455 SUS_ITMY W: 66 PVs, 10 SPMs
2015-05-06T22:16:20.67828 SUS_ITMY W: SPM snapshot: /ligo/cds/lho/h1/guardian/archive/SUS_ITMY/SUS_ITMY.spm

H1 SEI

Print this report.

thomas.shaffer@LIGO.ORG - posted 13:37, Tuesday 05 May 2015 (18251)

BRS Damper turned back on

The BRS settled down to about +/-7000 counts, so I went down to the end station and turned the damper back on but I did not do the gravity dance with it. It should still take a bit for the damper to settle the BRS down to its nominal range so it is not yet usable.

H1 AOS (ISC, SUS)

Print this report.

kiwamu.izumi@LIGO.ORG - posted 13:25, Tuesday 05 May 2015 (18246)

PR3 oplev not functioning

Jason, Kiwamu,

PR3 oplev has not been properly behaving. We don't know when it ran into the issue. We will take a close look in the next maintenance Tuesday as we are suspecting a bad QPD and/or bad electronics.

[Cross-coupling issue]

Currently the symptoms are that:

Moving the PR3 suspension in pitch shows a large cross coupling to yaw (more than 50%) and the same is true when moving the suspension in yaw.
When each segment receives equal amount of light, segment 2 seems to respond much lesser than everyone else to the suspension angular motion.

At this point, we are not sure if this is due to a bad QPD segment or some kind of electrtonics issue.

[Dip switch confusion]

Independently of the cross-coupling issue, we found that a dip switch for the seg3 whitening filter had been set differently than the rest of three segments. We thought this would fix the cross coupling issue at the begginig, but switching it to the position that everyone else have been did not solve the issue because the cross-coupling behavior which is described above arose in turn. It is unclear how long the dip swtich has been in this configuration. Note that the last maintenance activity on PR3 was performed almost a month ago (on 7th of this April, alog 17722)

LHO VE

Print this report.

kyle.ryan@LIGO.ORG - posted 13:17, Tuesday 05 May 2015 (18250)

Prepped BSC6 RGA for bakeout

Changing WP #5182 -> had intended to bake out BSC6 RGA for 24 hours starting today but will bake in 4 hour increments over the next few maintenance days instead -> As such, pump cart at BSC6 will only run during maintenance periods.

H1 SUS

Print this report.

betsy.weaver@LIGO.ORG - posted 12:48, Tuesday 05 May 2015 - last comment - 12:52, Tuesday 05 May 2015(18244)

Update to SUS status screen

After the guardian states were rekeyed during the March SUS guardian revamping (alog 17259), the SUS_GUARDIAN_STATES_OVERVIEW_CUST.adl screen has been incorrectly displaying the SUS GRD status. Today I fixed this and now the status lights accurately represent what state the SUS GRD is in.

Images attached to this report

Comments related to this report

betsy.weaver@LIGO.ORG - 12:52, Tuesday 05 May 2015 (18247)

Note, here's is the address of the medm file:

/opt/rtcds/userapps/release/sus/common/medm

H1 CDS

Print this report.

david.barker@LIGO.ORG - posted 12:48, Tuesday 05 May 2015 (18245)

CDS Maintenance Summary

ALS build against RCG2.9.2 [WP5183]

Jeff, Jim:

h1alse[x,y] models were built against RCG Tag2.9.2 and restarted. No DAQ restart was required. RCG version number on the GDS_TP screens is 4002 for this build.

DAQ reconfiguration [WP5184]

Jeff, Jim, Dave:

The DAQ was restarted at the following local times: 07:24, 07:25, 09:58, 11:39

The first two restarts were to apply the new INI files if they had been updated (they had not). The first raised DAQ errors on certain front ends, the second was to see if they could be cleared.

The third was to apply the new H1BROADCAST.ini and H1EDCU_HWS.ini files. Again certain front ends needed their mx-streams restarted.

It was then found that dataviewer would not show any fast channels in the signal selection list, and the slow channels were not quite correct. Jim tracked this down to a badly formed line in my updated H1EDCU_HWS.ini file. I have forgotten to put a close-square-bracket at the end of one channel. This was corrected and the fourth DAQ restart applied the fix (this time no frontends were DAQ glitched).

Take home message, always run inicheck on new ini files.

Guardian Reboots:

Jamie, Betsy, Jeff, Dave:

we rebooted the h1guardian0 machine twice this morning. First was to see what the load averages start with after a reboot (answer, 7 after 1 hour running). The second was to apply Jamies newer version of guardian.

prior version (guardian, ezca) = 1390,443

new version = 1445:474

H1 SEI

Print this report.

jim.warner@LIGO.ORG - posted 12:33, Tuesday 05 May 2015 - last comment - 13:31, Tuesday 05 May 2015(18243)

DARM and EX/Y ISI St1 blends

On Saturday, I was able to get some data on the effect of different blend filters on DARM. It looks like we probably don't want to be using the 45mhz blends, or they need some re-working to reduce their low frequency performance. The attached plots are DARM from 2 lock stretches on Saturday. This is the CAL CS DELTAL spectra, which Jeff helped me calibrate, hopefully he'll explain in a comment. Blue traces are both end stations with 45mhz blends, orange traces are both end stations with 90 mhz blends, black is the ground. Ground was pretty similar between the 2 cases, range was similar, though slightly higher with the 90mhz blend, possibly better alignment? First plot is .01 hz to 3 hz, where most of the action is, the second plot is 1hz to 100hz.

The first plot shows the 90 mhz blend does as well as the 45mhz blend down to .3 hz, then does a factor of several worse until ~50mhz, where the gain peaking on the 45mhz blend causes more motion. Above 1 hz the 90mhz blend shows more RMS, I'm not sure of the cause, but there are features visible in the second plot at about 8-15hz that I don't understand. But they are probably not due to the blend change.

Images attached to this report

Comments related to this report

jeffrey.kissel@LIGO.ORG - 13:31, Tuesday 05 May 2015 (18248)CAL, DetChar, ISC, SEI

The method for calibrating the CAL-DELTAL_EXTERNAL_DQ DARM spectrum and getting it "right" around and below 10 [Hz]:
(1) undo the 5 zeros at 1 [Hz], 5 poles at 100 [Hz] whitening DAQ filter LHO aLOG 16702 as one would normally do for this channel at all frequencies.
(2) compensate for the digital UIM control filter (FM1 & 2, "int" and "lowboost", two poles at 0 [Hz], two zeros at 0.1 and 0.3 [Hz]) that we don't replicate in the CAL-CS actuation path because of numerical precision noise. (See LHo aLOG 17528)

That means, in DTT, one has to apply the following calibration filter:
Gain: 0.03
Poles: 1,1,1,1,1, 0, 0
Zeros: 100,100,100,100,100, 0.3, 0.1
where the gain of (exactly) 0.03 is to normalize the z:p = ([0.3 0.1] : [0 0]) filter necessary for getting the actuation at low frequencies correct in step (2) -- i.e. 
prod(2*pi*[0.3 0.1]) / (2*pi)^2 = 0.03

Why (2) works:
Remember that DELTAL_EXTERNAL is the sum of the calibrated DARM_ERR and DARM_CTRL channels,
DELTAL_EXTERNAL = (1 / C) * DARM_ERR + A * DARM_CTRL
where C is the sensing function (i.e. the IFO's "test mass DARM displacement sensor" calibration) and A is the actuation function (i.e. the ETMY transfer function). A dominates this sum below the DARM UGF at ~40 [Hz]. As such, well below 40 [Hz],
DELTAL_EXTERNAL ~ A * DARM_CTRL.
Since we're using hierarchical feed back to ETMY, where the UIM/TST or L1/L3 cross-over frequency is ~1 [Hz], then well below *that*,
DELTAL_EXTERNAL ~ A_{uim} * DARM_CTRL,
i.e. the total calibration for DELTAL_EXTERNAL "well" below 1 [Hz] is dominated by how accurately we reproduce / calibrate / model the UIM actuation path. Since the UIM digital filters we've intentionally left out in CAL-CS have frequency content below ~0.5 [Hz], they're simply "missing" from the calibration of DELTAL_EXTERNAL, and we can, offline, just multiply all of DARM by these filters, and get the "right" answer.

This being said, *all* calibration below 10 [Hz] still should be treated with some skepticism, because we have little-to-no precision measurements of the scale factor, DARM OLGTF frequency dependence, and/or TST/UIM cross-over frequency in this band (and we don't plan on making any). I could say it's "within a factor of two," because I think we've done everything right, but I have no measured proof to bound the uncertainty quantitatively. 

Above 10 [Hz], the latest estimate of precision and accuracy are described in detail in LHO aLOG 18186.

H1 GRD (GRD, SEI, SYS)

Print this report.

jeffrey.kissel@LIGO.ORG - posted 11:38, Tuesday 05 May 2015 - last comment - 13:13, Tuesday 05 May 2015(18240)

ISI HAM3 Guardian Fails to Advance Past

J. Kissel, D. Barker, B. Weaver

After the first reboot of the guardian machine this morning, all SEI chambers except HAM3 came up as expected: the SEI manager and ISI / HPI subordinates are coded to be smart enough to figure out what state the platforms are actually in and restore to that state upon initialization. HAM3's ISI subordinate did not. I was able to identify it because the HAM3 SEI manager was complaining that it's subordinate's request had changed. The solution was to simply by-hand change the request to HIGH_ISOLATED.

No big problem here, just want to start recording the outcomes of reboots so we can address any systematic issues. Note this did *not* happen on the second guardian machine reboot today.

Images attached to this report

Comments related to this report

jeffrey.kissel@LIGO.ORG - 11:58, Tuesday 05 May 2015 (18241)

This also happened for HEPI HAM1, at least after the second reboot. BUT this may be because he's unique in that it doesn't have a SEI chamber manager telling him where to go, not because of any errant code.

I've manually moved the requested state to ROBUST_ISOLATED, which is where the platform was already.

jameson.rollins@LIGO.ORG - 13:13, Tuesday 05 May 2015 (18249)

These are two totally different issues. The HPI_HAM1 issue is just because it doesn't have an initial request state defined. I think Hugh has now fixed that.

H1 AOS (SUS)

Print this report.

kiwamu.izumi@LIGO.ORG - posted 10:42, Tuesday 05 May 2015 (18237)

oplev calibration on ETMX and ETMY

Jason, Kiwamu,

We revisted the calibration of the oplev on ETMX and ETMY which showed calibration error of a factor of a few (alog 18218). In fact, they alll had underestimated the suspension angle by roughtly a factor of two. Here is a summary table of the calibration factors:

	old calibration [urad/cnts]	new calibration [urad/cnts]
ETMX PIT	81.2	222.5
ETMX YAW	115.2	263.4
ETMY PIT	77.94	172.2
ETMY YAW	53.55	115.4

We also updated the SDF so that these new values are already reflected. Note that the number I updated yesterday was not accurate enough (alog 18218) since I was using the misaligned ETMX. We calibrated it again with the aligned suspension. I attach the measurement data nad fitting codes as a zip file.

Non-image files attached to this report

H1 ISC

Print this report.

filiberto.clara@LIGO.ORG - posted 10:30, Tuesday 05 May 2015 - last comment - 11:03, Tuesday 05 May 2015(18238)

QPD Whitening Filter Chassis Replaced - EY

Replaced QPD Whitening Filter Chassis S1101595 with S1101628. Keita reported 900 count DC offset on segment 2.

Comments related to this report

richard.mccarthy@LIGO.ORG - 11:03, Tuesday 05 May 2015 (18239)

Looks like the spring influx of wildlife has had ramifications on our IFO.  More testing will be done but looks like mice may have contributed to the problem with the whitening chassis.  An opAmp was covered in corrosion and other problems on the board looked like a mouse outhouse.  We have cleaned and disinfected the chassis and are waiting for it to dry before doing more tests.
See attached photo

Non-image files attached to this comment

H1 SEI

Print this report.

hugh.radkins@LIGO.ORG - posted 10:02, Tuesday 05 May 2015 - last comment - 12:22, Tuesday 05 May 2015(18235)

HEPI Pump Stations Pressures shown little coherence with IFO control signals during run

Similar to yesterday's plot but I've added MICH SRCL & PRCL

See the attached three panel for all the three building Pressures coherence to trhe IFO control signals.

Corner Station had coherence approaching 0.7 with Mich at ~20mHz, everything else is less.

Images attached to this report

Comments related to this report

hugh.radkins@LIGO.ORG - 12:22, Tuesday 05 May 2015 (18242)

Scanning through coherence plots from the LVEA pressure to individual platforms and DOFs finds some continuous coherence to the HPI BS RZ. See it on the upper right panel of the attached graph. The thin dark green is the current coherence and still not as bad as the pale thick lighter green reference line from before our controller tweeking back in Jan/Feb. However, there is a fair swath of non zero area from a few mHz to 100mHz. The same area where we see some coherence with MICH.

So why is the BS the most coherent. While the pump servo does get its signal from the pressure sensors at the BS, I'm more suspicious about the very large constant drive the Z DOF on the BS is currently applied by HEPI. When the Pump Stations are off, the BS HEPI sags so low that some of the vertical IPS are out of their linear range. This requires the DC BIAS to be almost 400um for the Z DOF. Maybe this gives us some Z to somethin-mich-is-sensitive-to coupling. It is on our wish list to lift this up with the HEPI Mechanical Springs.

Images attached to this comment

Displaying reports 67281-67300 of 85053.Go to page Start 3361 3362 3363 3364 3365 3366 3367 3368 3369 End