Displaying reports 76721-76740 of 85682.Go to page Start 3833 3834 3835 3836 3837 3838 3839 3840 3841 End
Reports until 16:55, Monday 13 January 2014
H1 CDS (SUS)
david.barker@LIGO.ORG - posted 16:55, Monday 13 January 2014 (9244)
Investigation of LED errors on ITMY Hardware Watchdog

Jim and Dave

Over the weekend the HWWD unit attached to ITMY has been giving LED error status roughly once an hour but randomized. Each error is only a few seconds in duration. The sister unit in the DTS has shown no errors (we installed a long 37pin cable on friday). This afternoon at 12:50 we replaced the ITMY unit (S1301699) with the DTS unit (S1301706). The only issue with the swap is that the 706 unit did not boot up automatically on application of power, we had to press the reset button. On the other hand the 699 unit when powered up in the DTS booted first time every time.

About an hour later we saw an LED error condition on ITMY (now the 706 unit) so the problem seems to be with the ITMY osem/sat-amp/cabling and not the HWWD (the 699 unit now in the DTS has shown no errors). Jim and I went out to the CER and LVEA to verify the monitor cables look ok at 15:18. We noticed that the ITMY M0/R0 sat amp is a replaced unit, the original unit is stored on the BS shelf. Filiburto remembers there was a possible low frequency issue with this sat amp, hence the swap out.

We trended the photodiode signals of the ITMY top osems to verify that nothing is actually physically happening with the LEDs or their light output. No correlation was seen.

Next step is to look at the LED current monitor signals coming from ITMY to see if the signal is dropping out at this very low rate of one second every hour or so.

H1 SEI (INS, SEI)
jim.warner@LIGO.ORG - posted 16:26, Monday 13 January 2014 (9243)
HAM4 SEI Install Progress

HughR, MitchR, JimW

Today, we finished our inital payloading of the HAM4 ISI, removed the shipping braces, locked the ISI, took a look at the level, and started working on cabling. Not many issues, but  a few. Currently, HAM4 ISI corner 3 CPSes read out on the corner 1 of HAM5 ISI. Hugo is looking at the model, Filiberto is looking at the IO chassis cabling. The level of the ISI is a little out, but I think good enough for now. We may address the level of the ISI with HEPI tomorrow, after we look at the numbers more. Hugh also powered on and verified that the HEPI pier pods seemed to be working. Tomorrow we will look at cabling more, and start balancing the ISI.

LHO General
justin.bergman@LIGO.ORG - posted 16:07, Monday 13 January 2014 (9242)
Ops

Monday 13 JAN 2014

-Windy conditions all day, 20-30mph

-X-Arm impassable due to tumbleweeds. Y-arm passable with caution. Bailing crews at work on both arms.

 

-920-940 Apollo using sawzall at BSC1

-919 AndresR looking for parts in around HAM4/5

-950 EY transitioned to laser HAZARD for welding operations

-957 LVEA transitioned to laser SAFE

-1000 Koji/DickG/DanielS working on electronic racks at H1PSL; unk completion time (1200?)

-1009 Bubba opening LVEA outside exit door at NE corner

-1019 TravisS, BetsyW, Giles and JasonO begin welding ops at EY

-1026 -1200 Hugh/JimW/Mitch working at HAM4

-1030-1600 Filiberto working on documentation at HAM6

-1244 DaveB and JimB swapping out hardware watchdog in the CER

-1330-1600 Mitch, JimW, HughR continuing SEI work at HAM 4

-1358-1445 JohnW, Sheila going via offroad route to EX

-1459 Sheila, Alexa, DanielS to EX (on the road to MX, then offroad)

-1512-1545 JimB and DaveB returning to CER to work on HWWD

LHO VE
john.worden@LIGO.ORG - posted 15:19, Monday 13 January 2014 - last comment - 20:25, Monday 13 January 2014(9241)
ENDX Ion Pump

I noticed that LLO was running their main ion pump at 7kv in the end station. Ours was set to 5kv.

