Displaying reports 56041-56060 of 81604.Go to page Start 2799 2800 2801 2802 2803 2804 2805 2806 2807 End
Reports until 12:44, Saturday 26 March 2016
X1 DTS
david.barker@LIGO.ORG - posted 12:44, Saturday 26 March 2016 (26269)
new 3.0.8 kernel boot server installed

We installed the boot disk Keith provided into a new boot server called x1boot1. Thats to Keith's extensive prep work, the install was very quick. We moved the fast front end computer x1susey from the 2.6 boot server over to the new 3.0.8 server. Next tasks are to rebuild the models on this machine.

x1susey ~ # uname -a

Linux x1susey 3.0.8 #3 SMP Wed Mar 9 16:13:18 CST 2016 x86_64 Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz GenuineIntel GNU/Linux

H1 ISC
sheila.dwyer@LIGO.ORG - posted 00:54, Saturday 26 March 2016 - last comment - 14:53, Wednesday 30 March 2016(26267)
ASC phasing script, not stable above 10 Watts yet

We did a little bit of ASC work today.  

First, while Kiwamu was running a TCS test I started a script to automate phasing of the WFS.  It uses the lockin, first runs a servo to set the phase of the lockin demod, then servos to minimize some signal.  We have it set up right now to phase the refl WFS to minimize the PR2 pit signal in Q for both REFL 9 and 45, and to minimize the SRM pit signal in AS 36 Q.  There is some code for exciting DHARD, but we need to test amplitudes, phases and gains for this.  The current version of the script does its job although it is painfully slow, and is checked into the svn under asc/h1/scripts  THe resulting phases are in the attached screenshot. 

We saw that the instability in CHARD pit was becasue somehow the LP9 got turned on again, this is now off and CHARD seems fine.  

We tried powering up, were fine at 10 Watts.  We had an instability in PRC1 and PRC2 yaw at 13 Watts.  I reduced the Q on the complex zeros at 1.1 Hz for PRC2Y, which gives us slightly better phase and gain near the point where we seem to be unstable. Attached is a screenshot of the OLG measured with white noise at both 2 Watts and 10Watts, we might need to do a swept sign to get a good measurement around 1 Hz. 

After about 10 minutes at 12 Watts, we had the usual fluctuations in the recycling gain.  So the high bandwidth PRC2 loops haven't totally solved the problem. 

For the record, these are angle settings that give approximately good CO2 powers tonight, and the powers to aim for from Kiwamu's note:

  X power (W) X angle Y Y angle
unlocked 0.5 76 0.23 82
10W   78   79
20W 0.3   0.1  

We have twice had the rotation stage for CO2 Y go to an angle that was wrong by a lot (sending a few watts to the test mass for a few seconds).

I'm leaving the IFO locked at 10Watts. 

Images attached to this report
Comments related to this report
john.worden@LIGO.ORG - 09:14, Saturday 26 March 2016 (26268)

Sheila,

Do you know how much power was transmitted at CO2 Y to any precision? Can you say what the upper limit was?

 

thanks

sheila.dwyer@LIGO.ORG - 16:14, Monday 28 March 2016 (26294)

The first time  H1:TCS-ITMY_CO2_LSRPWR_MTR_OUTPUT read back 3.2 Watts for about 20 seconds.  

THe second time H1:TCS-ITMY_CO2_LSRPWR_MTR_OUTPUT  read 3 Watts for about 10 seconds. 

sheila.dwyer@LIGO.ORG - 16:34, Monday 28 March 2016 (26295)

This morning I looked at some of the data from friday night when we had our usual CSOFT instability.  (16-03-26 7:52:56 UTC)

First, I used the moment of interia here, and the calibration of the arm circulating power from the transmon QPDs here, to estimate i it is reasonable that radiation pressure due to the fluctuations in arm circulating power (on the order of 2.5% fluctuations on 35 kWatts of circulating power) could cause the angular motion that we see (0.1-0.4 urad pp on the test masses), and it is not, the miscentering that would be required is far too large.  

sheila.dwyer@LIGO.ORG - 14:53, Wednesday 30 March 2016 (26343)

I never attached the sreenshot of the PRC2 Y OLG to the original alog.  Here it is. 

