Displaying reports 71081-71100 of 84550.Go to page Start 3551 3552 3553 3554 3555 3556 3557 3558 3559 End
Reports until 23:38, Tuesday 09 September 2014
H1 ISC (SUS)
sheila.dwyer@LIGO.ORG - posted 23:38, Tuesday 09 September 2014 (13852)
SRY actuators

Sheila, Alexa, Lisa, Kiwamu

Today we went back to locking SRY as described in 13726, to try make sure we have some reasonable crossovers for the SRC actuation.

First we adjusted the phase for AS_45, to -71.9.  We also had to flip the sign, so we are now locking with a gain of -400 in SRCL. 

we are using a gain of 1 in SRM and SR2 ISC INF. 

After talking to Ryan we moved the 27 Hz notch to the SRM M2 lock filter, and disengaged the 27Hz notch in SRM ISCINF.  This keeps the DAC from saturating at the 27 Hz vertical mode, without causing a notch in the open loop gain.  

We have a ugf of about 30 Hz, measurements in the SRM path and the SRM M2 path are also attached.  It seems that we do not ring up the vertical mode in SR2 as easily as we ring it up in SRM. 

Images attached to this report
H1 SEI
jeffrey.kissel@LIGO.ORG - posted 21:40, Tuesday 09 September 2014 (13850)
H1 ISI ITMY DACKILL State Variable Missing
Causes outer "ability to drive" boarder to go white on overview screen.
H1:ISI-ITMY_ST1_WD_MON_STATE_INMON 
H1:ISI-ITMY_ST1_MASTER_SWITCHMON 
H1:ISI-ITMY_DACKILL_STATE         <-- This one shows red on middle click.
H1:IOP-SEI_B1_DACKILL_STATE
Images attached to this report
H1 SEI
jameson.rollins@LIGO.ORG - posted 21:29, Tuesday 09 September 2014 (13719)
'NOMINAL' states added to SEI guardians

[This work was done last week, but I forgot to submit this log.]

I added NOMINAL state definitions for all SEI systems, including HPI, ISI stages, and HAM and BSC chamber managers.  All SEI guardian nodes were restarted to affect these changes.

NOMINAL state for HAM managers is "ISOLATED".

NOMINAL state for BSC managers is "FULLY_ISOLATED" (HPI and both ISIs isolated).

NOMINAL state for HPI is "ROBUST_ISOLATED", for both HAMs and BSCs.

NOMINAL state for ISI stages is "HIGH_ISOLATED".

Other than HAM 5 and 6, which are still being commissioned, everything except BS is set to be in the NOMINAL state, and is in the NOMINAL state.

We are currently operating the BS ISI with only stage 1 isolated, and stage2 left damped, corresponding to "ISOLATED_DAMPED" in the BS chamber manager (MICH locking has a tendency to trip the ISI stage 2 if isolated).  However, I decided to leave the NOMINAL settings to the default for ISI_BS_ST2 and SEI_BS, so that we're reminded to address this issue down the line.  Here's a crop from the GUARD_OVERVIEW, showing that the SEI_BS and ISI_BS_ST2 are not in their nominal states, as indicated by the far left OK indicators being orange:

We still need to add numeric indices for all the SEI states.  This will require a bit more work for SEI since the HPI and ISI states are generated based on the particular configuration.

Images attached to this report
H1 SEI (DetChar)
jeffrey.kissel@LIGO.ORG - posted 21:16, Tuesday 09 September 2014 - last comment - 09:57, Friday 12 September 2014(13848)
Random HAM2 HAM3 ISI Trip
J. Kissel, J. Rollins, S. Dwyer, A. Staley

While Sheila and Alexa began to lock PRMI on carrier, the HAM2 and HAM3 HEPI and ISIs tripped for an unknown reason. We'll leave this to people offline to figure out what happened. See attached actuator trip plots from the ISIs.
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 21:36, Tuesday 09 September 2014 (13849)
Again with the tripping. Only HEPIs this time. Only in the vertical direction.
Images attached to this comment
jeffrey.kissel@LIGO.ORG - 21:45, Tuesday 09 September 2014 (13851)
Now can't bring up HAM2 or HAM3 HEPIs with out tripping. Took a look at HEPI pump controller -- the screen's not very non-expert friendly, but there's a red light at the pressure indicator ...
Images attached to this comment
hugh.radkins@LIGO.ORG - 08:25, Wednesday 10 September 2014 (13857)