Today at 22:30 UTC I set the voltage to 7kv. The immediate response has been a small increase in pressure at PT510. We'll watch for a few days and see where it goes.

 

Comments related to this report
john.worden@LIGO.ORG - 20:25, Monday 13 January 2014 (9252)

Here is the last 11 hours of pressure. Looks like the 7kv is doing its thing.

Non-image files attached to this comment
X1 DTS (DAQ)
james.batch@LIGO.ORG - posted 14:41, Monday 13 January 2014 (9239)
Fixed minute trend readback from NDS on DTS
Fixed an error which specified a non-existent file for minute trends on the x1nds1 server.  Minute trends can now be read by dataviewer and other clients.  Note that minute trends have been written properly, but could not be read back using nds.
H1 SUS (SUS)
betsy.weaver@LIGO.ORG - posted 13:30, Monday 13 January 2014 (9238)
ITM03 Test Mass processing incident

On Friday, Gerardo and I encountered an issue while processing the optic as per the ear bonding procedure.  During the processing, the optic suffered a 3mmx 3mm crack at the bevel on the HR side of the optic and some scratches out near the edge of the HR face.  We're working to understand whether or not it can be used in BSC3, but our expectation is that it can, owing to the small nature of the crack.  We are also working with COC/SUS/SYS so this damage does not occur during future processing.

H1 ISC
stefan.ballmer@LIGO.ORG - posted 13:17, Monday 13 January 2014 (9237)
PRX locking stably
Kiwamu, Stefan

We did some tweaking of the PRCL servo in order to get stable locking of the low finesse half-PRC for further actuator commissioning.

- We are feeding back to PR2 and PRM.
- We removed any low-pass filter from the PRCL control filter, but left a CPL300 in the M3 locking filters of PRM and PR2. Currently only M3 and M2 are feeding back - the filter modules snapshots are below.
- This gives a PRCL UGF of about 18Hz (see OLG measurement, as well as the signal levels in counts below). 
- With that, fine-tweaking the alignment showed that PR3 was moving too much in pitch. We increased its L and P damping gain, and engaged corresponding boost filters. (snapshot below)
Images attached to this report
H1 ISC
koji.arai@LIGO.ORG - posted 12:42, Monday 13 January 2014 - last comment - 22:50, Monday 13 January 2014(9236)
2f demodulator installed

[Dick, Daniel, Koji]

The POP 2f demodulator unit previously installed on row 28 of the ISC R2 rack (c.f. this entry ) was replaced with the 2f demod unit.
This unit has a 24MHz LPF and a 80MHz HPF on CH1 and CH2, respectively, forming a diplexer configulation for 18MHz (2xf1) and 90MHz (2xf2) signals.
Therefore, the temporary power splitter for the POP 2f path was removed.

Because of this action, we expect that the demod phase for the POPAIR18 and POPAIR90 were changed.

The 3f demods (CH3/4) still have the power splitter. This will be removed when the 3f diplexer unit is installed on row 27.

We also cleaned up some of the RF cables:

- The REFLAIR9 cable plugged on row 34 is now routed through the patch panel on row 27.
This means that the demod phase of the REFLAIR_A_RF9 was changed.

- The cable for REFL9 was made and connected to the demodulator on row 34.

- Unnecessary connectors/cables were removed from the patch panel on row 29.

Comments related to this report
daniel.sigg@LIGO.ORG - 14:48, Monday 13 January 2014 (9240)

We also added the cables between the greeen PFDs and the PLL error signals, as well as 2-pin LEMOs between the PLL servo outputs and the VCO tune inputs.

kiwamu.izumi@LIGO.ORG - 22:50, Monday 13 January 2014 (9254)

Then I adjusted the demod phase of REFLAIR_A_RF9 by toggling the swtiches of the phase shifter. This was adjusted for PRX. I haven't done it for REFL_A.

