Displaying reports 55221-55240 of 84669.Go to page Start 2758 2759 2760 2761 2762 2763 2764 2765 2766 End
Reports until 16:05, Thursday 06 October 2016
H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:05, Thursday 06 October 2016 (30276)
Ops Day Shift Summary
Title:  10/06/2016, Day Shift 15:00 – 23:00 (08:00 - 16:00) All times in UTC (PT)
State of H1: IFO lost lock due to PI ring up. IFO was coming back up when I came in. Was able to damp PIs M2 and M10. IFO relocked at NOMINAL_LOW_NOISE with no problems	   
Outgoing Operator: N/A
 
Activity Log: All Times in UTC (PT)

14:20 (07:30) Chris & Apollo – Going down Y-Arm to work on beam tube sealing near CS
14:30 (07:30) Damped PI modes M2 & M10 – IFO relocked at NOMINAL_LOW_NOISE	
14:50 (07:50) Robert – In LEA doing injections
15:10 (08:10) Peter – Going into PSL to adjust power & install new PD (WP #6219)
15:10 (08:10) Christina – Forklift crate from LSB to Mechanical building
15:12 (08:12) Richard – In MSR to replace batteries (WP #6218)
15:15 (08:15) Karen – Cleaning in Optics Lab
16:00 (09:00) Kiwamu – Going into PSL for PD install (WP #6219)
16:09 (09:09) Karen Out of Optics Lab
16:20 (09:20) Peter & Kiwamu – Out of PSL
17:32 (10:32) Robert – Running injection
21:45 (14:45) Dave – Adding new DBB signals to frames & DAQ restart (WP #6220)


Shift Details: 10/06/2016, Day Shift 15:00 – 23:00 (08:00 –16:00) All times in UTC (PT)
Support: Cheryl,               
Incoming Operator: Travis

Shift Summary:  Broke lock around 14:00 (07:00) due to PI ring up. At around 14:30, damped PI Mode #2 by changing phase from 30 to 80 and PI Mode #10 by changing phase from 30 to 80. Modes responded quickly and we relocked at NOMINAL_LOW_NOISE with no problems. 
PI Modes 2 & 10 rang up again – damped mode 2 buy changing phase from 80 to 30. Damped Mode 10 by changing phase from 80 to 60.
Most of shift spent in commissioning and relocking. 
H1 ISC (DetChar, ISC, PSL)
gabriele.vajente@LIGO.ORG - posted 15:00, Thursday 06 October 2016 - last comment - 17:15, Thursday 06 October 2016(30274)
Transfer function between ISS_PDA and DARM

Following up on entry 30273, I computed the coherence and transfer function between ISS_PDA_REL_OUT (which should be calibrated in RIN units) and CAL-DELTAL_EXTERNAL (including the proper calibration). Coherence is good enough to estimate a transfer function over all the frequencies above 10 Hz. I'm not injecting any additional noise, just using the signals as they are, so the fact that we have coherence doesn't necessarily mean that we really have a coupling of intensity noise to DARM.

However, the transfer function has a very interesting shape (see figure). It's behaving like 1/f^3 up to ~80 Hz, and above that frequency it increases like f. The region below 80 Hz might very well be consistent with radiation pressure coupling of intensaity noise. We'll have to run some numbers to be sure that this makes sense. I have no clear explanation of the increase above 80 Hz.

Addition:

A quick and dirty estimate of the expected coupling of RIN at the ISS PDs to DARM due to radiation pressure

x = 2 deltaP / c / (m * (2*pi*fr)^2) / (fr / fr_pole_doublecav) = 2 P_arm / c / (m * (2*pi*fr)^2) / (fr / fr_pole_doublecav)  * RIN

At 30 Hz the coupling should be about 2e-11 (maybe off by a factor of 2 or so due to the two arms, etc..). This is many orders of magnitude LARGER than what measured in the TF discussed above. So it is unlikely that PDA/PDB see real intensity noise that goes into the IFO.

Images attached to this report
Comments related to this report
gabriele.vajente@LIGO.ORG - 17:15, Thursday 06 October 2016 (30285)

I checked how stable this transfer function was over time. I picked the lock stretch that started around GPS 1159781417, last night.

The first plot shows the transfer functions CAL_DELTAL / PDA_RIN for 23 segments, each 600 seconds long. The second plot shows the same transfer functions, but divided by the overall mean, to emphasize the variations. It's clear that there are variations up to ~40% during this time period.

FInally, the last plot shows the value of the transfer functions averaged in four different frequency bands, as a function of time. This shows more clearly the variation and the more accentuated trend at the beginning of the lock stretch.

Images attached to this comment
H1 DetChar (DetChar)
gabriele.vajente@LIGO.ORG - posted 14:55, Thursday 06 October 2016 - last comment - 16:41, Thursday 06 October 2016(30273)
Coherences

I ran a BruCo scan for the last night lock, using ten minutes of data when the range was at ~65 MPc. Results are available here:

https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1159774937/

Summary

There is a lot of coherence a bit everywhere:

The "jitter noise" above 100 Hz shows a lot of coherence with many signals, of different origins. Most of the IMC WFS signals are coherent, for example: IMC-WFS_A/B_DC_PIT/YAW_OUT (fig. 5 and 6).

The most interesting coherence is however with the intensity stabilization: PSL-ISS_PDA_REL_OUT and PSL-ISS_PDB_REL_OUT shows quite large coherence, as well as the ISS control signal: PSL-ISS_AOM_DRIVER_MON_OUT. It seems that PDA and PDB (first loop ISS) are completely dominated by what the ISS second loop is doing (as shown by the control signal). The coherence with DARM in the 100-1000 Hz region is very close to one. See fig. 7 and 8.

Note that in the same 100-1000 Hz region, the coherence with PSL lab accelerometers is also significant, but mostly on the peaks (fig. 9)

En passant, a narrow feature at 56.75 Hz and 113.50 Hz are coherent with EX magnetometers (PEM-EX_MAG_EBAY_SEIRACK_X/Y PEM-EX_MAG_VEA_FLOOR_Y/Z)

Multicoherence

I selected the channels with the largest coherence from the BruCo report, and run a multicoherence code.

chnames = {'H1:LSC-MICH_OUT_DQ', 'H1:LSC-SRCL_OUT_DQ', 'H1:LSC-PRCL_OUT_DQ', ...
            'H1:ASC-AS_B_RF45_Q_YAW_OUT_DQ', 'H1:ASC-OMC_B_YAW_OUT_DQ', 'H1:ASC-OMC_B_PIT_OUT_DQ', ...
            'H1:LSC-REFL_A_RF45_I_ERR_DQ', 'H1:LSC-REFL_A_RF9_Q_ERR_DQ', 'H1:IMC-WFS_A_DC_PIT_OUT_DQ', ...
            'H1:IMC-WFS_B_DC_PIT_OUT_DQ', 'H1:IMC-WFS_A_I_YAW_OUT_DQ', 'H1:IMC-WFS_A_Q_YAW_OUT_DQ', ...
            'H1:PSL-ISS_AOM_DRIVER_MON_OUT_DQ', 'H1:PSL-ISS_PDA_REL_OUT_DQ', 'H1:PSL-ISS_PDB_REL_OUT_DQ', ...
            'H1:PSL-ISS_SECONDLOOP_RIN_INNER_OUT_DQ', 'H1:PSL-ISS_SECONDLOOP_RIN_OUTER_OUT_DQ', ...
            'H1:PSL-PMC_HV_MON_OUT_DQ', 'H1:IMC-IM4_TRANS_SUM_OUT_DQ', ...
            'H1:PEM-CS_ACC_PSL_TABLE1_X_DQ', 'H1:PEM-CS_ACC_PSL_TABLE1_Y_DQ', 'H1:PEM-CS_ACC_PSL_TABLE1_Z_DQ', ...
            'H1:PEM-CS_ACC_PSL_PERISCOPE_X_DQ'};

The code take into account the cross-coherences between channels and produce the total coherence and an estimate of the noise projection, base on that coherence. The last figure (10) shows this coherence and the projection into the DCPD signal. A lot of noise can be explained by the coherences.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 16:10, Thursday 06 October 2016 (30277)

Just a quick note:  Since I was running a2l many times during last night's lock, there isn't a lot of time that the lines aren't there.  The 10 min that Gabriele chose include the lines.  This doesn't change any conclusions except the peaks right around 20Hz. 

Anyhow, Gabriele is going to take a quick look at the next lock, after I left for the night just in case.

gabriele.vajente@LIGO.ORG - 16:41, Thursday 06 October 2016 (30283)

Analysis results for the next lock are available here:

https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1159781417/

No much difference, except that now DHARD_PIT is more relevant, see plot.

Images attached to this comment
H1 ISC
jenne.driggers@LIGO.ORG - posted 13:01, Thursday 06 October 2016 - last comment - 16:16, Thursday 06 October 2016(30272)
Laser power was too high - 60W was actually ~60W

So, apparently Peter went into the PSL this morning and adjusted the HWP to give us more power incident on the rotation stage.  However, this was not communicated to commissioners / people in the control room, so the ISC_LOCK guardian was still requesting 60W.  With the hardware change, this was actually giving us ~60W into the vacuum.  Something in the ASC didn't like this, and we lost 2 locks after ~1 hour each, with something drifting away. 

EDIT:  I guess some commissioners did know that we were getting 60W and decided to try running with it, we just didn't think it would have such a deleterious effect on the ASC.

Comments related to this report
peter.king@LIGO.ORG - 16:16, Thursday 06 October 2016 (30279)
The half waveplate before the IO EOM was adjusted to yield a maximum of 60W as displayed by the
Ops Overview MEDM screen.  Said activity was performed under the watchful gaze of the day operator,
who was also my interlocutor whilst the waveplate was adjusted.

So the power table looks like ...

Requested power Indicated power
60 59.7
50 54.5
40 43.5
25 27.4
2 2.2
For the record, turning the small adjustment knob clockwise as you look at the mount, increases the power. Peter & (the day time operator)
H1 AOS (AOS, SEI, SUS)
corey.gray@LIGO.ORG - posted 12:15, Thursday 06 October 2016 - last comment - 16:14, Thursday 06 October 2016(30270)
Optical Lever 7 Day Trends

The only oplev which is furthest off (approaching -10urad) is the HAM2 oplev (pit & yaw).  This closes out FAMIS#4696.

Images attached to this report
Comments related to this report
jason.oberling@LIGO.ORG - 16:14, Thursday 06 October 2016 (30280)

Nothing here looks out of the ordinary.

H1 CAL (DetChar)
jeffrey.kissel@LIGO.ORG - posted 12:04, Thursday 06 October 2016 - last comment - 12:59, Thursday 06 October 2016(30269)
PCALX Roaming Calibration Line Frequency Changed
J. Kissel, S. Karki

As we've done in O1, we're creating a high-frequency ( > 1 kHz ) excitation via PCALX whose frequency is changed over long-duration in order to map out the interferometer's sensing function out to as high as is needed for burst and binary neutron star coalescence searches. For quite some time now (since July! see LHO aLOG 28301), this line has been gathering data at 3501.3 [Hz]. We haven't moved it because the IFO's duty cycle has been low, the power level has been inconsistent, and our person power has been limited.

Today is the day!

I've resumed moving this line, following the schedule posted by Sudarshan in LLO aLOG 28070, which I repeat here for convenience:

Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00      
1501.3       35k                      02:00     
2001.3       35k                      02:00     
2501.3       35k                      05:00      
3001.3       35k                      05:00                   39322.0           Oct 06 2016 18:39:26 UTC
3501.3       35k                      05:00                   39322.0           Jul 06 2016 18:56:13 UTC    Oct 06 2016 18:39:26 UTC      months
4001.3       40k                      10:00
4301.3       40k                      10:00       
4501.3       40k                      10:00
4801.3       40k                      10:00  
5001.3       40k                      10:00

Several things to note: 
- The line frequency was changed in the middle of the lock stretch.
- This lock stretch has been with the PSL power at 58.7W (we hope to run ER10 / O2 at 50 W).
- Alignment of SRC optics is being slowly changed by commissioners
- Robert has also been playing with Intensity Noise coupling, which is currently limiting the sensitivity at these high frequencies, so the SNR of the line may be varying quite wildly.
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 12:59, Thursday 06 October 2016 (30271)
The past and current lock stretches at 60 W were unintentional consequences of a readjustment of the PSL HPO output waveplate without changing the power request back to 50 W (which had been changed to be 60 W yesterday when it was identified that the HPO wasn't putting out enough juice; see LHO aLOG 30239 and LHO aLOG 30260).

We've now, mid-lock readjusted the power back down to 50W, so we expect to return to normal ER10/O2-like operation. So the CAL lines should be measured beyond this point.
H1 SEI (SEI)
jeffrey.bartlett@LIGO.ORG - posted 11:24, Thursday 06 October 2016 (30268)
ISI CPS Noise Spectra Check FAMIS #6866
   Posted are the plots for the BSC and HAM ISI CPS noise spectra. All plots are near or below the reference and there are no particular CPS noted. Closed FAMIS task #6866  
Images attached to this report
H1 TCS (TCS)
vernon.sandberg@LIGO.ORG - posted 08:28, Thursday 06 October 2016 (30264)
TCS Chiller Status and Fill Report

TCS-X: No additional water required, water level 29.0, 3.7 gpm, 20.1 deg. C.

TCS-Y: Found water level at 5.8, added 300 mL water, raised water level to 9.8, 4.0 gpm, 21.0 deg. C.

H1 PSL
peter.king@LIGO.ORG - posted 07:19, Thursday 06 October 2016 - last comment - 09:12, Thursday 06 October 2016(30261)
long range actuator motion
Not that it is a concern but attached is a plot of the Long Range Actuator (LRA) position versus the
laser room temperature.  I only note it because the 32 micron travel is perhaps the longest I've seen
it move, and represents 64% of the available travel before a PZT reset.

    The data dropout corresponds to the DAQ restart at 23:02 UTC yesterday.
Images attached to this report
Comments related to this report
john.worden@LIGO.ORG - 09:12, Thursday 06 October 2016 (30267)

Heat was increased into the LVEA on Wednesday morning - it would be interesting to see the correlation with the increase in the table temperature. 

H1 ISC
jenne.driggers@LIGO.ORG - posted 02:06, Thursday 06 October 2016 (30259)
Another fruitless search for an SRM signal

I tried a few things to look around for a useful signal for SRM ASC at 50W, and had no luck. 

I am pretty convinced that there's no signal that's useful in REFL45 for the SRM.  I couldn't get rid of the ~0.16 Hz oscillation that we see in the PRC1 and PRC2 control signals, which I tried in an effort to see something better in REFL45.  (I tried adding res-gains in both PRC1 Pit and PRC2 pit, to no avail.  Out of loop motion as measured by POPB didn't change.)  I eventually tried "cheating" by lowpassing the REFL45A pitch and yaw I signals (these are not in-loop for anything), but there's really nothing at all there for the SRM.  I also tried moving SR3 (after disabling the cage servo), but that also didn't really have a good signal anywhere but AS36B.  Both SRM and SR3 have an okay signal in AS36B, but I was hoping to find something that wouldn't leave us back in the "sensing matrix of the day" regime. 

Interestingly, the noise at high frequencies seems to get better when POPAIR90 is higher and rattier.  I'm not sure right now why a misaligned SRC would help suppress frequency noise. 

I tried Nutsinee's CSOFT offsets from the other night (alog 30085), and while they do seem to improve the sensitivity in the bottom of the bucket, they noticeably reduce the power recycling gain.  I tried a few other offsets, but I think 0s everywhere for the SOFT loops is about the best in terms of power buildup.  I was running a2l at each offset, and the calibration lines at 330 and 1100 Hz were roughly constant, so I don't think I was fooling myself too much.  So, why do we get better sensitivity in the bucket with lower recycling gain (28 rather than 30)?  I see the buildups go down in the arm transmissions as well as POPDC, so it really is a reduction in the recycling gain. 

Note to self for the morning:  Were good / bad range times really correlated with times when the AS90 dark offsets jumped?  It vaguely seemed that way, but I need to check.  The AS90 signal would occassionally pop up and be visible on the front tv striptool, even though it should be too low for that with the beam diverters closed.  It was sudden jumps, not obviously related to alignment changes, so I think it was dark offset changes.  If that's true, do we need to finally figure out why the electronics at the HAM6 rack are so finicky?  No one was out in the LVEA, so I'm not sure why the offsets were changing.

H1 General (ISC)
travis.sadecki@LIGO.ORG - posted 23:00, Wednesday 05 October 2016 - last comment - 02:09, Thursday 06 October 2016(30248)
OPS Eve Shift Summary

TITLE: 10/05 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Ready to go to Observing when Jenne is done.
INCOMING OPERATOR: Travis
SHIFT SUMMARY: Locking has been going well. Unlocking has also been going well. No issues to report.
LOG:

23:02 DAQ restart

23:14 Nutsinee to LVEA Hartmann work

23:30 Initial alignment

0:02 Nutsinee out

5:50 Nutsinee filling TCSY chiller

6:00 End of shift due to Guardian training early shift start (22:00)

NOTE to Commissioners: In order to get Guardian to let us go to Observing we had to (and will have to fix later):

Comments related to this report
jenne.driggers@LIGO.ORG - 02:09, Thursday 06 October 2016 (30260)

Earlier in the evening, we also changed the ISC_Lock parameters to request 60W from the LASER_PWR guardian, since that's what will give us the max ~48W that we can have for today.  I've also changed the nominal to be this 60W value in the LaserPwr guardian, so that I can hopefully hit the intent bit before I leave.

H1 CDS (CDS, ISC)
jenne.driggers@LIGO.ORG - posted 20:48, Wednesday 05 October 2016 - last comment - 08:44, Thursday 06 October 2016(30258)
DTT not ramping excitations down

DTT is once again not ramping down excitations.  The exciting new "feature" here is that it's not just upon an Abort.  Even when the measurement completes fully, it still just immediately stops the excitation.

This has caused 1 lockloss so far tonight, and 2 scary glitches that could have been locklosses. 

I attach my DTT settings - Noise (Gauss), and I do have a ramp up/down times defined. 

-----

Looking at it again (still running measurements, just hoping for the best when they complete), it looks like it waits and leaves the excitation on for the number of seconds set in the RampDown box, and then cuts it off.  So, the excitation doesn't get suddenly cut off as soon as I click Abort, it gets suddenly cut off 3 seconds after I click Abort.

Images attached to this report
Comments related to this report
james.batch@LIGO.ORG - 08:20, Thursday 06 October 2016 (30263)
Your excitation contains a filter that rings like a bell long after the input has been cut off.  Since the excitation and filter are implemented in the AWG on the front end, there's nothing DTT can really do about this, other than hold the excitation test point open until the program quits.  The ramp down applies to the input to the filter, not the output.
james.batch@LIGO.ORG - 08:44, Thursday 06 October 2016 (30266)
Step response of filter for excitation, 500 seconds.
Images attached to this comment
H1 TCS
nutsinee.kijbunchoo@LIGO.ORG - posted 20:39, Wednesday 05 October 2016 - last comment - 17:01, Thursday 06 October 2016(30257)
SLED swapped back and HWS code resumed
Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 17:01, Thursday 06 October 2016 (30284)

Both HWSX and HWSY centroid refernces re-initialized after IFO unlocked for 2 hours. ITMs, BS, and SR3 are all aligned.

16:49 Re-initialized HWSX centroids ref

16:51 Re-initialized HWSY centroids ref

H1 ISC
keita.kawabe@LIGO.ORG - posted 18:43, Wednesday 05 October 2016 (30256)
DBB QPDs and DARM again, in nominal low noise, with less caveats.

Related: alog 30221

In addition to what Daniel has posted, I measured the coherence and DBB QPDs again, this time in nominal low noise.

Probably due to lower IFO noise, the coherence is larger and broader, extending down to 70Hz or so.

The differences between today and yesterday are:

Images attached to this report
H1 IOO (IOO)
cheryl.vorvick@LIGO.ORG - posted 16:06, Wednesday 05 October 2016 - last comment - 08:35, Thursday 06 October 2016(30246)
IM alignment slider values saved in SDF

I kind of think I saved the new alignment slider values after changing the alignment slider gains on Sept. 30th, but found them at the old values in SDF.  I accepted the new values.  Screenshot attached.

Images attached to this report
Comments related to this report
cheryl.vorvick@LIGO.ORG - 08:35, Thursday 06 October 2016 (30265)IOO

I also asked TJ to put the IM alignment check (IM1, IM2, IM3) back in DIAG_MAIN.  While we moved the IMs it didn't make sense to have DIAG_MAIN show their alignment as an error, but now that we've had this IM alignment for about 10 days, it's stable enough to start tracking it again.

Displaying reports 55221-55240 of 84669.Go to page Start 2758 2759 2760 2761 2762 2763 2764 2765 2766 End