Displaying reports 49801-49820 of 88172.Go to page Start 2487 2488 2489 2490 2491 2492 2493 2494 2495 End
Reports until 11:15, Monday 20 November 2017
H1 PSL
peter.king@LIGO.ORG - posted 11:15, Monday 20 November 2017 (39486)
PSL table temperature sensor signals
I switched the cables for the PSL table temperature signals, H1:PSL-ENV_LASERRM_TBLS_TEMP_DEGF (table south) and H1:PSL-ENV_LASERRM_TBLN_TEMP_DEGF
(table north) at the back of the PSL environmental chassis.  This corrects the north/south identity problem.  So now the signal labelled TBLN
really is the "north" end of the table, as per the documentation.
H1 SEI
hugh.radkins@LIGO.ORG - posted 11:10, Monday 20 November 2017 - last comment - 11:11, Monday 20 November 2017(39484)
WHAM6 ISI CPS Corner3--Suspicious of readings...

Noticed the Corner3 CPS readings were both railed at -23k -32k and the Near Limit light was illuminated on the CPS Satellite box.  I trace this back to the point in time that the ISI was being locked and the Corner3 Feedthru was being reworked back in early October.  For the vertical sensors, the rail cleared when the exterior copper shield was cleared from the BNC bayonet which is used in the circuitry.  The Horizontal would not yield so easily.  On the vacuum side the Horizontal reading would clear if the cable inside was mucked with but it was not satisfying to this troubleshooter.  It seems this corner of cables need serious reworking.

Comments related to this report
hugh.radkins@LIGO.ORG - 11:11, Monday 20 November 2017 (39485)

FRS 9477

H1 General
jeffrey.bartlett@LIGO.ORG - posted 10:09, Monday 20 November 2017 (39483)
09:00 Meeting Minutes
Work plan for week of 11/20-2017

HAM2: Zero out bias sliders
	   IM4 trans alignment 

HAM3/4: Baffle alignment
	     Torque SR2
	     B&K Hammering
	     MC2 alignment and By-Pass work

HAM5: Adjust/mod height of spacers
	    Align OFI, ZM1-6, OM1, OM2, and SRM
	    Septum Window 
	    B&K Hammering
	    SMR alignment

BSCs: Baffle alignment 
	   Chamber closeout tasks

The BRS-X needs to be recentered

VAC: Vacuum group asked to be informed of all changes to Purge Air. Any changes should be communicated through the operator. 
	  
H1 PSL
edmond.merilh@LIGO.ORG - posted 08:37, Monday 20 November 2017 (39482)
PSL Weekly Report - 10 Day Trends FAMIS #6175

Nothing besides the trending "unusuals" to report other than curious looking oscillations in OSC_DB4_PWR that appear to correlate to the temp issues and don't seem to be as prominent in 1-3.

Images attached to this report
H1 PSL
peter.king@LIGO.ORG - posted 08:14, Monday 20 November 2017 (39481)
Crystal chiller topped off
Topped up the crystal chiller with 250 ml.
H1 CAL (CAL)
aaron.viets@LIGO.ORG - posted 19:02, Sunday 19 November 2017 - last comment - 11:27, Saturday 25 November 2017(39480)
gstlal calibration pipeline resampler fix for C02
I have added new features to the element lal_resample used in the gstlal calibration pipeline so that it can perform upsampling for the actuation equal in quality to the old gstreamer (version 1.4.5) resampler. The upgrade to gsteramer-1.10.4 on the clusters introduced a ~2% systematic error in the C01 frames from ~50 Hz to ~1 kHz during the month of August. See, e.g.,
https://ldas-jobs.ligo.caltech.edu/~alexander.urban/O2/calibration/C00_vs_C01/H1/day/20170802/

The change made was the addition of a sinc table filter in the upsampling routine. Several tests were done, and plots are attached:

The first two plots show the filter's response to a series of impulses separated by 4 seconds. This input data was upsampled from 128 Hz to 1024 Hz. The first of these plots shows 30 seconds of data, and the second is a close-up on a single impulse.
The 3rd plot is a 10-second sinusoid upsampled from 8192 Hz to 16384 Hz.
The 4th plot is a 30-second stream of ones upsampled from 128 Hz to 1024 Hz. The apparent thickness of the line indicates the amount of digital error, of order ~10^-8.
The 5th and 7th plots are ASD comparisons between the output produced by the calibration pipeline using this new resampler and the C00 frames from August.
The 6th and 8th plots are ASD comparisons between the output produced by the calibration pipeline using this new resampler and output pruduced with no resampling at all (i.e., all actuation was filtered at 16384 Hz). I suspect the wiggle above 1 kHz is due to a ~2% contribution from the actuation that is lost in downsampling to 2 kHz for the filtering.

For information on filters to be used for C02 production, see
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=39419
https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=36707
Images attached to this report
Comments related to this report
aaron.viets@LIGO.ORG - 11:27, Saturday 25 November 2017 (39519)
[Greg Mendell, Maddie Wade, Aaron Viets]

Greg's tests revealed problems with the new gstlal-calibration code that were not present in the old versions, producing error messages like:

*** Error in 'python': munmap_chunk(): invalid pointer:
0x00002babb1345780 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7ab54)[0x2ba8010eab54] ...
...

I've found and fixed two bugs in the new resampler:
1) In certain places, a  pointer to the next output buffer being produced was being incremented (but not dereferenced) beyond the end of the allocated memory of that buffer.
2) There was a particular corner-case where a pointer to where input data from previous buffers was being temporarily stored was being shifted to an incorrect location.

After the fix, I ran the same tests, and they produced identical results. The only difference was that the jobs I found that produced errors no longer produced those errors.
LHO VE
kyle.ryan@LIGO.ORG - posted 17:31, Sunday 19 November 2017 (39479)
1720 hrs. local -> Adjusted purge air to LVEA


			
			
H1 SQZ
sheila.dwyer@LIGO.ORG - posted 18:34, Friday 17 November 2017 - last comment - 21:04, Friday 17 November 2017(39477)
Sanity check on beam height discrepancy for ZM2

TJ, Sheila

This morning/afternoon we ( Keita, Jeff K, TJ, me, Lisa, Alvaro and Calum) realized that the riser for ZM2 (the squeezing TT in HAM5) is too tall, since it is set to match the height difference between HAM 5+ HAM6 at L1, which is not the same at H1.  

TJ and I went to the chamber to make some sanity checks that the discrepancy is about what we should expect based on drawings. We first set up a laser pointed that was mounted on a small breadboard in the cleanroom by HAM3 in the back of HAM6, pointing towards HAM5.  We leveled this by measuing the distance of the beam off the table near the laser pointer and again at the far edge of HAM6, roughly a meter away.  With our final tin foil adjustment we got the beam parallel to the table to within a mm over this distance.  The laser beam was 99 mm off of the HAM6 table top, and 203 off of the HAM5 table top, so we estimate the difference this way to be 104mm, or 4.1 inches.  

We also measured the height of the center of the ZM2 mirror to be 223 mm off of HAM5, or 8.78 inches.  That means that the center of ZM2 is 8.78-4.1 = 4.69 inches above the level of HAM6, them beam height in HAM6 is 4 inches.  Calum looked at drawings earlier and said that the riser height should be 0.76 inches too tall for H1 if it is based on L1 heights. 

We also attempted to measure the height of the center of the output aperture of the OFI off HAM5, which was a little difficult with our too short ruler and an akward angle.  We measured 3 times and got 207.5 mm, 205 mm, and 209.5mm.  (8.16 inches average, so 0.617 inches below ZM2).  

It seems like these measurements are in agreement with what Calum found in the drawings, within the precision of this measurement technique. 

Comments related to this report
keita.kawabe@LIGO.ORG - 21:04, Friday 17 November 2017 (39478)

Polarization rotation due to geometric effect won't be too bad even if we don't fix the height error.

If we don't correct the wrong height of ZM2, the polarization of the beam coming from VOPO is rotated when it goes into OFI. Wrong polarization is a loss.

I did a simple calculation and it seems like the rotation angle due to this is about 3.5 degrees and the loss is about 0.4%. This is small enough, we could choose NOT to fix the height of ZM2 though it will somewhat complicate the initial alignment procedure. OTOH, it seems as if it's possible to modify the raiser relatively quickly.


I eyeballed the positions of OFI steering mirrors and ZM2 in the horizontal plane on HAM5 from D0901134 and D1700472.

