Displaying reports 58241-58260 of 84550.Go to page Start 2909 2910 2911 2912 2913 2914 2915 2916 2917 End
Reports until 16:45, Thursday 05 May 2016
H1 DAQ (CDS)
james.batch@LIGO.ORG - posted 16:45, Thursday 05 May 2016 (27035)
The h1tw0 trend writer is running.
The trend writer on h1tw0 has been started after a lengthy absence due to equipment repair.  
H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 16:23, Thursday 05 May 2016 (27033)
Ops Day Shift Summary

All time in UTC

13:47 Chris S. working on beam tube enclosure sealing. Approx. be locateed 1/4 to 1/2 way toward Mid-X. Morning work.

15:19 Christina to LVEA

15:51 Jason heading to PSL

16:10 Joe to LVEA

16:15 Cheryl making measurement on IMs.

17:07 Hugh and Jim to EX.

17:21 Ed to LVEA

17:37 Ed back

17:40 Travis to LVEA to the racks near HAM2,3.

17:53 Manny to End stations looking for extension cords.

17:56 Joe out

18:13 Dave restarted LSC, ISC model

18:17 Hugh to LVEA retrieving equipment near HAM2.

18:24 Jenne and David start cutting floors in the LVEA

18:31 Hugh out

18:51 Hugh to EY making some measurement

18:57 Jason and Peter out for lunch

19:04 DAC restart (EX)

19:54 DAC restart (PEM EX)

20:23 Manny out

20:46 Manny to LVEA

21:06 Fil removing electronics box from ISCT1.

           Richard and Gerado to LX and beer garden look at VAC channels. BSC7 and BSC8  high pressure alarms were their doing.

21:25 Chris to EX to unload pile of lumber.

21:47 DAC and SUS ETMY model restart

22:30 Fil out

22:40 Peter and a group of operators to LVEA for Transition training.

23:00 Peter et al out.

Keita to ISCT1 sometimes between 22:00-23:00

 

NOTE TO ALL: MUST LET OPERATOR KNOW IF YOU ARE GOING TO END STATIONS. You are potentially causing BRS to ring up just by being there. If couldn't find operator on shift, let Jim know.

H1 GRD (SEI)
thomas.shaffer@LIGO.ORG - posted 11:47, Thursday 05 May 2016 (27031)
Added new ISI_OFFLINE state to SEI managers

Added a new ISI_OFFLINE state to the sei manager guardians that has the ISIs in Ready and HEPI Isolated. This state is mainly used while the sei team is testing and not for normal operation. To get to ISI_OFFLINE I added a couple of transition states from DAMPED that will turn Off the ISI damping loops, and then turn them back on before entering DAMPED again. (HAM and BSC graphs attached)

Tested yesterday on ITMX and HAM5. Loaded the new code into all of the managers today.

Images attached to this report
H1 CAL (CAL)
travis.sadecki@LIGO.ORG - posted 11:45, Thursday 05 May 2016 (27029)
LHO PCal End X and End Y Calibration

Darkhan T., TJ S., Travis S., Evan G.

Yesterday, we took PCal end station measurements for both end stations.  See attached pics if you are interested in the raw data and timestamps.  Otherwise, see T1500129 and T1500131 for the summary reports for each end station.

A quick glance at the optical efficiency of X end seems to indicate that the known clipping issue is getting worse. 

Images attached to this report
LHO VE
chandra.romel@LIGO.ORG - posted 10:44, Thursday 05 May 2016 (27028)
data history shortage
Can't see data before 4/26 on PT100. Surveyed other gauges over 15 days. PT100 seems to be the only one that gets cut off on 4/26. Dave Barker is investigating.
Images attached to this report
LHO VE
chandra.romel@LIGO.ORG - posted 10:31, Thursday 05 May 2016 - last comment - 19:59, Thursday 05 May 2016(27027)
unexplained vacuum gauge signal stepping
After Tuesday activities, noticed a step change in pirani gauge signals. Attached is plot of PT100 (on HAM 1) and PT140 (on BSC4). Note:  PT100 CC gauge keeps turning on and off due to pirani set point and stepping.

PT120 also shows a step in signal. Yesterday Richard & Gerardo pulled the leads on PT120 while measuring the voltage. Voltage read higher valve when lifted from rack.

PT140 pirani trend over 15 days shows a major step from 4/26 (when Beckhoff was installed) to 5/3 when power was switched and system rebooted.
Images attached to this report
Comments related to this report
michael.zucker@LIGO.ORG - 14:24, Thursday 05 May 2016 (27032)

