Displaying reports 63741-63760 of 84445.Go to page Start 3184 3185 3186 3187 3188 3189 3190 3191 3192 End
Reports until 00:04, Monday 07 September 2015
H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 00:04, Monday 07 September 2015 (21259)
EVE Shift Summary

(All time in UTC)

23:00 Take over from Ed. IFO has been locking and observing. Dick's inside optics lab.

01:21 Dick out of the lab.

05:00 Dan's on site. Will be here for the rest of the night.

07:00 The ifo has been locking over 26 hours now! Handing off to Travis.

 

- Quiet shift. Wind still below 20 mph. No seismic activity. Saturation alarm hasn't been complaining about anything else other than ETMY, which has been the only source of big glitches on the DMT Omega.

- Camera 3 control was very slow. At one point I thought it was busted. Seems to be working fine again.

H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 20:48, Sunday 06 September 2015 - last comment - 21:52, Sunday 06 September 2015(21257)
Mid EVE shift Summary

The interferometer is still locking and going strong. Wind below 20 mph. Quiet seismic activity. No one on site but me. I'm hoping for another record breaking lock stretch!

LLO has been locking and observing over the past two hours.

Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 21:52, Sunday 06 September 2015 (21258)

The ifo has been locked 24 hours now!

H1 General
edmond.merilh@LIGO.ORG - posted 16:02, Sunday 06 September 2015 (21255)
Shift Summary -Day

Summary:

ACTIVITY LOG:

H1 General
edmond.merilh@LIGO.ORG - posted 08:36, Sunday 06 September 2015 - last comment - 11:08, Sunday 06 September 2015(21252)
Shift Summary -Day (arrival)

Arrival:

Comments related to this report
edmond.merilh@LIGO.ORG - 09:26, Sunday 06 September 2015 (21253)

16:26UTC - Interestingly, the range has trended back up to 71.5Mpc despite no noticeable downward trend in the microseism.

nutsinee.kijbunchoo@LIGO.ORG - 11:08, Sunday 06 September 2015 (21254)
I forgot to turn on the second stage OMC whitening btw.
LHO General
patrick.thomas@LIGO.ORG - posted 08:08, Sunday 06 September 2015 (21251)
Ops Owl End Shift Summary
~13:00 - 13:09 UTC Stepped out of control room.
14:49 UTC dust monitor invalid alarm at end X

Remainder of shift quiet. Range seems to be slightly dropping with slow increase in microseism.

Handing off the Ed.
LHO General
patrick.thomas@LIGO.ORG - posted 04:05, Sunday 06 September 2015 (21249)
Ops Owl Mid Shift Summary
07:12 UTC Handoff from Nutsinee. H1 in observing mode at around 70 Mpc. Kiwamu only other person here.
07:16 UTC Lights are off in the LVEA and PSL enclosure. Lights appear to be off at the mid and end stations.
07:17 UTC Checked IP9. Both A and B pumps HV around 7kV.
07:53 UTC Momentary end X HEPI pump station pressure minor alarm.
08:52 - 08:58 UTC Stepped out of control room.
09:06 UTC Kiwamu leaving site. I'm alone.
10:50 - 10:57 UTC Stepped out of control room.

No lock losses or changes in observing mode. SUS ETMY saturations at 08:44:54 and 11:00:19 UTC.
H1 CAL
kiwamu.izumi@LIGO.ORG - posted 01:43, Sunday 06 September 2015 - last comment - 20:05, Monday 07 September 2015(21250)
some updated on analysis codes for suspension calibration

I worked a bit more on the analysis codes that Jeff has written (alog 21015 and alog 21049). I was not able to finish deriving the suspension scale factors. Tomorrow, Jeff and Darkhan will pick up them at the point where I left and will continue working on it.

Major updates:

Next steps:

 

Some notes:

In the course of the code update, I changed the file organization structure of the ALS diff and Pcal scripts so that they have only one analysis code which can be invoked by specifying a set of data parameters. This organization approach is the same as those for the DARM open loop analysis.

As for ALS diff, the core analysis code is