H1 SUS
jeffrey.bartlett@LIGO.ORG - posted 11:45, Monday 13 January 2014 (9235)
TFs for H1-SR2
   After making several adjustments to the Coil Holder, the BOSEMs, flag alignments, and adding the third Coil Holder Mounting Bracket on H1-SR2, a new set of transfer functions were taken Friday evening. (See aLOG #9211). The plots for this latest set of transfer functions are posted below. All scripts and data files have been committed to the SVN repository. 

Note: The 4th Coil Holder Mounting Bracket has been modified and is being run through C&B this week. It will be installed on the suspension as soon as it comes out of clean and Bake.    
Non-image files attached to this report
LHO General
justin.bergman@LIGO.ORG - posted 10:26, Monday 13 January 2014 (9234)
Sawzall work at BSC1

Apollo doing some cutting 920-940

H1 General
corey.gray@LIGO.ORG - posted 09:41, Monday 13 January 2014 (9233)
Engineering Run #5 (ER5) Begins Today!

Here is an site email announcment made with regards to ER5:

Would like to announce an addition/change to our duties for DAY shifts.  This is mainly due to the upcoming Engineering Run #5 (ER5 from Jan13-Feb28) which focuses on HIFO-X at H1 & L1.  There have been a few Engineering Runs in the aLIGO era, but they have required minimal Operator input.  For Science Runs (& starting with ER5) primary activity occurs at the Sites for obvious reasons, but data analysis occurs at other institutions around the world after-the-fact.  For many of these people, they have no idea what goes on at the site on a day-to-day basis, and many are not familiar with our LIGO lingo & naming conventions.  This is where we will help out.
 
For ER5, we (the Operators) want to offer guidance/help for off-site and after-the-fact analysis, and we'll do this with giving a play by play run down of activities with the aLOG during our DAY shifts.
 
Operator Reporting Of Site Activities Via The aLOG
During our daily shifts we note tons of activities as they occur (via text file on your computer, running draft in aLOG, or pen & paper) & we generally post these activities in a summary at the end of the shift.  For ER5, let's report any major activity as an entry by itself when it starts. 
What constitutes a "major activity"?  I'd say any activity which is out of the ordinary and/or will possibly have drastic effects on channels Analysts may look at later.  Examples:
  • Moving of the cranes
  • Rebooting of a system(s)
  • Commissioning work (i.e. changes to alignment, oplev work, etc.)
Let's make an entry when it STARTS (so we timestamp the activity).  In the "Title" field, state the work.  In the body of the entry make any notes (we don't need much/anything here; especially if the work is self-explanatory in the Title.  We can leave specifics to those performing the work to aLOG themselves). 
 
When you are notified the activity is COMPLETE, make a sub-entry stating so.
 
This notice is just for our DAY shifts during ER5.  I believe Commissioners will be asked to do the same for their evening work, and we'd also like the last person on site to submit an "End Of Day's Activity" entry (so Data Analysts will know when a stretch of unperturbed time begins).
 

This is a step in getting closer to our ultimate goals as Operators, and that is running shifts during a Science Run. 


 
OK, that is all.  If you have any questions please talk to Fred (Co-Chair of the Joint Run Planning Committee[JRPComm]) or myself.  Oh, and if you ever want to know information about Engineering Runs, see the JRPComm wiki.  In addition to the ops email list, I'm also cc-ing relevant commissioners & others at LHO (please forward to anyone I'm missing).
 

Thanks!

Corey

LHO FMCS (PEM)
dale.ingram@LIGO.ORG - posted 09:09, Monday 13 January 2014 (9232)
Seismic and wind trends
Three days of minute trend maxima for the LVEA PEM seismometer and the LVEA weather station, ~9:00 AM local on Friday through the current time.  The period of highest winds was Saturday afternoon and evening.
Images attached to this report
H1 ISC
sheila.dwyer@LIGO.ORG - posted 06:46, Monday 13 January 2014 (9229)
green arm work starting for today

I set the mode cleaner requested state to down and turned off the alingment offsets on MC1 to avoid confusion from MC flashing.

