Displaying reports 67761-67780 of 84478.Go to page Start 3385 3386 3387 3388 3389 3390 3391 3392 3393 End
Reports until 15:48, Tuesday 10 March 2015
H1 CAL
jeffrey.kissel@LIGO.ORG - posted 15:48, Tuesday 10 March 2015 (17179)
h1calcs model with new gamma calculation installed
J. Kissel

I've compiled, installed, and restarted the h1calcs front-end code to absorb the changes described in LHO aLOG 17114 this morning. Most of the changes require brand-new custom MEDM screens (yaaaayyyy), so I'll post more of how the infrastructure has been filled in once I have some screens to show. For now, I've confirmed that the DARM calibration stuff is still ON and the input for the slow optical gain correction is turned OFF, and NOT changing the DARM calibration.
H1 ISC
daniel.sigg@LIGO.ORG - posted 13:57, Tuesday 10 March 2015 (17176)
EtherCAT software updates

A couple of EtherCAT software problems were address today:

Images attached to this report
H1 CDS (DAQ)
james.batch@LIGO.ORG - posted 13:49, Tuesday 10 March 2015 (17177)
Awgtpman for h1asc is
The h1asc awgtpman is a special version which will allow the full 64 test points to be set.  In order to do this, the awgtpman_h1asc.cmd script (generated by RCG) was replaced with a hand-edited version which starts up awgtpman-2.9-asc-special (instead of awgtpman) and also includes a -A option to the command line.

If the h1asc model is rebuilt, this will be undone by the RCG. Coordinate model rebuilding and restarting with Jim Batch in order to ensure the modified awgtpman is running.  

This is a temporary solution to allow commissioning to continue where more testpoints are needed.  We will decide on a complete solution for the next RCG release.
LHO VE
john.worden@LIGO.ORG - posted 13:21, Tuesday 10 March 2015 (17175)
X1 Beam Tube Pressure during wash process.

The two plots show the vacuum gauges at either end of the X1 module for the past 100 days.

The features shown are due to large gate valve closures at the corner station. PT144 is next to the corner station while PT343 is at the Mid station.

Images attached to this report
H1 CDS
patrick.thomas@LIGO.ORG - posted 13:09, Tuesday 10 March 2015 (17174)
Updated alarm handler config file for dust monitors
I removed the locations that are not currently used. This cleared all the invalid alarms. All that remain are the calibration errors for the dust monitors in the optics lab and bake out room.
H1 GRD (GRD, ISC, SUS, SYS)
jeffrey.kissel@LIGO.ORG - posted 12:32, Tuesday 10 March 2015 (17173)
An Exercise in Guardian Management Initialization
J. Kissel, B. Weaver, J. Rollins

We (Betsy and I) had begun returning all the corner station SUS to ALIGNED while Jamie was restarting all of the Guardian code. After the dust settled, we noticed that ITMY and PRM were stalled in their SAFE state. After a little bit of poking around in the guardian logs, we discovered that upon initialization, LSC_CONFIGs manager took possession of SUS_ITMY and SUS_PRM as expected. However, a minute or so after, when the IFO_ALIGN manager initialized, it superseded control. Neither the LSC_CONFIGS nor IFO_ALIGN managers' initialization state is coded enough to acknowledge that its subordinate has stalled in SAFE and to issue its commands, so the SUS remained stalled in SAFE. 

This *didn't* happen on any of the other SUS because the SUS were already in the ALIGNED state -- the state that IFO_ALIGN (who had gained management this time) expects them to be in -- so no action was taken. Betsy and I had not yet gotten to requesting ALIGNED of PRM and ITMY. Therefore the nodes went down in the SAFE condition, restarted, initialized, found the SUS in the SAFE state, jumped to SAFE, and stalled because their manager didn't tell them to continue up to the requested state of ALIGNED.

In summary, there are several flaws that caused this issue:
- PRM and ITMY (and probably other SUS) are doubly managed by LSC_CONFIGS and IFO_ALIGN.
- LSC_CONFIGS lost management of PRM and ITMY, and didn't acknowledge it or throw a warning. Nor did LSC_CONFIGS notice the stall and tell the SUS to keep going.
- IFO_ALIGN doesn't know how to handle a stalled subordinate node; again, upon initialization, it doesn't acknowledge the node is stalled, throw a warning, or do anything about.
- Globally, the ISC managers were not properly initialized to send out the proper commands to their subordinates upon a reboot.

