Displaying reports 47741-47760 of 86146.Go to page Start 2384 2385 2386 2387 2388 2389 2390 2391 2392 End
Reports until 08:33, Monday 27 November 2017
H1 PSL
edmond.merilh@LIGO.ORG - posted 08:33, Monday 27 November 2017 (39521)
PSL Weekly Report - 10 Day Trends FAMIS #6176

Everything looks nominally ok. The humidity spikes are curiously sharp on the 24th.

Images attached to this report
H1 ISC (INS, ISC, SQZ)
keita.kawabe@LIGO.ORG - posted 20:06, Wednesday 22 November 2017 - last comment - 15:02, Saturday 25 November 2017(39518)
OFI SQZ path mostly done for now (TJ, Gerardo, Jenne, Sheila, Keita)

OFI was realigned by Gerardo. Irises on HAM6 were put in place by TJ.

We installed a temporary HWP on OFI.

The beam was first centered on the steering mirror on OFI closer to ZM2 by using the other steering mirror on OFI. The centering accuracy is not good but it's not that important.

Then the beam was centered on ZM2. Centering accuracy I would say is a mm or so.

We rotated ZM2 so the beam is centered on the HAM6 iris closer to VOPO (i.e. more important one) for YAW. Fortunately the PIT was already about right, we didn't have to rebalance ZM2. All PIT fine adjustment was done using one of the steering mirrors on OFI.

Only after the beam was centered on the HAM6 iris closer to VOPO, we moved the second HAM6 iris in place and centered the iris without touching the beam.

The beam dump to catch the septum window reflection was roughly adjusted by eyeballing. Unfortunately it was impossible to see the AR reflection using IR viewer and a card, so instead I looked at the reflection of the ZM2 mirror outline on the septum window while positioning my eye on the line connecting the IR beam position on the septum and the apex of the V of the beam dump. The power coming to sqz path is like 300uW as of now, AR reflection should be much smaller than uW. Maybe we can increase the power to 10W (a factor of 40 increase) and see the beam.

Sheila and Jenne measured the power of the beam in the main sqz path using a power meter.

On OFI between M1 and M2 steering mirror 286 uW
Before 1st iris (closer to HAM5) on HAM6 288 uW
After 2nd iris (closer to VOPO) on HAM6 276 uW

ZM2 and beam dump dog clamps are not super tight as I wasn't able to find the right tools. They need to be tightened and after that we need to confirm that the beam still comes through both of the irises.

Pictures to show the positions of ZM2, beam dump and two irises will be posted later.

Comments related to this report
keita.kawabe@LIGO.ORG - 15:02, Saturday 25 November 2017 (39520)

1: HAM6 iris closer to VOPO.

2: HAM6 iris closer to HAM5.

3: ZM2.

4: ZM2 viewed from the front.

Images attached to this comment
LHO VE
kyle.ryan@LIGO.ORG - posted 18:43, Wednesday 22 November 2017 (39517)
1840 hrs. local -> made small adjustments to purge air in LVEA


			
			
H1 AOS (AOS, SQZ)
gerardo.moreno@LIGO.ORG - posted 17:10, Wednesday 22 November 2017 (39516)
HAM5 OFI Update

Beam is centered on the input and output irises, I stopped at that point to allow Sheila and Keita to continue with the squeezer path.

Cage still needs some dog clamps, currently it has 3 holding it in place, input baffle needs to be replaced, AOSEMS need to be installed and damping needs to be revisited, table had to go up to center the beam on the apertures, thus changing the damping behavior.

Note about the output baffle, the beam is close to the -X side of the aperture.  I will post a photo as one comes available.

LHO General
thomas.shaffer@LIGO.ORG - posted 16:00, Wednesday 22 November 2017 - last comment - 16:24, Wednesday 22 November 2017(39507)
Ops Day Shift Summary

TITLE: 11/22 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: Sheila, Nutsinee, and Terry still out in the SQZ Bay. Gerardo still tweaking OFI.
LOG:

Comments related to this report
gerardo.moreno@LIGO.ORG - 16:24, Wednesday 22 November 2017 (39515)

