Displaying reports 66621-66640 of 83068.Go to page Start 3328 3329 3330 3331 3332 3333 3334 3335 3336 End
Reports until 01:49, Wednesday 25 February 2015
H1 TCS (ISC)
kiwamu.izumi@LIGO.ORG - posted 01:49, Wednesday 25 February 2015 (16905)
TCS X CO2 was off, turned it back on

Looking at some of the LSC demodulated signals, I found that the RF phases changed by some noticable amount. I then found that the CO2 laser on ITMX had been tripped at 13:51 local (or 21:51 UTC) today. I went to the rack at the floor and saw that a red indicator for 'TEMP' was on at the front panel. Power cycling the unit with the key untripped it. I pressed the red button for opening the gate and confirmed that the laser power was back to the nominal of 210-ish mW in the medm screen. The attached is a one day trend of the laser power, calibrated into the power at ITMX.

I did not do any deep investigations at this point.

Images attached to this report
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 17:23, Tuesday 24 February 2015 (16904)
CDS Maintenance Summary

ISC/SUS Code Changes

Daniel, Jeff, Kiwamu:

During the maintenace period the following models were restarted for new code: h1lsc, h1omc, h1alsex, h1alsey, h1asc, h1susetmx, h1susetmy, h1susitmx, h1susitmy, h1oaf, h1susbs. LSC to OAF Dolphin IPC channels were removed from the LSC, Daniel renamed the IPC channels being used by the OAF to their CAL equivalent channels.

DAQ Restart

To support the code changes and the new guardian system several DAQ restarts were performed.

Guardian Reboot

Jamie and Dave:

13:34PST the h1guardian0 machine was rebooted to test its autostartup. No problems were found.

RFM Diagnostics

Daniel, Jim, Dave:

To test the remaining IPC errors on the ETM SUS models, an ISC model (we chose PEM) was temporarily changed to read the same RFM IPC. The ISC receiver shows zero errors, so the problem appears to be within the SUS front end only. Investigation is continuing.

We perfomed some RFM tests on the LHO DTS, verifying the RFM loop transit direction.

H1 SUS
stuart.aston@LIGO.ORG - posted 17:16, Tuesday 24 February 2015 (16896)
SDF Monitoring rolled-out for BSFM Suspension
[Stuart A, Betsy W]

After earlier using the front-end to take a safe SDF snapshot of the Beamsplitter Suspension (see LHO aLOG entry 16886), thus stripping out the redundant read-only channels and alarms, I used Jamie's script to set all channels to be monitored (see LLO aLOG entry 15907) i.e.

sdf_set_monitor 1 h1susbs_safe.snap.

I've since manually edited the SDF snapshot setting channels we do not wish to monitor, which are essentially consistent with those reported at LLO (see LLO aLOG entry 15987).

Finally, I've checked the safe SDF snapshot into the svn:
/opt/rtcds/userapps/release/sus/h1/burtfiles/
M        h1susbs_safe.snap

Need to monitor for changes in the BSFM configuration as commissioning/locking continues overnight...
Images attached to this report
H1 CDS
patrick.thomas@LIGO.ORG - posted 17:06, Tuesday 24 February 2015 - last comment - 17:11, Tuesday 24 February 2015(16902)
Updated Conlog channel list
Added 352 channels. Removed 302 channels. There are still 7 channels unmonitored:

H1:GRD-ISI_ETMY_ST2_REQUEST_S
H1:GRD-ISI_ETMY_ST2_STATE_S
H1:GRD-ISI_ETMY_ST2_STATUS
H1:GRD-ISI_ETMY_ST2_TARGET_S
H1:GRD-ISI_ITMY_ST1_LOGLEVEL
H1:GRD-ISI_ITMY_ST1_MODE
H1:GRD-ISI_ITMY_ST1_NOMINAL_S
Comments related to this report
patrick.thomas@LIGO.ORG - 17:11, Tuesday 24 February 2015 (16903)
They connected, just took a little while.
LHO VE
kyle.ryan@LIGO.ORG - posted 16:51, Tuesday 24 February 2015 - last comment - 10:14, Wednesday 25 February 2015(16901)
Pumped HAM1 to rough vacuum (4 hours pumping = 0.3 torr at pump inlet, HAM1 pressure???)
Kyle, Gerardo 