H1 ISC
kiwamu.izumi@LIGO.ORG - posted 18:29, Sunday 12 January 2014 (9228)
corner locking today: all the diodes aligned on ISCT1, phase adjusted for 2f signals, PRM and PR2 were saturating

[Stefan, Kiwamu]

Here are our corner locking activity today.

We completed the alignment of all the diodes on ISCT1:

The razor blade beam dumps for the POP PDs are not aligned yet because the beam was not bright enough.

 

The demod phase of 2f signals were adjusted:

We adjusted the demod phases to get the signals maximized in I. When the 2f signals go positive, it indicates that the carrier is resonant in the power recycling cavity, and negative for the sidebands on resonance.

Note that the demod board that currently in the rack is not the final version (see alog 9103 and 9093).

 

The signals looked too small for the simple Michelson:

We misaligned PRM to see how big signal we could get for the simple Michelson. However, the RF and DC signals looked too small to acquire the lock. For example, REFLAIR_A_LF fluctuated only by a few ADC counts. It seems that it would be very tough to lock the Michelson without the power recycling at this power level.

 

PRM and PR2 are saturating:

We then moved onto PRX in order to establish stable lock of PRC. Wth both PRM and PR2 actuated, we could still see a saturation in them. We must revisit the multiple-stage offload in PRM and PR2 and activate the top stage stably. Currently none of the M1 stages are not in use because we haven't commissioned them. Also, at the same time, we should spend some time to reduce the seismic disturbance in the first place to ease the PRC lock.

H1 ISC (ISC)
sheila.dwyer@LIGO.ORG - posted 18:21, Saturday 11 January 2014 - last comment - 08:25, Monday 13 January 2014(9221)
X arm alignment, fiber polarization, X arm tumbleweeds

 

I went through the X arm alignment again, unfortunately the computer crashed before I saved the alog but the centered values for TMS are 147.5 PIT -234 YAW (+10 in pit compared to yesterday, +6 in YAW) ITM 72 PIT -62 YAW (basically the same as yesterday).

It was easy enough to find the pointing of TMS and the ITM using the baffle PDs starting from the last alingment in alog 9191.  However, I could not easily find the ETM pointing.  I did find the beams on the baffle PDs by doing a slow scan (Strip chat screen shot attached) and found:

with 40dB gain, PD3 has 2.1 V with ETM PIT 292 YAW 44.  REFL B then has 15400 counts

with 20dB gain PD1 has 2.6 Volts with ETM PIT 246 YAW 101 Refl B has around 1100 counts. 

From this the aligned position should be 269 PIT 72.5 Yaw.  This is remarkably different from where I found similar fringing yesterday, 384 PIT -77 YAW.  While there was some HEPI commisioning yesterday afternoon, I would have expected this to change the TMS and ETM alingments by the same amount, so either one or the other of these alignments is bad or something moved.  Also, the ETM oplev has moved quite a lot. 

The PD levels for these alingments seem suspicously low, if the mode matching was perfect I would expect the intensity on the diodes to only decrease by a factor of the ETM reflectivity compared to the straight shot from the transmon (alog 9191) Instead these are a factor of 100 and a factor of 10 lower. Either these are not the right beams or the mode matching could be wrong.  There was clearly some fringing on the refl PD and COMM (which I am using as an X arm trans readback for now). 

It is possible to find some light on the PDs for ETM alignments that don't make sense (PD1 on the wrong side of PD4 ect), probably a second bounce beam hitting the PD. 

I also changed the polarization into the X arm fiber (photo of settings attached). 

Once I saw some fringing I was able to "lock the arm"  and the "lock"  would stay for 10s of seconds although I'm not sure this was really locking to any reasonable mode of the cavity.  On the camera I could see that the beam motion is large, we have verry high winds.  I also could not go out to the end station to work on the locking because of tumbleweeds, photo attached. 

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 08:25, Monday 13 January 2014 (9231)