We've relieved the stall by asking LSC_CONFIGs directly to go to DOWN (even though LSC_CONFIGS itself is managed by ISC_LOCK). LSC_CONFIGS then regained control of SUS_PRM and ITMY, and they traversed their graphs to ALIGNED as expected.

We'll work with the ISC team to sort out the management confusion and flush out the proper initialization sequence.
H1 SEI
hugh.radkins@LIGO.ORG - posted 12:07, Tuesday 10 March 2015 (17172)
Corner Station HEPI Pump Station Maintenance & Pressure Disruptions

There was some pressure excursions that may impact platform position/performance from 1608 to 1638utc on 10 March 2015.

Fluctuations of +- a few PSI were experienced--See Attached 30 minute trends of Pressure and Motor control drive.  Usually, with the servo in Auto control, a pump station can be ramped down over 300 seconds and the servo would keep the pressure up by speeding up all the other Pump Stations.  However, with the 10mhz controller parameters, it was not keeping it at set point and the controller was switched to manual and dealt with by hand.  We usually always have a glitch right at the end of the ramp down or ramp up in Pump Station output as we close/open the valve (keeping the pump from rotating backwards.)  We will examine why the pump stations could not keep these at Set point--Since this ramp down is just a abruptly starting linear ramp in motor speed, the frequency (at the start at least) was likely too fast for the servo.  Not too much harm anyway, no HEPI Platforms tripped at least.

Maintenance Performed: Pump Stations 5 & 6 (Check medm or Pump Station label) had motor grease added (2 tsp=5 gun pumps) in each of two bearings.  Accumulator pressures checked, #1 on PS was very low.  All others near nominal (60-90% of operating fluid pressure, set with no fluid pressure.)

Images attached to this report
H1 CDS
patrick.thomas@LIGO.ORG - posted 10:46, Tuesday 10 March 2015 (17169)
Conlog restarted
Stopped running this morning with the following error:

Mar 10 09:05:08 h1conlog1-master conlog: ../conlog.cpp: 301: process_cac_messages: MySQL Exception: Error: Out of range value for column 'value' at row 1: Error code: 1264: SQLState: 22003: Exiting.
H1 GRD
jameson.rollins@LIGO.ORG - posted 10:16, Tuesday 10 March 2015 (17168)
Guardian install updated; all nodes restarted

All guardian nodes have been upgraded to the latest version of guardian and cdsutils:

The guardian machine (h1guardian0) was rebooted and all nodes came up fine with the latest versions.

The only issue has been a problem with the latest nds2-client install that is not properly exporting the nds2-client python bindings.  So far this is only affecting OMC_LOCK.  This should be fixed momentarily.

Release notes

These changes include a couple of bug fixes and one new feature:

H1 ISC
stefan.ballmer@LIGO.ORG - posted 09:56, Tuesday 10 March 2015 - last comment - 01:11, Saturday 14 March 2015(17166)
2h lock overnight
We left the IFO on a DC lock last night. Attached is the spectrum. Two nights were notable:

1) The hump around 800Hz (apparently known as "twin peaks") was bigger than ever. Interestingly it was NOT there at all during earlier locks during the day. The only thing we know we did between the locks was a complete initial alignment. Also, over the period of about 1h, the hump completely disappeared.

2) The low-frequency noise (20Hz to 100Hz) is significantly less stationary now. (This did not improve over time.)
Images attached to this report
Comments related to this report
stefan.ballmer@LIGO.ORG - 11:39, Tuesday 10 March 2015 (17171)
ASC showing up in displacement / roll mode ringup

a) The first plot, middle graph, shows coherence between ASC loops and DARM. CHARD shows up very prominently - it's narrow stop-band get imprinted on the coherence. The same noise is also seen in IMP1_P, but it is likely just a witness, since it shares sensors with CHARD. Bottom lime: CHARD needs a proper low-pass.

b) The first plot, bottom graph shows some coherence between the 20Hz-100Hz excess and ASC_MICH_P. ASC_SRC2_P also shows it, but might again just be a witness (it uses AS_C as error signal). That excess BTW is all glitches.

c) The roll mode was seen to ring up over the 2h lock. Interestingly both ETMX and ETMY modes seem to be ringing. Since DARM feedback only goes to ETMX, but CHARD goes to both, I again suspect CHARD. Again: CHARD needs a proper low-pass.

Images attached to this comment
daniel.hoak@LIGO.ORG - 17:08, Tuesday 10 March 2015 (17184)