aligocalibration/trunk/Runs/ER8/H1/Scripts/ALSDiff/Matlab/analyze_alsdiff.m

and the parameter files are in the same directory and named as

H1ALSDIFFparams_20150826.m

H1ALSDIFFparams_20150828.m

H1ALSDIFFparams_20150829.m

As for Pcal, the core analysis code is

aligocalibration/trunk/Runs/ER8/H1/Scripts/PCAL/analyze_pcal.m

and the parameter files are in the same directory and named as

H1PCALparams_20150826.m

H1PCALparams_20150828.m

H1PCALparams_20150829.m

Each parameter file loads H1DARMOLGTFmodel_ER8 with the latest electronics information and subsequently returns the parameter structure, or the familiar variable "par". As usual the parameter structure can be then fed to the analysis code (e.g. analyze_alsdiff.m or analyze_pcal.m) as an input argument. I have not carefully thought about the final return variables from the core analysis codes, but in principle we can write them such that they return the calibrated suspension transfer functions in meters/counts together with some error bars and also perhaps some statistical values. In this way, the final step of performing apple-to-apple comparison between various measurements from various dates can be less painful.

I tried propagating the same file organization structure to the free-swinging Michelson codes, but apparently I am running out my energy for the night and did not finish it yet.

Comments related to this report
kiwamu.izumi@LIGO.ORG - 17:35, Monday 07 September 2015 (21274)

Today, I worked on the analysis code for the free-swinging Michelson which was something I was not able to finish the other day. They are now organized and analyzed in the same fashion as the rest analysis codes (i.e. DARMOLGTFs, ALS diff and Pcal).

The core analysis code can be found at:

/aligocalibration/trunk/Runs/ER8/H1/Scripts/FreeSwingMich/analyze_mich_freeswinging.m

In the same way as the ALS diff and Pcal analysis codes, the analysis code can be fed with a parameter sturcture or "par". The parameter structure can be loaded by running a paramter script which is separated by the measurement date:

/aligocalibration/trunk/Runs/ER8/H1/Scripts/FreeSwingMich/H1FSMparams_20150826.m

/aligocalibration/trunk/Runs/ER8/H1/Scripts/FreeSwingMich/H1FSMparams_20150828.m

/aligocalibration/trunk/Runs/ER8/H1/Scripts/FreeSwingMich/H1FSMparams_20150829.m

darkhan.tuyenbayev@LIGO.ORG - 20:05, Monday 07 September 2015 (21279)CAL

H1 SUS ETMY PUM driver analysis has been alogged in LHO alog 21232.

H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 00:00, Sunday 06 September 2015 (21242)
Ops EVE Summary

(All time in UTC)

23:00 The interferometer is down. Take over from Ed.

23:51 Dick to optics lab

23:56 IMC had trouble locking. MC2 pitch seems to have moved the most from the time the ifo was still locking so I touched it and managed to get IMC locking again. Ed had to touch ITMY to get the green to lock, fearing that this might give me trouble during DRMI afterward I reverted his changes and tried adjusting ETMY and gave TMSY a small touch.

00:36 Wind reached 40 mph. I adjusted PR3 to maximize COMM beatnote. Can't really do much at this point. Waiting until the wind calm down.

01:20 Dick to LVEA.

01:38 Dick back

01:51 Robert to LVEA

01:55 Robert back

02:11 After trouble locking DRMI AND PRMI, I decided to do initial alignment. I didn't see that Patrick already did this last night.

03:24 After the inital alignment locking DRMI still seems hopeless. Locking PRMI.

03:48 PRMI also have difficulty locking. I adjusted BS, PRM, PR2. Adjusting PR2 seems to be the most effective. Maybe adjusting BS and PRM wasn't necessary...

04:20 PRMI is good but I still can't get the DRMI to lock.  I've been adjusting SRM pitch and yaw but no luck. Not sure what on earth is going on. POP18 and POP90 is flashing high so I know the PRMI is good.