Added remaining bolts to HAM1 West door and finished torquing -> Soft-closed GV5 and GV7 (GV5 hard-closed on its own at only 20 psi) -> Pumped HAM1 with scroll pump via vent/purge valve (as such, atmospheric pressure remains on air-side of closed vent/purge valve) -> Opened GV5 and GV7 

Richard M. is investigating getting signal cables to HAM1 gauges 
Comments related to this report
kyle.ryan@LIGO.ORG - 10:14, Wednesday 25 February 2015 (16910)
Kyle, Gerardo

~0910 hrs. local, Wednesday morning -> Installed temporary pirani gauge controller on top of HAM1 so as to view pressure until CDS cabling gets installed -> HAM1 now showing 0.4 torr which is as expected.

In retrospect, I should have not pumped HAM1 without this to monitor -> I had reasoned that the view ports are exposed to 2 atmospheres (gauge) differential (both directions) during bench testing so are considered "safe" -> I now consider the failure mode whereby a view port could have cracked during pumping resulting in a measurable change in the pump down curve -> In this scenario we would not have opened GV5 and GV7 -> Lesson learned 
H1 SUS (ISC)
stuart.aston@LIGO.ORG - posted 16:47, Tuesday 24 February 2015 (16891)
Roll-out of AS WFS damping of QUAD roll modes at M0 stage (WP#5069) - ECR E1500090
[Stuart A, Jeff K]

After yesterday’s preparation and discussion (see LHO aLOG entries 16874 and 16868), this morning we completed the roll-out with the aim of providing AS WFS damping of roll modes, for all QUADs, as follows:

(1) LSC, OMC and ASC models were restarted (see LHO aLOG entry 16893), which enabled the necessary IPC/RFM senders. However, there were some channel name changes to deal with...

(2) ETMs H1:LSC-ETMX_DARM_ERR renamed to H1:OMC-ETMX_DARM_ERR (same goes for ETMY).

(3) ITMs H1:LSC-OAF_DARM_ERR renamed to H1:LSC-ETMX_DARM_ERR (originated from LLO using the calibrated version of DARM ERR for ITMs and raw for ETMs).

(4) Svn'd up the common MEDM screens (after remotely committing them from LLO):
/opt/rtcds/userapps/trunk/sus/common/medm/quad/
U       SUS_CUST_QUAD_M0_DAMP_MATRIX.adl
U       SUS_CUST_QUAD_M0_DAMP_MODE.adl
U       SUS_CUST_QUAD_OVERVIEW.adl

(5) Removed LLO's Tidal implementation from the Overview Screen (see LLO aLOG entry 16753).

(6) Rebuilt, installed and restarted the h1susetmx, h1susetmy, h1susitmx, h1susitmy models.

(7) Noticed some white boxes on Overview Screen, which were site specific to L1, so I fixed these with a $(IFO) substitution and re-committed SUS_CUST_QUAD_OVERVIEW.adl to the svn.

Screen-shots below show the updated MEDM screens.

This should help inform ECR E1500090 and Integration Issue #1015, in determining which AS WFS channels are most suitable for damping QUAD roll modes at each site.
Images attached to this report
H1 ISC (CAL, DetChar, SUS)
jeffrey.kissel@LIGO.ORG - posted 16:45, Tuesday 24 February 2015 (16900)
Removed IMC X Channels from MC2 Model
J. Kissel

During the furious model re-arrangement this morning, I took the opportunity to remove IMC X channels from the top level of the MC2 front end model. After the changes to the front end model, this required a recompile, reinstall, restart and restore. The IMC is now locked happily.

I want to remove these channels because they are now to be derived in the CAL model, like every other of the IFO's cavity length signals. I'm still in the process of creating a set calibration filter that makes sense for the actuation chain. I would copy and paste what's in the IMC X bank, or what's in the OAF bank, but it turns out the filters that have been in use since Apr 2013 (LHO aLOG 5945) have been wrong. Namely, the M3 stage filter is a copy of the M1 stage filter. The M3 stage filter should (at least) fall off as 1/f^2, which, of course, the M1 stage filter does not. Further, this has been copied, in one way or another to every other place where we've tried to calibrate the IMC length signal since, i.e. the OAF model. 

So, I'm trying to break the cycle, and stick in sensible filters, and even update them with the what ever current non-sense damping scheme we're using by applying the real damping filters and gains to the SUS model. BUT I'm running onto the classic problem of turning something in matlab into something that foton will chew on. Mostly it's because basic functions like minreal and zpkdata are not cancelling right-half-plane poles in a sane way. I'll bang my head on this more tomorrow. If you want to fight with me, check out
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/MC2/Common/H1SUSMC2_GlobalTFs_to_Foton_20150224.m

Two plots attached:
- the bad IMC X / OAF calibration filters.
- What the transfer function should look like for MC2 with the current filters and gains.

Screenshot shows that the three outputs near the bottom of the main, yellow, MC2 block -- M1, M2, and M3 _LOCK_L_Outs -- are now terminated.

I've committed the changes to the userapps repo,
jeffrey.kissel@operator1:/opt/rtcds/userapps/release/sus/h1/models$ svn commit -m "Removed IMC X calibration channels from top level. These will now be calcuated in CAL-CS." h1susmc2.mdl 
Sending        h1susmc2.mdl
Transmitting file data .
Committed revision 9902.
Images attached to this report
Non-image files attached to this report
H1 SEI
jim.warner@LIGO.ORG - posted 16:45, Tuesday 24 February 2015 (16897)
GS-13 Gain settings on ISI's

It has been noticed in the past that ISI's sometimes trip when de-isolating. This causes Guardian to pause and wait for the operator to untrip the watchdog, which gets inconvenient when trying to bring multiple chambers to a de-isolated state. The GS-13s seem to be the main culprit, as the BSC St1's don't seem to trip when de-isolating. We may want to try running the GS-13's in low gain, to reduce the odds of tripping on them. I looked at the perfromance of ITMX ISI with the GS-13's in 3 different states, our nominal high gain mode, low gain and "ultra-low" (see Hugh's post 16416 and subsequent comments by JeffK) . It looks like in an isolated state, none of these configurations hits ADC noise below 100hz (see first attached plot, red is high gain, blue low, green ultra-low, ADC noise is brown(?)), although "ultra-low"  looks like it might be getting close above 100hz where the ISI is not actively isolating. I also looed at the performance of the ISI in the low and high gain states (second figure, dashed are high gain, solid are ultra-low) and it looks like even in ultra-low gain we still have good performance. I looked at HAM6 (third plot, red is high, blue low, green ultra-low, brown is ADC) as well, not in as much detail, but I suspect we could run in low gain on the HAM's, too.