The bounce and roll mode ringups were due to human intervention -- Chris and I stayed a bit later last night working on the violin mode damping, and we couldn't resist changing the gains on the feedback loops, enough that things became unstable.  At 09:10 UTC when Stefan took his DTT spectrum, the gains on the feedback were nonzero, which impresses bounce & roll mode noise on the M0 stage OSEMs.  When the feedback gain is zero you can't see these modes in the top stage OSEMs -- this makes identifying the optic that's bouncing or rolling a challenge.  It may have been only one ETM was rolling, or an ITM (although I suspect both ETMs thanks to the ASC loops, as Stefan says.)

The attached images from the summary pages show the roll mode increasing around 09:40 UTC, when we realized our feedback was hurting more than helping.  After this I zeroed the gain on the DARM --> ETM M0 feedback and the mode stayed the same height for the rest of the night.  (When the noise got very bad after 11:00 UTC the bounce mode stayed pretty much the same.)

That said I would not argue against some roll-off filters for CHARD!

Images attached to this comment
christopher.wipf@LIGO.ORG - 01:11, Saturday 14 March 2015 (17266)

The attached screencaps show the roll mode damping setup that has worked well for us, tonight. (ETMX gain 10000/ETMY gain -600)

Images attached to this comment
LHO General
patrick.thomas@LIGO.ORG - posted 09:35, Tuesday 10 March 2015 (17165)
Morning meeting notes
Lots of maintenance activity planned, please see white board.
LVEA to be transitioned to laser safe.
H1 CDS (DAQ)
james.batch@LIGO.ORG - posted 09:08, Tuesday 10 March 2015 - last comment - 10:47, Tuesday 10 March 2015(17162)
Updated NDS2 Client Software
WP #5094

The NDS2 client software has been updated to nds2-client-0.11.4 for Ubuntu 12.04 workstations.
Comments related to this report
james.batch@LIGO.ORG - 10:47, Tuesday 10 March 2015 (17170)
Updated user environment configuration script to include LD_LIBRARY_PATH and PYTHONPATH environment variables.
H1 SUS (CAL, DetChar, IOO, ISC, SUS)
jeffrey.kissel@LIGO.ORG - posted 07:38, Tuesday 10 March 2015 - last comment - 09:30, Tuesday 10 March 2015(17159)
Maintenance Day Prep & Corner-station SUS in SAFE for Free-Swinging ASDs
J. Kissel

Came in and IFO had been unlocked for ~1.5 hours. In preparation for today's maintenance activities, I've brought the IFO_LOCK guardian to DOWN, and saved any alignments that had not yet been saved -- specifically the ITMs, SR3, the OMC, and the three OMs. 

Such that @DetChar can get a few hours of undamped / fre-swinging SUS before the DAQ restart that will be needed after this morning's front-end model changes, I've requested the IMC_LOCK guardian to DOWN, and turned off the input to the IMC common mode board, and requested all of the following suspensions to be in SAFE:
PRM, PR2, SRM, SR2, SR3, MC1, MC2, MC3, BS, ITMX, ITMY.
This has been the case since 14:26 UTC (7:26a PDT).

I plan to leave the SUS in this state until 17:00 UTC, or 10a PDT -- THEN we can do a DAQ restart to capture all of the channel name changes, but we don't need to wait to make the model changes.

In this state, we need NOT halt any LVEA incursions. Go on in at your leisure.
Comments related to this report
jeffrey.kissel@LIGO.ORG - 08:03, Tuesday 10 March 2015 (17161)
Due to miscommunication, SRM was aligned briefly at 15:01 UTC. Take SRM off the list of SUS that have been free and undisturbed for these hours. We'll get him on Thursday.
jeffrey.kissel@LIGO.ORG - 09:14, Tuesday 10 March 2015 (17163)
ITMX ISI Tripped at 16:14 UTC. Take him off the list.
jeffrey.kissel@LIGO.ORG - 09:30, Tuesday 10 March 2015 (17164)DetChar
Period of free resonances is now closed as of 16:30 UTC. Other maintenance activity begins!
H1 ISC
stefan.ballmer@LIGO.ORG - posted 19:47, Monday 09 March 2015 - last comment - 19:13, Wednesday 11 March 2015(17151)
New DARM filters implemented
Alexa, Sheila, Evan, Chris, Stefan

We implemented Peter's DARM 'SUScomp' from alog  16728. Since we can't lock with that filter directly (see alog 16840), deleted the old 'LLO' filter, but instead loaded a difference filter called 'acqLP' that makes the 'SUScomp' look like the old 'LLO' filter:
  zpk([80;500-800i;500+800i],[50;70;200],1,"n")

Guardian was updated to turn off acqLP' in FM8 instead of turning on a lead.