Images attached to this comment
H1 General
edmond.merilh@LIGO.ORG - posted 21:12, Friday 25 March 2016 (26266)
Shift Summary _Evening

TITLE: 03/26 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC

STATE of H1: Planned Engineering

INCOMING OPERATOR: None

SHIFT SUMMARY:' Large tour group in the control room. Got a chance to really talk at length with some guests about my job and a little bit about various subsystems with a camera guided tour around the LVEA. Completed the last ofthe Sat Amp modifications. Did a little bit of re-locking for Sheila. She's going to be working on DRMI/TCS relationships for the remainder of the night.

LOG:

23:21 Chandra back from CP3 refill

00:15 Terra and Nutsinee to EY to do some signal injections

 

0:46 Terra and Nutsinee back

H1 SEI (CDS, SEI)
krishna.venkateswara@LIGO.ORG - posted 20:43, Friday 25 March 2016 (26265)
BRS-2 Installation DAY 2: Code works, angle data in beckhoff computer and BRS-1 restarted

Michael, Krishna

This morning, we repositioned the EX_BRS-1 damper turn-table and restarted EX_BRS-1 software. The system worked normally and started to damp the balance but was unable to damp it all the way to small amplitudes (< ~50 counts/nrad). The reason seemed to be that the turn-table vibrations were driving up the beam-balance (see here). Looks like the foam sheets under the turn-table aren't effective at vibration damping any more. Later, Hugh handed us some soft polymer damping pads which we'll try out tomorrow. In the meantime, I've disabled the damper but the tilt data is available.