Images attached to this report
H1 SUS
keita.kawabe@LIGO.ORG - posted 16:32, Tuesday 24 February 2015 (16895)
Damping M0 PIT of ETMX

Summary:

A new ETMX M0 P damping filter was made, together with a new damping gain (first and second attachment), to make the L1 length to L3 PIT coupling at 0.5Hz smaller.

This makes the coupling at 0.5Hz smaller by 8dB or so, but it increases the coupling at 5.5Hz and 3.5Hz, and overall it seems to give us about a factor of 1.5 or so of reduction on average.

This was only done to ETMX, and moving to the new damping of course affects the WFS, so I left it with the old configuration.

Details:

(All of the measurements were made without oplev damping.)

People say that a higher BW WFS is necessary during CARM reduction, and that oplev damping is necessary for ALS. The problem could be a large (and noisy) length drive coupled to the angle.

Instead of optimizing the top mass damping for making test mass as quiet as possible without drive, I tried to minimize the coupling from L1 length drive to L3 PIT. I injected a [0.2Hz, 0.8Hz] uniform noise to L1 Lock L filter so the L1 coil drive does not exceed +-5000 counts or so peak to peak (otherwise the resulting PIT motion becomes too large so the OPLEV starts to miss an entire quadrant).

I started by simply making the gain of the existing filter up or down. This didn't do much, as the steep phase slope of 0.5Hz boost filter makes it such that when you gain something at 0.5Hz you quickly loose at 0.4Hz and 0.55Hz by gain peaking.

After some trial and error I ended up with a broader version of the original filter (second attachment).

The third attachment shows my old/new/old/new test (Old = Red traces, FM2 on, FM3 off, gain = -1. New = green traces, FM2 off, FM3 on, gain=-4).