ETM PIT is not affected by HEPI/ISI PIT much if any, only TMS PIT is affected. The fact that OpLev moved much means that your alignment is still bad, it's likely that the baffle PD signal you saw was something other than the direct beam from ETM.

H1 ISC
kiwamu.izumi@LIGO.ORG - posted 16:41, Friday 10 January 2014 - last comment - 15:58, Sunday 12 January 2014(9211)
HAM1 in-vac work: finally completed

[Alexa, Koji, Kiwamu]

We finally completed the in-vac work in HAM1 and the Apollo crews put the door back on. All the necessary beam comes out to ISCT1 and all the necessary beam hit the in-vac diodes. Yeah!

Some pictures will be uploaded in ResouceSpace later.

Here are a list of what we did today:

Comments related to this report
kiwamu.izumi@LIGO.ORG - 13:18, Sunday 12 January 2014 (9225)

Pictures are now available in ResourceSpace:

kiwamu.izumi@LIGO.ORG - 15:58, Sunday 12 January 2014 (9226)

Notes on the WFS locations:

As reported in the previous alog, we have touched the location of both WFS_A and WFS_B because they needed to be rotated more to have a spatially well separated reflection. Before and after applying this modification, we took several pictures to estimate how much the WFSs were shifted along the beam propagation axis since this can affect our WFS signal extraction.

  • According to the pictures, the position of WFS_A (or equivalently WFS_1) was shifted by 9.4 mm toward the west.
  • Also, WFS_B (or equivallently WFS_B) was shifted by 10 mm toward the west.

For some more details, see the attached pictures.

Images attached to this comment
H1 PSL
alexan.staley@LIGO.ORG - posted 09:11, Friday 10 January 2014 - last comment - 12:53, Sunday 12 January 2014(9200)
PSL FSS Oscillation

(Alexa, Kiwamu)

We noticed that the FSS was osillating significantly. I first lowered the resonant threshold from .8V to .5V. I also decreased the Common Gain from 30dB to 10.4dB. This seemed to help. It's possible the oscillation was due to instability in the MC servo. 

Comments related to this report
kiwamu.izumi@LIGO.ORG - 12:53, Sunday 12 January 2014 (9224)

I set the common gain back to 30 dB to see the instablity still persists. So far, I don't see any instablity. I am leaving it 30 dB.

H1 ISC
keita.kawabe@LIGO.ORG - posted 16:31, Thursday 12 December 2013 - last comment - 16:01, Sunday 12 January 2014(8932)
HAM1 WFS: awesome

After an initial assessment that stated "not too bad, not too good" (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=8919), which was based on just two data points (beam radius on WFSs), I added the third point further downstream of the WFS2 and it turns out that actually it's excellent.