At EY, Carlos helped us to get the autocollimator software (in C#) working on the BRS-2 Beckhoff computer. We then proceeded with the vacuum can assembly and then aligned the autocollimator and adjusted the beam-balance position to get clear images on the CCD. By the end of the day, the angle data of the beam-balance was visible on the Beckhoff computer.

Plan for tomorrow:

1. Try out other vibration damping pads under the BRS-1 turn-table. Also try out some BRS-1 code changes to improve the software live-time, which crashes once in ~two weeks.

2. Continue BRS-2 vacuum can assembly. If possible, start pumping the vacuum can.

3. Hook up the SEI-Interfacing beckhoff modules.

H1 ISC (TCS)
kiwamu.izumi@LIGO.ORG - posted 17:29, Friday 25 March 2016 - last comment - 21:02, Friday 19 August 2016(26264)
Another CO2 differential lensing test

This is a quick summary of today's TCS joy. I ran another differential lensing test today. I went to the other side of the differential lensing (CO2X goes higher power).

The highest cavity pole was 352 Hz in this test.

This time, I also took many measurements of the intensity and frequency noise couplings periodically throughout the test using Evan's automated measurement script (20470). I will analyze and post them later. The second attachment is trend of some relevant channels.

Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 14:07, Wednesday 30 March 2016 (26340)

This is a report on the intensity noise coupling measurement to DARM during the same TCS testing period.

The below is an animated plot showing how the intensity noise coupling evolved as a function of time during the test. The transfer function was measured from ISS-SECONDLOOP_SUM14_REL to CAL-DELTAL_EXTERNAL. DELTAL_EXTERNAL is unwhitened.

 

As shown in the above animated plot, the intensity noise increased at the beginning and then went back down to where it was. The overall spectral shape almost did not change, but the scaling factor has changed roughly by a factor of two comparing the minimum and maximum. The magnitude of the coupling rises in proportion to frequency -- if I plotted them for a coupling to DCPDs, they would be almost flat due to the cavity pole correction taken out.

Here is another plot showing the evolution of coupling as a function of time.

The upper plot shows the transfer coefficient at 2500 Hz (in arbitrary unit) as a function of time. The bottom plot shows the CO2 lensing from the same period. The transfer coefficient shows a clear correlation with the defocus of ITMs. I can not say for sure if the differential was a dominant cause of this effect because I had a few uD defocus as well in the same fashion.

Images attached to this comment
kiwamu.izumi@LIGO.ORG - 15:02, Wednesday 30 March 2016 (26342)

Here is the same analysis for the frequency noise coupling to DARM. The variation in the coupling is more drastic than that of intensity noise.

The below is a same type of animated plot. The transfer function was measured from REFLA_RF9_I_ERR to CAL-DELTAL_EXTERNAL. Note that DELTAL_EXTERNAL is properly unwhitend.

It seems that the coupling has two different mechanisms, one for the coupling below 300 Hz and the other for the above. As the CO2 setting changed, the high frequency part increased at the beginning and decreased later while keeping the same spectral shape. On the other hand the low frequency part varied in an opposite fashion; it decreased as the high frequency part increased. The slope of the high frequency coupling seems to be almost proportional to f. If we convert it into [OMC DCPDs [A] / laser frequency [Hz]], it will be more like 1/f due to the cavity pole and REFL's transfer functinon against the laser frequency.

Here is another plot showing the evolution of the transfer coefficient at 2500 Hz. The coupling coefficient changed by a factor of 15 at this frequency. This is much more drastic than that of the intensity noise coupling which varied by a factor of two or so.

 

A preliminary conclusion:

With the 2 W PSL, the DARM cavity pole prefers a high CO2 differential lensing while the laser noise couplings prefer a low differential lensing.

Images attached to this comment
kiwamu.izumi@LIGO.ORG - 15:09, Thursday 23 June 2016 (27899)

This is a belated analysis on the intensity noise coupling. The punch lines are:

  • The intensity noise coupling did not seem to have hit an optimum point where the coupling is minimized.
  • The magnitude of the coupling at high frequency is too high by a factor of 10 compared to a simple model.

[Noise coupling v.s. differential lensing]

As seen in the plot above, the coupling coefficient shows a linear relation to the differentianl lensing. This likely indicates that the differential lensing is not optimized to minimize the intensity noise coupling. I should note that this measurement had used the badly clipped COY beam (27433) which was later fixed in May 2016; a smaller differential lensing means less power in CO2Y than CO2X.

[Intensity noise coupling]

Here is a plot showing the intensity noise coupling of the various TCS settings. This time the coupling coefficient is converted to OMC power [W] / input RIN. The dashed line in the magnitude represents the expected value calculated by

 (coupling) = 2 * J1^2 * Pin * Tomc * Tifo [W/RIN] = 5.5e-6 [W/RIN],

where Pin = 2 W is the PSL input power, Tomc = 61.4 ppm is the OMC transmission for the 45 MHz RF sidebands, and Tifo is the transmission of the intereferometer for the 45 MHz RF sidebands which I have assumed to be 1 for quick calculation. As seen in the plot, the expected noise level (limited by the 45 MHz RF sidebands) is lower then the measurement by roughly a factor of 10. These two plots support the hypothesis that we are far from the optimum point.

Images attached to this comment
evan.hall@LIGO.ORG - 21:02, Friday 19 August 2016 (29214)

Here are the beamsplitter angles as a function of differential lensing. (There are some data dropouts in the trends).

This seems to indicate that a differential lens change of a few tens of microdiopters causes the beamsplitter yaw to change by a few hundreds of nanoradians, presumably via changes in the 36 MHz angular plant. In pitch it is less clear whether we are seeing angular control effects or simply drift over time.

Images attached to this comment
H1 ISC (ISC)
keita.kawabe@LIGO.ORG - posted 17:06, Friday 25 March 2016 (26263)
Fast shutter is still working

In today's HAM6 vent meeting people asked if the shutter was working at all. It still works.

The first attachment shows that the shutter closed (green trace) last night when the IFO lost lock. Brown is the tirigger voltage, and the trigger threshold is 2V.

Red is the OMC DCPD, blue is the DC of ASAIR_A, vertical lines indicate where the shutter triggered.

Due to some strange timing problem of Ethercat signals transported to EPICS that was reported in alog 17445, you cannot compare the timing of the green and the brown trace with red and blue, so the trigger timing on this plot is just a guesstimate obtained as follows:

  1. Trigger voltage (brown) is produced in ASC AS_C interface box by adding all four segments in analog, and the analog output is directly plugged into the shutter box. This voltage is just AS power, so is supposed to be proportional to ASAIR_A_LF (blue).
  2. Before the IFO lost lock, trigger voltage was 0.12Volts, ASAIR_A_LF was about 1200 counts, so the equivalent trigger threshold for ASAIR_A_LF would be 20000 counts where the shutter should have triggered.

The second plot shows that the shutter has been firing all the time for recent 100 days.

One thing that is strange is that the LSC-ASAIR_C_LF_OUT_DQ is recorded on the frame at 16kHz but the input is grounded in the frontend. If my memory is correct Dan Hoak wanted to record the trigger voltage at 16kHz, and my guess is that ASAIR_C_LF was supposed to be used for this because it's not used, but nobody implemented it.

Images attached to this report
LHO General
patrick.thomas@LIGO.ORG - posted 16:52, Friday 25 March 2016 (26262)
Ops Day Shift Summary
15:03 UTC Krishna and Michael to end X to look at BRS
15:04 UTC Jeff B. to LVEA near HAM6 to make clearance measurements for upcoming vent
15:23 UTC Neither DRMI or PRMI locking. Starting initial alignment.
15:26 UTC Filiberto and Manny to end Y to pull cables for BRS and BPG402 vacuum gauges
16:10 UTC Initial alignment done
16:15 UTC Sheila testing script
16:23 UTC Sheila done. Starting locking.
16:29 UTC Krishna and Michael done at end X. Krishna, Michael and Carlos to end Y.
16:44 UTC Jeff B. to LVEA to change dust monitor settings
Fire department here and gone
17:50 UTC Filiberto, Manny and Leslie back from end Y. Filiberto to mid Y to retrieve something for Dick.
18:05 UTC TJ adding bounce/roll guardian node
18:05 UTC Chandra and possibly Carlos to LVEA. Chandra to read vacuum pressures and disconnect pump cart.
18:32 UTC Filiberto back from mid Y
19:04 UTC Brynley looking for equipment in LVEA
19:25 UTC Brynley back
19:25 UTC Kiwamu running measurement
19:37 UTC Chandra done
20:33 UTC Carlos to end Y to setup remote desktop on BRS computer
21:04 UTC Terra and Brynley back from looking at end station electronics racks
22:21 UTC Chandra walking to CP3 to do overfill
H1 General
edmond.merilh@LIGO.ORG - posted 16:15, Friday 25 March 2016 (26258)
Shift Summary - Evening Transition
TITLE: 03/25 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    Wind: 11mph Gusts, 5mph 5min avg
    Primary useism: 0.63 μm/s
    Secondary useism: 0.41 μm/s 
QUICK SUMMARY:

LHO VE
chandra.romel@LIGO.ORG - posted 16:06, Friday 25 March 2016 (26257)
CP3 overfill
1530 - 1600 hrs. local -> To and from Y-mid 

Exhaust check valve bypass opened, LN2 at exhaust after 2:16 mins with LLCV bypass open 1/2 turn 

Next CP3 over-fill to be Sun. before 4:00 pm hrs. local 
LHO VE
chandra.romel@LIGO.ORG - posted 12:47, Friday 25 March 2016 (26253)
Aux pump cart disconnected from XBM
I disconnected G32964 sm pump cart from the X-beam manifold and capped the 2nd valve with a blank 2-3/4" CFF and Cu gasket (small IP is still connected). The cart remains in that location, but free to use elsewhere. Note, there are no pressure gauges on it.
LHO VE
chandra.romel@LIGO.ORG - posted 11:54, Friday 25 March 2016 (26252)
Diagonal annuli pressures
Pressures falling:

HAM 7/8:   8e-6 Torr (yesterday=2e-5 Torr)
HAM 9:      6e-6 Torr (yesterday=3e-5 Torr)
HAM 11/12:  5e-6 Torr (yesterday=4e-5 Torr)

Continue to monitor pressures to detect any potential outer oring leaks.
H1 ISC (ISC)
jenne.driggers@LIGO.ORG - posted 11:40, Friday 25 March 2016 (26250)
Current DHARD loop shape

In preparation for designing ASC filters for increasing the laser power, I've looked at what we're actually using right now.  The filters that we are turning on during the "noise tunings" state is giving us 15dB of gain peaking in the pitch loop around 10 Hz.  Since the DHARD Yaw loop isn't so carefully tuned, it has much more phase margin, and so doesn't have egregious gain peaking.

I just noticed the noise tunings filter and its effect for the DHARD loops today. I didn't measure high enough frequencies to see the problem when I was measuring loops back in alog 25368.

Right now, I'm working on designing filters for DHARD Pit for power-up (almost done), designing filters for DHARD Yaw so that we have only a single UGF even at current powers (just starting), and doing similar work for the CHARD loops (not started).

Non-image files attached to this report
H1 SEI (CDS, ISC, SUS)
brian.lantz@LIGO.ORG - posted 10:04, Friday 25 March 2016 - last comment - 13:08, Friday 25 March 2016(26249)
suggested flow for the SUSpoint signals
We're working to get the calculations for the SUSpoint motion in the IFO basis installed
see ECR E1600028 ,
FRS issue 4694 : https://services.ligo-la.caltech.edu/FRS/show_bug.cgi?id=4694
and totally-out-of-date Tech doc T1500610 

here is an updated white-board drawing showing what we want to do.
It is weird because:
1) ISI models are not attached to the RFM network, so we need to pipe the data to another model first and PEM has lots of extra time
2) We really want 2 channels, but both are pretty slow, so Joe B made us a multiplexer to save RFM data.


