Displaying reports 68201-68220 of 77131.Go to page Start 3407 3408 3409 3410 3411 3412 3413 3414 3415 End
Reports until 16:45, Friday 10 January 2014
H1 SUS
jeffrey.bartlett@LIGO.ORG - posted 16:45, Friday 10 January 2014 - last comment - 09:50, Tuesday 14 January 2014(9212)
L to Y Cross Coupling on H1-SR2
   Last set of TFs on H1-SR2 showed a longitudinal to yaw cross coupling at 1.51 and 2.77Hz. I adjusted the Coil Holder and recentered the BOSEMs.
 
   There were only two of the four Coil Holder Mounting Brackets installed, (which may be a source of the noise in this suspension and a contributor to the cross coupling) when the earlier TFs were taken. The missing two Mounting Brackets required modification due to misaligned mounting slots. These modifications were not completed in time to be installed on the suspension before it was moved to the LVEA. One of the Mounting Brackets was modified correctly; and has been installed on the suspension. The second Mounting Bracket was not modified correctly and will need to be reworked before it can be installed. Three of the four Mounting Brackets are now clamping the Coil Holder to the Weldment. 

   I have started a new set of TFs on H1-SR2, to see if the BOSEM adjustment and the addition of the third Mounting Bracket will improve the performance of the suspension over that revealed in the earlier TFs.        
Comments related to this report
betsy.weaver@LIGO.ORG - 09:50, Tuesday 14 January 2014 (9262)

For my own apparent nomenclature, the "coil mount brackets" that Jeff is referring to is actually the tablecloth mounting brackets which attach it to the structure.

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 General
andres.ramirez@LIGO.ORG - posted 16:00, Friday 10 January 2014 (9210)
Ops Shift Summary
8:00 - Performing alignment work at End X – Sheila
9:30 - Roofing contractors/inspectors on site today 
9:40 - Work on HAM4 – Hugh/Jim W.
9:45 -Inspecting the Corner Station roof – Inspectors/John/Richard
9:50 - Continuing Baffle work at LVEA West bay – Mitchell
10:16 - Roof inspectors going to End Y
11:36 - Finished working on LVEA – Mitchell
1:05 - Back to Baffle work on  LVEA – Mitchell
1:16 - Transitioning End Y to Laser hazard – Operator
1:46 - Re-checking SR2 BOSEMs – Jeff B.
1:50 - Going to End X to do measurements – Sheila
2:00 - Finished working on HAM1 - Kiwamu
2:20 - HAM1 East door installation – Apollo
3:05 – Powering up Ring Heater chassis at End X – Filiberto/Aaron
H1 ISC
alexan.staley@LIGO.ORG - posted 15:27, Friday 10 January 2014 (9209)
HAM 1 beam diverter/PLC changes

While in HAM 1, we verified that the beam diverters were functional. Indeed they were; however, Corner Pop beam diverter (BDIV_B) was flipped in regards to open/close, so I have updated the PLC to reflect the proper positioning.

X1 DTS
james.batch@LIGO.ORG - posted 14:33, Friday 10 January 2014 (9207)
Moved H2 Minute Trend Files
The minute trend files for H2 used to be in /frames/trend/minute_raw.  They have been moved to /frames/trend/minute_raw_old, which allows for somewhat easier searches for files in the 0-ff directories.  If anyone really wants to look for minute trends from the H2 system, the NDS configuration file will need to be modified to look in that directory.
H1 CDS
david.barker@LIGO.ORG - posted 13:54, Friday 10 January 2014 (9206)
created watchdog button on MEDM SITEMAP for hardware watchdog screens

I added a new WD button to the SITEMAP for the CDS Watchdog screens (dark blue, bottom left). The new Hardware Watchdog (attached to ITMY) and the IOP software watchdog screens are accessible via this new button.

H1 ISC
sheila.dwyer@LIGO.ORG - posted 11:47, Friday 10 January 2014 (9191)
ETM transmission appears to be 37% for 532, X arm cavity alignment, ISCT1 PDs
  TMS (PIT, YAW, V) ITMX ETM
PD1 (102.5, -209.5, 2.37)0dB gain (54, -79, 5.85)  
PD4 (171, -271, 2.38)0dB gain (88, -45,5.77)  
alinged (136.75, -240.25) (71, -62)  

After alinging TMS and the ITM using the bafle PDs, I was unable to find light on the ITM baffle PDs using the old ETM referece (alog 9126). 

I found some fringing at: ITM 75 -59 ETM 384, -77 TMS 136.8, -240.3.  The ETM was moving too much to make a reasonable alingment.  Hugh, Jeff and Jim helped to get both the ETM and ITM to level one isolation, so things are moving less now. 