I'm done tweaking the OFI Alignment for the day.

H1 General
travis.sadecki@LIGO.ORG - posted 14:38, Wednesday 22 November 2017 (39512)
HAM6 septum accelerometer installed

G. Moreno, T. Sadecki

The accelerometer and mount were installed on the HAM6 septum viewport.  See attached photos for the serial number of the installed accelerometer.  The accelerometer was plugged into the plug labeled 'B' on the octopus cable (interestingly, there was no plug labeled 'A', just 'B' though 'I').  The DB25 end of the octopus cable was NOT connected to the feedthru since other accelerometers are to be installed on the table at a later date, requiring that SEI lace the cable down the ISI.  

In the last photo (DSCN0142), one can see (although not that clearly) that the hex head of the accelerometer mounting screw has the "curly shavings" from the hex head stamping process still intact.  I recall these being a subject of concern during aLIGO install, so wanted to bring it up.  This accelerometer is in the segregated HAM6 volume and has presumably passed an RGA scan, so perhaps there is no issue here.

Images attached to this report
H1 PSL
thomas.shaffer@LIGO.ORG - posted 14:27, Wednesday 22 November 2017 (39514)
Weekly PSL Chiller Reservoir Top-Off

FAMIS 6550

Added 200mL to the crystal chiller.

H1 SEI
thomas.shaffer@LIGO.ORG - posted 14:19, Wednesday 22 November 2017 (39513)
ISI CPS Noise Spectra Check - Weekly

FAMIS 6925

During vent CPS check.

Images attached to this report
H1 SQZ
thomas.shaffer@LIGO.ORG - posted 14:09, Wednesday 22 November 2017 (39508)
ZM2 Spacer Reinstalled After Height Reduced

I wanted to get a quick summary of events on this spacer, but if I missed something or have something wrong please let me know.

On Friday, Keita and Sheila were aligning HAM5 and noticed that the beam height was odd going to ZM2. Jeff Kissel was consulted and he looked up drawings and found a possible discrepancy in the beam height. Some emails were exchanged with Lee McCuller and Koji, and in the mean time Keita, Sheila, Gerardo, and I talked to Lisa and Calum on TeamSpeak.  Turns out that the spacer that sits under the ZM2 tip tilt (D1600005) was 0.76" too tall. Sheila and I measured in chamber and confirmed this (alog39477). This height difference comes from the difference in beam height on HAM5 between L1 & H1. Our two options:

a) Remove 0.76" from the spacer height and then clean, rebake, and reinstall.

    - There was not enough material to remove from the bottom, and the top would need some holes drilled and tapped, then vent holes drilled on the sides. Modifying the top would create a higher contamination risk but seemed like easiest way to modify this. To speed up the process, we would need an approval on a waiver to allow a truncated version of cleaning and baking.

b) Deal with the height difference and try to move on with alignment.

    - This was the ugly option because after we align the beam to ZM2, we are going to shoot it into HAM6 and through two iris's that will remain until the VIP is installed. The irises are nominally 4" off the HAM6 table, but with the ZM2 up 0.76" they would need to be raised up slightly. Finding correctly sized posts and making adjustments would be a pain. The other issue with this option is there was potential for loss due to the polarization change in the changing height. Keita did the matlab math (alog39478) and it turns out that it wouldn't be an issue, but the ugly alignment doesn't go away. 

It was decided to chop the top (option a) and on Monday I pulled out the spacer, handed it off to Tyler to machine, and then he gave it to Chris for a clean and 12hr air bake. Yesterday, I reinstalled the spacer and aligned ZM2 to the coordinate drawing. Keita, Sheila, and I aligned the beam from the OFI to ZM2 in pitch and will do more with yaw either today or Monday after the holiday. Pictures attached to show height difference. For reference the spacer under the beam dump is what the TT spacer used to be.

Aside: the beam dump also sits on a spacer that is 0.76" too tall. This was an easy fix of just getting a slightly smaller post, so it wasn't the main character of this story.

 

Images attached to this report
H1 SUS
travis.sadecki@LIGO.ORG - posted 13:17, Wednesday 22 November 2017 - last comment - 13:20, Wednesday 22 November 2017(39510)
SRM alignment