Pump System is fine--80psi at the output.

Sorry about the medm--been waiting for the long promised Beckoff system to upgrade channels etc.  The Red light is the reservoir level, not pressure; the level switch is not hooked up to system.

jeffrey.kissel@LIGO.ORG - 09:48, Thursday 11 September 2014 (13880)CDS, DetChar
This issue was (sadly) resolved with a restart of front-end processes; see LHO aLOG 13858.

If DetChar's bored they can help CDS trace the problem by grabbing the exact time of failure.

SEI Team -- is the CDS state word used in computing the "you have the ability to drive" outer ring of green?
hugh.radkins@LIGO.ORG - 09:57, Friday 12 September 2014 (13901)

Jeff--The first step of the out ring of the HEPI medm not being green is to go orange or something like that.  This means only that the HEPI L4C have seen some saturations and the counter is no longer zero.  The system is still operating normally even though the medm perimeter is not green.

I don't think this is used to calculate the ODC state bit--I'll investigate.--Jeff, I'm not sure what the CDS state words is.  The ODC state word is green now on ITMX HEPI where the outer perimeter is orange and the Isolation loops are closed.

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 20:31, Tuesday 09 September 2014 (13846)
CDS model and DAQ restart report, Monday 8th September 2014

model restarts logged for Mon 08/Sep/2014
2014_09_08 12:41 h1fw0

unexpected restart of h1fw0.

H1 AOS
jason.oberling@LIGO.ORG - posted 17:20, Tuesday 09 September 2014 (13844)
ITMy OpLev Laser Replaced, No Change

As the title says.  I replaced the ITMy oplev laser today and there is no change.  Data looks exactly the same as in Keita's previous alog.  Will continue to investigate tomorrow.

LHO VE
kyle.ryan@LIGO.ORG - posted 16:40, Tuesday 09 September 2014 (13842)
X-end vacuum configuration change -> Closed GV20, valve-out IP12, valved-in turbo
GV20 to have been closed next week anyway for X2 pressure accumulation 
H1 DAQ
james.batch@LIGO.ORG - posted 16:10, Tuesday 09 September 2014 (13841)
Restarted h1nds1
Found h1nds1 had died about 15:49 PDT.  Rebooted computer, as it was unresponsive.  Note that the daqd process for h1nds1 had restarted itself at 15:30 PDT.
LHO General
edmond.merilh@LIGO.ORG - posted 16:00, Tuesday 09 September 2014 (13827)
Daily Ops Log

08:04 Karen - mopping at exit door in LVEA.

08:21 Aaron and Fil to LVEA to pull power cables for Illuminators and cameras from HAM3 F rack to Biergarden. Also, install junction box on top of HAM3 field rack. Drilling will be done and vacuums will be used.

08:25 Hugh to End stations to check on HEPI pumps.

08:47 Fire Dept on site to do annuals on fire extinguishers

09:02 D Barker - out to LVEA to start the Quad tst stand FE

09:59 Quad tst stand back up. Dave and Jim to restart OAF

10:11 Cris to End-X 

10:20 Richard out to LVEA by Fil

10:35 OAF is back up

10:47 J Kissell taking down HAM4,5 ISI to recompile model to include OpLev

10:57 Richard out of LVEA

10:58 P King into H1 PSL enclosure to execute work permit 

11:02 Hugh back from end stations

11:06 Jason out o LVEA to swap out ITMY oplev LASER

11:07 D Barker - DAQ restart

11:11 Praxxair called 10 minutes ahead of delivery - en route

11:55 Jason out for AHM 

12:00 All HANDS MEETING

13:43 Jason back into LVEA -replace bad power supply at IMTY oplev

14:27 Alistair into LVEA to "play with LASERS" - his words.

14:50 Mitch into the LVEA

15:00 Mitch out of the LVEA

15:45 Jason out of LVEA - apparently successful

 

H1 SEI
hugh.radkins@LIGO.ORG - posted 15:11, Tuesday 09 September 2014 (13839)
WHAM4 ISI deep zero may be explained by HEPI controller

BrianL Hugo JimW Hugh

When I collected HAM4 TFs 3 Sept, a deep zero here seen in the first plot as compared to the second, caught our eyes and it looks to be a problem possibly in the HEPI Isolation loop.

