Displaying reports 55121-55140 of 83119.Go to page Start 2753 2754 2755 2756 2757 2758 2759 2760 2761 End
Reports until 14:03, Monday 01 August 2016
LHO VE
kyle.ryan@LIGO.ORG - posted 14:03, Monday 01 August 2016 - last comment - 14:04, Monday 01 August 2016(28781)
~1100 hours local -> Started CS vent/purge air supply (Kobelco)
Chandra, Gerardo, Kyle

Added ~ 2 Qts Turbine oil.  Routing output to LVEA
Comments related to this report
kyle.ryan@LIGO.ORG - 14:04, Monday 01 August 2016 (28782)
~1330 hrs. local 

Measured dew point in LVEA < -35C 
H1 IOO
cheryl.vorvick@LIGO.ORG - posted 13:30, Monday 01 August 2016 - last comment - 15:17, Monday 01 August 2016(28780)
Lightpipe is closed - no IR beam in the vacuum system

In order to move ISCT6, the lightpipe from the PSL needed to be closed.

Jenne closed it and locked it closed - it should remain until after the HAM6 vent.

Comments related to this report
cheryl.vorvick@LIGO.ORG - 15:17, Monday 01 August 2016 (28788)

Not quite...

  • lock didn't match the key, so Peter King took a new lock out and secured the lightpipe
  • Richard has the key
H1 General
cheryl.vorvick@LIGO.ORG - posted 13:26, Monday 01 August 2016 (28779)
snapshot of last alignment before closing the lightpipe
Images attached to this report
H1 SEI
jim.warner@LIGO.ORG - posted 12:58, Monday 01 August 2016 (28778)
Change to ITMX Coil Driver seems to have worked