The top panel shows the transfer function from the L1 length drive to the oplev PIT, and the bottom panel is the oplev PIT spectrum with the length drive into L1. As you see the TF shows the reduction at 0.5Hz but some increase due to gain peaking at higher and lower frequency, and the overall RMS reduction in the TM angle due to the length drive is about a factor of 1.5.

A reduction in the RMS of the test mass angle when we're not driving L1 length is not large, but it is reduced by a small amount (4th attachment, red old, green new).

It would be very difficult to reduce the l2p coupling at 0.55Hz just by the top mass local damping, as there's a sharp dip in the OLTF of the top mass damping that should come from the lower suspension structure (5th attachment, blue=OLTF, red = top OSEM P to oplev P, both measured while driving M0 DAMP_P_EXC). A gain of -3 or so with the new filter to make the damping less aggressive, combined with some other means of decoupling, seems necessary to obtain an advanced awesomeness.

Images attached to this report
H1 SEI
hugh.radkins@LIGO.ORG - posted 16:27, Tuesday 24 February 2015 (16899)
HEPI Pump System Service/Upgrade/Improvement at EndY BSC10 ETMY

Looks like a little upkeep can go a long way!  Still waiting for more time on system to collect high resolution spectra for comparison but the early views look like the ASD of the Pump Pressures are lower by several factors and the remaining coherences still around after the controller changes JeffK engineered have now all gone away.

This was achieved by

1) strapping the common legs of the Pos & Neg power supply to ground.  Verbose: The + side of the Neg voltage output is tied to the - side of the Pos voltage output but this was not explicitly strapped to the green ground plug.  When I did this before taking the Pump System down, the swing of all pressures dropped immediately by 4x  at least--See 1st attachment: 10 minutes of second trends.  I have tried this at the corner station as McCarthy suggested long ago but I did not get the same clear affect there--needs more study.

2) Charging up all the Accumulator Bladders--Most of these were extremely low and needed full charging of N2.

See the second attachment, 3 hours of minute trends of the pump station pressures, remote pressures from the BSC10 and their difference and the controller Out signal, for the maintenance period play-by-play.  1) Grounded Power Supply 2) Maintenance work while pump is off: grease motor, check Accumulator pressures, Bleed laminar flow resistors. 3) System back up while retreaving full N2 Bottle 4) Pump back off while Accumulators are charged 5) Pumps back up when complete.

Note: Obvious change in all pressure signals and the reduction of the CONTROL_VOUT which drives the motor from the quieter DIFF_PRESS.  I don't know if it is obvious or just wishful thinking but maybe all the signals are quieter with the appropriately changed Accumulators.

Most of the Accumulators were not within the spec of being charged to 60-90% of operating Fluid-Side pressure.  One Accumulator on the Pump Station was leaking and held no charge.  I was able to tighten the Schraeder Valve and it holds N2 now.

I will post comparative coherence plots in a few more hours.

Images attached to this report
H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 16:19, Tuesday 24 February 2015 (16898)
Daily Ops Summary

= Ops Summary =

7:30 Richard and Ken to Mid X, End X, End Y to do heater work
7:45 Let in truck for ldas work
7:50 Jeff in LVEA PSL area
8:03 Jeff and Peter K. to PSL
8:17 Jason and Ed to PSL
8:28 turned off EY dust monitor. The alarm goes off constantly even when nobody's in the VEA.
8:31 Doug to LVEA (OPLEV work)
8:45 Kyle to bolt HAM1 west door
     Filiberto running cable from HAM7
     Betsy to LVEA
9:08 Andreas to Betsy in the LVEA
     Sudarshan and his guest to LVEA for a tour
9:15 OMC down
     Travis to LVEA (3IFO work)
9:35 Sudarshan to End Y
9:49 Doug back
9:52 Hugh at EY - HEPI pump down
     Greg to LVEA (3IFO work)

    Model reboot going on all morning

