Displaying reports 68181-68200 of 77131.Go to page Start 3406 3407 3408 3409 3410 3411 3412 3413 3414 End
Reports until 09:41, Monday 13 January 2014
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 PSL
kiwamu.izumi@LIGO.ORG - posted 12:33, Sunday 12 January 2014 (9223)
Another touch on ISS

I found that the diffraction power of ISS had decreased again.

This time, it seems that somebody changed the offset setting for some reason (or maybe it was related to Stefan's ODC activity, see alog 9222). I set it back such that the diffraction power stays at 10%.

H1:PSL-ISS_REFSIGNAL = -1.93 (had been set to be -1.95 by someone on 11th of January)

Note that this value is the same as what I set on this past Friday (see alog 9219)

H1 CDS
stefan.ballmer@LIGO.ORG - posted 00:37, Sunday 12 January 2014 (9222)
ODC cleanup for PSL
I did some cleanup work for the PSL odc channels

- Updated the ODCV2.mdl library to use the MODAL_RATE part from RCG 2.8. This replaces the need to manually set the model rate. This library is in almost every model currently running, but there is no real urgency to push the change everywhere.
  Updated SVN: ODCV2.mdl revision 6837

- Added ADC/DAC overflow and Excitation monitoring to ODC for the PSL. Updated and restarted the following files (SVN revision 6839):
        h1pslfss.mdl
        h1psliss.mdl
        h1pslpmc.mdl


- Updated the PSL ODC medm screens. PSL_ODC.adl                    SVN revision 6838  (picture attached)
- Updated the ODC overview screen.  SYS_CUST_ODC_SITE_OVERVIEW.adl SVN revision 6842

- Updated the h1setODCbitstrings and h1setODCbitmask scripts in cds/h1/scripts to include the PSL settings. SVN revision 6841.


Images attached to this report
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
stefan.ballmer@LIGO.ORG - posted 21:38, Friday 10 January 2014 (9220)
PRC work
Keita, Koji, Stefan

I went out to ISCT1 and steered the REFL beam on to REFLAIR_A_9. After a little bit of alignment tweaking and closing the PRC loop (no MICH loop yet) we got some pretty decent REFL dips. More later this weekend.
Images attached to this report
H1 PSL
kiwamu.izumi@LIGO.ORG - posted 19:56, Friday 10 January 2014 (9219)
ISS diffraction was too low and set to 10%

Looking at the IMC transmitted light, I realized that the laser power occasionally dropped by 15% and came back to the nominal level in 10-ish seconds (see the attached screenshot). Since I knew this was usually associated with ISS, I took a look at ISS. Sure enough, the diffracted light was too low and it was about 5% or perhaps even less. According to the trend (see the second file attached), it seems that the diffraction power started decreasing after around 18th of December in the last year and recently dropped steeply. This too low diffraction was causing the frequent unlock of the ISS loop.

I adjusted the offset voltage to increase the diffraction power to 10% as was done by Doug (see alog 7810).

H1:PSL-ISS_REFSIGNAL = -1.93 ( which had been -2.00)

It seems this fixed the glitching issue as of now.

Images attached to this report
H1 PSL (CDS, PSL)
stefan.ballmer@LIGO.ORG - posted 19:24, Friday 10 January 2014 (9218)
Updated the LHO PSL code to syrnchronzie with LLO
I updated the the LHO PSL code (FSS, ISS, PMC) to syrnchronzie with the LLO status, using all the common parts already in svn. This was slightly tricky, since there were some local changes at LHO that were never committed because the LLO files had changed. This also brings the PSL ODC code to the same status as LLO. Some more ODC threshold setup work will be required over the weekend to make sure the channel is green when it should be.

Files checked into svn: version 6832:
h1pslfss.mdl
h1psliss.mdl
h1pslpmc.mdl

I also re-implemented the local LHO changes to the common files, namely:
- $Id$ and $HeadURL$ tags for svn version keeping 
- Defining science channels by adding * in the DAQ block for the following channels:
   pslfss: FAST_MON_OUT, MIXER_OUT
   psliss: AOM_DRIVER_MON_OUT, PDA_OUT, PDB_OUT
   pslpmc: HV_MON_OUT, MIXER_OUT

Files checked into svn: version 6833:
pslfss.mdl
psliss.mdl
pslpmc.mdl

I guess LLO should syc those files to have the PSL run of the same library at both sites.


There is one more thing: psldbb.mdl I did not touch it today. LLO is up to date. LHO has some local mods (presumably from the MATLAB2012 move), BUT:
Both versions are so messed up with wiring that I do not dare touch it.


H1 SEI (INS, SEI)
jim.warner@LIGO.ORG - posted 18:24, Friday 10 January 2014 - last comment - 19:18, Friday 10 January 2014(9216)
HEPI Position loops installed on ETMX

Lots of work on ETMX HEPI today. Because of the potential for HEPI pump glitches to feed into the BSC ISI's St1 T240s, we worked on installing position control on HEPI. These loops are now working and we have left the entire SEI platform (HEPI & ISI) in an isolating cofiguration. This does mean that commissioners will have to enter their offsets in a somewhat different manner, but Fabrice has explained it to Kiwamu. We have also attempted to put HEPI back in it's tilted state, it's not exactly where it was, but its pretty close. Monday, we will have to update safe.snaps for HEPI.

Comments related to this report
hugh.radkins@LIGO.ORG - 19:18, Friday 10 January 2014 (9217)

The tilting required to get the ETMX TMS pitched back to the corner is now done as usual in that the value is in the target of the BIAS screen.  This value is -610000.  Please call me if there are issues--H

H1 SUS (SUS)
travis.sadecki@LIGO.ORG - posted 17:39, Friday 10 January 2014 (9215)
ETMy reweld status

The ETMy has had two of its four new fibers rewelded. 

H1 ISC
sheila.dwyer@LIGO.ORG - posted 17:34, Friday 10 January 2014 (9214)
PLL servo board

Daniel, Sheila

We measured some tranfser functions of the PLL servo board.  

 

Attached files are : X end PLL servo board 10kHz to 100kHz

AA1.txt , common compensation on, 0dB gain, generic filter on

AAA2.txt, 0dB gain, common compensation on, fast option on (this is a 292.48kHz notch)

AAA3.txt 0dB gain, nothing on  (we were using the common mode servo which has a high impedance output to drive the RF analyzer which has 50Ohm inputs, we also used a BNC T. This might be why there is strange 2dB feature around 200kHz which should be subtracted from the other traces).  

Non-image files attached to this report
H1 SUS (CDS, IOO, ISC, SUS)
jeffrey.kissel@LIGO.ORG - posted 17:09, Friday 10 January 2014 (9213)
ECR E1300578 -- HTTS Screens Complete, Ready for Install at LLO
J. Kissel

After a few more tweaks of the individual HSSS screen, and creating the grouped RM and OM ALL screens, all HTTS modifications are complete and ready for deployment. Detailed instructions on how to install are listed below. Once LLO installs these changes (slated for next maintenance period), we can finally close out ECR E1300578. All necessary changes are committed to the userapps repo in various locations, again detailed below.

Installation Instructions
-------------------------
Capture alignment settings
(1) Make sure you either have alignment settings captured in a safe.snap, or at least handy for later.

SVN:
(2) svn update the sus corner of the userapps repository. (If you haven't accidentally updated already JAMIE, then) You should see a plethora of new files in the folders mentioned in LHO aLOG 9195. I've made further updates since that log, so be sure to update right when you're ready to install. Update the cds/h1/medm/ corner as well, so you get a feel for how the MEDM marco files need to be called from a sitemap.

Simulink:
(3) Create a new model ${ifo}sushtts.mdl (which you can probably copy from h1sushtts.mdl, to minimize labor). You'll need to 
- change the cdsParameter block to reflect the new ${ifo}, 
- change all of the IPC channel names,
(4) Create a new model ${ifo}susauxasc0.mdl (which again, you can copy from h1susaux.mdl, to minimize labor). You'll only to
- change the cdsParameter block to reflect the new ${ifo}
(5) Copy over changes (or simply overwrite) the ${ifo}susim.mdl model. You'll need to
- change the cdsParameter block to reflect the new ${ifo}, 
- change all of the IPC channel names,
(6) Compile all new/updated models.

Screen preparation:
(7) Set up your sitemap to call up either the individual HSSS screen,
${userapps}/sus/common/medm/hsss/SUS_CUST_HSSS_OVERVIEW.adl
or either of the groupings of HSSS,
${userapps}/sus/common/medm/hsss/
SUS_CUST_OM_OVERVIEW_ALL.adl
SUS_CUST_RM_OVERVIEW_ALL.adl
/opt/rtcds/userapps/release/sus/common/medm/haux/
SUS_CUST_HAUX_OVERVIEW_all.adl
(Note, eventually we'll move the HAUX overview into the hsss folder, and rename it properly capitalized)

Installation:
(8) Ask your sysadmin to prepare for the new installs by
- Removing h1asctt from 
- Adding h1sushtts and h1susauxasc0 to
all EDCU, master, IPC, .ini, etc files.
(9) Make-install and start the models.
(10) Restart the DAQ
--------------------

Once LLO has successfully installed everything and confirmed all necessary functionality, we can get rid of the 
${userapps}/sus/common/medm/haux, and 
${userapps}/sus/common/medm/htts 
folders, and get of any leftover HTTS stuff in the ASC folder, like the screens in 
${userapps}/asc/common/medm/asctt
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 68181-68200 of 77131.Go to page Start 3406 3407 3408 3409 3410 3411 3412 3413 3414 End