Displaying reports 48281-48300 of 86133.Go to page Start 2411 2412 2413 2414 2415 2416 2417 2418 2419 End
Reports until 16:45, Monday 09 October 2017
H1 General
thomas.shaffer@LIGO.ORG - posted 16:45, Monday 09 October 2017 (38954)
Attached HAM Install Arm on HAM5

This morning Mark, Tyler, Bubba, and I attached the install arm on to the West side of the North door on HAM5. We couldn't find the tub of bolts dedicated to this assembly, but found some others nearby (which included some of the door bolts, that we will need to remember to put back when we are finished). The arm is currently only held on with 3 of the 4 bolts that were previously used with this arm. HEPI blocked access from the front to the lower right thru hole, and there was not enough clearance in the back. Perhaps this arm hasn't been used wiht the new style HEPI's yet? Bubba doesn't think the missing bolt will cause any problems and a possible fix with a shorter piece of all-thread is in the works.

Picture attached of the arm installed but all covered up. (Forgot to take pictures until we were walking away.)

Images attached to this report
H1 IOO
edmond.merilh@LIGO.ORG - posted 16:11, Monday 09 October 2017 (38953)
I/O work in HAM2

Cheryl V., Ed M.

This afternoon we installed an access platform into HAM2 on the SW corner of the ISI table for accessing IM3.

Images attached to this report
H1 General
corey.gray@LIGO.ORG - posted 16:00, Monday 09 October 2017 (38930)
Operator DAY Shift Summary

Day's Log Of Activities

H1 CDS
david.barker@LIGO.ORG - posted 15:30, Monday 09 October 2017 - last comment - 15:31, Monday 09 October 2017(38950)
SITEMAP changes

Jeff, Sheila, Dave:

to show off my recently acquired skills in drawing ellipses using gimp, the attached plot shows the three main changes made to the LHO SITEMAP as part of SQZ install.

1. PEM has been reduced from two to one button. To permit this, I have replaced the links to building detail screens with a launcher screen.

2. OPS and O1 (sic) screens have been merged to the OPS button

3. new SQZ button added.

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 15:31, Monday 09 October 2017 (38951)

here is a wiki page to show how ellipses and circles can be drawn:

https://cdswiki.ligo-wa.caltech.edu/wiki/GIMPDrawOvalsAndCircles

