Displaying reports 66741-66760 of 77186.Go to page Start 3334 3335 3336 3337 3338 3339 3340 3341 3342 End
Reports until 14:05, Friday 14 March 2014
H1 SYS
kaitlin.gushwa@LIGO.ORG - posted 14:05, Friday 14 March 2014 - last comment - 17:16, Friday 14 March 2014(10759)
BSC10 contamination

Travis, Margot, and Kate

Removed the horizontal 4" wafer from the beamtube (between the purge air port and ACB). The 1" optic that was placed with the wafer couldn't be removed (no PETG containers available), so it was moved to the opposite tube for the time being. When possible, it should be moved back to its original location or removed. A new 1" optic (s/n 1195) was mounted vertically to the QUAD.

Refer to Betsy's earlier alogs on contamination in BSC10 (1052210675 & 10686). There is still a lot of particulate contamination, even after cleaning. The first photo shows a wipe used to clean the tube on Monday. Dust, metal, a few red fibers, and white fuzzies were observed on the tube floor from the ACB all the way to the PCAL periscope. The iphone photos and videos don't really do it justice. There was a much higher concentration of white fuzzies along one half of the tube (on the right side, if you have your back to the ACB and are facing the periscope). Travis took an FBI sample, and then vacuumed the area.

Images attached to this report
Non-image files attached to this report
Comments related to this report
travis.sadecki@LIGO.ORG - 17:16, Friday 14 March 2014 (10768)

After finishing PCal alignment, I replaced the 1" optic to it's original position between the purge air port and the ACB/ETM.  I then wiped my way out of the chamber.

H1 ISC
sheila.dwyer@LIGO.ORG - posted 13:44, Friday 14 March 2014 - last comment - 13:50, Friday 14 March 2014(10760)
Help from DetChar or SEI offsite?

We've had at least 6 times this morning that HEPIs have tripped on the L4Cs, and there isn't a clear reason looking at the seismic conditions why today should be worse than other days.  The chambers that have tripped are (at least ) IMTX twice, ITMY once, HAM2 once, BS twice.  Attached are plots of the two most recent BS trips. 

No one on site really has the time to sort through the data and figure out what is happening, is there anyone from SEI or DetChar that can take a look?

Thank you,

Sheila

Images attached to this report
Comments related to this report
fabrice.matichard@LIGO.ORG - 13:50, Friday 14 March 2014 (10761)

Sheila,

thanks for the note. We start looking into it.  Since the L4C are not even in the loop, please feel free to temporarily rise the WD value (the code will slowly bring it back to standard value at teh rate of 1 ct/s or so).

We get back to you asap. 

H1 General
jeffrey.bartlett@LIGO.ORG - posted 11:49, Friday 14 March 2014 (10758)
Dust Monitors
Dust monitor #2 at End-Y (next to the BSC10 chamber) and dust monitor #1 in the HMA5 cleanroom are both online and functional. 
H1 SEI
sheila.dwyer@LIGO.ORG - posted 10:25, Friday 14 March 2014 - last comment - 11:45, Friday 14 March 2014(10756)
ITMX and Ham 2 tripped

It didn't seem like there was much seismic noise based on the PEM FOMs, but they both triped around the same time.  Plots for ITMX attached

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 11:45, Friday 14 March 2014 (10757)

This time ITMX and ITMY both tripped again at the same time.  Here are plots for IMTX again, Robert was making an injectiong at this time but he doesn't think it should have tripped the ISI.  There isn't much in the PEM FOMs again.

Images attached to this comment
LHO VE
kyle.ryan@LIGO.ORG - posted 10:08, Friday 14 March 2014 (10754)
~0945 hrs. local -> Started pumping GV18's annulus


			
			
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 09:47, Friday 14 March 2014 (10753)
CDS model and DAQ restart report, Thur 13th March 2014

2014_03_13 16:14 h1ioppemmy

2014_03_13 16:15 h1ioppemmy

2014_03_13 16:18 h1ioppemmy

2014_03_13 16:22 h1ioppemmy

2014_03_13 16:48 h1ioppemmy

2014_03_13 16:50 h1pemmy

 

no unexpected restarts.

H1 General
andres.ramirez@LIGO.ORG - posted 09:35, Friday 14 March 2014 (10752)
PSL Check