-- email chain here so I don't lose it --


From: Jeff Kissel 
Subject: Re: SEI RFM channels from end to corner.
Date: March 24, 2016 at 4:34:30 PM PDT
To: David Barker 
Cc: Joseph Betzwieser , jim warner , Dave Barker , "Vern Sandberg" , Keith Thorne , Hugh Radkins , Joe Betzweiser , Rolf Bork , Brian Lantz 

Hey Dave,
	Yup, next Tuesday for removal.

Cheers,
Jeff Kissel


On Mar 24, 2016, at 3:42 PM, David Barker  wrote:

Hi Jeff,

yep, I’ll confirm with Daniel if we can get rid of the sender-with-no-receiver RFM channels.

Are we planning on giving this a try next Tuesday, and if so on one or both arms?

cheers,

Dave



On Mar 24, 2016, at 15:34, Jeff Kissel  wrote:

Hey Joe,
	Thanks for putting this together. 

Hey Brian,
 	Are we definitely going this MUX route to save on transmission channels?

Hey Dave,
	Side statement: we should also clean up all of the RFM channels you’ve identified as unused here

in the end station ALS, ISC, and corner station OAF models too.

Cheers,
Jeff Kissel
Controls Engineer


On Mar 24, 2016, at 2:06 PM, Joseph Betzwieser  wrote:

Hi,

Just want to provide an update on the MUX code.  In the prior e-mail I had indicated I had not done full testing of all functions.  I have now done so on the LLO test stand, and after some minor copy/paste bug fixes in the 4 and 8 channel versions, all currently coded functions are working as expected.

This includes functions for combing 2, 4, and 8 channels together and then demuxing them at the end, assuming the same data rate throughout.  In addition, there is a demux function for a 2 channel input which can handle a 4x data rate change from slower to faster (i.e. 4 kHz to 16 kHz).

If/When needs change, its fairly simple to copy the current functions and change them to different data rates or number of channels.
Again, links to code are at:

https://redoubt.ligo-wa.caltech.edu/websvn/filedetails.php?repname=cds_user_apps&path=%2Ftrunk%2Fcds%2Fcommon%2Fsrc%2FLOW_FREQ_MUX.c

https://redoubt.ligo-wa.caltech.edu/websvn/filedetails.php?repname=cds_user_apps&path=%2Ftrunk%2Fcds%2Fcommon%2Fsrc%2FLOW_FREQ_DEMUX.c

I am to use these in the code we are planning to push next Tuesday for the ISI RFM communication to the corner.

Cheers,
Joe


On Wed, Mar 23, 2016 at 1:03 PM, Joseph Betzwieser  wrote:
I forgot to attach the pdf.

Here it is.

Joe

On Wed, Mar 23, 2016 at 12:22 PM, Joseph Betzwieser  wrote:
Hi,

Based on the discussions I had with Brian Lantz, I've put together a very simple diagram this morning describing what I think is what we should do for the RFM communication.  I don't remember the exact channel names (and there may have only been 1 channel going from the corner to the end), but I think the attached pdf is generally correct.  At the vary least its a discussion starting point.

I'm working under the assumption that the IPC problems are on the reading end (i.e. each RFM read takes 1-2 microseconds), so that sending is not an issue.  Given Brian Lantz wants to read out channels into OAF, that read in can't be avoided, although we can condense it down to 1 channel per end via Muxing.