Sounds like the input impedance of the Beckhof ADC is lower than the original VME card ADC. These form a voltage divider with the gage head's output impedance.  I/O impedances  should be listed in the respective instrument datasheets.  There may be a jumper/selection available.

Beyond recalibrating epics records,  good to confirm that the gage heads are happy driving whatever impedance they see full-scale.  

 

kyle.ryan@LIGO.ORG - 19:59, Thursday 05 May 2016 (27040)
Good idea Chandra.  I hadn't even considered looking at the piranis!
H1 TCS (ISC)
nutsinee.kijbunchoo@LIGO.ORG - posted 20:10, Wednesday 04 May 2016 (27023)
Rotation stages performance

Daniel, Nutsinee

After Daniel made some changes to the RS configurations today (alog27008), I ran the random walk script again. 

Result:

CO2X RS requested angle and measured angle agree within 0.01 deg -- Better than ever

CO2Y RS requested angle and measured angle agree within 0.02 deg -- Better than ever

And PSL RS requested angle and measured angle agree within 0.004 deg -- Awesome!

 

I have also recalibrated the power vs. angle calculator for CO2 RS.

Images attached to this report
H1 CDS
patrick.thomas@LIGO.ORG - posted 19:06, Wednesday 04 May 2016 (27021)
restarted conlog
Suspect Beckhoff work again.
H1 PSL (PSL)
peter.king@LIGO.ORG - posted 17:55, Wednesday 04 May 2016 (27018)
HPO Status
Bit the bullet and started adjusting the 4f lenses.  The beam profile currently is a
little better than the attached image.  The output power as measured with the power
meter located near the external shutter is ~151W (~148W on the external power meter).
All powers are with the corona aperture in.

    Adjusting the homogenisers and fibre bundle positions did not yield the breakthrough
in output power I was hoping for.
Images attached to this report
H1 CDS (SUS)
david.barker@LIGO.ORG - posted 17:29, Wednesday 04 May 2016 (27016)
code changes to route downsampled OMC-DCPD from lsc front end to sus etm front ends for PI

Tega, Ross, Jim, Dave:

here is an overview of the signal flow to get the OMC DC-PD signals from the corner station to the SUS-PI models at the end stations. For example, lets take the ETMX system:

h1lsc0 front end computer:

h1omcpi model (running at 64kHz). The OMC DCPD A and B ADC signals are downconverted into four pairs of I and Q phase signals. These 8 signals are transmitted out of h1omcpi as local SHMEM IPC channels.

h1omc model (running at 16kHz). The 8 SHMEM IPC signals are received, and MUX'ed to a single channel. This channel is split and sent out as an RFM channel on the X and Y RFM loops.

h1iscex front end computer:

h1pemex model (running at 16kHz). The RFM signal is received, and sent through a 1-to-8 DEMUX. The time delay of 1 cycle is compensated for. The resulting 8 signals are sent as 8 Dophin PCIe IPC senders.

h1susex front end computer:

h1susetmxpi model (running at 64kHz). The 8 Dolphin channels are received and upconverted.

H1 General
cheryl.vorvick@LIGO.ORG - posted 16:49, Wednesday 04 May 2016 (27015)
Ops Day Shift:

State of H1:  PSL is being realigned, no light to the IFO

Activities:

H1 ISC
stefan.ballmer@LIGO.ORG - posted 16:20, Wednesday 04 May 2016 - last comment - 08:35, Thursday 05 May 2016(27011)
10msec transients every 100msec are from RFID

With the ring antenna and the battery powered scope I chased down the time-domain transients that I observed on the L2 coil cable (10msec burst every 100msec). They are due to the RFID tag, and get huge close to the RFID stations (35Vpk when the antenna is held close to the RFID board).

Attached are 4 scope traces, as well as a 3MHz span spectrum. The frequency content is 124kHz plus (mostly odd) harmonics. The y-axis is arbitrary, as the gain depends on the distance from the source.

Images attached to this report
Comments related to this report
stefan.ballmer@LIGO.ORG - 16:23, Wednesday 04 May 2016 (27013)

I also verified that these time-domain bursts disapear in the L2 coil cable common signal. However, most of the high frequency junk on those cables is still there - as expected only the 124kHz and harmonics disapear.

stefan.ballmer@LIGO.ORG - 19:39, Wednesday 04 May 2016 (27022)