By misalinging the ITM I measure 12830 counts on refl B.  If I misaling the ETM by 40urad, I can clearly see two return beams, a brighter one from the ETM and a less bright one from the ITM.  Misaligning the ETM by 80urad, the etm return beam is no longer on the refl B PD.  I adjusted the ITM alignment to maximize the power on the refl B PD, at PIT 75 YAW -59 there are 2850 counts on refl B.  Blocking the refl B PD completely we have 52 counts.  I also misalinged the itm to see the signal disappear, so I do believe this beam was really from the ITM. 

The ratio of the ITM return to the ETM return beam is (1-Retm)^2*Ritm/Retm.  Assuming that the ITM reflectivity is 99%, this gives Retm=63%.  This reflectivity will only get lower is the ITM reflectivity is lower than 99%.  With Retm=63%, our measurement of the return beam power from monday night (alog 9171)means that the TMS effiicency  (one way) is 78%, matching better with Keita's prediction (alog 3077) of 82%.  In the first version of this alog I made a mistake, and wrote that the reflectivity was 53%.  

I measure 12uW of 532 arriving on ISCT1 with the ITM misalinged (single shot beam, about 34mW input from ISCEX) ), there is 1.6uW on the DC PD monitoring the X trans.  The DC PD does not seem to be working, it is cabled (R4 ISC1:2) but changing the gain on the medm screen does not change the monitor output for this channel.  I also alinged the single shot beam onto the Comm BBPD, there are 3.5mW there with the ITM misalinged. The slow controls readout of this PD is also not working, but I can see that the PD is working in H1ALS-C_COMM_A_LF.  I added a -62 counts offset (the dark offset) now get around 40 counts with 3.5 uW on the PDs.  

H1 SEI (CDS, SUS)
jeffrey.kissel@LIGO.ORG - posted 11:03, Friday 10 January 2014 - last comment - 16:29, Monday 09 June 2014(9204)
SUS Hardware Watchdog Threshold Test
J. Kissel, R. Bork, B. Abbott, D. Barker

In order to determine a good threshold for the new SUS Hardware Watchdog, we've shaken the ITMY chamber vigorously in various states of excitation. 
In summary, with 
- the HEPI and SUS user watchdogs disabled (actuator and inertial sensors set to un-tripably high values)
- ISI damping, SUS damping, and HEPI loops OFF (I just left the ISI tripped the whole time) and 
- driving HEPI at the limit of its DAC range (in Y, RX, and RZ), 
we shook the suspension (and ISI) enough that I would say "Wow, that's a *lot* of motion; it's giving me the willies. We should cut off SEI excitation after 10-20 minutes of this." 

This level of excitation produces roughly 110 [mV] RMS* from the RMS circuit of the SUS Hardware Watchdog. 
* The Hardware Watchdog currently does not expose the output RMS variables, either to analog or digital, so we've replicated what we believe is the SUS Hardware Watchdog's signal chain in the IOP model for the h1susb123's computer, based on the limited documentation available (namely Fig 4 of T1200306), and the DC gain of 31.2 [V/V] from the SUS Hardware Watchdog Chassis, measured on an identical setup in the H1 DAQ Test Stand (thanks Ben/Rolf!).

My figures of merit were 
- the ISI BLRMS Performance matrices, in which 
     - ST1 was solid red above the 0.3 [Hz] band in XYZ, 
     - ST1 was solid red in all frequency bands, and 
     - ST2 was solid red in all bands in all DOFs
- the QUAD M0 OSEM speed dials (the raw ADC input version), in which (for these particular DOFs of excitation from HEPI)
     - F1, F2, and F3 (which are the L, P, and Y sensors) were swinging quickly over *most* (not all) of their range (which is 0.7 [mm])
     - LF, RT, (which are the V and R sensors) showed signs of abnormally large movement, say 25% of their range
     - SD was moving minimally
- The DAC saturation counter screen for HEPI, which was showing several channels off-and-on saturating
- The ITMY Optical Lever, which was not swinging out of its range, but moving abnormally large, say 50% of its range



For future forensics, the rough times that I had this large excitation going was roughly between 
GPS: 1073411801 and 1073412182
UTC: Jan 10 2014 17:56:25 - Jan 10 2014 18:02:46
PST: Jan 10 2014 09:56:25 - Jan 10 2014 10:02:46 

Drive was 0.1 to 10 [Hz] "uniform" white noise, using three independent awggui sessions, driving channels
H1:HPI-ITMY_ISO_Y_EXC    100000 [cts]
H1:HPI-ITMY_ISO_RX_EXC   100000 [cts]
H1:HPI-ITMY_ISO_RZ_EXC   100000 [cts]