I've written a number of user C functions in /opt/rtcds/userapps/release/cds/common/src/LOW_FREQ_MUX.c and LOW_FREQ_DEMUX.c

Links to code are:

https://redoubt.ligo-wa.caltech.edu/websvn/filedetails.php?repname=cds_user_apps&path=%2Ftrunk%2Fcds%2Fcommon%2Fsrc%2FLOW_FREQ_MUX.c

https://redoubt.ligo-wa.caltech.edu/websvn/filedetails.php?repname=cds_user_apps&path=%2Ftrunk%2Fcds%2Fcommon%2Fsrc%2FLOW_FREQ_DEMUX.c

The idea is you take data from 2 different channels, one on an even cycle, then one on the odd cycle.  In this way you can transmit two 8 kHz channels over one 16 kHz channel, for example.  

I've tested some but not all of these functions, so the principle seems to work fine.  You will need to add low pass filters before and after to clean up the data transmitted.

Joe

On Mar 22, 2016 6:49 PM, "David Barker"  wrote:
Hi Brian,

sounds good, let’s plan on trying this on H1 next Tuesday and discuss the details tomorrow.

Dave


> On Mar 22, 2016, at 16:41, Brian Thomas Lantz  wrote:
>
> Dave,
> I’d like to install that RFM sender into Hanford next Tuesday so we can get the suspension point motion from each end to the corner at LHO.
> Can we discuss briefly at the CDS call on Wed?
> Joe B has a suggestion for plumbing, since the SEI models are not attached to the RFM network.
>
> Thanks
> -Brian
>
Images attached to this report
Comments related to this report
joseph.betzwieser@LIGO.ORG - 13:08, Friday 25 March 2016 (26254)SEI
I've created a technical document on how to utilize the C code blocks I've written to combine multiple low frequency channels together into a single higher frequency channel.  It is T1600083.

To use them on Tuesday, you'll need to have done an svn up in /opt/rtcds/userapps/release/cds/common/src to get the LOW_FREQ_MUX.c and LOW_FREQ_DEMUX.c files.

You can then use the normal CDS_PARTS.mdl user C code blocks.

The idea is to take the 2 channels sent from the h1isietmx/y to the h1pemex/y model (already low passed filtered in the ISI model) and pass them to the h1pemex/y model.  There they probably should be low passed again after upsampling, and then combine those two input channels into one with the low_freq_mux2 function (so 2 inputs, 1 output), and sent the output over the RFM to the h1oaf model, where it will then go into a low_freq_demux2 function, with the first input being a -1, indicating the data was sent from a cycle ago, and the second input being the combined channel sent over RFM.  This will then come out as two channels which can be used in the h1oaf model or sent further on as needed.  As both the sender and receiver will be in 16 kHz models, further filtering should not be necessary in the h1oaf model.
H1 AOS
kiwamu.izumi@LIGO.ORG - posted 02:11, Friday 25 March 2016 - last comment - 08:49, Monday 28 March 2016(26245)
Cavity pole strongly depends on the differential lensing

Preliminary conclusion: the DARM cavity pole seems to be a strong function of the differential lensing. I was able to change it from 357 Hz to 220 Hz (!!!)

I will post more details tomorrow.

The cavity pole measurement is not valid until t=80 min. and also in the time band approximately between 230 and 250 min. The interferometer was locked on the DC readout with ASC fully engaged, The PSL power stayed at 2 W throughout the measurement.

Learning this behavior, I would like to do the followings in the next test:

By the way the second attachment is trend of various channels during the test.

Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 16:48, Friday 25 March 2016 (26261)

Actually, Hang pointed out that SRM and SR2 showed much more visible reactions in their alignment. See the attached.

In particular, SR2 pitch seems to trace the lensing curve.

Also, looking at PRM and PR2, we did not see drift or anything interesting.

Images attached to this comment
gabriele.vajente@LIGO.ORG - 09:13, Friday 25 March 2016 (26248)

A simulation  with substrate lensings as reported in the elog did not show a large variation of the cavity pole: about 1% or so. My suspect is that the change in differential lensing is causing the IFO working point to change: alignment or longitudinal offsets? In my simulation the longitudinal working point is obtained from simulated error signals, so I don't see any offset in the locking error signals.