10:07 Betsy back o LVEA
10:31 Jeff B., et al. out of PSL
10:41 Picomoter HAM1, 3 disabled
10:50 Jeff B., et al. out of LVEA
11:00 Sudarshan back
11:26 Sudarshan to LVEA - put PEM patch panel on IOT2R and ISCT6 (WP5075)
12:46 Karen to Mid Y
12:51 Jeff B. to End X (Not VEA area)
13:15 Travis back to LVEA
13:37 Dave rebooted Guardian
13:48 Karen leaving Mid Y
14:03 Jeff B. to clean area
14:04 Ken the Electrician to End X
14:17 Jeff B. back
14:21 Ken out of End X
15:48 Travis and Betsy to LVEA
16:02 Kyle opening gate valves ~ 15 mins
16:06 Mitchell to LVEA
16:23 Mitchell back

Hard close on GV-5 and soft close on GV-7 all day. No green beam on the monitor.
Several systems have been brought down/rebooted
Caltech server is dead around 3:30 - 4 pm Can't get data from ligo-wa. nds.ligo left me hanging.

Happy Maintenance Day.

H1 ISC
daniel.sigg@LIGO.ORG - posted 16:03, Tuesday 24 February 2015 - last comment - 19:08, Wednesday 25 February 2015(16893)
OMC/LSC Model Split

(Kiwamu, Dave, Jim, Jeff, Daniel)

The LSC and OMC models have been re-partitioned, so that DARM and CARM (to the ifo) are processed in the OMC.

The current processing times are:

  mean (µs) max (µs)
lsc 30 37
omc 13 14
alsex 32 35
alsey 32 34
iscex 5 7
iscey 5 7
susetmx 48 50
susetmy 50 56

Only the OMC sends data to the ETMX/Y, and only ISCEX/Y send data back to the LSC. With no more than 13µs processing time one might expect that there is plenty of time to send the DARM signal to the ETMs without an IPC errors. But no! We still have one every couple of seconds. This is down from a ~10Hz error rate. Strangely, the ALS, which picks up the common tidal signal and is located after the SUS in the fiber loop, does not see any errors. We now suspect a problem at the receiving end. More investigations ongoing.

Comments related to this report
jeffrey.kissel@LIGO.ORG - 19:08, Wednesday 25 February 2015 (16926)CAL, DetChar, INJ
A few comments on the DARM topology changes that were made as a result of this split:

* Now that the OMC's DCPD's are fed into the DARM filter bank and the output is sent directly to the suspensions, we have removed one, inter-process communication, 16 [kHz] cycle (61e-6 [s]), delay or the equivalent of 22 [deg] of phase loss at 1 [kHz] (among other benefits like decreasing the turn-around time on the LSC computer, removing a whole bunch of will-never-be-needed input and output matrix elements, and just general cleanliness).

* The location / topology of where MICH, and SRCL feed-forward corrections are made has changed. The infrastructure for PRCL feed-forward correction does not exist (why? Every interferometer I know has *some* that has been corrected for in the past...).
Now, the MICH, and SRCL control signals are picked off, feed through a "MICHFF" or "SRCLFF" bank, respectively, and the outputs are sent to the LSC model's LSC output matrix. The LSC output matrix still have outputs for the ETMs, but their outputs are now fed via shared memory to the OMC model, and added in independently and respectively directly after the OMC model's LSC output matrix.

* Similarly, any *other* corner station photo-diode signals (POP, REFLA, POPAIR, REFLAIRA, REFLAIRB, TRX, TRY and their various combinations, REFL9, The Digitized Additive Offset for CARM, etc.), which can be chosen in the LSC model's LSC input matrix are fed over IPC directly to the output of the OMC model's input matrix.

* That means the location of feed-forward, with respect to hardware injections has changed, but this does not affect their impact on the loop. It has *not* changed with respect to the calibration lines, i.e.  the calibration lines are still added *before* DARM_CTRL is picked off.

I attach an updated diagram (the .pdf) of how the DARM path gets distributed about the interferometer. This updated diagram also lives here
/ligo/svncommon/CalSVN/aligocalibration/trunk/Common/Documents/T1300088
Images attached to this comment
Non-image files attached to this comment
H1 SEI (INS)
jim.warner@LIGO.ORG - posted 15:50, Tuesday 24 February 2015 (16894)
Last 3IFO BSC-ISI in the can

GregG, KenM, MyronM, TJS, JimW

The last 3IFO BSC-ISI went in the can this afternoon. Whole operation went off relatively smoothly. The can is now sitting by the door, waiting for transport to it's final resting place in the LVEA. 