The QUAD, ISI, and HEPI survived admirably (as expected), and after the excitation was turned off, SUS and ISI damping loops were immediately functional again, and it quieted down to normal damped motion with ambient input motion from an unisolated chamber. All software watchdog values have been set back to their nominal values.
Comments related to this report
jeffrey.kissel@LIGO.ORG - 14:51, Friday 10 January 2014 (9208)CDS, SUS
Regarding what it means for the ISI BLRMS performance matrix elements to be "solid red" -- remember the color corresponds to the ratio of the band-limited RMS of the motion currently and the aLIGO requirement for that stage. If the elements are red, the platform motion is greater than 100x the motion requirement for that isolation stage in that frequency band. For example, the RMS of the 1-3 [Hz] requirement is 6e-12 [m] RMS for ISI ST2, so the motion at ST2 caused by the excitation exceeded 6e-10 [m] RMS. Check out figure 2 of section 3.5 in E990303 for the full requirements, and T1100613 for details of the RMS calculation. I don't think there's specific documentation on the performance matrices themselves. 
jeffrey.kissel@LIGO.ORG - 16:29, Monday 09 June 2014 (12272)CDS, SUS, SYS
Just for posterity, I've trended the former version of the IOP, software watchdog's, RMS output values during this excitation test; see attached. 

Recall that this watchdog's trip threshold had been set arbitrarily at 15000 [ct] RMS. One can see that at this threshold, it would have never tripped for this amount of motion rendering it useless. The maximum (minute trend) peaked at roughly 8500 [ct], half of what the threshold has been for these trigger channels.

This version of the watchdog's RMS algorithm is known to be buggy, ringy, and will be replaced in the next release of the RCG, meaning this test will have to be performed again to properly tune its threshold. 
Images attached to this comment
H1 SUS (CDS)
david.barker@LIGO.ORG - posted 10:55, Friday 10 January 2014 (9205)
fixed adc problem with h1susauxasc0 model

The new h1susauxasc0 model was showing zero for the ADC channels. Problem was identified with the adc parts and bus selectors in the model. This was fixed and the model was restarted at 10:39.

Earlier (10:11) the DAQ was reconfigured to include this model and restarted.

H1 ISC
kiwamu.izumi@LIGO.ORG - posted 10:06, Friday 10 January 2014 (9203)
TMSX alignment of the day

I did the same alignment procedure as we did yesterday to steer TMSX to get the green light on the center of ITMX using baffle PD1 and 4.

TMSX alignment in its bias sliders:

Each of them could go up to 2.5 V when the gain is at 0 dB.

H1 AOS (AOS, TCS)
thomas.vo@LIGO.ORG - posted 09:34, Friday 10 January 2014 (9201)
TCS ITMY Ring Heater
The Integration Team found that the ITMY RH was giving off some false readback numbers like 7E+34 Amps, which is sure to be false. The glitch seems to have occurred on 12/24/13 around 8:19 AM PT.  The SVN shows that the code has not been changed since 12/10/13 and we had tested the pair on 12/04/13 as noted in ALOG 8816 so things were working before Christmas Eve.

After seeing this, I power cycled the chassis and ring heater driver and it seems to have fixed the problem.  Just as a precaution, I also added the trend of the vacuum pressure during this time and it doesn't show signs of any pressure changes.  I'll try to keep an eye on this in the future to see what the root cause might be.
Images attached to this report
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
alexan.staley@LIGO.ORG - posted 19:29, Thursday 09 January 2014 - last comment - 10:00, Friday 10 January 2014(9196)
HAM 1 Work

Alexa, Kiwamu, Koji, Sheila, Stefan

 