B. Weaver, T. Sadecki

While we were investigating alignments of baffles, etc. while in HAM 4, we steered SRM such that the reflected beam went back to SR2.  Screenshot of the new SRM slider values attached as a comment. 

Comments related to this report
travis.sadecki@LIGO.ORG - 13:20, Wednesday 22 November 2017 (39511)
Images attached to this comment
H1 SUS
travis.sadecki@LIGO.ORG - posted 13:13, Wednesday 22 November 2017 (39509)
SR2 SUS structure dog clamps torqued

The dog clamps securing SR2 to HAM4 have been torqued to 8.5 ft/lbs (as close to 100 in/lbs (E1100411) as our torque wrench would allow) except for those on the north side of the structure.  The heads of the screws for the dog clamps on the north side are so close to the structure that the head of the torque wrench would not fit.  I attempted to duplicate the torque on these dog clamps by testing the already torqued dog clamps on the other sides of the structure and doing my best to replicate the force required to produce the torque using a normal flex handle socket wrench.  Upcoming B&K measurements of this structure will tell if I did well.

LHO General
thomas.shaffer@LIGO.ORG - posted 08:50, Wednesday 22 November 2017 (39506)
Ops Day Shift Transition

TITLE: 11/22 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 8mph Gusts, 6mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.87 μm/s
QUICK SUMMARY:  Late post, quiet morning so far.

H1 DetChar (DetChar, PEM)
evan.goetz@LIGO.ORG - posted 05:16, Wednesday 22 November 2017 (39505)
O2 lines and combs in H1 data
Pep Covas, Evan Goetz, Ansel Neunzert, Brynley Pearlstone, Keith Riles

Summary:
We report on lines and comb investigations by the CW group that lead toward a version 1 lines and combs safe for cleaning in O2 H1 data. Run averaged spectra (covering all of O2 except a 1 month epoch, details below), provide a basis for data quality issues that can degrade CW/Stochastic searches. Any sharp spectral feature has a potential to contaminate and degrade astrophysical searches. We attempt to find all of the combs that are obviously non-astrophysical, and to determine any environmental influence for single lines.

If we can mitigate the most prevalent/egregious combs, this would go a long way towards improving the science that can be done with LIGO data. These combs are mostly at low-frequency (f < 100 Hz):

Comb spacing / offset
---------------------
1.0000 Hz / 0.0000 Hz
1.0000 Hz / 0.5000 Hz
1.0000 Hz / 0.9994 Hz
1.0000 Hz / 0.9987 Hz
0.9999862 Hz / 0.2503172 Hz
0.9878881 Hz / 0.0000 Hz

Notching or replacing data from the narrow bins only works as long as no other contamination is in nearby bins. Thus, it would be better to mitigate these combs in hardware.

A full list to the version 1 line/comb list can be found by following this link. Also through this link, one can find the un-vetted lines found in the H1 run-averaged spectrum.

Attached below are plots of the run-averaged spectrum in full, and in narrower frequency bands.

Details:
Using the C01 calibrated h(t) for O2 through July 2017 and C00 calibrated h(t) for Aug. 2017, we produce 7200 s long Short Fourier Transforms (SFTs), excluding CAT1 CBC vetoes. This mimics many CW searches and also provides good frequency resolution and coherence length so that most narrow spectral features that can impact CW searches can be found. We exclude the period from March 14, 2017 17:00:00 UTC to April 18, 2017 23:00:00 UTC to avoid the bad spectral contamination caused by the Pcal camera ethernet adapter (see aLOG 35640).

In the figures below, the noise-weighted run averaged spectra are plotted over the O2 run and notable features:
Figure 1, 20 Hz - 2 kHz; overall, better than O1
Figure 2: 20 Hz - 50 Hz; combs and lines galore (too many to list here)
Figure 3, 50 Hz - 100 Hz; more combs and lines but better than below 50 Hz, oddball narrow comb forest around 75 - 80 Hz
Figure 4, 100 Hz - 200 Hz; much better here than below 100 Hz, oddball narrow comb forest around 153 - 155 Hz
Figure 5, 200 Hz - 400 Hz;
Figure 6, 400 Hz - 1 kHz; violin harmonic regions are difficult/impossible to analyze (damping these modes may help immensely), oddball narrow comb forest around 970 Hz
Figure 7, 1 kHz - 2 kHz; violin harmonics problematic (again, damping will likely help), other oddball narrow comb forests around 1022 Hz and 1046 Hz