Here is the transverse controller from HAM3 4 & 5 in the attached.  The HAM3 controller is the top graph, appears to be done by hand and at a UGF of 2hz.  The middle graph is HAM4 and are the HAM HEPI Generic Loops developed by Hugo w/a ugf of 5hz and implemented by Hugh.  The bottom graph is HAM5 and again like HAM4, are generic and installed by me.  It is surprising that the HAM4 looks more of an issue than the very sharped peaked HAM5; but, the shoulders of the peak are higher at the ISI zero for HAM4 and the zero at HAM5 is below 6hz rather than above.  That said, the HAM5 HEPI controller is obviously equally problematic given this gain peaking.

Bottom lines--Generic loops while easy to install, should be carefully checked

Is a 5 hz loop best, warrented, needed?

Post HEPI turn-on ISI TFs should be collected and thoroughly checked.

Apologies to my above co authors--they have not been consulted for this entry.

Images attached to this report
H1 SEI (AOS)
jeffrey.kissel@LIGO.ORG - posted 15:01, Tuesday 09 September 2014 (13838)
HAM4 & HAM5 Table Optical Levers added to ISI Front-End Models and sitemap
J. Kissel, D. Barker

Completing the work I'd started with the HAM4 & 5 table optical levers (see LHO aLOG 13785), I recompiled, reinstalled, restarted and restored (4R'd) the HAM4 and 5 user models (h1isiham4, h1isiham5) to install the table oplev infrastructure. 

Note to the seismic team: we should modify the generic HAM-ISI overview screen to include a link to their respective oplev screen, instead of having these be separate line items in the sitemap pull down menu. Even better -- if anyone ever intends to *use* these levers -- we should make the infrastructure like the rest of the QPD / Optical lever world, and use the QPD Simulink library part, as well as the same screen. 

*ahem*...

Detailed list of activities
- Ramping down each ISI to the "READY" state, turning off the master switch
- Capturing  a new safe.snap for each (and committing the result to the userapps svn repo)
- Recompiling, reinstalling, restarting, and restoring the HAM4 and HAM5 models
- Restarting the DAQ / frame builder / data concentrator -- this failed, because of a duplicate channel naming bug in the HAM4 model 
- Fixing the bug in the HAM4 model
- Recompiling, reinstalling, restarting, and restoring the HAM4 model
- Restarting the DAQ / frame builder / data concentrator
- Turning on the HAM4 & HAM5 master switch, and returning HAM4 to "HIGH ISOLATED" and HAM5 to "ROBUST ISOLATED" via guardian.
- Committing the updated models to the userapps svn repo
- Adding the HAM4 and HAM% optical lever screens to the corner station ISI pulldown menu on the sitemap
- Committing the new sitemap to the userapps svn repo.
H1 ISC
keita.kawabe@LIGO.ORG - posted 14:49, Tuesday 09 September 2014 - last comment - 20:53, Tuesday 09 September 2014(13837)
PR3 and BS drift during carrier lock

Yesterday people found that PR3 and BS seemed to move when PRC is carrier locked.

For PR3, there's no feedback and we see a clear correlation between the carrier power (sorry the first plot doesn't have the carrier power, only the AS power) and both OL and witness OSEMs. All in all PR3 oplev seems to slowly go negative in PIT after the carrier lock and goes back positive after lock loss, though this doesn't completely describe the behavior shown on the first plot.  PR3 DC OPLEV servo should be able to counter this if needed.

For BS it's somewhat more difficult to see partly because of the length feedback, but there's definitely a correlation between the carrier buildup and the BS oplev.  Unlike PR3, every time there's a carrier lock OPLEV  PIT goes positive and slowly comes back. BS oplev doesn't seem to be well correlated to the mean length feedback, so this is not the effect of the DC length push tilting the BS.

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 15:45, Tuesday 09 September 2014 (13840)

Note that the plots posted above show that BS and PR3 moved about 1 to 1.5urad over 10 minutes.

Our PSL  power is 10W, recycling gain at the moment is about 10.

These numbers sound as if this is a factor of 10-ish smaller than what the LLO people observed, but I'd appreciate any input.

lisa.barsotti@LIGO.ORG - 20:53, Tuesday 09 September 2014 (13847)ISC
These are the LLO numbers we were using for comparison:

BS drift (without BS baffle): 5 urad @ 60 W on BS (LLO entry 9920);
PR3 drift (without PR3 baffle): 12 urad / min (most likely still with 60 W on BS, entry 8960).
H1 ISC (CDS)
nicolas.smith@LIGO.ORG - posted 14:27, Tuesday 09 September 2014 (13836)
OMC model rebuilt and restarted

There had been a conflict between the svn server version of the omc/common model and what we were running. The only difference was the addition of the channel H1:OMC-ASC_DITHER_MASTER which is just a switch for enabling/disabling the alignment dither drives.

I merged the models and committed to the svn. Then I rebuilt, installed, and restarted the OMC model.

The .ini file was not modified (md5sum unchanged), but the DAQ status is showing 0x2000, so it's not clear yet it we need to restart the DAQ. Dave is investigating.

H1 CDS
david.barker@LIGO.ORG - posted 10:42, Tuesday 09 September 2014 - last comment - 20:16, Tuesday 09 September 2014(13830)
h1oaf0, 16bit DAC adapter card replaced with PCIe card

WP4834 Jim and Dave

We replaced the 16bit DAC card in h1oaf0 (PCIX card on PCIe adapter) with a PCIe DAC card. This is the second DAC card in h1oaf0, the first is an 18bit DAC. Procedure was:

This does not close out the WP, we have SUS EY and SEI EX still to complete.

Comments related to this report
david.barker@LIGO.ORG - 20:16, Tuesday 09 September 2014 (13845)

Alastair, Jim, Aaron, Filiburto, Dave

Alastair later found that the new DAC card was not functioning correctly. We found that channel 12 was outputting 24V instead of 8.4V. We tried swapping out ribbon cable and interface cards, but eventually put the original DAC-on-carrier-card back in to get TCS back on track for this evening. We will investigate further later in the week.

H1 SEI
jim.warner@LIGO.ORG - posted 10:00, Tuesday 09 September 2014 - last comment - 17:04, Tuesday 09 September 2014(13828)
Open loop measurements of ITMX ISI controls
Trying to get this in before the SEI T&C call. Pictures are from open loop measurements of ITMX. Foton pics are comparing T240 blends and X loops from ITMY and ITMY.
Images attached to this report
Comments related to this report
jim.warner@LIGO.ORG - 17:04, Tuesday 09 September 2014 (13843)
It looks like the blend filters installed at ITMX may be different. Using the plot_current_blends script, I looked at ITMY and ITMX. I need some help interpreting, but the complementarity plots don't all look the same.
Non-image files attached to this comment
H1 ISC
kiwamu.izumi@LIGO.ORG - posted 02:32, Tuesday 09 September 2014 - last comment - 13:41, Tuesday 09 September 2014(13822)
PRMI locked on sidebands

Lisa, Sheila, Alexa, Nic, Jamie, Kiwamu

We managed to lock the PRMI on the sidebands tonight. We estimated the servo gain settings from the gains in the carrier-locked condition. The lock was stable and lasted for more than 40 min.

Also, we saw an angular drift in pitch of PR3 when the carrier was locked. This behavior was consistently observed.

 

(Carrier lock)

We intensively worked on the carrier-locked PRMI in the daytime and we could repeatedly lock the PRMI on the carrier. The script which Alexa wrote is now interpreted in a guardian code by Sheila. It uses the variable finesse technique. The code is available but it is still a working progress. 

At about 3 pm local, we noticed that the motion in the Michelson was too large for us to keep locking the PRMI. At that time, Fil and Aaron were working around the beer garden, but this may not be a direct cause of the Michelson fluctuation because we did not see a significant improvement after they left. At this particular point, we could not keep closing the Michelson locking loop because of too large angular motion in the Michelson. This large motion gradually disappeared some time later and we could get back to the locking activity in the evening.

(PR3 tends to drfit in pitch)

When we locked the carrier-PRMI, we noticed that the power build-up degraded on a time scale of approximately 10 minutes or so. After some investigation, we identified it to be PR3 which drifted only in pitch by about 0.5 urad. We repeated the same observation a couple of times. PR3 always tends to drift to the negative side in the oplev counts. After a unlock event, it tends to go back to the original angle on a similar time scale. This indicates some kind of thermal issue. In fact, I did not observe a similar effect when the PRMI was locked on the sidebands. Sheila implemented an oplev servo on PR3 to mitigate the issue. In parallel, we should start working on some ASC loops.