Robert and Nutsinee tested the effect of turning the RFID system off in alog 23169.

robert.schofield@LIGO.ORG - 08:35, Thursday 05 May 2016 (27026)
In iLIGO we did switch off the RFIDs as a precaution, however, there was a desire to keep them on for aLIGO to monitor access to the experimental areas. It may be that this is not longer as important now that we have made a detection.
 
The on/off tests dont probe below the noise floor, so we should keep doing these tests as our sensitivity, especially in the 10 Hz region, increases. However, I think it will be obvious if RFID begins to affect DARM so I have been and continue to be OK with leaving them on. This is because the RFIDs are pulsed at 10 Hz and so produce sharp peaks at 10Hz and harmonics. The CW group monitors for such combs and would let us know even if the peaks were not obvious in second-scale spectra.
H1 TCS
daniel.sigg@LIGO.ORG - posted 15:55, Wednesday 04 May 2016 - last comment - 18:58, Wednesday 04 May 2016(27008)
Rotation Stages

Turns out that the rotation stages are sufficiently different that the same parameters won't give optimal results. In particular, the CO2Y rotation stage seems to require significantly more current for the same velocity.

For TCS I reduced the maximum speed even further, since it is unlikely that we ever need high speed. The maximum is now about 100 times slower than originally. The speed can simply be left at 100% with 10 sec acceleration and deceleration times. I also needed to reduce the PI loop gains by 2 for X.

I noticed that the motion always falls short of the final destination. For large angles the errors tend to be somewhat larger. I added a fine adjust feature which, when engaged, will nudge the motor, after it finishes its initial motion. This feature includes an adjustment angle which is intended to compensate for the shortfall.

The busy flag gets stuck quite often, and the auto-abort is required for the fine adjust feature to work consistently.

In order to connect the duty cycle and current readbacks, the 0x1A07 and 0x1A09 regions need to be assigned in the process data configuration of the motor terminal. This will add "DCM Synchron info data channel" structures which contain the info1 and info2 channels.

Comments related to this report
daniel.sigg@LIGO.ORG - 15:57, Wednesday 04 May 2016 (27009)

Here are the CoE parameters for the TCS motor controller.

Non-image files attached to this comment
daniel.sigg@LIGO.ORG - 16:05, Wednesday 04 May 2016 (27010)

Here is a snapshot of the rotation stage settings screens, as well as updated medm screens for the rotation stage and the readbacks, respectively.

Images attached to this comment
daniel.sigg@LIGO.ORG - 18:58, Wednesday 04 May 2016 (27020)

When using the adjust feature, the busy flag of the rotation stage is no longer a good indicator to see, if the laser power has reached its final value. The internal state of the laser power controller is now available in EPICS—as well as a state_busy flag which indicates that the power controller (rather than the rotation stage controller only) is busy.

LHO VE
chandra.romel@LIGO.ORG - posted 09:14, Wednesday 04 May 2016 - last comment - 21:54, Wednesday 04 May 2016(26995)
CP2 PID experiment
I am adjusting the CP2 LLCV PID parameters controlled by Beckhoff system. 

1. Set to manual mode at 35% open and adjust PI settings while in manual mode and observe value in data viewer real time. PI still updates its values in manual mode. Note that every time a PID value is changes the LLCV % open value resets.


The pneumatic actuator is physically jouncing up and down and will wear out prematurely at current Beckhoff settings. 

The new electronic actuator on CP1 is not jolting as much as CP2, but up/down movement is still noticeable at rapid rate - PID parameters should be addressed.