04:25 I noticed that SR3_CAGE_SERVO wasn't engaged. I think it HASN'T been engaged this whole time that I was having problem with DRMI. It saw SR3 misaligned at some point and never turned itself back on. SR3_CAGE_SERVO supposed to correct SR3 misalignment due to interferometer heating/cooling. Otherwise locking DRMI will be a problem. So, note to self, MAKE SURE THE CAGE_SERVO IS ON!!!

04:29 ISC_DRMI Connection Error. I called Jenne and it was an easy fix. Just request STOP, and EXEC again at ISC_DRMI. DRMI is now locking again (thank goodness).

04:47 Locked at NOMINAL_LOW_NOISE. Back to Observing. 71 Mpc (hooray!).

05:00 Kiwamu arrived doing calibration work.

07:00 Wind below 20 mph. The saturation alarm hasn't been complaining much. Handing off to Patrick.

 

Note:

- I checked and the SR3_CAGE_SERVO wasn't turned off until I started the initial alignment. Whatever was giving me hell with DRMI and PRMI earlier wasn't the cage servo. But to be fair I didn't touch any optics in trying to fix PRMI before I went and did the initial alignment (PRMI never had trouble locking itself in my experience!). I guess I should have...

- I have been getting calls from an unknown number all day and nobody talks when I answered. The last call was just a few minutes ago. It's really annoying....

H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 21:48, Saturday 05 September 2015 (21247)
Back to Observing

04:47 UTC at 71 Mpc.

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 19:54, Saturday 05 September 2015 (21244)
CDS model and DAQ restart report, Friday 4th September 2015

ER8 Day 19, no restarts reported

H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 17:50, Saturday 05 September 2015 - last comment - 21:29, Saturday 05 September 2015(21243)
Windy!

After I got the IMC back up (it had trouble locking itself so I touched MC2 pitch a little), the wind picked up speed. It has just reached 40 mph and the forecast says it should come down in 3 hours or so. I'm waiting for the wind to calm down before moving on. Hopefully I don't have to wait 3 hours...

Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 21:23, Saturday 05 September 2015 (21245)

Difficulty with DRMI

2:11 UTC After almost an hour not able to lock DRMI and PRMI, I decided to do the initial alignment (this was before I saw Patrick alog that he already did one last night). After the initial alignment the PRMI still wasn't able to lock itself. I had to touch BS, PRM, and PR2.

4:20 PRMI is good but I still can't get the DRMI to lock.  I've been adjusting SRM pitch and yaw but no luck. Not sure what on earth is going on. POP18 and POP90 was flashing high so I know the PRMI was good.

nutsinee.kijbunchoo@LIGO.ORG - 21:29, Saturday 05 September 2015 (21246)

ISC_DRMI CONNECTION ERROR

I called Jenne and was able to cleared the error easily. I just noticed that SR3_CAGE_SERVO wasn't engaged. Turned it on and DRMI is locked again.

Images attached to this comment
H1 ISC (ISC, SUS)
sheila.dwyer@LIGO.ORG - posted 16:52, Saturday 05 September 2015 - last comment - 20:07, Tuesday 08 September 2015(21240)
ETMY drive upconservsion

Kiwamu, Sheila, Evan

Durring the calibration activities last week Kiwamu noticed that there was upconversion of the drive from ETMY.  Specifically when he drove in the L3 LOCK filter, he saw a second harmonic. When he drove each stage individually, through the test filter bank with a similar amplitide he saw no evidence for upconversion.  This suggests that the upconversion might come about by driving mutliple stages, or through the length 2 angle paths. 

We went back through the data and looked at the relative heights of the peaks.  We also calculated a ratio of the amplitude of the second harmonic to the square of the amplitude at the fundamental :
  ASD(2f) = alpha * (ASD(1f))^2

