Displaying reports 66681-66700 of 77188.Go to page Start 3331 3332 3333 3334 3335 3336 3337 3338 3339 End
Reports until 13:13, Tuesday 18 March 2014
Logbook Admin General
jonathan.hanks@LIGO.ORG - posted 13:13, Tuesday 18 March 2014 (10830)
aLOG maintenance completed

The aLOG maintenance has been completed.

Changes:

LHO VE
kyle.ryan@LIGO.ORG - posted 11:57, Tuesday 18 March 2014 (10825)
Soft-cycled GV7 for crane activities


			
			
H1 CDS
cyrus.reed@LIGO.ORG - posted 10:46, Tuesday 18 March 2014 (10819)
h0dust Windows Updates

Took VM snapshot, then installed all current updates available in WU on h0dust.  Also installed the .NET 4.5.1 update and associated patches.  Patch process took about an hour, two rounds of updates.

H1 AOS
thomas.vo@LIGO.ORG - posted 09:30, Tuesday 18 March 2014 - last comment - 10:47, Tuesday 18 March 2014(10816)
Cyrus R and Patrick T updating software 9:29 AM PT
Work Permit 4509, update windows virtual machine for dust monitors
Comments related to this report
thomas.vo@LIGO.ORG - 10:47, Tuesday 18 March 2014 (10820)
Done at 10:47 AM
H1 AOS
thomas.vo@LIGO.ORG - posted 09:10, Tuesday 18 March 2014 (10815)
Jodi at MY @ 6:15 AM PT
Throughout the day as well
H1 AOS
thomas.vo@LIGO.ORG - posted 09:01, Tuesday 18 March 2014 (10814)
Apollo using the main crane at 9:00 AM PT


			
			
H1 AOS
thomas.vo@LIGO.ORG - posted 08:57, Tuesday 18 March 2014 (10813)
03/18/2014 PSL Check
LASER IS ON

 - Output Power = 28.3 W

 - Watchdog is active

 - System status is good

PMC

- Locked for 14 hours

- Refl Power = 1.2 W, Trans Power = 10.1 W

FSS

- Ref Cav locked for 14 hours

- Alignment looks slightly off but still resonant, PD threshold = .812 Volts

ISS

- 13.2% diffracted power

- Saturated 14 hours ago.
Logbook Admin General
jonathan.hanks@LIGO.ORG - posted 08:55, Tuesday 18 March 2014 - last comment - 13:07, Tuesday 18 March 2014(10812)
aLOG maintenance today, 12:15pm. Save all log entries prior to that time
As a reminder the aLOG is down for maintenance today starting at 12:15pm pacific.

Please save your log entries as drafts or post them to the log book prior to this time, or they will be lost.
Comments related to this report
jonathan.hanks@LIGO.ORG - 13:07, Tuesday 18 March 2014 (10829)
The maintenance is completed.
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 08:27, Tuesday 18 March 2014 (10811)
CDS model and DAQ restart report, Monday 17th March 2014

model restarts logged for Mon 17/Mar/2014
2014_03_17 23:20 h1fw1

unexpected restart of h1fw1, it has gone slightly unstable in the past week.

This is the only restart since last Thursday.

H1 ISC (ISC, PEM)
corey.gray@LIGO.ORG - posted 08:21, Tuesday 18 March 2014 - last comment - 11:36, Wednesday 19 March 2014(10810)
Monday Evening EY TMS Alignment Work & Dust Monitor Check

TMS Work (Corey, Jax, Keita, Margot)

Apollo roughly positioned the ISCT-EY Table (via floor markings).

Chamber Floor was first cleaned upon entry for work (did not do an exit floor wipe).  Margot then entered the chamber to remove First Contact from inside surface of pair of TMS Viewports (then went out and removed First Contact off outer surfaces).  She mentioned "finger prints" on the outside surface of one of the TMS viewports; Margot will document in the DCC.

By eye, we checked position of the table, we ended up pushing the table about 3" west.  We then attached ducting between the chamber and the table.  Then we went in to check our line of sight from the TMS Table to the Table Periscope.  This required us to move the GREEN periscope an inch east, and also the top periscope mirror down 4-6".  At this point the laser wasn't quite making it down the ductThis is about where we ended things last evening.