Laser Status: 
SysStat is good
Output power is 28.4 W (should be around 30 W)
FRONTEND WATCH is Active
HPO WATCH is red

PMC:
It has been locked 2 d, 11 h 15 minutes (should be days/weeks)
Reflected power is 1.2 Watts  and PowerSum = 11.3 Watts.
(Reflected Power should be <= 10% of PowerSum)

FSS:
It has been locked for 0 d 0 h and 5 min (should be days/weeks)
Threshold on transmitted photo-detector PD = 0.9 V (should be 0.9V)

ISS:
The diffracted power is around 13.4 % (should be 5-15%)
Last saturation event was 2 d, 11 h and 15 minutes ago (should be days/weeks)
H1 PSL (PSL)
justin.bergman@LIGO.ORG - posted 09:25, Friday 14 March 2014 (10751)
H1 Diode room cleaning

Chris ran the swiffer in the Diode Room this morning for the first time in 8 months. Will try to make cleaning more regular.

H1 ISC
sheila.dwyer@LIGO.ORG - posted 02:34, Friday 14 March 2014 (10750)
Input beam pointing noise doesn't contribute much to ALS COMM noise

Earlier tonight Alexa made some measurements of IMC transfer functions to for matching with her model, and I worked on the slow feedback to the ETM top mass. (alog about that coming in the morning, in short the L2P decoupling has helped)

Now I've made some measurements similar to what ALexa and I did on Monday night (alog 10668) of the linear coupling from the test mass angles to the out of loop frequency noise sensor (the normalized refl PDH).  This time I dithered the PZTs on ISCEX, and measured the spectrum of the normalized PDH and the green QPDs on the input beam on the TMS table.  I haven't calibrated the QPDs, or measured the loop gain, but these are verry slow loops and I dither the PZTs at 5Hz so that should not matter. By dithering each PZT in both pitch and yaw, and finding the peak in the spectrum of both QPDs each time, we get 2 measurements of the coupling from each QPD to frequency noise.

  Hz/ count measured by dithering PZT1 Hz/count measured by dithering PZT2
QPDA PIT 114 126
QPDA YAW 66 154
QPDB PIT 92 44
QPDB YAW 51 69

As you can see the measurements made with different PZTs aren't always consistent.  Using these and measured spectra of the QPDs, we can make the projection of the linearly coupled  noise from input beam pointing to ALS frequency noise, it is not a significant contribution (below 100Hz) based on any of these measurements. At around 100 Hz these projections seem to explain the noise, I believe this is just the noise of the QPDs, but will check in the morning. 

I also checked the linear coupling from the ETM pitch to frequency noise, to see how much it changes with alignment. I measured 424Hz/urad, moved the ETM by 0.1urad, measured 1.12kHz/urad, tried to move it back to the original spot and measured 2.03kHz/urad.  Then I tweaked up both pitch and yaw on the ITM and ETM to try to maximize the green transmission, and got 3.2kHz/urad. So we can change the linear coupling by adjusting the alingment; by hand I only seem to make it worse but hopefully the WFS will do better.

I am leaving the green arm locked, and the guardian running the ALS COMM handoff, so hopefully the IR will be resonanting in the arm some part of the night.

Images attached to this report
H1 CDS
cyrus.reed@LIGO.ORG - posted 17:50, Thursday 13 March 2014 (10746)
h1pemmy Working (Finally)

h1pemmy is finally up and working.  The first problem relatively easily found was a bad ADC card, which was swapped early on after it was seen to generate 'channel hopping' errors to dmesg.  Said card has been marked as bad (it was probably pulled from somewhere else, but not actually labelled as bad which led to it's later unfortunate re-installation).  The second issue was that after replacing the ADC card the duotone signal was not appearing on CH31 (numbered from 0).  This led to a number of time consuming component swaps to eventually find that the cause was a bad cable from the internal 16 channel Contec card to the IO chassis backplane.  I could verify with the IO chassis powered up, but the front end computer off, that the duotone signal was present on the correct pin of the cable feeding the ADC.  After boot/code initialization, the duotone input was switched off by the relay on the adapter board, and the last channel of the AA chassis would then feed the ADC (verified by injecting a signal through the AA chassis).  I could also verify the relay control voltage with the Duotone0_select testpoint on the backplane.  The code is (in it's present form, in theory) hard coded to never activate this relay, so seeing 5V here is not right.  The cable itself is mis-crimped, such that pins 1/20, 2/21, ... , 18/37 are shorted together, with pin 19 not connected at the male/Contec side of the cable, a fact not immediately obvious in the back of a dark rack, but more so once exposed to the light...  The moral of this tale is to double check the internal 37 pin cable that controls the backplane if the duotone signal seems to go missing between the testpoint on the board and the ADC sometime after boot, there may be more of these floating around.