Hugh did a lot of work over the last few weeks diagnosing the ITMX ISI, with respect to it tripping earlier than the other platforms during an earthquake. His fix last week seems to have worked, at least for the earthquake Friday. First 2 attached plots are the ST1 WD Triggers (the ISI has tripped when the trigger /= 0, first plot shows the triggers separately, second is all on the same plot) , and ITMX, ITMY and ETMX all trip at roughly the same time. ETMY and the BS trip several minutes later, but they were in different configurations (BS is always Isolated_Damped, ETMY had it's sensor correction turned off). This was a large earthquake that came up quickly (third plot shows ETMY Z STS 30-100 mhz BLRMS and ITMX WD trigger) , but for now it looks like ITMX is behaving like the other platforms.

Images attached to this report
H1 TCS (ISC, TCS)
aidan.brooks@LIGO.ORG - posted 11:29, Monday 01 August 2016 (28776)
Common and differential ITM lens estimates for O1

The following is a short calculation of the ITM lensing estimates for O1 for the recycling cavities based on the measurements from the HWS.

CO2power: [X = 0.225W, Y = 0.0W]
dS/dP_co2 = [+62E-5 D/W, ?? D/W]
Lens = [14.1E-6 D, 0 D]
 
Arm Power ~ 100kW
absorption: [X = 2.5E-7, Y = 2.8E-7]
SelfPower: [X = 0.025W, Y = 0.028W]
dS/dP_self = 4.87E-4 D/W
Lens = [12.2E-6 D, 13.6E-6 D]
 
Static Lenses = [-12E-6, +1.7E-6]
 
So net lenses are:
 
X = (14.1 + 12.2 -12) uD = 14.3 uD
Y = (0 + 13.6 + 1.7) uD = 15.3 uD
 
Common Lens = 14.8 uD (or 67.6 km equivalent)
Diff Lens = 1 uD
H1 ISC
kiwamu.izumi@LIGO.ORG - posted 10:44, Monday 01 August 2016 - last comment - 08:54, Wednesday 03 August 2016(28772)
PI models will be restarted tomorrow to accommodate drum head modes control

WP 6022

I have updated the PI models (28462) in order to accommodate four excitation paths for test mass' drum head modes. The h1omcpi and h1susprocpi models will be restarted tomorrow. The modification will be used

  1. as a part of the OMC beacon (or deacon) dither alignment control, and
  2. as a part of study on the mobility of test mass's mechanical modes.

This update actually involves not only h1omcpi and h1susprocpi models but also h1omc. However, in light of the upcoming in-vac activity with the OMC, we will hold off the update on h1omc so that we can recover the interferometer with least confusion. The update on h1omc will go in some time later once we recover the interferometer.


[eLIGO amplitude locked loop]

Here is a screenshot of the digital amplitude locked loop of a drum head mode that had been used in eLIGO.

This algorithm is imported to the current PI models. One update we might additionally implement in some future is a clock recovery with iWave instead of the clipping-based clock recovery.

 

[Modification on h1omcpi]

h1omcpi has one update i.e., normalization of the OMC DC signals.

I modified one of the down conversion channels, chan 8, to have a normalization using the OMC DCPD SUM. It is show in the orange-shaded region. This signal is sent to the susprocpi model and processed to generate feedback signals for the test masses.

 

[Modification on h1susprocpi]

Here is a screenshot of the top level of h1susprocpi in which a parallel excitation block for the drum head modes (a pruple block at the bottom) are shown.

This block contains four identical amplitude locked loop for generating excitation signals. The feedback outputs (shown as yellow tags) are summed on the right hand side of the output matrix so that they are sent to the test mases to excite the drum head modes. Also the rms information of a selected mode will be sent back to h1omc through an PCIe communication so that it can be used as a beacon alignment error signal. The contents of the purple block look like this:

As seen in the upper right, one can select which mode to use for the OMC alignment. The red blocks on the left hand side contain the function blocks as seen in the following screenshot.

The amplitude error signal is generated by a combination of an Abs block and lowpass filter. Then it is fed back to the output of the clock generator (which is based on the clipping technique as was done in eLIGO). The bandpass filter on the left allows one for selecting a mode out of the four modes. In addition, we placed an iWave block so that we can read out the frequency directly. A future expasion would be to use the output of the iWave block to generate the clock or sinusoidal excitation signal instead of the clipping-based one.

Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 08:54, Wednesday 03 August 2016 (28834)

This change has been implemented yesterday (28826).

H1 GRD (SEI)
thomas.shaffer@LIGO.ORG - posted 10:30, Monday 01 August 2016 (28775)
Fixed bug in SEI configuration nodes

The Problem: The SEI configuration nodes have been in error since Friday at 2:58 local due to a bug in the WD decorators, and a bit of oversight by the one who coded that part (me). The regular SEI guardian nodes were tripped and then someone requested the config nodes to change, but these config nodes were not designed to be changed when everything was tripped. The decorator that caused the isse is just copied code and so it tried to jump to a state that didn't exist. Glad this was found before O2.

The Fix: removed all of the decorators that check on WD's, isolation, and damping of the regular nodes. Jim W and I talked and decided that it wasn't really necessary for the config nodes to even have to watch that, so lets lose them. Changing the config states while it is tripped or isolating was thought to maybe be an issue before, but doesnt seem to pose a problem anymore.

H1 SEI (SEI)
cheryl.vorvick@LIGO.ORG - posted 10:13, Monday 01 August 2016 (28773)
documenting current HAM6 SEI setup today - hopes for tomorrow
Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 09:51, Monday 01 August 2016 (28769)
Monday Morning 8:30 Meeting Notes

Status:  Discussed smoke from nearby fires.  DetChar F2F starts this morning.  HAM6 vent plan for the week--most likely crack bolts on HAM6 on Tues, BUT we will only start this work when we confirm no dust/smoke issues in the LVEA.

Due to upcoming vent work, we did not go through status of the SEI & ISI.

Bake RGA at end station might start today (Kyle)

HAM6 ISI:  should be isolated or atleast damped (see Hugh)

For Tuesday Maintenance:  Timing work and PI model work were mentioned as primary tasks.  PSL work will cover Mon/Tues per work permit.

For any tours, please remember to fill out a work permit & check with the operator as to whether it is OK (if there is active work in an open chamber we may want to limit tours at that time.)

Visitors This Week:  DetChar people, visitors from China (Fred), KAGRA visitors for PCal (Kiwamu), Krishna/Micahel from UofWA (Hugh)

H1 PEM
corey.gray@LIGO.ORG - posted 09:16, Monday 01 August 2016 - last comment - 14:16, Monday 01 August 2016(28770)
Trends Of LVEA Dust Monitors

Attached are trends of the LVEA Dust Monitors.  

On the 24hr trend, there was a little bit of dust in the LVEA between 8am-1pm, but in the cleanroom, were have been near zero for the last 24 hrs.

On the 4-day trend, the only dust in the HAM6 cleanroom was from technical cleaning on Friday.

Jeff is going to take some more readings outside.

Images attached to this report
Comments related to this report
jeffrey.bartlett@LIGO.ORG - 10:21, Monday 01 August 2016 (28774)
   Checked particle counts from outside and inside the OSB and in the LVEA. 

   Summary: Outside air is currently around 330,000 for 0.3um particles. As one moves through the OSB towards the LVEA the counts drop as the building air filtration system does its job. Counts in the LVEA range from 1290 to 270 03.um particles. The attached spreadsheet has the complete readings for all sampled locations. 

   Will continue to monitor as the fire continues to burn.   
 
Non-image files attached to this comment
jeffrey.bartlett@LIGO.ORG - 14:16, Monday 01 August 2016 (28783)
   Second Mid-day check of air around the site shows air quality is not improving. Fires continue to burn or smolder and light wind is not helping clear the air. Posted are the 13:00 hours data. Outside and inside counts are up considerable. Particle counts inside the cleanrooms remain well within acceptable levels for in chamber work.   
Non-image files attached to this comment
LHO General
corey.gray@LIGO.ORG - posted 08:22, Monday 01 August 2016 (28767)
Status Of Nearby Fire: No Issue At LIGO & Hanford Site

During the drive in one can certainly see a smoldering Rattlesnake Mountain (did not see much activity [i.e. active fires/personnel] by eye).  From our End-Y building looks like the fire was about 6-7 miles away.

Fred mentioned there were no issues mentioned on the radio with regards to the fire and the Hanford Site.  Ryan pointed me to the hanford.gov advisory site (there is a banner link which you can get the following info about yesterday's nearby fire):

 

Brush Fire Causes Closure to State Route 24  
There are no impacts to Hanford work schedules at this time.

A brush fire that started off the Hanford Site has spread to the Arid Lands Ecology Reserve (ALE) area of the Hanford Site west of State Route 240. As of 6:00 p.m. on Sunday, July 31, 2016, State Route 24 closed from milepost 14 to milepost 39 at the junction of State Route 240. State Route 24 will remain closed and an estimated time to reopen is undetermined. Hanford employees will need to use alternate routes.

We will continue to monitor the situation and update this message if conditions change.

For specific questions regarding company policy contact your manager.

Images attached to this report
H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 02:40, Monday 01 August 2016 (28766)
Rattlesnake as seen from the site.

Terra, Nutsinee

Images attached to this report
H1 ISC
stefan.ballmer@LIGO.ORG - posted 23:20, Sunday 31 July 2016 - last comment - 12:49, Monday 01 August 2016(28765)
LSC-PR_GAIN back at 30 for 50W

Terra, Evan, Stefan

With the spot move script from last alog we could reliably maximize the recycling gain. We reached 30 (as measured by LSC-PR_GAIN - Evan claims this is more like 35).

The instability in AS90 could be removed by manually aligning the SRM - but POP18 got worse when doing so.

Interestingly - the same move that fixes the recycling gain at 50W, has almost no impact on the recycling gain at 2W.

 

For reference, the last lock loss was at about 6:15 UTC on Aug 1st.

We had to adjust the soft loop gains to

            ezca['ASC-DSOFT_P_GAIN'] = 0.5 # 3 killed it
            ezca['ASC-DSOFT_Y_GAIN'] = 3  # oscillates at lower UGF when much lower
            ezca['ASC-CSOFT_P_GAIN'] = 0.5 # designed differently
            ezca['ASC-CSOFT_Y_GAIN'] = 3  # oscillates at lower UGF when much lower
 

Comments related to this report
stefan.ballmer@LIGO.ORG - 12:49, Monday 01 August 2016 (28777)

Estimating the spot mosition move required to regain the recycling gain.
====================================================

Conclusion: The corner spot moved by about 8mm in pitch and yaw.

The move direction (to improve the recycling gain) in each arm is a soft translation of the beam axis towards the other arm (yaw), as well as up (pit).
====================================================

 

We used two methods to estimate the spot move on the ITM/BS/PR3.

A) using IM4 angle readback:

Since PR2 doesn't move, looking at how much IM4 moved allows us top simply project the move on PR3. The effecive lever arm (incl. the PRM and PR2 lens effects) is 151.4m.

To regain the best recycling gain we moved IM4 26.2urad in pit and 25.5urad in yaw. This corresponds to (note the factor of 2 for beam steering vs optic angle)

IM4 PIT projection on PR3: 7.9337mm
IM4 YAW projection on PR3: 7.7217mm
 

B) using the test mass oplevs:

The move recorded by the test mass oplevs (in urad) are (EX,EY,IX,IY) are:

PIT:
    1.8700
    1.6500
    2.5000
    2.0600
YAW:
    2.7000
    2.8200
    3.3200
    3.2600

Since it is always hard to get a clean soft that is not masked by residual hard, we project out any spurios hard move.

i) Without removing the hard:
ITM:-1.9858mm, ETM:12.091mm
ITM:0.91049mm, ETM:7.2637mm
ITM:2.4191mm, ETM:10.6978mm
ITM:6.315mm, ETM:6.329mm
 

ii) removing the hard by forcing the ETM and ITM spot move to be the same:

i.e. we force the spot move to be the same on ETM and ITM:
ITM:4.5198mm, ETM:4.5198mm
ITM:3.8466mm, ETM:3.8466mm
ITM:6.2452mm, ETM:6.2452mm
ITM:6.3215mm, ETM:6.3215mm
 

iii) forcing the spot to be zero on the ETM (that's how we think we tuned the SOFT loop sensors):
ITM:8.4743mm, ETM:0mm
ITM:7.1944mm, ETM:0mm
ITM:11.674mm, ETM:0mm
ITM:11.7903mm, ETM:0mm

The reality probably lies between ii) and iii)

 

FInally, note that the control signal recorded in alog 28764 can't be used because of all the radiation pressure torque effects.

 