Similarly I eyeballed the position of ZM1 and the direction of the beam connecting VOPO and ZM1 on HAM6 from D1700464.

I used D0901920 to determine HAM5-HAM6 distance.

I assumed that ZM2 is 0.76 inches higher than everything else and that ZM1-VOPO beam is level.

I started with a perfectly level S-pol light reflected by the first steering mirror on OFI, and propagated it through the second OFI steering mirror, ZM2, ZM1, and  finally to VOPO.

Quick and dirty Matlab scripts are attached.

Non-image files attached to this comment
H1 PEM
robert.schofield@LIGO.ORG - posted 17:34, Friday 17 November 2017 (39476)
Comparison of PSL PEM channels before and after new water manifold installation

The attached plot shows no change in PSL PEM signals, accelerometers and microphone, that can be attributed to the new manifold.

Images attached to this report
H1 SEI (SEI)
sam.cooper@LIGO.ORG - posted 16:46, Friday 17 November 2017 - last comment - 12:25, Monday 20 November 2017(39475)
HEPI Watchdog trip levels

S Cooper, J Warner

We've been investigating the reasons into why HEPI tripped during O2 to see if anything could be done to prevent it. To do this we've been looking at both the time series sensor data in the local basis (H1,H2,V1,V2 etc), for the IPS, STS, L4C's and Actuators, the saturation counts and the watchdog status for every chamber (BSC's and HAM's - with the exception of HAM1). The first earthquake we ran this on was the Montana earthquake (GPS 118335800) as this was the only earthquake where HEPI was the first to trip.

When we if we look at the saturation counts, we find that only the L4C's are hitting their saturation threshold and are therefore likely causing watchdog trips, the horizontal L4C's are the first to saturate. 

If we then compare the levels that the watchdogs trip at across all 10 chambers, we find that ETMX trips at 10% the level of the other chambers. I've attached an annotated PNG highlighting the BSC chambers, and a .fig file that contains the saturation data for all 10 chambers. The dashed lines indicate the watchdog level (multiplied by 10,000 for easier comparison) with the solid lines indicating the specific chambers L4C. 

I'm now running the same script for other earthquakes that HEPI tripped in to see if this is an isolated case. 

Images attached to this report
Non-image files attached to this report
Comments related to this report
jim.warner@LIGO.ORG - 12:25, Monday 20 November 2017 (39487)

I'm attaching some plots showing the difference between ITMX and ETMX. The first & third subplots are the L4Cs for each chamber, the second and fourth plots are and the watchdogs and number of L4C saturations for each chamber. The L4Cs show roughly the same motion for each chamber (if anything ITMX is worse), but the red traces for the second and fourth plots show that, as Sam found, ETMX is tripping at a much lower number of saturations than ITMX. Actuators and IPS don't saturate for this trip. Hugh, Dave and I have all looked at the models, but haven't found any point where ETMX differs from the other chambers. The saturation threshold is user set, but is the same for all chambers. Not sure what's happening here.

Images attached to this comment
H1 AOS (AOS, ISC, VE)
gerardo.moreno@LIGO.ORG - posted 16:33, Friday 17 November 2017 (39474)
HAM6 Main Beam Septum Viewport

(Travis S, Gerardo M)

We removed the main septum viewport and set it inside the cleanroom for HAM4 to clean it, first contact was applied on one face and it should be ready for removal on Monday.

For reference before removal, the fiducial line on viewport was at 1 o'clock, see attached photo.

Images attached to this report
H1 AOS (AOS, SQZ)
gerardo.moreno@LIGO.ORG - posted 16:27, Friday 17 November 2017 (39473)
HAM5 OFI Update

The OFI cage was moved, beam was verified and it appears to be going through the aperture without clipping, for some reason the beam was moving a bit too much on pitch, purge air was dialed down but did not help.  Cage is being held in place by one dog clamp, the rest will be done on Monday.

H1 General
jim.warner@LIGO.ORG - posted 16:06, Friday 17 November 2017 (39472)
Shift Summary

TITLE: 11/18 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
LOG:

16:30 Nutsinee to SQZ
17:00 TJ to HAM5, Nutsinee and Terry to SQZ, JeffB to LVEA
17:15 Gerardo to HAM5
17:45 Ed, Fil moving squeezer electronics into LVEA
18:15 Travis to HAM5
18:51 TJ - Out of the LVEA
18:52 Travis - Out of the LVEA
21:15 Travis, Jason to LVEA for elliptical baffles
22:00 Peter out of PSL
22:30 Travis out
23:00 Travis, Gerardo to HAM6, removing main viewport
23:15 TJ, Sheila to HAM5
0:00 Travis out

H1 PSL
peter.king@LIGO.ORG - posted 15:00, Friday 17 November 2017 - last comment - 15:11, Friday 17 November 2017(39470)
New bull's eye detector installed on table
The new bull's eye detector (S1700201) was placed onto the table where the prototype one was located.
Adjusted the beam using the mirror located in front of the detector.  Between pins 3 and 8 of the DB9,
~ -14V was measured.  Between pins 1 and 6, ~ -26.5V.  Although it was a bit difficult to see with an
IR viewer, the spot on the photodiode looked reasonably well centered.  Powering up the detector caused
the high power shutter to close.  I reset the error condition without any issues.

    Not sure of the exact cause of the signal degradation of the previous detector, as reported by
Sheila, but a cable was close to the beam path.

    To debug some temperature related signals, I placed my hand on/over the temperature sensor closest
to the entrance of the laser room for more than a few seconds.  If I remember what Richard told me,
the signal labelled "north" on the MEDM screens, is in fact the south sensor and vice versa.
Images attached to this report
Comments related to this report
vernon.sandberg@LIGO.ORG - 15:11, Friday 17 November 2017 (39471)

This completes FRS ticket "Ticket 9459 - PSL bullseye misaligned during maintenance, replacement diode is ready".

H1 SEI
sam.cooper@LIGO.ORG - posted 16:36, Thursday 16 November 2017 - last comment - 13:51, Friday 17 November 2017(39455)
Number of watchdog trips per subsystem during O2

S Cooper, S Dwyer, J Warner, 

Attached in this alog are some overviews of the total number of watchdog trips by subsystem (HEPI,ISI,SUS) per chamber over the course of O2 for some known large earthquakes. We get this data by looking at the state of the watchdogs for each subsystem over the course of two hours during an earthquake using minute trended data. To generate these plots we look at the WD_MON State channels and just check for if they ever deviate from their ideal value (1 in most cases) and sum the number of events that these trip. We also pull the interferometer lock state to a) monitor lock losses and b) to veto any trips caused by frontend crashes rather than earthquakes. 

Also attached is some comma delimited text files containing information on which of these watchdogs tripped first for each earthquake, with a list of GPS times listed for each of these events. Note, again because of the minute trended nature of the data its hard to pinpoint what watchdog tripped first, as watchdogs that trip within a minute of each other will appear as having tripped at the same time. With the data being minute trended, it appears as if the suspension trips first, though this is not the case when examining the each of these events using finer timesteps. Note opening these in web browser will screw with the formatting. 

There are two events where HEPI appears to trip first when examining these events in minute trend these only appear to occur on ETMX, please take this with a grain of salt as this is based off minute trended data, so there may be other trips before HEPI on ETMX, that occur within the same minute, or HEPI trips on other chambers first before ISI trips. I plan to investigate these further with second trended/ full data rate  data.  

Images attached to this report
Non-image files attached to this report
Comments related to this report
sam.cooper@LIGO.ORG - 10:26, Friday 17 November 2017 (39468)

As an update to this, I've just checked all the eathquake times where the minute trended data reported that either HEPI or the suspension was the first to trip. On all the analysed earthquakes (116 during O2) the suspension never tripped first. HEPI only tripped first on the montana earthquake (I've yet to check the ISI trips in more detail to verify this). On the montana earthquake (gps time 1183358000), HEPI tripped first on all the chambers. All other earthquakes that had watchdog trips, the ISI was the first to trip.

sam.cooper@LIGO.ORG - 13:51, Friday 17 November 2017 (39469)

Update 2: I've included files that show GPS times of each earthquake where HEPI, ISI and SUS tripped per chamber. From this we see: ETMX has one more HEPI trips than the other chambers. ETMY has the most suspension trips.

Non-image files attached to this comment
Displaying reports 49801-49820 of 88172.Go to page Start 2487 2488 2489 2490 2491 2492 2493 2494 2495 End