aidan.brooks@LIGO.ORG - 11:43, Friday 25 March 2016 (26251)

The differential lens change is about 18 microdiopters. For what it's worth, there is ~2.3% of power scattered from the TEM00 mode on a double-pass through such a lens. Whether such a purely differential lens in the SRC would manifest solely as a 2.3% round-trip loss in the differential TEM00 mode of the arms is questionable. I still need to run the numbers for the effect on the DARM cavity pole if we simply added this loss to the SRM mirror.

kiwamu.izumi@LIGO.ORG - 16:15, Friday 25 March 2016 (26255)

Here are some more small points to note.

[Two cavity pole measurements]

At the beginning of the run before I started changing the CO2 power, I ran a Pcal swept sine measurement in order to get the cavity pole frequency. The DARM open loop was also measured within 10 minutes or so in order for us to be able to take out the loop suppression. In addition, I ran another pair of Pcal and DARM open loop measurements to double check the measurement. The attached below shows the transfer functions with fitting. The fitting was done with some weighted least square algorithm using LISO.

As shown in the plot, the shift in cavity pole is obvious. Also the optical gain is different between the two measurements.

[Evolution of the sensing function throughout the test]

The optical gain and cavity pole are negatively-correlated. The trend of the optical gain looks very similar to the one for the power recycling gain, but the variation in the optical is much larger-- the optical gain increased by 20 % at most relative to the beginning. As pointed out by Valera in the ISC call today, a fraction of the variation in the optical gain could be due to the OMC mode matching.

[Alignment drift]

As Gabriele pointed out in the comment, it may be possible that the CO2 lasers affected the alignment of the interferometer and changed the amount of losses in some parts of the interferometer or introduced some other impact on the cavity pole. Hang and I have looked at trend of optical levers during the time.

There are two optics that seemingly reacted to the differential lensing, that are BS yaw and ETMX PIT. The showed a kink point at the time when the CO2 power changed. In addition, ETMY pit slowly drifted by 2 urad and ETMY yaw moved by 1-ish urad. Other large optics also moved but were within 1 urad. From a naive point of view, the alignment does seem to explain the behavior of the cavity pole going down and up during the measurement because none of them clearly showed a going-up-and-down type behavior. However, it is possible that the true misalignment was covered by drift of the oplev itself.

 

[Online cavity pole measurement]

The cavity pole was measured by injecting a line at 331.9 Hz at the DARM output. The DARM loop is notched out at the same frequency. The measurement method is described in 18436.

Images attached to this comment
gabriele.vajente@LIGO.ORG - 08:49, Monday 28 March 2016 (26279)

Some simulations I did months ago for the MIT commissioning meeting (https://dcc.ligo.org/LIGO-G1500593) showed that the cavity pole is very sensitive to SRC matching. I therefore expect the cavity pole to be also very sensitive to SRC alignment, as seems to be sugegsted by the SR* mirror drifts.

H1 TCS (TCS)
aidan.brooks@LIGO.ORG - posted 10:17, Thursday 24 March 2016 - last comment - 15:57, Friday 25 March 2016(26231)
HWSX camera images still glitching after H1HWSMSR reboot

Dave B rebooted the H1HWSMSR machine yesterday. Unfortunately, an investigation of the HWSX images shows that they are still glitching for an unknown reason. 

Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 15:57, Friday 25 March 2016 (26256)

Nutsinee, Kiwamu,

As requested by Aidan, we have restarted the cameras and the computer yesterday after the LHO ISC meeting. We remotely shut the cameras by pressing the buttons on the medm screens. Then we went to the MSR and pressed the reset button to restart the computer. Aidan reported that the corrupted image issue has gone before we shut off the cameras. After rebooting the computer and cameras, we restarted the HWS codes using the old tmux sessions.

Also Aidan discovered that when the images were corrupted it reported an anomalously high pixel mean peak values and in fact it exceeded the theoretical limit with the 12 bits data = 4096 counts. This motivated us to set up a diagnosis test in the DIAG guardian as reported in 26243.

Displaying reports 56041-56060 of 81604.Go to page Start 2799 2800 2801 2802 2803 2804 2805 2806 2807 End