Images attached to this report
H1 SUS
keita.kawabe@LIGO.ORG - posted 17:48, Thursday 13 March 2014 - last comment - 10:21, Friday 14 March 2014(10747)
ETMX PUM Y2P decoupling done

Offending Y2P peak between 1 and 2Hz (pink) was removed after a new decoupling filter was put in place (green).

In the H1:SUS-ETMX_L2_DRIVEALIGN_Y2P filter, I put the same invP2P filter in FM1 as in the P2P path, then added a diagonalization filter ("Y2Pdiag") in FM2, and another filter that is a 3rd order elliptic BP in FM3. I didn't try to remove 0.4-0.5Hz Y2P peak, it's not great but probably good enough.

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 17:52, Thursday 13 March 2014 (10748)

ITMX PUM P2Y and Y2P measurement was done, but I need to leave before generating decoupling filter.

Seems like ITMX PUM is somewhat better diagonalized than ETMX PUM, but I'll remove 1.4Hz P2Y peak anyway.

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 19:37, Thursday 13 March 2014 (10749)ISC
Remember, the ITM is a wire hang QUAD (the test mass is suspended from the PUM via a wire loop and prisms), and has significantly different dynamics than the ETM fiber welded QUAD. This may be an explanation for the different dynamics.

I also imagine you'll have to do this process all over again with the ITM once it becomes monolithic like the ETM.

 
keita.kawabe@LIGO.ORG - 10:21, Friday 14 March 2014 (10755)

We probably need to re-do everything once it's re-hang.

H1 SYS (SYS)
corey.gray@LIGO.ORG - posted 16:46, Thursday 13 March 2014 (10743)
H1 Ops Overview MEDM

Thomas started work on an Operator Overview screen.  This screen has a graphic of H1 with all of its chambers.  For each chamber, we have buttons to easily & directly open HEPI, SEI, & SUS screens.  The buttons are also colored such that they indicate whether Watchdogs are GREEN or RED.  So for quick glances, this medm can give you an idea of ALL WATCHDOGS.

This is a living screen, and we plan to add more features (Guardian, "Measurement In Progress", etc.).  This medm currently resides at: 

/opt/rtcds/userapps/release/sys/h1/medm

We currently have this medm is now an FOM & currently on our video1 Wall Monitor.  The CDS SUS Overview also shares this FOM, but we may remove that screen since that screen is sort of redundant (or it will be once we get all SUS screens on the Ops Overview screen).

Images attached to this report
H1 INS (SEI)
jim.warner@LIGO.ORG - posted 16:45, Thursday 13 March 2014 (10745)
TF running on ETMY ISI on opsws1

TF is setup on the workstation with a 2.5 hour delay, to allow for PCAL work. Lucky number 3.

LHO General
corey.gray@LIGO.ORG - posted 16:31, Thursday 13 March 2014 (10740)
Ops DAY Summary

.......LVEA:  Laser SAFE..............EY:  Laser SAFE.........EX:  Laser HAZARD.......

A major activity today was the installation of the Spool at EY, installation of viewports on the spool, and then getting PCal pylons staged into position.  Other activities are:

H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:29, Thursday 13 March 2014 (10744)
Dust Monitors
End-Y - The dust monitor in the spool cleanroom (#2) at End-Y failed with a low battery message. Filiberto replaced a blown fuse in the network junction box. The dust monitor appears to be working at this time. The dust monitor for the BSC10 chamber (#1) is charging and will be replaced in the morning. There is a temporary handheld unit in the chamber cleanroom. 

HAM5 Cleanroom – Getting communications errors on the dust monitor in the HAM5 cleanroom. Filiberto found low voltage on this unit. It is shut down for charging overnight. I will bring it back on line in the morning.     
Displaying reports 66741-66760 of 77186.Go to page Start 3334 3335 3336 3337 3338 3339 3340 3341 3342 End