A note on the previous filter is also found in alog 16381.

Comments related to this report
alexan.staley@LIGO.ORG - 20:04, Monday 09 March 2015 (17152)

I have attached a plot comparing our various configurations:

1. Red trace: RF DARM sus compenstation as designed by Peter to obtain more phase margin. The LSC DARM configuration is: FM1(suscomp), FM2(2:0), FM3(resG), FM4(4^2:1^2), FM5(2:0), Gain 800 (LHO#16728, 16840)

2. Blue trace: Our old RF DARM sus compenstation where we used the LLO control filer and a 200Hz lead filter. (LHO#16381)

3. Green trace: ALS DIFF sus compensation. This is the configuration we use to lock ALS DIFF. The LSC DARM configuration is: FM1(suscomp), FM2(2:0), FM3(resG), FM7(SB60), FM8(acqLP),FM10(RLP33), Gain 400. As Stefan mentioned, FM1+FM8 returns our old LLO control filter.

 

I have also attached the RF DARM OLTF model with the new (red) and old (blue) configuration as described above, along with the respective measured data. The RF DARM UGF is now 55 Hz with a phase margin of ~45deg.

Images attached to this comment
Non-image files attached to this comment
evan.hall@LIGO.ORG - 20:00, Monday 09 March 2015 (17153)

Measurement of new DARM loop on dc readout is attached.

Non-image files attached to this comment
jeffrey.kissel@LIGO.ORG - 07:58, Tuesday 10 March 2015 (17160)CAL
I've saved Evan's .xml to the calibration repository here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Measurements/DARMOLGTFs/2015-03-09_DARM_OLGTF_LHOaLOG17153.xml
and exported text files of the transfer function and coherence,
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Measurements/DARMOLGTFs/
2015-03-09_H1_DARM_OLGTF_LHOaLOG17153_coh.txt
2015-03-09_H1_DARM_OLGTF_LHOaLOG17153_tf.txt

Transfer function contains the following columns (i.e. I exported IN1 / IN2 "as is"):
Frequency [Hz]    Real Part [ ]    Imaginary Part [ ]

We'll use later for calibration / noisebudget model verification!
Non-image files attached to this comment
evan.hall@LIGO.ORG - 10:32, Wednesday 11 March 2015 (17196)

Also including the CARM OLTF that we took at 9 W.

Non-image files attached to this comment
kiwamu.izumi@LIGO.ORG - 19:13, Wednesday 11 March 2015 (17206)ISC

I checked the measured DARM open loop transfer function posted by Evan against my DARM open loop model. Even though I did not do a fitting or any fancy analysis yet, it seems that the optical gain was consistent -- the measurement matched the model with an optical gain of 1.1x106 cnts/m or 9.09x10-7 m/cnts which we have been using since Feb. 21st (alog 16843) for the CAL-CS front end model.

Here is a plot showing the model and measured one:

The matlab script to generate this plot is archived in calSVN:

 /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Scripts/DARM_OLTFGTF_LHOaLOG17153.m

 

Note for myself:

optical gain in the model = 1.1e6

ESD strength in the model = 2.8e-10 [N/V^2] (see alog 16843)

LSC_DARM_GAIN = 800 (instead of 400)

Only ETMX was actuated

Images attached to this comment
H1 ISC
sheila.dwyer@LIGO.ORG - posted 14:43, Wednesday 28 May 2014 - last comment - 15:42, Tuesday 10 March 2015(12120)
Whitening not switching and solution

The corner whitening filters were not switching, with an error message invalid data chn and readback different for Refl 9 and refl air 9, and for POP we had an error message invalid data for channels 1, 2, 3 and 4. 

Daneil fixed this by going to the system manager for the corner, finding the X gateway under device 1, corner MSR L0, Corner MSR L8_9 Vertex, going to the Online tab, and clicking on several of the buttons under state machine (Init, pre-op, safe op, op) in an order that seemed random to me. 

I am just writing down the solution to this problem so that we can look it up next time it happens.

Comments related to this report
sheila.dwyer@LIGO.ORG - 15:42, Tuesday 10 March 2015 (17178)

This happened again, we repeated what we did, on the Corner Chassis 2 L-2 (X-gateway) under Online the current state was safeop.  We hit a bunch of buttons (including clear error) until it arrived in OP.  We repeated this for L-1, which was also in safe OP.  

An alternative solution would be to restart h1ecatc1

Displaying reports 67761-67780 of 84478.Go to page Start 3385 3386 3387 3388 3389 3390 3391 3392 3393 End