Dust Monitor Check Of Purge Air For BSC10 (Corey, John, Keita)

John whether there was dust coming from the purge air.  So I, with handheld Dust Monitor in hand, crawled under the ACB, and took a few measurements from the Dust Monitor (which was running continuously).  I took measurements at four spots above the input of the purge air.  At the highest point, I had readings which would hover between 1500-2500 counts of 0.5um particles.  At the lowest point (with sensor of Dust Monitor right at the input), the 0.5um counts could be kept at basically 0-counts (with flashes of a few hundred possibly.  So, it would seem the purge air is relatively clean.

Comments related to this report
betsy.weaver@LIGO.ORG - 09:42, Tuesday 18 March 2014 (10817)

These 2 statements seem contradictory:

"At the highest point, I had readings which would hover between 1500-2500 counts of 0.5um particles.  [At the lowest point ...]  So, it would seem the purge air is relatively clean."

Maybe can John elaborate at where he thinks the high counts are "coming from" if not the purge?  Is it just that the air is turbulent in chamber and stirring up the 1500-2500 counts already in the chamber?

john.worden@LIGO.ORG - 10:41, Tuesday 18 March 2014 (10818)

Corey saw high background levels in the beam manifold but was able to drive the particle counts to zero by moving the detector close to the purge port at the floor of the beam manifold. I walked around the VEA sampling and found low levels throughout. Counts inside cleanrooms were close to or equal to zero except at the open BSC door. There was activity here as well as equipment staged. Corey was inside and Keita was outside at the BSC entrance. The overhead work platform reduces the effectiveness of the clean room in this location.  Inside, the arm cavity baffle obstructs access to the beam manifold so any work in the beam manifold requires a person to laydown and slide under the baffle. This may very well abrade clothing. I recommend we establish a horzontal clean flow as we have while working in HAM chambers.

A reminder that the purge air can only provide 25--50 cfm of air flow into the chamber. In a 6 foot diameter tube (beam manifold) this translates to air velocities of only 0.6 to 1.2 feet per MINUTE. Think how far you walk in a minute.

My impression is we have a reservoir of particulate in the vacuum chamber from the series of operations which have taken place - for example there have been two cartridge installs and one removal. Also this cartridge is an early assembly - probably assembled prior to some of the "in process" cleaning steps we have adopted.

corey.gray@LIGO.ORG - 11:35, Tuesday 18 March 2014 (10822)

Yes, I should elaborate a little (was quickly entering alog during Morning Meeting).  So we did measure counts while I was in BSC10.  And seemed like we had steading counts in the several thousands [for 0.5um counts with continuous sampling].  When I took measurements along the Purge Air plume, I would get up to 2500 at the most at the top of the plume (6' high).  As I went closer and closer down to the Purge air inlet, the counts started to drop.  And it was zero right at the inlet.

So the picture looked as though we have a baseline of particles floating in the chamber.  And in the turbulent air above the Purge Air inlet the counts waiver a bit, but counts decrease the closer you are to the inlet.  So above the purge we have particles moving around more (vs further away from purge these particles are more "statically" floating...perhaps they are more on the floor when someone like me isn't shuffling them into the air).

Basically we have particles all over the surfaces in the chamber/tube.  They may be gently floating around or resting on the floor.   They get rustled around when we work in-chamber & also get blown around and away from the Purge Air inlet.  We need to remove these particles...which I know is obvious and daunting. 

We're going to coninue wiping these particles on the floor toward door, but not sure what that does.  Hopefully, particles get attached to our wet wipes, but I wonder if particles just get pushed to the edge of the floor and then fall over the edge of the temporary floor and then rain down to the bottom of the chamber.  Sad sad.

patrick.thomas@LIGO.ORG - 11:36, Wednesday 19 March 2014 (10863)
Are these raw or normalized counts?
H1 SEI (SYS)
jeffrey.kissel@LIGO.ORG - posted 20:06, Monday 17 March 2014 (10809)
H1 HAM2 ISI Does Not Isolate with Guardian
J. Kissel, A. Staley

The H1 HAM2 ISI consistently trips using the guardian on the GS13s, right as the X, Y, Z, RZ isolation filters begin to turn on, just after the RX and RY alignment biases are slewed. I had thought it might have been because I found the GS13s in high gain mode (why? because of a restart of the guardian process maybe?), but I switched them back to low gain mode (with dewhitening ON) and things still trip because we're trying to engage horizontal GS13s that that just been yanked around in tilt. I confess, we *didn't* reset the CPS offsets and store them in the target before getting started and I don't know the difference between the equilibrium state and the current target, nor do I know the last time they were reset and stored, so it might be fine if I just do that.

I'm surprised to see the RX and RY alignment biases being ramped in between turning on each of the isolation filters already. We have certainly discussed doing this, but I would have expected more testing to iron out these bugs. Jamie's update aLOG doesn't mention anything about it, other than nodes have been restarted with some minor bug fixes.

For the evening, I left the requested state in damping, and brought up the isolation loops using the commands script. That works because it doesn't play with the biases until the isolation filters are completely engaged. Also note, that if you manual put the ISI into the HIGH ISOLATED state, and then switch the request to such, it turns the isolation loops off and starts from scratch. Not desirable, but may be tough to code up / or insure that you're actually in high-isolated.

I post to examples of the GS13 trip, but it's clear what's happening, as I describe above.
Images attached to this report
H1 ISC
alexan.staley@LIGO.ORG - posted 19:46, Monday 17 March 2014 (10808)
PZT EY

(Alexa, Jax)

The PZTs on ISCTEY are now working. We had found that the AA chassis hooked up to the DAC channels was turned off. The PZTs move as expected. When we run the servo we might want to be aware of the sign convention (it seems to obey positive counts in pitch moves the beam down).

 

NOTE: Anti-Aliasing chassis in slot 9 of rack ISC-C1 has no power cable. Filiberto help!

H1 PSL (PSL)
patrick.thomas@LIGO.ORG - posted 18:03, Monday 17 March 2014 (10805)
H1 PSL check
Output power is 28.4 W (should be ~30 W)
Watchdog is active
Only warning in SYSSTAT.adl is 'VB program online'.

PMC is NOT locked
FSS is NOT locked
ISS is NOT locked
H1 SEI (ISC, SUS, SYS)
jeffrey.kissel@LIGO.ORG - posted 14:28, Monday 17 March 2014 - last comment - 19:33, Monday 17 March 2014(10795)
March at LHO: In like a Lion, out like a Lion, and a Lion in the Middle
J. Kissel

We're really getting pummelled by ground motion, especially the past few days. I attach plots of the band-limited RMS in the Z direction of PEM ground inertial sensors in the corner station and the X end station over the past 48 hours. We've been hit by earthquakes (in the 30-100 [mHz] band), high-micro seism from windstorms and spring ocean activity (in the 100-300 [mHz] band), and gusts of wind and anthropogenic noise (in the 1-3 and 3-10 [Hz] bands). I think this is an excellent representation of why we've had so much trouble trying to find a configuration of the isolation systems that "just works" -- the characteristics of the input motion radically change constantly on a ~3-hour timescale. Not to mention there are times (like in the middle of the plot, 2014-03-16 21:50 UTC) where the earth is just down right angry with all three bad things at the same time.

I apologize for the ambiguity in calibration, I have an email out to Robert asking the proper calibration into physical units. The FOMs with these channels on the wall suggest that the channels are calibrated into "[decaum/s]" in the frames (which I think is 10 * 1e-6 [m/s]) but with no calibrations in the DMT template (and none on the data viewer trace, obviously), I get different numerical values. pem.ligo.org suggests that both the corner-station and endx should be 0.0076e-6 [m/s]. I think whatever units they are, they're at least self-consistent. I'll take spectra at choice times to gather the diversity; stay tuned.
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 16:57, Monday 17 March 2014 (10801)
Here're the promised, associated spectra. I attach an annotated version of the BLRMS too, with vertical lines demarcating the UTC time in the same colors as the traces on the spectra.

As indicated by the legend, I chose representative times that reflected the variety of ground motion:
2014-03-16 15:45 UTC - High micro-seism
2014-03-16 18:05 UTC - High micro-seism + Gusty Wind
2014-03-16 21:45 UTC - High micro-seism + Large Earthquake, in Chile + Gusty Wind
2014-03-17 05:50 UTC - Medium micro-seism + Cluster of Small Earthquakes (Chile, Again in Chile, Philippines, Puerto Rico, and Mexico, at magnitudes 6.2, 5.0, 5.1, 3.0, and 2.8 respectively).
2014-03-17 18:45 UTC - Low micro-seism + Gusty Wind

Notes:
- While we don't necessarily expect to be able to stay up during large earthquakes, it's good to see a sort of upper bound, and the contrasting color of the ground motion as it fills in the 30 to 100 [mHz] band. 
- It's interesting to see that during periods of high microseism, the peak at 55 [mHz] seems to be present regardless of whether the winds are gusting or not (comparing BLUE and RED) .
- Further, there exists times (i.e. MAGENTA) where there is lots of gusting winds, but the microseism is relatively low.
- Most importantly we see that ground is sort of oscillating between requiring more isolation in the 30 to 100 [mHz] band and in the 1 to 10 [Hz] band.
- The variations in the 30 to 100 [mHz] band can be as much as a factor of 100 during earthquakes, but not too much change between windy and not windy, maybe at most a factor 5 in a small range between 40 and 80 [mHz].
- There's very little to no change in the region of the lowest SUS resonances between 0.2 and 0.6 [Hz] between all of these seismic bad times
- Naturally, gusty wind times are the worst at high frequency, but again the variation is only a factor of 3 to 4. We should be able to ride this out.

Let's see what the HEPI L4Cs say, maybe the gusts have an interesting affect playing with the pier flag poles.
Non-image files attached to this comment
jeffrey.kissel@LIGO.ORG - 19:16, Monday 17 March 2014 (10806)ISC, SUS, SYS
J. Kissel

Here're the HEPI L4Cs for each of the times described above. While they show the same sort of variety at the microseism and below (where they can sense the ground motion above their self-noise), the most interesting is how much more varied the tilt spectra are (in this case RY) in the 0.3 to 1 [Hz] band -- exactly where the translation degrees of freedom claim there's very little difference. And naturally the ITM reacts differently than the ETM, just to make things difficult.

For ITMX, both high microseism conditions and gusty wind show elevated tilt in the 0.3-1 [Hz] band, by about a factor of 10. Only the during the medium microseism + small earthquakes did the L4C hit it's (tilt) noise floor.

For ETMX, there's quite a variety, with gusty winds alone being the worst-case scenario.

But the moral of the story is that, where translation degrees of freedom get tossed around by an order of magnitude between 0.03-0.3 [Hz] and 1-10 [Hz] during these excurisions, the tilt fills in the 0.3-1 [Hz] gap with its own order of magnitude variation, and as we know *both* tilt and translation of the table affects the optics just about equally. 

So -- if we want to operate the isolation systems during these 90th percentile times, we're gunna have a lot of automation and blend tailoring to do, but just increasing the blend frequency won't necessarily win. Further, when we *do* #movetheblendup, the green still can't handle the loss in performance.
Non-image files attached to this comment
jeffrey.kissel@LIGO.ORG - 19:33, Monday 17 March 2014 (10807)ISC, SUS, SYS
The data for the above measurements can be found in the following templates:
/ligo/svncommon/SeiSVN/seismic/BSC-ISI/H1/Common/Data/
2014-03-16to17_GroundMotion_ASDs.xml
2014-03-16to17_HEPIPierMotion_ASDs.xml

There's way to many curves for me to export, but all curves shown are stored as references so you can export them at your leisure and use them in any models.
                          Ground Motion           Pier Motion
2014-03-16 15:45 UTC       Ref.   0-11            Ref.  0-23
2014-03-16 18:05 UTC       Ref.  12-23            Ref. 24-47
2014-03-16 21:45 UTC       Ref.  24-35            Ref. 48-71
2014-03-17 05:50 UTC       Ref.  36-47            Ref. 72-95
2014-03-17 18:45 UTC       Ref.  48-59            Ref. 96-119

All plots and templates are committed to the repository as of this entry.
Displaying reports 66681-66700 of 77188.Go to page Start 3331 3332 3333 3334 3335 3336 3337 3338 3339 End