Also, the BS oplev showed an approximately 0.5 urad drift once, but this did not seem to correlate with the power degradation. Perhaps this was simply some readout noise or something.

(Carrier lock without the variable finesse technique is difficult)

I still don't understand why this is so difficult, but locking the carrier-PRMI without the variable finesse turned out to be difficult. Since we already knew the right gain settings based on the variable finesse condition, we tried locking the PRMI directly. However, I succeeded in locking it only once. Plus, the lock did not last more than 20 seconds or so. Probably this was because I did not have the power normalizations which make the servo loops less sensitive to the angular fluctuation in the PRMI. This needs further investigations.

According to the variable finesse technique, we estimated the right MICH gain with ASAIR_RF45_Q to be -7, and the PRCL gain to be -0.2 with REFL_A_RF45_I. When I obtained the short lock, the gain settings were -9 and -1 for MICH and PRCL respectively. I used a trigger and triggered filters for both loops. It was around 4:23:56 in UTC.

(Sideband lock)

We then moved onto locking of the sideband-resonant PRMI. I simply flipped the sign of the PRCL loop to do this. But, this did not work -- I did not get a short lock. So I suspected some kind of cross-coupling in the sensing matrix and started trying to the other REFL sensor, REFL_A_RF9, which should be less sensitive to the Michelson motion. I measured the difference in the readout gain of the RF9_I and RF45_I by locking the carrier. The RF9 was smaller by 13 dB than the RF45. Taking this into account I tried some gain settings in MICH and PRCL while keep using ASAIR_A_RF45_Q for the MICH control. I attach a trend of some signals below to show the PRMI had been locked for a while, more than 40 min. Note that I did not have to re-align an optic to maintain the lock. I did not see drift in PR3 in this configuration.

The first acquisition was made with a MICH gain of -10 and PRCL gain of 0.7. These numbers are not far from the expected. Once it started locking, I tuned up the alignment, demodulation phases, UGFs and locking thresholds. I attach a screenshot of the whole settings, MICH  and PRCL open loop transfer functions.

It seems that lock acquisition is smoother with a slightly lower gain in MICH. For example, I kept using a MICH gain of about -7 for locking and increased it to the nominal gain of -17 once it was locked.

Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 02:36, Tuesday 09 September 2014 (13823)

P.S.

I was asked by Keita to take some video of the PR2 and PR3 baffle cameras when the carrier-PRMI is locked.

Here are the recorded videos from tonight. It looks like the frame rate was screwed up for some reason -- it looks as if they are fast forwarded ... both vidoes were originally taken for roughtly 10 seconds.

Non-image files attached to this comment
kiwamu.izumi@LIGO.ORG - 02:56, Tuesday 09 September 2014 (13825)

I am leaving the sideband-resonant PRMI locked.

kiwamu.izumi@LIGO.ORG - 13:41, Tuesday 09 September 2014 (13834)

(Some lock stretches were observed)

There are three major lock stretches last night. They lasted 2 hours, 3 hours and 1.5 hours in chronological order. The attached below is trend of the intracavity sideband power.

 

(A lock loss analysis)

I looked at two lock loss events from the last night at around 10:33:46 and 13:59:00 in UTC to see if there is a clue to improve the stability of the PRMI.

Both lock losses seemed have been triggered by some misalignment. The attached below is a number of time series for the first event:

Note that the second event looked similar to the first one. Here are my observatoinal notes:

  • It seems that the PRCL loop turned in unstable presumably because of the bad alignment. An oscillation is visible in the PRCL error signal a few second before the lock broke.
  • Also, the ITMX oplev yaw resembles the intra cavity power curves -- indicating that ITMX may have been leading the power fluctuation through its misalignment at that time.  Also it resembles the MICH feedback signal. Probably ITMX was lound at this point for some reason.
  • In parallel to the ITMX yaw motion, the BS pitch oplev showed some fluctuation before the lock loss. I guess this is because of the large longitudinal feedback on BS which tried to keep up with a large motion of ITMX, resulted in a large L2P coupling in BS.
  • Note that I did not install a power normalization for the length signals last night.
Images attached to this comment
Displaying reports 71081-71100 of 84550.Go to page Start 3551 3552 3553 3554 3555 3556 3557 3558 3559 End