Have not surveyed the other five actuators (CP3 doesn't count).
Comments related to this report
chandra.romel@LIGO.ORG - 18:50, Wednesday 04 May 2016 (27019)
Unsuccessful in adjusting PI parameters today (P & I gains set too low from nominal 6 & 360 s. values, respectively), which significantly reduced the physical jitter in the LLCV by reducing % open signal amplitude but did not settle to the set point.

But good news! At the end of the day, Patrick provided the magic button. There is a way to apply a smoothing factor on the CP liquid level (0

		
		
kyle.ryan@LIGO.ORG - 21:54, Wednesday 04 May 2016 (27024)
Good work Chandra - keep at it - this is a worthy pursuit for familiarity with the new Beckhoff controls - I will need you and Gerardo to brief me on the new environment as soon as time permits
H1 ISC
stefan.ballmer@LIGO.ORG - posted 20:52, Tuesday 03 May 2016 - last comment - 22:12, Wednesday 04 May 2016(26992)
Banging noises from the GN2 pipes at End X

While I was at End X (around 7pmish) I heard repeaded banging noises coming from the GN2 pipes (GN2 BURST, GN2 VENT and GN2 REGEN). Not sure whether that's a know isssue, but it was rather loud, and the support piers were shaking noticably.

Comments related to this report
stefan.ballmer@LIGO.ORG - 09:02, Wednesday 04 May 2016 (26994)

This was observed between 00:46 and 0144 UTC on May 4th (17:46-18:44 PDT on May 3rd).

Also, the observation was done inside the building. I did not investigate the outside.

vernon.sandberg@LIGO.ORG - 11:41, Wednesday 04 May 2016 (26998)

GN2 = "gaseous nitrogen"

LN2 = "liquid nitrogen"

for those tracking our jargon.

kyle.ryan@LIGO.ORG - 22:12, Wednesday 04 May 2016 (27025)
John and I investigated Wednesday afternoon and found everything quite -> John excited the ambient-air vaporizer (large finned aluminum ambient heat exchanger mounted on the concrete slab near the supply dewar outside of the building and piped in-line with the GN2 REGEN connection to the pump and which is easily mechanically excitable with wind) while I was in the VEA listening - Nothing -> We also created excessive LN2->GN2 boil-off in CP8 by filling in manual mode at a "high" LLCV %OPEN setting - Nothing.  

We did note that, nowhere in the piping between the ambient air vaporizer and CP8 was the piping clamped to anything.  In fact, it was just resting on pipe stands.  Also, an "ice ball" had formed on the bellows at the pump penetration - reminding us of the fact that all of the ambient air vaporizers on the X-arm have severed welds at the ASA connection flange which results in a parallel path for the GN2 exhaust to exit he pump -> We then capped the piping to eliminate this as an excitation mechanism
H1 PSL (PSL)
peter.king@LIGO.ORG - posted 17:25, Tuesday 03 May 2016 - last comment - 17:46, Wednesday 04 May 2016(26972)
HPO status
The attenuated output from the front end, or seed, laser was admitted into the high
power oscillator ring.  No signs of clipping on the intermediate optics was observed.
However the overlap between the beam promptly reflected from the oscillator's output
coupler and the beam that traversed the ring was slightly off - the interference
fringes were clearly left of centre.  This was corrected for.  The mis-alignment of
the output coupler was most likely caused by the drag wipe cleaning the previous day.

    Each laser head was powered up with 5A of pump current.  No bright spots were
observed on the optics that would indicate some kind of point damage.  Each head was
powered up to 50A and again, no point damage spots were observed.

    The oscillator was then fully powered up, starting at 40A-45A per head.  The
laser power was noticeably down.  The beam from the oscillator, shown in
FirstTurnOn1.png, was ugly but stable.  My interpretation of this was that there
was no point damage on the optics but that the resonator was severely mis-aligned.
The exact reason for why the resonator would have become mis-aligned is not clear
to me.

    Adjusting the output coupler did improve the beam shape but not the output
power.  A more thorough alignment process will be embarked on tomorrow.
Images attached to this report
Comments related to this report
peter.king@LIGO.ORG - 17:46, Wednesday 04 May 2016 (27017)
Forgot to add this picture yesterday, which was after adjusting the output coupler.
Images attached to this comment
H1 TCS
nutsinee.kijbunchoo@LIGO.ORG - posted 14:04, Monday 02 May 2016 - last comment - 11:20, Thursday 05 May 2016(26927)
Restarted h1hwsmsr and restarted HWSX code

~21:01 UTC I turned off the camera, frame grabber, then powercycled the computer (then turned the frame grabber and the camera back on). Only HWSX code is running at the moment. Things look good for now.

Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 09:45, Tuesday 03 May 2016 (26960)

May 3 16:44 UTC Stopped HWSX code and ran HWSY code alone. HWSX code had been running fine since yesterday.

nutsinee.kijbunchoo@LIGO.ORG - 11:20, Thursday 05 May 2016 (27030)

May 5th 18:20 UTC  I noticed HWSY code stopped running. There has been many comuter and front end restart since I left it running so it was unclear what caused it to stop. I reran it again and going to leave it again for another day.

Displaying reports 58241-58260 of 84550.Go to page Start 2909 2910 2911 2912 2913 2914 2915 2916 2917 End