drive Frequency (Hz_ amplitude at drive frequency (m/rt Hz) amplitude at second harmonic (m/rt Hz) alpha (1/m)
4.98 5.8e-14 2e-15 5.9e11
5.9 5.6e-14 9.8e-16 3.1e11
6.4 3e-14 2.8e-16 3.1e11
10 3.6e-15 2.8e-18 2.2e11

If we ignore other frequencies which could mix and only consider the second harmonics of DARM control, we would expect this upconversion to be something like a factor of 10 below our measured noise at 20 Hz, and near the measured noise at 10 Hz.

The next step is probably to identify which stages contribute to this upconversion, for example it seems probable that this is only noticeable for frequencies where L2 get a significant fraction of the DARM control signal. 

Comments related to this report
sheila.dwyer@LIGO.ORG - 20:07, Tuesday 08 September 2015 (21316)

We made some injections into ETMY to check when exactly this upconversion shows up.  It is much smaller today than it was durring Kiwmau's measurement.  

An injectionat 5 Hz  (500 counts in ISCINF) that increased the DARM noise there by a factor of 67 produced a peak at 10 Hz that is a factor of 2.6 above the noise floor.  We also injected in L2 L2L (which will bypass the L2P and L2Y filters) to produce a simlar peak, and got a similarly low level of noise at 10 Hz.  

It may be that part of the problem durring Kiwamu's measurement was that some ASC loops were accidentaly off. 

Images attached to this comment
H1 General
edmond.merilh@LIGO.ORG - posted 16:21, Saturday 05 September 2015 - last comment - 16:56, Saturday 05 September 2015(21239)
End of Shift Summary and Lock Log - Day

Summary:

 

ACTIVITY LOG:

 

LOCK LOG:

Comments related to this report
sheila.dwyer@LIGO.ORG - 16:56, Saturday 05 September 2015 (21241)

The guardian checks for locklosses of the mode cleaner and DRMI, and it is just a roll of the dice which it will noticed first.  In the early stages of lock acquisition it makes sense to proceed to LOCK_DRMI if only DRMI has lost lock, that saves us from unecesarily relocking ALS.  In full lock I agree tihs doesn't really make sense, but if the guardian goes to LOCK_DRMI after a lockloss it will imediately proceed to lockloss as you saw.

H1 PEM (DetChar)
robert.schofield@LIGO.ORG - posted 19:36, Friday 04 September 2015 - last comment - 18:00, Sunday 06 September 2015(21226)
More injections to test coupling of site activities

 

Injection

Time of first injection,

UTC

Injection spacing

Total number of injections

Good channels for environmental signal

 

Sept. 5

 

 

 

crowd (10 people) walking randomly for 2 or 3s periods in control room

1:39:00

5s

12

HAM2 seismometer, vertex seismometer

H1:PEM-CS_ACC_LVEAFLOOR_HAM1_Z

 

crowd (10 people) walking randomly in hall just outside control room

1:41:00

5s

12

same

External door near control room shutting by itself

1:44:00

5s

12

same

chair rolling in control room (most common chair)

1:46:00

5s

12

same

Single large steps in control room

1:50:00

5s

12

same

Airlock door (door to lab area near control room) shut by hand

1:52:00

5s

12

same

slamming office door (Sheila, Kiwamu, Me)

1:54:00

5s

12

same

hammer dropped from waist height in vacuum lab

1:59:00

5s

12

same

setting car battery down in OSB shipping area

2:02:00

5s

12

same

continuous bouncing for 5s on exercise/seating ball

2:07:00

10s

6

same

Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 18:00, Sunday 06 September 2015 (21256)DetChar, SEI, SUS

I've attached the result. Quick observation from the spectrograms tell me that dropping hammer from waist height in vacuum lab (aka Kyle's lab) and setting car battery down in OSB shipping area coupled into DARM.

Instead of plotting the spectogram starting at the time of injection, this time I did +/- 10 seconds instead so it's more clear when the injection started and when it's ended.

 

Since I have never really explained what I did in finding noises in the sensors and in DARM, I'm taking some time to explain it in this alog. First I looked for injections in appropreiate sensors (accelerometer, microphone, seismometer). I zoomed in the spectrograms until I get the signal to show up >3 pixels or so in both frequency and time domain (as Robert suggested). Once I was certain that the injections were there, I went to look for them in DARM. I started with the same frequency range that the injections showed up in the sensors I used, if I couldn't find anything then I move up/down in frequency domain to look for any possible up/down conversions with increments depending on how wide the injections were in terms of frequency. Until I reached the lowest/highest frequency that the injections could possibly showed up, if I still didn't see anything only then I would conclude that the injections didn't show up in DARM.

 