The procedure to find the lines and combs was mostly a divide-and-conquer manual inspection of the data. Narrow features were flagged, and combs could be identified by their common spacing. Some automated tools were helpful, but manual inspection was usually necessary. Combs are obviously non-astrophysical, so almost no vetting needs to be done, but the cause of these combs can remain elusive. 

Making the timing system LEDs stop blinking has reduced the amplitude of the 1 Hz comb with 0.5 Hz offset, the comb is not completely mitigated in O2 data. Further investigations are underway. Other 1 Hz combs also remain prevalent in the O2 data, probably GPS synced due to their narrowness. Coherence between the sites of these lines has not yet been established, but if GPS synced, then likely coherent (bad for any CW/Stochastic GW search).

Other lines that were found to have environmental cause in O1 and again appearing in O2 data are also in the version 1 line/comb list. Still other lines that are found to be correlated using the NoEMi tool on auxiliary channels are being vetted further using coherence tools. As further investigations proceed on other lines, we may have a version 2 of the lines/combs list.

Takeaway message: Mitigating the most prevalent of combs is going to have the biggest across-the-board impact on CW searches. These combs are listed in the summary section above.
Images attached to this report
H1 INS (INS, ISC, SUS)
keita.kawabe@LIGO.ORG - posted 22:51, Tuesday 21 November 2017 (39504)
OFI and downstream alignment 20171121 (TJ, Gerardo, Travis, Sheila, Betsy, Keita)

1. Betsy and Travis scrutinized the beam position on SRM and SR2.

After they're done, to me the beam position on the back baffle hole of SRM seems to have moved further to -X direction by a mm or two but the beam was moving and we weren't sure.

2. At this point the rejected beam from OFI cleared the rotator.

Good.

The beam cleared the OFI rotator and was going to the direction of ZM2. The beam spot on two steering mirrors on OFI were to the +X direction. Since Koji didn't want to move the mirror base plate position while he was here, we only turned the mirror holder to center the beam on the second mirror (the first mirror is still off centered but it's far enough from the edge).

TJ installed the ZM2 on the new riser and put it roughly at where it should be, so we aligned the second steering mirror on the OFI to roughly center the beam on ZM2. TJ also installed the beam dump with the right post.

Gerardo needs to confirm the OFI alignment relative to the beam again.

3. Septum window was rotated 180 degrees.

The scribe mark showing the thickest side is now at 9 o'clock position (i.e. +X).

Yesterday the beam was at X=-36mm on OM1, I expected that the septum rotation will bring the beam to -9mm position (alog 39491). In reality the beam was at -13mm position. At least the movement in the correct direction, height is still correct.

Without doing anything, the beam was already hitting OM2 though too low. Attached shows some measurement numbers we made.

4. What needs to be done for HAM6.

VOPO path:

This needs to be done before corner pump down. Irises need to be installed. ZM2 and OFI steering mirror on HAM5 needs to be adjusted to center the rejected beam on irises on HAM6.

In principle the following could be done after the corner pump down with the IMC locked, but we should convince ourselves that this will absolutely work.

OMC path:

To make sure that no part of the beam comes too close to any of the edges, unfortunately OM2 needs to be moved to +X direction, meaning OM3 needs to be rotated.

OM1 is pushed to -X by 13mm, rotated to send the beam to the center of new OM2 location (and rebalanced as the beam is too low on OM2).

OM2 is pushed to +X by 19mm or so, this will increase the distance between the OM1-OM2 line and the edge of the OM3 by 10mm-ish. OM2 also needs to be rebalanced as the angle of the beam coming from OM1 will be different.

OM3 is rotated to accommodate the beam angle change.