Attached is a snapshot of the arm oplev motion.

Images attached to this comment
H1 ISC
stefan.ballmer@LIGO.ORG - posted 22:23, Sunday 31 July 2016 (28764)
Script for moving the whole interferometer, changing the corner spot position

We reached 50W relatively stable and reliable, and were able to use the POP A offsets to drag the interferometer around.

I recorded that particular alignment vector, and stuck it into a script. This now allows moving the full interferometer in this degree of freedom very rapidly, without taxing the soft loops too much.

We see a clear recycling gain dependence on this degree of freedom. However, one oddity is that when we reach the maximum recycling gain, the AS90 buildup becomes very ratty. I am wondering whether we get close to clipping somewhere with this move, or whether it is related to our SRM alignment dither.

The alignment vector for this move is

# pit
gppr3=0.07
gpprm=-13.2
gpim4=-325
gpsr2=-2.39
gpsrm=3.2
gpex=-0.7
gpey=-0.7
gpix=-0.45
gpiy=-0.35

# yaw
gypr3=0.028
gyprm=11.07
gyim4=61.22
gysr2=2.22
gysrm=2.74
gyex=-0.5
gyey=+0.5
gyix=+0.32
gyiy=-0.31
 

Non-image files attached to this report
H1 ISC
stefan.ballmer@LIGO.ORG - posted 19:22, Sunday 31 July 2016 (28763)
Test mass ASC offloading x-over at 0.1Hz

Sheila, Stefan

Based on yesterday's measurement, the ASC PUM to TOP x-over was at 0.002Hz and 0.0029Hz (before the 10dB increase in the script).

I added gains of 50 for pitch and 34.5 (for now in the L1_LOCK modules) to move this x-over to 0.1Hz.

The only loops for which this 0.1Hz offload is critical are the soft loops. Thuis I added z=0.01Hz:p=0.1Hz lead filters to all soft loops. I also turned the soft loop bandwidth up by 3x.

The guardian now sets those gains before turning on the soft loops - and sets them back in the down state.

We still should do some more loop tuning for the soft loops - their response should be sped up

We got to 50W - but lost it when moving the PRM - the soft loops seem to be still too slow to follow, resulting in the Izumi-Ballmer instablility.

H1 General
cheryl.vorvick@LIGO.ORG - posted 16:11, Friday 29 July 2016 - last comment - 09:24, Monday 01 August 2016(28744)
Ops Day Summary:

State of H1: earthquake, unlocked, ISC_LOCK set to Down, IMC_LOCK set to Offline

Activities:

Since EQ:

Comments related to this report
cheryl.vorvick@LIGO.ORG - 16:18, Friday 29 July 2016 (28745)

SEI_CONF guardian is set to EARTH_QUAKE

Hugh and I opened the Blends MEDM and changed the SEI_CONF.

Should be returned to WINDY_NO_BRSY when locking resumes.

MEDM attached

Images attached to this comment
thomas.shaffer@LIGO.ORG - 09:24, Monday 01 August 2016 (28771)

Be very careful here! Even though the SEI_CONF says that it is in the correct state, it also has 10 notifications saying that 10 of its suborrdinate nodes are in ERROR. So it actually never got to its EARTHQUAKE state fully. If Guardian nodes are ever in error, someone who knows how,  needs to fix them. In this particular case it is a bug that I will post an alog about soon.

H1 ISC
jenne.driggers@LIGO.ORG - posted 13:38, Friday 29 July 2016 - last comment - 08:07, Wednesday 17 August 2016(28737)
OMC alignment turned off

The OMC alignment servos keep turning on, even though the OMC guardian is paused.  I found that it gets turned on in engage_wfs_centering whenever we do any ASC since it's in a generate states function.  So, I have commented out that line, but we must uncomment it when we have the OMC back and are ready to use it again.  It is currently line 113 in ISC_GEN_STATES.

Comments related to this report
hugh.radkins@LIGO.ORG - 08:47, Monday 01 August 2016 (28768)

Maybe this should have a work permit to make sure this isn't forgotten; or at least some mechanism to undo the change in a timely manner.

corey.gray@LIGO.ORG - 08:07, Wednesday 17 August 2016 (29145)

Not sure when it happened, but looks like this has been restored to normal & uncommented (probably some time after the HAM6 work last week).

Making a note in Operator Sticky Notes wiki.

Displaying reports 55121-55140 of 83119.Go to page Start 2753 2754 2755 2756 2757 2758 2759 2760 2761 End