More investigations on how some of these injections coupled into DARM will take days, weeks, I don't know. The point of these injections was to determine what activities can and cannot be performed during Observing run. This is why I posted spectrograms first and not wait until I'm done with the analyses. I simply let DARM spectrogram speaks for itself.

 

I have also attached better spectrograms of the super ball injection, produced using Dan's script.

Images attached to this comment
Non-image files attached to this comment
H1 ISC
evan.hall@LIGO.ORG - posted 22:55, Monday 24 August 2015 - last comment - 17:51, Sunday 06 September 2015(20347)
Circulating arm power from tidal offloading

Stefan, Evan

This is an analysis that Daniel suggested a while ago.

When we increase the interferometer power from 3 W to 24 W, we increase the common-mode radiation force on the test masses. Since the suspensions are compliant, this produces an extra displacement in the test masses along the beamline relative to their suspension points. The CARM loop senses this common-mode displacement and compensates by applying a slow control voltage to the IMC VCO. This control voltage is offloaded to the UIMs of the end station suspensions, and then subsequently to the endstation HEPIs, thereby moving the suspension points of the ETMs forward so as to cancel the radiation-induced displacement. Therefore, an appropriately calibrated HEPI tidal signal can be used to estimate the amount of power circulating in the arms.

We looked at a data stretch from 2015-08-07, when we had been sitting at 3 W for a while and then powered up cleanly to 24 W, and found the following:

On the other hand, when we make a similar estimate from the end-station QPDs, we have something like 24 W × 0.88 × 1/2 × 40 W/W × 283 W/W = 120 kW. [The factor of 0.88 is the modecleaner transmission.]

The calibration of the HEPI tidal signals into nanometers is sort of loose [to within 10%?], according to Hugh. Similarly, there is some spread in the power inferred from the endstation QPDs, which gives an uncertainty that is also on the order of 10%. With a more precise HEPI calibration, perhaps we could use this method to better constrain the optical calibration.

Images attached to this report
Non-image files attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 17:51, Sunday 06 September 2015 (21248)

Hugh, Richard, and I had a discussion about the precision of the HEPI calibration, and in the end Richard suggested to just measure the calibration in some locked interferometer configuration (whereby we could read out some calibrated control signal).

I had a go at this by locking ALS DIFF (with IMC F offloading off) and driving HEPI at 200 mHz, with the goal of calibrating HEPI against the PLL. I got an OK measurement by driving 100 nm pk for 8 minutes or so, but then Jim and Hugh pointed out that the ISI was already suppressing some of the HEPI drive, so the measurement probably had significant systematic error. Additionally, Daniel was skeptical that one could cleanly separate length and angle changes on the test mass (both of which can contribute to the sensed CARM displacement).

Jim, Dan, and I thought a bit about this, and (to make a long story short) we forwent HEPI calibration entirely. Instead, we decided to lock the interferometer at 2.2 W, turn off the offloading of the UIMs to the HEPIs, and then power up. The dc portion of the CARM control signal should then accumulate on the UIMs. Since the calibration group already produces estimates of the dc UIM calibration for EY (the ER7 estimate was 5.1×10−11 m/ct), we therefore already have a calibrated readout of the displacement induced by the circulating power (again neglecting angle effects). I don't think the calibration group produces similar estimates for the EX UIM.

This power-up happened around 2015-09-03 09:56:30, from 2.2 W to 22.4 W. I did a linear fit of the UIM drive before and after the power up (see attached). The initial/final slopes are 5.32 nm/s and 5.06 nm/s, so there is some error here in determining the amount of radiation-induced drive (about 10 %). Using the ER7 EY UIM calibration, the amount of radiation-induced UIM displacement is 2.95(30) µm. Using the formulas described above, this translates to a circulating power in the Y arm of 95(10) kW.

Non-image files attached to this comment
Displaying reports 63741-63760 of 84445.Go to page Start 3184 3185 3186 3187 3188 3189 3190 3191 3192 End