H1 PEM
jeffrey.bartlett@LIGO.ORG - posted 15:28, Monday 09 October 2017 (38949)
Dust Monitor Quarterly Testing (FAMIS #7316)
  Checked all monitors except PSL (will do on Wed when in for other work), and #2 and #10 in the LVEA. These are in running cleanrooms with vent work underway. Will check these early in the morning before the work day starts. 

   The rest of the monitors are working within specifications.   
H1 PSL
corey.gray@LIGO.ORG - posted 14:52, Monday 09 October 2017 (38947)
PSL Weekly Report (FAMIS #7459)

Summary:  Looks like some alignment touch up might be needed due to high PMC Refl & a low ISS diffracted power.

Laser Status:
SysStat is good
Front End Power is 35.87W (should be around 30 W)
HPO Output Power is 153.9W
Front End Watch is GREEN
HPO Watch is GREEN

PMC:
It has been locked 1 days, 20 hr 22 minutes (should be days/weeks)
Reflected power = 24.41Watts
Transmitted power = 49.64Watts
PowerSum = 74.05Watts.

FSS:
It has been locked for 0 days 1 hr and 46 min (should be days/weeks)
TPD[V] = 2.007V (min 0.9V)

ISS:
The diffracted power is around 1.8% (should be 3-5%)
Last saturation event was 0 days 1 hours and 54 minutes ago (should be days/weeks)

Possible Issues:
PMC reflected power is high
ISS diffracted power is Low

 

LHO FMCS
bubba.gateley@LIGO.ORG - posted 13:50, Monday 09 October 2017 (38945)
HVAC Controls Upgrade
Apollo is back on site to resume HVAC Control work. This morning shortly before lunch, we took down both of the LVEA air handlers for about 45 minutes. We then restarted AHU-1 only and continue to run on that AHU only. I increased the air flows on both fans and opened the face/by-pass damper slightly. Temperatures in the LVEA are stable and I will continue to monitor. 
H1 SEI (DetChar, ISC, SQZ, SUS)
jeffrey.kissel@LIGO.ORG - posted 13:11, Monday 09 October 2017 (38943)
New ISI CART2EUL Projection Matrices for SQZ SUS, Connected New and Pre-Existing L Outputs to OAF for Cavity Basis Projection
J. Kissel, D. Barker

Now that we've moved the suspension point projections into the ISIs (e.g. LHO aLOG 26363), it's much easier to add new interesting suspension point projections to each platform. I've added new projection infrastructure to ISI HAM2, ISI HAM5, and ISI HAM6 to include
- ISI HAM2: Connecting the pre-existing IM1, IM2, IM3, and IM4 projections' longitudinal output via dolphin IPC destined to be picked up by h1oaf.mdl. 
- ISI HAM5: Creating new SUSPOINT projections for the OFI and ZM2 with associated new senders via dolphin IPC to the h1oaf.mdl. The new projections are stored in the frames at 4096 Hz.
- ISI HAM6: Creating new SUSPOINT projections for VOPO and ZM1 with associated new dolphin IPC senders to the h1oaf. The new projections are stored in the frames at 4096 Hz. Also, creating new dolphin IPC sensors for the pre-existing longitudinal output for the OMC, and OM1, OM2, and OM3.
- OAF: In OAF, all corresponding new and newly added longitudinal suspension point projections were added as inputs to the giant cavity basis matrix, with new output elements,
    - "IOL" for "Input Optics Length," imagined* to be the coherent sum of IMs L, to recreate path length displacement between the IMC output and PRM IFO input
    - "ASL" for "Anti-Symmetric Length," imagined* to be the coherent sum of the OFI, the OMs, and the OMC, to re-create path-length displacement between the SRM IFO output and the OMC
    - "SQZL" for "SQueeZe Length," imagined* to be the coherent sum of the VOPO and the ZMs to recreate the squeezer path length displacement between the VOPO and the OFI
*I say "imagined to be" because that's what I naively think should go into the coherent sum to recreate the path length, but the matrix has been setup that it can be the coherent sum of any optic, if we so chose later.

Attached are screenshots of the relevant parts in each model that were affected by this change. 

We'll make the modifications to each HAM ISI's custom SUSPOINT screen in due time. We don't yet have projections for any of these new suspensions (or from the OMs), but I'll eventually work with the systems group to get something good enough.

Finally, of note, I've *removed* the last of the suspension point projection displays from the OM ALL and RM ALL MEDM screens, as has been done some moons ago for all other SUSs.
Images attached to this report
H1 SEI (SUS)
sam.cooper@LIGO.ORG - posted 12:46, Monday 09 October 2017 - last comment - 15:55, Wednesday 11 October 2017(38919)
What should we do during large earthquakes?

J Warner, S Dwyer, S Cooper

We've been looking at what we should do during large earthquakes. The attached plots show the state of both the SEI Guardian (State N), and the L2 watchdog (L2 WDMON) channel, the L3 Oplev and the HEPI L4C's (as the ground STS's saturated) for the 8.1 magnitude Mexico earthquake (GPS: 1188881718), alog 38570, for the chambers ITMX,ITMY,ETMX,ETMY. During the earthquake, all the ISI's tripped as well as the ITMX suspension watchdog. From these plots we think that the decrease in amplitude of the Oplev signal is due to the reduction in ground motion around this time, rather than damping of the ISI, as both the damping and the reduction in ground motion occurred at similar times.

Images attached to this report
Comments related to this report
jim.warner@LIGO.ORG - 14:42, Monday 09 October 2017 (38946)

We've also talked about seismic watchdogs a bit and why the ISIs trip after the isolation loops are shut off by the guardian. Both ETMs are in damped right now so we set the T240 threshold to 100 counts, and sure enough, the T240s started counting saturations, but did not trip the watchdog. Attached plot shows the T240 saturation counts, threshold and ST1 WD mon state. The dip on the top left plot is where we reduced the threshold, the spike on the bottom left is where the model started counting T240 saturations, and the flat line bottom right shows the watchdog didn't trip. This is as it should be.

However, what I think I've seen during ISI trips before, is the ST1 T240s saturate, ST1 trips and ST2 runs for a little bit then trips. This results in ST1 getting whacked pretty hard. I'll try to see if that's what happened with this earthquake.

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 15:23, Monday 09 October 2017 (38948)SEI
J. Kissel, inspired by conversation from S. Cooper, S. Dwyer, J. Warner

I'll remind folks that this collective SEI/ SUS watchdog system has been built up sporadically over ~10 years in fits and spurts as reactionary and quick solutions to various problems by several generations of engineers and scientists. Also, the watchdog system is almost entirely designed only to protect the hardware from a software failure, and never designed to combat this latest suggestion -- protecting the hardware from the earth. So I apologize on behalf of that history at how clunking and confusing things are when discussing what to do in that situation. 

Also, I'll remind people that there are three "areas" of watchdogs: 
    (1) in software, inside the user model -- typically defined by the subsystem experts
    (2) in software, inside the upper level iop model -- typically defined by CDS software group, with input from subsystem experts
    (3) in hardware, either in the AA/AI chassis, or built into the analog coil drivers -- typically defined during initial aLIGO design phase

In my reply here, I'll only be referring to (1) & (2), though I still have an ECR pending approval regarding (3) -- see E1600270 and/or FRS Ticket 6100.

With all that primer done, here's what we should do with the suspension user watchdogs (1), and not necessarily just for earthquakes:
    (a) Remove all connection between SUS and the ISIs user watchdogs. The independent software watchdogs (2) should cover us in any bad scenarios that that connection was designed to protect against.
    (b) Update the RMS system to be *actually* an RMS, and especially, one that we can define a time-constant. The RMS system that is currently installed is some frankenstein brought alive before bugs in the RCG were appreciated (namely LHO aLOG 19658), and before I understood how to use the RCG's RMS function in general. The independent software's watchdog (2) is a good role model for this
    (c) We should rip out all USER MODEL usage of the DACKILL part. The way the DACKILL used across suspension types and platforms with many payloads is confusing and inconsistent. Any originally designed intent of this part is now covered by the independent software watchdog.
    (d) Once (b) is complete, we should tailor the lower the time-constants and the band-passing to better match the digital usage of the stage. For example, the worst that can happen to a PUM stage is getting sent junk ASC and Violin Mode Damping control feedback signals when the IFO has lost lock, but the guardian has not figured it out and switched off control.
    (e part 1) Upon watchdog trip, we should consider leaving the alignment offsets alone. Suddenly turning off alignment offsets often causes just as much of a kick to the system as what had originally set off the watchdog. HEPI has successfully implemented such a system.
    (e part 2) We should re-think the interaction between the remaining USER watchdog system and the Guardian. Currently, after a watchdog trip the guardian state immediately jumps to "TRIPPED" and begins to shut off all outputs and bringing the digital control system to "SAFE." 
    (f) Add a "bypass" feature to the watchdog such that a user can request the "at all costs, continue to try damping to top mass" in the case of earthquakes.
jim.warner@LIGO.ORG - 15:55, Wednesday 11 October 2017 (38985)

I'm attaching some more plots of what happened to the ISIs during this earthquake. The first plot is the saturation count time series for all seismometers and actuators for the test mass ISIs. All of the chambers saturated on the Stage 2 actuators first, this is the first green spike. This tripped the high gain DC-coupled isolation loops, and probably cause Stage 2 to hit it's lockers. The watchdog stopped counting all saturations for 3 seconds (by design), then immediately tripped damping loops on the saturated L4Cs or T240s. I'm not sure why the GS13s don't show up here.

The second plot I attach shows how long the ETMX was saturating different sensors. The L4Cs were saturated for about 45 seconds, the T240s and GS13s were saturated for minutes. The L4Cs never had their analog gains switched, but the chamber guardian should have switched the GS13s automatically. For this reason, if we increase the pause time in the watchdog (between shutting off the isolation loops and full shutdown), I think this shows that for this earthquake the ride-thru time needs to be more than 45 seconds.

 

Images attached to this comment
H1 CDS
david.barker@LIGO.ORG - posted 12:32, Monday 09 October 2017 (38942)
CDS POST-O2 overview MEDM updated to show new h1susopo model
Images attached to this report
H1 SQZ (CDS, DAQ)
david.barker@LIGO.ORG - posted 12:22, Monday 09 October 2017 - last comment - 13:12, Monday 09 October 2017(38941)
SQZ model changes and DAQ restart

WP7162 Sheila, Patrick, Jeff, Dave:

h1susauxh56: latest version of this code was installed.

h1susopo: DACKILL part in OFI was removed.

h1isiham2: new IPC sender channels (qty 4) added.

h1isiham5: new IPC channels (qty 2), DAQ changes, 12 fast channels added to frame.

h1isiham6: new IPC channels (qty 5), DAQ changes, 12 fast channels added to frame.

h1oaf: IPC receivers added.

Sheila and Patrick updated the SQZ beckhoff PLC DAQ ini file. I added it to the DAQ for the first time.

DAQ was restarted to resync with: h1susauxh56, h1susopo, h1isiham[5,6], h1oaf, H1EDCU_ECATC1PLC4

Restarts were unremarkable, partial second trend file was renamed as per normal procedure.

 

Comments related to this report
jeffrey.kissel@LIGO.ORG - 13:12, Monday 09 October 2017 (38944)DetChar, ISC, SQZ, SUS
J. Kissel, D. Barker

Description of changes to ISI and OAF top-level models can be found in LHO aLOG 38943.
H1 SUS (DetChar, SQZ)
jeffrey.kissel@LIGO.ORG - posted 11:54, Monday 09 October 2017 (38939)
H1 OMs 1-3 EPIC Infrastructure Resinstalled; Not Yet Tested Because In-Air Cabling Not Yet in Place
J. Kissel, D. Barker, R. McCarthy

As was done with RMs last week (see LHO aLOG 38883) I've re-populated the EPICs records and foton filters for H1 SUS OM1, OM2, and OM3 after having moved them over from the old h1sushtts.mdl front end model to the h1susomc model. 

Having reminded myself of all that was needed with the RMs (including DAMP and COILOUTF gains), I believe I've covered all bases. 

Several Things of Note:
- I've gone back to the RM_OVERVIEW and HSSS_OVERVIEW screens because the GDS_TP screen was incorrectly still pointing to the H1SUSHTTS GDS TP screen of the OMs. So, I created a new macro variable MASTERMODEL (and lowercase mastermodel) in all of the HSSS macro files (rmall, omall, imall, and each individual file).

- We also have compiled and installed the new h1susauxh56 to pick up all the new SUS' coil driver monitoring.

- I have NOT yet updated / created a new safe.snap for the h1susomc model that includes the OMs.

- I have not bothered to restore alignment offsets. 

In-air cabling and electronics (re)install for OMs is not yet complete -- in addition to the front-end / IO chassis ADC and DAC card shuffle, which is complete -- the OMs' feedthrough exit out of HAM6 are getting re-arranged to make room for all the new SQZ elements in HAM6 and the former in-air cabling is just ~10 ft. too short. As such, we won't get the chance to confirm /test that all the digital infrastructure has been restored properly until that stuff gets finished.
H1 SYS (ISC, VE)
hugh.radkins@LIGO.ORG - posted 11:21, Monday 09 October 2017 - last comment - 14:55, Tuesday 10 October 2017(38938)
WHAM6 -X Position Septum Window VP Installed

With GregG in chamber and JimW helping outside, the installation of the ViewPort onto the -X most Septum Window was pretty straight forward.  A new o-ring was used and the window/flange clocking mark was put at 9o'clock (-X) and was torqued in three steps to 16 ft-lbs.  Attached photo shows these men in action.

Images attached to this report
Comments related to this report
hugh.radkins@LIGO.ORG - 14:55, Tuesday 10 October 2017 (38971)

Numbers from packaging: D1101092 SN #3, O-Ring Parker #2-373 C100002

H1 PSL
jeffrey.bartlett@LIGO.ORG - posted 11:12, Monday 09 October 2017 (38937)
Add Water to PSL Crystal Chiller
   Added 250ml water to the PSL crystal chiller. Diode chiller water levers were OK. 
   Both filters look good as well. 
H1 SUS
travis.sadecki@LIGO.ORG - posted 17:42, Friday 06 October 2017 - last comment - 16:05, Monday 09 October 2017(38924)
ITMx fiber welding complete

A. Bell, J. Oberling, T. Sadecki

ITMx has been successfully hung as a newly welded monolithic.  I'll leave it to Jason to post the actual numbers, but the PUM to TM differential pitch better than the old version of ITMx.  Now to put it back together in chamber next week.

Comments related to this report
jason.oberling@LIGO.ORG - 16:05, Monday 09 October 2017 (38952)

Final alignment numbers for the new monolithic are below.  All measurements were done with the ITMx suspended, PUM and UIM locked.  All directions assume the reader is looking in the +X direction (i.e. at the ITMx AR surface); it should be noted for future reference (if comparing to the numbers in the alignment notebook) that this is opposite the convention used in the alignment notebook, which is set relative to the IAS equipment used in the alignment and looks in the -X direction (at the ITMx HR surface).

  • Roll
    • PUM: 0.15 mm CCW
    • ITMx: 0.20 mm CCW
  • Pitch
    • PUM: 1.51 mrad down
    • ITMx: 1.20 mrad down
    • Differential: 310 µrad up
  • Fiber Stretch
    • Left: 5.7 mm
    • Right: 5.8 mm
  • PUM/ITMx Center of Mass Separation
    • Left: 601.5 mm
    • Right: 601.4 mm

The serial numbers of the fibers used and their locations in the monolithic are as follows:

  • +X/+Y
    • SN S1400158
  • -X/+Y
    • SN S1400137
  • -X/-Y
    • SN S1400164
  • +X/-Y
    • SN S1400154
H1 IOO (ISC, SYS)
jim.warner@LIGO.ORG - posted 13:40, Friday 06 October 2017 - last comment - 11:52, Thursday 12 October 2017(38918)
Broken glass found in HAM6

On the 5th I opened the soft covers on HAM6 to lock the ISI and noticed that one of the black glass pieces was broken. I'm posting a couple of pictures here. Betsy, JeffK and others have looked to see if we noticed this during the last HAM6 vent, but none of the pictures in the alog show this glass in any detail. 

Images attached to this report
Comments related to this report
bubba.gateley@LIGO.ORG - 03:44, Sunday 08 October 2017 (38928)
Do you think you should write an incident report on this?
betsy.weaver@LIGO.ORG - 09:41, Monday 09 October 2017 (38933)

No, I don't think this warrants an incident report, since I believe this is a laser burn which broke the glass, not some other "accident".  It does warrant an FRS however, since we will likely need a better "fix" to this.  Further details:

 

On Friday, Keita and I inspected this broken beam dump on the North side of the HAM6 table in chamber.  I have more pictures attached below.  When I carefully pushed the 2 pieces of broken glass back together (like a puzzle) on the mount, I could see a hole of missing glass (PIC 1 and 2 below).  As well, there is a shard of black glass sitting on the table about 8 inches in front of the beam dump, maybe "launched" from the hole site of the glass piece (PIC 3, circled in BLUE).  As well, there are 2 other burn marks on this same piece of black glass off to the left visible in the first pics.

Sheila is going to help me with another round of inspections here and help determine beam propogation.  We will also look into timing with potential shutter/toaster fussiness, and HAM6 pressure changes to hone in on when this may have occured since April 2016 when it was deemed healthy.

Images attached to this comment
betsy.weaver@LIGO.ORG - 09:45, Monday 09 October 2017 (38936)

While inspecting HAM6 last week, I also looked a bit at the "toaster" fast shutter.  A quickish look it's wires did not reveal any burn spots.  Pictures attached.

As well, there is another black glass beam dump in the NW side of the table, close to the viewport which shows what appears to be some burn markings (last Picture).  Likely another FRS addition.

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 11:52, Thursday 12 October 2017 (39003)INS, ISC, Lockloss, SYS, VE
For further follow up on the broken beam dump -- identified as the OMC REFL Beam Diverter dump -- check out LHO aLOG 38998 and FRS Ticket 9196.

Regarding the dump which has a "glancing blow" burn mark, that's the dump catching the OM3 TRANS beam. Indeed, the burn mark appears on the *outside* of the functional part of the dump. So, I don't think there's a need for action there (and hence no need for an FRS ticket).
Displaying reports 48281-48300 of 86133.Go to page Start 2411 2412 2413 2414 2415 2416 2417 2418 2419 End