In the attached plot, blue circles represent the measured beam width, blue crosses on both sides of blue circle represent the potential position error (Jamie claims +-1cm though probably it's too generous), red line is a fit over the three points, green is the curve generated by the design parameters.

As you can see, in both horizontal and vertical direction, the waist is very close to the middle of the WFSs, and the waist radius is very close to the designed 250um.  Gouy separation for X (horizontal) and Y (vertical) are 82.6 and 87.1 degrees, respectively.

This was obtained from just two iterations of measurming at WFS1 and WFS2 and pushing RM2 toward RM1 based on the measurement. Downstream was measured just once after we were satisfied with WFS1 and WFS2.

  relative position (mm) position error (mm) X diameter mean (um) X diameter std X goodness of fit X goodness of fit std Y diameter mean Y diameter std Y goodness of fit mean Y goodness of fit std
WFS1 0 +-10 746.79 4.6 0.01 0.000 688.9 4.2 0.00 0.000
WFS2 369 +-10 746.25 10.1 0.00 0.000 758.18 4.4 0.00 0.000
downstream 763.2 +-10 1574.92 4.95 0.02 0.000 1666.38 1.79 0.01 0.000

Distance from RM3 to the first lens on the sled is, according to Jamie, between 48.0 and 48.25 inches.

Also, as noted earlier, the above data was obtained after having moved RM2 toward RM1 by 22.5mm. Everything else is the same as what Sheila reported much earlier.

We also measured at one point between RM3 and the sled (14.5" downstream of RM3).  Together with upstream number measured yesterday (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=8893), these are:

  position position error X diameter (um) X std X goodness of fit mean X goodness of fit std Y diameter Y std Y goodness of fit Y goodness of fit std
After RM3 14.5" downstream of RM3 +-10mm 3750.18 4.885 0.01 0.000 3923.63 2.137 0.00 0.000
Upstream of telescope 44.7" downstream of 50:50BS right after the HWP +-1" 3851.01 1.982 0.01 0.000 3959.23 1.232 0.01 0.000
Upstream of telescope, head rotated 45 degrees same as above same as above 4117.74 1.475 0.02 0.000 3845.62 0.763 0.00 0.000

In all of the above measurements, "Profile averages" was 10, "Rolling profile Averages" was 3, the actual number of measuremets (i.e. the number of scans performed before I stopped the measurement) were larger than 10 but I don't know if the software was taking more than 10 points into the statistics or not.

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 17:04, Thursday 12 December 2013 (8934)

Several things to note.

We decided that we did NOT want to propagate the upstream measurements to downstream, because it was difficult to obtain more than one data points. (ModeMaster is supposed to overcome this, but in reality there are many caveats and you should know how to tell when which caveat applies.)

With NanoScan and limiting ourselves to the measurements with small beam, it was still difficult to obtain good data because of some kind of glitches. It's not clear if it was due to NanoScan or the beam, the beam was well damped and was not moving on the viewer card, there was no noticable intensity glitch either. But the symptom was that the statistics window shows nice steady data for anywhere from one second to 30 seconds, then there's some kind of glitch and the scan/fit image looked noticably different (not necessarily ugly), the diameter mean becomes larger and the stddev jumps to a big number (like 10% or more of the mean, VS up to a couple % when it's behaving nice), and the goodness of fit also becomes large. Somehow no glitch made the beam diameter number smaller. I just kept waiting for a good period and cherry-picked.

When the beam was moving it was impossible to obtain good data.

Another kind of glitch was "saturating" glitch where the software says there is a saturation. We disabled AGC of NanoScan and lowered the gain by 3dB in an attempt to eliminate saturation, it seemed to help but we couldn't kill that error completely.

keita.kawabe@LIGO.ORG - 17:08, Thursday 12 December 2013 (8935)

We (I and Jamie) will go in HAM1 tomorrow to set the eddy current damper spacing (now that Bram wrote a procedure to do that, plus it turned out that Jamie didn't check the ECD spacing on the back plates).

keita.kawabe@LIGO.ORG - 17:24, Thursday 12 December 2013 (8936)

Measurement apparatus. We flipped one steering mirror on the sled to direct the beam to Nanoscan that is placed at the same distance from the steering mirror as the WFS. Made measurement, flipped the mirror back, and moved to the next one.

Images attached to this comment
lisa.barsotti@LIGO.ORG - 04:26, Tuesday 17 December 2013 (8980)
Very nice!

This will become version 12 in D1000313.

It would be good to add the corresponding alamode file with the final distances here: https://dcc.ligo.org/T1300960-v1, I added a note to remind us that this is the relevant log entry.

kiwamu.izumi@LIGO.ORG - 16:01, Sunday 12 January 2014 (9227)

A update on 2014.Jan.12:

Alexa, Koji and I changed the position of both WFSs to dump the reflected light off of the diode (see alog 9226).

  • The position of WFS_A (or equivalently WFS_1) was shifted by 9.4 mm toward the west.
  • WFS_B (or equivallently WFS_B) was shifted by 10 mm toward the west.
Displaying reports 76721-76740 of 85682.Go to page Start 3833 3834 3835 3836 3837 3838 3839 3840 3841 End