I and Sheila convinced ourselves that this will work though painful.

ASC-AS_C path:

Everything could be moved to -X by 13mm or so and it will be fine.

I and Sheila convinced ourselves that this will work.

OMC REFL path:

Beam diverter will be reused for SQZ path, OMC REFL QPD sled wasn't used and probably will not be used, so most of this path could be replaced by a single high power beam dump?

OMC TRANS path:

No need to do anything?

Images attached to this report
H1 ISC (ISC, VE)
gerardo.moreno@LIGO.ORG - posted 19:14, Tuesday 21 November 2017 (39503)
HAM6 Main Beam Septum Viewport

(Travis S, Gerardo M)

This time septum viewport was rotated 180 degrees, it's fiducial line is now pointing towards 3 O'Clock.  Bolts aren't torqued yet, this will allow for the installation of a bracket for an accelerometer in the coming days.

H1 SYS
betsy.weaver@LIGO.ORG - posted 17:10, Tuesday 21 November 2017 - last comment - 09:53, Monday 27 November 2017(39501)
La La alignment land

Following on from Keita's alog from yesterday, we spent all day attempting to convince ourselves that the SR chain of optics are hanging symmetrically within their structures, using little to no tooling.  Holding rulers up to various optics and structures, and painstakingly logging measurements, I could not find any reason to believe that the beam centering we've done between the center of SR2 and SRM is out by more than ~2mm.  The PSL beam line that we have set between the center of SR2 and SRM looks good to carry on.  Indeed, this may mean that the baffles do not look symmetric on the structures, but at least the beam path appears correct.  We'll revisit baffle positions an drawings tomorrow.

Meanwhile, since I was wandering the tube between HAM4 and HAM5, I took a look at the beam centering going through the newly built SR2 scraper baffle D1003300.  At first I was thrown off by the fact that the beam seemed to go through the baffle off center even though the baffle was installed using a template which I would have thought set it pretty close (within mm's).  A lunch break consult with Keita and Calum pointed out that the beam I was looking at was only the SR3-to-SR2 beam which straddles the centerline of the baffle ellipse hole with the SR2-to-SRM beam which is hard to spot when viewing the SR3-to-SR2 beam with an IR card.  A quick calculation, and a SW confirmation told us the 2 beams should be separated by 20mm and should straddle the centerline.   Now how to find the center of the hole while standing in the dark with a viewer card and not occulting the beam with your body...  I gave up trying to measure in-situ and instead opted for some pictures to scale.

Attached is the PDF scaled pic I used - I'm not spending any more time screwing around with the oddities of why the font is miniscule - what I did was:

- Scale the aperture in the picture to the 161mm dimension I read off the drawing D1003301 (for what ever reason Adobe makes starts the scale at a huge setting like some 40 inches or so)

- Using the new scaler, measure to the beam center shown in the picture

- 161mm /2 = 80.5mm is where the center of the aperture should be, so the beam center should be left of that by 10mm (half of the 20mm), 90mm.

- The beam is at 87.4mm.  Of course it's hard to estimate the beam center since the beam is ~20-30mm in diameter, fuzzy, and moves a bit.  I'd estimate the error of my ability to measure this centering to better than 5mm...  Feel free to redo.

Seriously, please let that be close enough.

 

I did however, take a picture of what can be seen from the plane of the MCTube Eyeball baffle closest to HAM4 on the beam path (see below).  Not sure I was able to place the camera on the beam line very well...  I can confirm that everything shown in the left lobe cutout of the baffle is in dead all HWS silver mirror reflections (and no metal from mounts).  It's hard to tell if there is a sliver of the right side of the SR2 optic still in the right portion of the right aperture lobe.  Maybe it's the angle of my camera view.  Dunno.

 

Images attached to this report
Non-image files attached to this report
Comments related to this report
betsy.weaver@LIGO.ORG - 09:53, Monday 27 November 2017 (39522)

A consult with Calum who agreed that this alignment is good.

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.
Displaying reports 47741-47760 of 86146.Go to page Start 2384 2385 2386 2387 2388 2389 2390 2391 2392 End