H1 PEM (FMP, PEM, SYS)
richard.mccarthy@LIGO.ORG - posted 15:08, Tuesday 24 February 2015 (16892)
EX EY Heaters
Installed the Variac system for the VEA heaters at both end stations.  Had quite the temperature excursion (69degF) due to the feed back to the controller not being properly setup For some reason in this state the Variacs go to full on.  We corrected this and the system is now functioning.  We still have problems at EX.  Half of the heater elements are bad so we are only running on a single stage at most.  I have Y end set to 7mAmps and X to 8mAmps.  Will probably turn Y down as the temperature settles to require less cooling for control.   At some point we will convert over to the heater being in the control loop but that will wait.
H1 SUS
stuart.aston@LIGO.ORG - posted 13:01, Tuesday 24 February 2015 - last comment - 10:34, Monday 23 March 2015(16886)
Roll-out of independent switching of BSFM M2 stage coil driver states (WP#5070) - ECR E1500045
[Stuart A, Jeff K]

As was recently carried-out at LLO (see LLO aLOG entry 16663), during this mornings maintenance period I was able to roll-out independent switching of BSFM M2 stage coil driver BIO filter states, as outlined in ECR E1500045. Hopefully, this should provide commissioners with the capability to smoothly (without breaking lock) transition from acquisition to the low-noise state coil driver, just for the Beamsplitter M2 stage, which was problematic at LLO.

This was implemented as follows:

(1) Svn'd up the common library parts:
/opt/rtcds/userapps/trunk/sus/common/models/
U       STATE_BIO_MASTER.mdl
U       BSFM_MASTER.mdl 

(2) Svn'd up the common MEDM screens:
/opt/rtcds/userapps/trunk/sus/common/medm/bsfm/
U       SUS_CUST_BSFM_OVERVIEW.adl
U       SUS_CUST_BSFM_BIO.adl
U       SUS_CUST_BSFM_M2_EUL2OSEM.adl

(3) Rebuilt, installed and restarted the h1susbs model without incident.

(4) Noticed some white boxes on EUL2OSEM Ramping Matrix MEDM screen, which were site specific to L1, so I fixed these with a $(IFO) substitution and re-committed SUS_CUST_BSFM_M2_EUL2OSEM.adl to the svn.

(5) 4 new EPICS channels are present for the M2 BIO states, as well as an additional 4 for the test coil enable, all which need to be configured:
- All coil enables were set to 1, and the BSFM M2 BIO state was set to the 'default' of 1, as I was informed by Jeff K was being used by commissioners n.b. LLO 'default' acquisition is BIO state 2, and low-noise is BIO state 3 (see LLO aLOG entry 16565). 

Screen-shots below show an example use case for the EUL2OSEM Ramping Matrix. with green indicating a nominal state i.e. set values and current value are equal, red when a new value has been set, and yellow after activating the LOAD MATRIX ramping in over the required duration.   

Finally, I took a new safe SDF snapshot using the same front-end technique I use at LLO:

- Transition the Suspension to a SAFE state via Guardian
- On the SDF_RESTORE MEDM screen available via the Suspension GDS_TP screen select FILE TYPE as "EPICS DB AS SDF" & FILE OPTIONS as "OVERWRITE" then click "SDF SAVE FILE" button to push a SDF snap shot to the target area (which is soft-linked to userapps).
- This safe SDF snapshot was then checked into the userapps svn:
/opt/rtcds/userapps/release/sus/h1/burtfiles/
M        h1susbs_safe.snap

This should close ECR E1500045 and Integration Issue #1003 for LHO.
Images attached to this report
Comments related to this report
stuart.aston@LIGO.ORG - 14:26, Tuesday 24 February 2015 (16890)ISC
LLO scripts for transitioning the BSFM M2 coil driver from acquisition (BIO state 2) to low-noise (BIO state 3) once IFO RF LOCK is archived have been checked into the repo and svn'd up here at LHO:
/opt/rtcds/userapps/release/lsc/l1/scripts/transition/als/
A        bs_m2_switch.sh
A        bs_m2_out_normal.snap
A        bs_m2_out_ll.snap
A        bs_m2_out_lr.snap
A        bs_m2_out_ul.snap
A        bs_m2_out_ur.snap

The above script applies a BURT snapshot to the BSFM M2 EUL2OSEM Ramping Matrix zeroing a quadrant/channel at a time using the other 3 to actuate while it's state is transitioned. Once transitioned the script moves on to the next quadrant, until all 4 are complete.

This functionality should be incorporated into a Guardian transition state.
evan.hall@LIGO.ORG - 10:34, Monday 23 March 2015 (17394)

I copied this scripts and the burt files into userapps/release/isc/h1/scripts/sus, replaced L1 with H1 throughout, and committed them to the SVN.

The script seems to work fine in terms of writing the right values to the right channels. We haven’t tried it yet with the interferometer locked.

H1 PSL
edmond.merilh@LIGO.ORG - posted 12:03, Tuesday 24 February 2015 (16888)
ISS maintanance

ISS AOM Diffracted power was adjusted from 15% to 8.5% by taking the refsignal from -2.07 to -2.14.

H1 ISC (SUS)
stuart.aston@LIGO.ORG - posted 11:56, Tuesday 24 February 2015 (16864)
Changes to ASC model to accommodate QUAD top stage bounce and roll damping using AS WFS (WP#5069)
[Jeff K, Stuart A, Kiwamu I]

To accommodate QUAD top stage bounce and roll mode damping using AS WFS as the sensor the h1asc model has been modified as follows:

(0) Observation that the h1asc model uses the library ASC part (the l1asc does not), and that h1asc is already checked in the the svn. Snapshots of the l1asc & h1asc top-level models are below. 

(1) Removed 2 RFM receivers from h1asc which were producing IPC errors (see IPC snapshot below). After discussing with Daniel it was established that these channels are no longer used (i.e. H1:ALS-X_REFL_B_SLOW_RFM & H1:ALS-Y_REFL_B_SLOW_RFM), thus inputs were terminated to the ASC block (IN_GR_PDHX & IN_GR_PDHY), as is also the case at LLO.

(2) Had to disable the link to the ASC library part, after discussing with Kiwamu, so that the AS_B_RF45_Q_PIT signal could be routed though to the top-level (see h1asc ASC snapshot below).

(3) Added 2 RFM and 1 IPC senders from h1asc to each QUAD i.e. channels H1:ASC-ETMX_AS_B_RF45_Q_P (card 0), H1:ASC-ETMY_AS_B_RF45_Q_P (card 1), and H1:ASC-ITM_AS_B_RF45_Q_P (see snapshot of new h1asc top-level model below).

(4) Renamed OAF channel names with CAL.

This model has been built, installed, and restarted during this mornings maintenance, with no issues.

I’ve checked the h1asc model into the svn:
/opt/rtcds/userapps/trunk/asc/h1/models/
M        h1asc.mdl
Images attached to this report
H1 PSL (PSL)
jason.oberling@LIGO.ORG - posted 11:07, Tuesday 24 February 2015 - last comment - 12:57, Tuesday 24 February 2015(16887)
PSL FSS Maintenance

P. King, J. Oberling, J. Bartlett, E. Merilh

 

We realigned the FSS RefCav this morning.  It was down around 0.7V on the FSS TPD.  We aligned both mirrors of the input periscope in both pitch and yaw.  Yaw alignment did not increase the RefCav TPD signal by much; most of the adjustmen was to pitch on both mirrors.  We left the FSS TPD reading 1.56V and locked the adjustment screws on both periscope mirrors.  We also found that the input periscope mirror mounts (they both mount to a ~1.5 inch diameter post that in turn is mounted to the PSL table itself) were a little loose.  Peter was able to tighten both mounts by ~1/8 to ~1/4 of a turn on the big screws that mount the mirrors to the post.  Will continue to monitor the FSS TPD to see if it continues to drift down.

We measured the laser power in 2 places after the alignment:

We also measured the voltage on the FSS REFL PD when the RefCav was locked and unlocked:

Comments related to this report
peter.king@LIGO.ORG - 12:57, Tuesday 24 February 2015 (16889)PSL
Luckily it seems that the reference cavity transmission signal in volts is one-tenth that of the transmitted
power in milliwatts.  As I recall ALS needs something like 10 mW in its beam path.  So if the reference cavity
transmission drops below 1 V, we should think about tweaking the alignment.
Displaying reports 66621-66640 of 83068.Go to page Start 3328 3329 3330 3331 3332 3333 3334 3335 3336 End