In the morning we worked on getting the green beam correctly positioned onto the periscope mirror and onto ISCT1. First we adjusted PR3 such that the beam was centered through the Swiss cheese baffle opening and the viewport. We then had to move the periscope mirror by 1.5inch toward the east, and move the top mirror up slightly. Following this, we finessed our adjustment of PR3 so that the ALS-X green beam was 4mm toward the east in the horizontal direction and 6mm up in the vertical (as specified by Ketia's alog). We also ensured the beam hit the periscope on ISCT1 with M11.

 

In the afternoon we were able to see IR POP flashes in HAM1. We had to adjust M10, M15, M16, BDIV1. The pop beam was centered on the LSC_POP_A PD; however, we do not see a strong enough signal. We do see a signal when we shine a flashlight onto the PD. We also aligned the pop beam onto the viewport towards ISCT1. Koiji adjusted the periscope location on ISCT1 so that the pop beam was well centered.  

Comments related to this report
kiwamu.izumi@LIGO.ORG - 06:38, Friday 10 January 2014 (9197)

Another thing we were not able to get finished was fine placement of the black glass beam dump for the reflected light off of the POP LSC PD. I was unable to see this beam even with an IR viewer. I will place the beam dump at a place which can be derived by the angle of the incident beam and the diode. I took several pictures of the PD for this particular purpose. Once I figure out a good location for the beam dump, we will enter HAM1 again today.

kiwamu.izumi@LIGO.ORG - 06:47, Friday 10 January 2014 (9198)

Also, Stefan and I installed an iris on ISCT1 for the X arm green light to record its landing point right. It is placed after the bottom periscope mirror. This should allow us to help speeding up the alignment recovery process. Note that when we put the iris, the green light coming to ISCT1 was the straight shot from TMSX and the arm cavity was intentionally misaligned.

kiwamu.izumi@LIGO.ORG - 08:19, Friday 10 January 2014 (9199)

I forgot to mention about one important quantity:

X arm green light at HAM1 was measured to be 27 uW with ETMX misaligned (i.e. non-resonant beam).

koji.arai@LIGO.ORG - 10:00, Friday 10 January 2014 (9202)

Supplimental info:

- Alignment adjustment by PR3
Pitch: H1:SUS-PR3_M1_OPTICALIGN_P_OFFSET
Yaw: H1:SUS-PR3_M1_OPTICALIGN_Y_OFFSET

- PR3 alignment at the middle of the visible range for the X green
Pitch: -254.0 / Yaw -254.4

- PR3 alignment to clip the beam at the edge of the mirror
Pitch: clipped at the top of the mirror:        -228
Pitch: clipped at the bottom of the mirror:  -265

Yaw: clipped at the negative Y side of the mirror: -226.4
Yaw: clipped at the positive Y side of the mirror: -288.4

- PR3 alignment to give the X green at the center of the periscope top
Pitch -246.5 / Yaw -257.4

- PR3 alignment slider to the spot displacement on the projection plane
Pitch 1.030 cnt/mm / Yaw 1.220 cnt/mm

- PR3 alignment slider to give the spot at (-4.2mm, 5.99mm) on the projection plane
Pitch -240.328 / Yaw -252.276


https://alog.ligo-wa.caltech.edu/aLOG/uploads/9202_20140110095939_HAM1_POP_Beam.png

Images attached to this comment
Non-image files attached to this comment
H1 SUS (CDS, IOO, ISC)
jeffrey.kissel@LIGO.ORG - posted 18:37, Thursday 09 January 2014 (9195)
ECR E1300578 Progress -- Finally a Passable Release of the new HSSS Infrastructure!
J. Kissel, D. Barker

I'll write a more detailed description of what was done later (and what will need to be done at LLO to absorb the changes), but I've *finally* finished the modifications to HTTS screens, and compiled and installed the new monitor model for the voltage readbacks of the HAM-A drivers. I don't claim perfection, but it's certainly good enough to commit to the SVN and release for more broad consumption.

New models:
${userapps}/sus/h1/models/
h1sushtts.mdl
h1susauxasc0
${userapps}/sus/common/models/
HSSS_MASTER.mdl

Tons of new screens:
${userapps}/sus/common/medm/hsss/SUS_CUST_H*.adl

Edited sitemap screen to call new screens:
${userapps}/cds/h1/medm/SITEMAP.adl

New / updated macrofiles:
${userapps}/sus/common/medm/*.txt
H1 SEI
fabrice.matichard@LIGO.ORG - posted 18:28, Thursday 09 January 2014 (9194)
SEI Matrices
After multiple errors were noticed in our change of basis calculations, we have been checking and recalculating all of them carefully. The results are compiled in T1000388. This document shows:
- the ISI and HEPI orientations with respect of the IFO axis
- the instruments locations and orientations
- the math and programs used to calculate the matrices
- the matrices for every set of sensors, and for each of the two possible modules orientation
- where the matrices are saved in the svn and how they are named
- the transfer functions for each type on instrument
- the old naming convention that we changed because it was too confusing

After thorough review, we are now confident with the HAM-ISI, HAM-HEPI and BSC-HEPI set of matrices. The BSC-ISI review is still in progress. 

Today we installed the HAM-ISI, HAM-HEPI and BSC-HEPI programs and mat files in the local directories, and we committed them in the svn. The old matrices have been backed up in "archives" sub-folders.

We have started populating the new (good) matrices in ETMX. In the coming days, the good matrices will have to be populated in other chambers when commissioning activities allow to do so. Safe.snap files will have to be saved accordingly. 
Displaying reports 68201-68220 of 77131.Go to page Start 3407 3408 3409 3410 3411 3412 3413 3414 3415 End