Displaying reports 48041-48060 of 87790.Go to page Start 2399 2400 2401 2402 2403 2404 2405 2406 2407 End
Reports until 16:50, Wednesday 07 March 2018
H1 PSL
jason.oberling@LIGO.ORG - posted 16:50, Wednesday 07 March 2018 - last comment - 16:54, Thursday 15 March 2018(40886)
PSL 70W Amplifier Installation Update

J. Oberling, E. Merilh

The last few days have been spent taking caustic measurements and searching for mode matching solutions so we can identify what lenses we need for mode matching prior to placing elements on the table; as a result there is not a whole lot of installation activity to report.  We left off Friday with a lovely LG01 mode in the Wincam.  On Monday morning Bubba very kindly shaved some mounts down for us (for WP02 and PBS02) to solve our clipping problem.  These were installed and the LG01 mode was still observed on the Wincam.  To see if we were seeing something real or just an issue with the Wincam, we borrowed a Thorlabs rotating slit beam profiler from the Pcal folks (who had lent it to the SQZ folks).  Setting this profiler up, we saw a nice Gaussian beam on the profiler.  Apparently something is up with that Wincam, so we will continue to use the Thorlabs profiler.

Using the same 300mm focal length lens, we took a measurement of the FE beam caustic, attached as LHO_FE_Caustic1.txt.  The first column is scale position in cm (corrected for the fact we had the wrong location of the sensor in the profiler when taking the measurement), and the last 2 columns are horizontal and vertical beam radii in µm, respectively.  This was imported into JamMT, the lens added, and the resulting FE waist given as 77.2 µm in radius, positioned ~15mm outside of the FE box.  This is uploaded as FE_caustic_after_distance_check.png (z=0 is the end of the scale used to take the caustic measurement, all distances are relative to that); we doubled checked all of our distance measurements this morning and made some small corrections, hence the filename.  While the location makes sense, the beam radius seems small as the LIGO FE lasers were all measured to be between 150µm and 250µm; although we have swapped the NPRO in the FE, which can have an effect on the waist size and location.  JamMT yielded only one mode matching solution with this initial waist that fits within the constraints of the beam path; this is uploaded as 70W_MM_solution1-FE_caustic_with_lens.png.  Unfortunately, I didn't think to take a picture of the measurement setup used; I'll take one tomorrow morning and upload it as a comment to this alog.

As a double check, we measured the caustic with no lens in place, and followed the same procedure as above.  The measurement is uploaded as LHO_FE_Caustic_no_lens.txt (same units as the previous .txt file, this time the position dimension is referenced to the FE box (since there was no lens installed)), and the resulting FE waist as FE_Caustic_no_lens.png.  As can be seen, something is not quite right with this measurement as it claims the waist is 2mm in diameter and located some 4.9 meters (yes, meters) behind the FE box (this is somewhere way past the NPRO and not in the FE box at all...), so this isn't the double check we thought it would be.  We tried installing a 400mm focal length lens in place of the 300mm, but this put the resulting focus off the edge of the table; a 200mm focal length lens gets the spot too small for the profiler to give accurate measurements.  We will do some more investigation of this in the morning (maybe try the 200mm lens anyway and see what we get), but at this point I think our best check is to set up the lenses from the given solution, put the Thorlabs profiler at the location the 70W amplifier expects the beam waist to be, and see what our beam diameter is.  If we're close, then onward we go; if not, then more investigation is needed.

Images attached to this report
Non-image files attached to this report
Comments related to this report
jason.oberling@LIGO.ORG - 16:54, Thursday 15 March 2018 (41029)

Promised picture of the setup used to measure the FE beam caustic.  This is the same setup used for both measurements, with the 300mm lens and with no lens.  The optics are, from right to left: 95%R output coupler, pump light filter, OD = 4.0 ND filter.  The Thorlabs beam profiler was moved along the scale attached to the table to get the distance measurements.

Images attached to this comment
H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:20, Wednesday 07 March 2018 (40883)
Ops Day Shift Summary
Ops Shift Log: 03/07/2018, Day Shift 16:00 – 08:00 (08:00 - 16:00) Time - UTC (PT)
State of H1: Unlocked during vent for upgrades
Intent Bit: Engineering  
Support: X
Incoming Operator: N/A
Shift Summary: Commissioning and upgrade work continues at both end stations. Vacuum work at Mid-Y. Alignment of the PSL 70W laser.  
 
Activity Log: Time - UTC (PT)
15:30 (07:30) Terry – In LVEA at ISCT6
16:00 (08:00) Start of shift
16:27 (08:27) Joel from RDO on site to deliver parts for tractor
16:43 (08:43) Marc – Going into the LVEA
16:44 (08:44) HFD – On site to run smoke tests at End-Y
16:46 (08:46) Sheila – Going to HAM6
16:57 (08:57) Marc – Out of the LVEA
17:11 (09:11) Travis – Going to LVEA to look for parts
17:17 (09:17) Richard – Going to LVEA to find headsets
17:30 (09:30) Travis – Out of the LVEA
17:31 (09:31) Jim – Going to End-X to lock the ISI
17:40 (09:40) Nutsinee – Going to ISCT6
17:58 (09:58) Rick, Niko, & Travis – Going to End-X for PCal work (WP #7404)
18:13 (10:13) Laser hazard at End-X
18:30 (10:30) TJ – Going to HAM6 for cabling work
18:31 (10:31) Jason & Ed – Going into the PSL enclosure for mode matching
18:31 (10:31) Marc – Going into LVEA to look a CRD
18:45 (10:45) Dave B. – Going into H2 building to work on 3IFO computers
18:50 (10:50) Betsy – Going to End-Y for chamber closeout work
18:54 (10:54) Chandra – Going to Mid-Y
18:56 (18:56) Corey – Going over the tube bridge to look for shipping container
19:04 (11:04) Elizabeth – Going to both end stations for marking off electrical exclusion areas
19:22 (11:22) Jason & Ed – Out of the PSL Enclosure
19:23 (11:23) Karen – Cleaning at Mid-Y
19:34 (11:34) Sheila – Out of the LVEA
19:38 (11:38) Nutsinee – Out of the LVEA
20:06 (12:06) Karen – Finished at Mid-Y
20:15 (12:15) Elizabeth – Back from end stations
20:21 (12:21) Rick, Niko, & Travis – Leaving End-X
20:21 (12:21) Laser Safe at End-X
20:54 (12:54) TJ – Out of the LVEA
21:02 (13:02) Terry – Out of the LVEA
21:03 (13:03) Contractor on site to see Chandra
21:14 (13:14) Karen – Cleaning in the H2 building
21:20 (13:20) Elizabeth – Into the LVEA for marking electrical exclusion zones
21:22 (13:22) Filiberto – Going to End-Y for ground loop checks
21:23 (13:23) Apollo crew – Taking one-ton to End-X to drop off pallet for SEI
21:27 (13:27) Jason & Ed – Into the PSL Enclosure for 70W amp work
21:31 (13:31) Karen – Finished in H2 building. – Going to Wood shop
21:46 (13:46) Sheila – Going to HAM6
21:44 (13:44) Marc – Going into LVEA to check the CRD
22:54 (13:54) Nutsinee – Going to HAM6
21:55 (13:55) Terry – Going to HAM6
22:15 (14:15) TJ – Out of the LVEA
22:41 (14:41) Rick, Evan, Darkhan, Niko – Going to End-Y for PCal
22:43 (14:43) Jason & Ed – Out of the PSL Enclosure
23:22 (15:22) Jim & TJ – Going to End-Y to work on relocking the ISI
23:38 (15:38) Marc – Going into the LVEA to check on the CRD
00:00 (16:00) End of Shift
00:03 (16:03) Marc – Out of the LVEA
 

 

H1 SUS
betsy.weaver@LIGO.ORG - posted 14:29, Wednesday 07 March 2018 - last comment - 13:34, Thursday 08 March 2018(40882)
ETMX SUS OPLEV trends - unexpected jump. Already.

This morning, Travis had to repoint the ETMX with some bias to get it back on the Oplev which I found odd.  The Oplev had been zeroed to the ETMX SUS last ~Monday reportedly by Jason.  However, besides that jump in the trend data, there is another jump on Tuesday.  I am guessing that the ISI EX model work/bootfest changed the pointing of the floating ISI/SUS.  Travis used the ETMX SUS to repoint back to zero.

This morning, Jim locked the ISI so hopefully there will be no more unexpected shifts due to anything ISIish.

Side note - try not to bump the OPLEV piers.  Ever. 

 

 

Images attached to this report
Comments related to this report
hugh.radkins@LIGO.ORG - 13:34, Thursday 08 March 2018 (40900)

Not that it isn't possible, but, it does not look to me like the reboots of the isi did anything to the OpLev readout.  Further, what can SEI do to pitch unless the optic is locked?  Based on everything I know and can see, I did not think the SEI could do this, it has only been DAMPED, READY or TRIPPED.

The attached 3 hour plot shows the OpLev Pitch, and WD, Guardian and CPS positions for the ETMX.  The step on the OpLev occurs at 1940 on Tuesday.  It is a full 14 minutes later that the Guardian is manipulated and 26 minutes later before the isietmx FE boot at 2006.  Below is the day boot start log--nothing is causal to the OpLev shift.  Meanwhile there is no hint of movement on the ISI (HEPI has been locked for more than a week) during the OpLev Pitch shift, (yaw is tiny) and none until the signals go to zero at 2005 at the start of the isi boot.  Just goes to show, sometimes you have to look closer.

hugh.radkins@opsws1:06 1$ more *.log
2018_03_06 11:13 h1asc
2018_03_06 11:13 h1omc
2018_03_06 11:13 h1sqzwfs
2018_03_06 11:15 h1susopo
2018_03_06 12:02 h1isiitmy
2018_03_06 12:04 h1oaf
2018_03_06 12:06 h1isietmx
2018_03_06 12:06 h1pemex
2018_03_06 12:13 h1alsex
2018_03_06 12:13 h1calex
2018_03_06 12:13 h1iopiscex
2018_03_06 12:13 h1iscex
2018_03_06 12:13 h1pemex
2018_03_06 12:24 h1oaf
2018_03_06 12:43 h1iopiscex
2018_03_06 12:43 h1pemex
2018_03_06 12:45 h1alsex
2018_03_06 12:45 h1calex
2018_03_06 12:45 h1iscex
2018_03_06 12:56 h1dc0
2018_03_06 12:57 h1dc0
2018_03_06 13:01 h1broadcast0
2018_03_06 13:01 h1dc0
2018_03_06 13:01 h1fw0
2018_03_06 13:01 h1fw1
2018_03_06 13:01 h1fw2
2018_03_06 13:01 h1nds0
2018_03_06 13:01 h1nds1
2018_03_06 13:01 h1tw1
2018_03_06 15:20 h1oaf
2018_03_06 15:20 h1pemcs
2018_03_06 22:03 h1fw0
2018_03_06 22:12 h1fw0
hugh.radkins@opsws1:06 0$ pwd
/opt/rtcds/lho/h1/data/startlog/2018/03/06
 

Images attached to this comment
H1 SQZ
daniel.sigg@LIGO.ORG - posted 13:17, Wednesday 07 March 2018 - last comment - 16:31, Wednesday 07 March 2018(40881)
VOPO Work

TJ Sheila Daniel

TJ fixed the short on DCPD2 betwen anode and case following Rich's suggestion of adding a piece of viton under the ceramic circuit board. The same was done for DCPD1.

However, wew found that for DCPD1 the anode and cathode are swapped. We made it work with some clip leads (for now).

We tested the PZTs and both of them are working.

Comments related to this report
thomas.shaffer@LIGO.ORG - 16:31, Wednesday 07 March 2018 (40884)

Small correction, I added a piece of Kapton tubing that we normally use to help route/control cables. I rolled the tubing and then cut a small slit vertically so that I could stick the top pin through and hold it in place. Picture attached.

Images attached to this comment
H1 SUS (CDS, DetChar, ISC, PEM, SEI, SUS, SYS)
jeffrey.kissel@LIGO.ORG - posted 13:01, Wednesday 07 March 2018 (40878)
EY / BSC10 Electric Field Measurements -- Take 3: Driven Fields Clearly Visible Above Sensor Noise
J. Kissel, G. Mansell

Georgia and I gathered one last data set with the prototype electric field sensor at BSC10 / EY, with the goal of measuring a few driven fields: the ISI coil drivers and the SUS ETMY's ESD Shield. With a reasonable drive (sine waves @300 Hz, with ~40% of the DAC range for the ISIs, as-low-as 5 Vpp on the ESD shields) we can resolve both clearly above the noise floor.

Attached are the results, in 2018-03-06_H1SUSETMY_BSC10_EFM_Results.pdf

We conclude (at the respective frequencies), the field generated per unit drive is 
                      Field Coupling     Units                          Notes
    ISI ST1 Coils        0.8723          (V.m^{-1}).A^-1                (Driven in V, 3 Vertical Actuators, 
                                                                         answer = mean(field ./ (3*current drive on V1)))
                         3.7284e-10      (V.m^{-1}).(DAC ct)_Z^{-1}  (answer = mean(field ./ (3*dac count drive on V1)))

    ESD Shield           0.0024451       (V.m^{-1}).V                   (answer = mean(field ./ voltage drive on shield))


%%%%%%%%%%%
Details
%%%%%%%%%%%
Measurement Setup Notes
    The ESD Cabling vs. The SHV Passthrough Box in which one can configure how the shields are connected, a.k.a "Shield Box"
    Associated Pictures: 2018-03-06_H1SUSETMY_ESD_CablesAtFeedThru_AsFound_Pics.pdf
        - We went up to the mezzanine work platform above BSC10 in order to connect / replace the current limiting resistor (CLR) box with the Shield Box, and we were surprised to find the chamber-feedthru-to-CLR-box-side of the ESD cables disconnected from the CLR box. This was both convenient and inconvenient for us: the cables we needed to connect to the Shield Box were already disconnected, but that meant we had to assume the cable ordering from the rack-side of the CLR box was correct and the box was a passthrough (I was 90% confident of this, but I note that this box is not in the wiring diagram -- D1400177). The order we found connected: 
        Rack-side CLR          Rack-side
          Box Label           Cable Label
            1                      LR
            2                      UR
            3                      UL
            4                      LL
            5                      Bias
        - Before connecting the chamber-feedthru-to-CLR-box-side of the ESD cables to the Shield Box, we tested whether the CLR-box side of the shields were grounded w.r.t. the chamber (a.k.a. "floating"). The were not grounded; they were floating. We did not check whether the chamber-feedthru side of the cables were grounded. We should have, but we're reasonably confident that the CDS team confirms this regularly.

    Driving the Shield:
    Associated Pictures: 2018-03-06_H1SUSETMY_BSC10_ShieldDrive_Setup_Pics.pdf
        - After connecting the chamber-feedthru-to-CLR-box-side of the ESD cables to the Shield Box (in the above described order), we had a frustrating amount of trouble trying to keep the Shield box (electrically) floating, i.e. preventing it from grounding, and making sure what voltage we applied to the Shield Box's shield "excitation" wire + gator clip actually went to the shields of the chamber-feedthru-to-CLR-box-side of the ESD cables. The "ShieldDrive_Setup_Pics" picks show that we needed the already-there clean wipe bag, and several used clean wipes in order to get the Shield Box chassis and all shields floating the desired affect, that driven voltage showed up on the shield and only the shield of the chamber-feedthru-to-CLR-box-side of the ESD cables.
        - We used an analog SR DS340 wave function generator to drive the shield, with the "func out" output set to High-Z. The output was connected to the gator-clip of the Shield Box's excitation cable with a BNC to clip-lead adapter that had its clip leads cut off. We were sure to wrap the gator-clip + (red) signal bare wire in a used cleanroom wipe to ensure shielding from ground. The (black) shield wire was floating in air.
        - In order to test that the drive was making it to the chamber-feedthru-to-CLR-box-side of the ESD cable shield and the system was otherwise floating, we requested a 1 V_{pk} offset from the SR DS340, and measured the potential difference between ground and the CLR-box side (now the Shield Box side) of the chamber-feedthru-to-CLR-box-side of the ESD cables.
        - We then BNC T'd in an oscilliscope to confirm the output levels of our various sine-wave drives (removing the 1V offset).

    The Field Meter:
    Associated Pictures: 2018-03-06_H1SUSETMY_BSC10_InChamber_Electrometer_Pics.pdf 
        - We re-installed the prototype field meter in the middle of the chamber on the bench that was in chamber. It was set up to measure the field in the longitudinal direction.
        - We guess that the field meter is about 0.75 meters away from the EY test mass, in the +X, +Y global coordinate direction.
        - Of acoustical note from the last time, this bench was sitting on used clean wipes, where as the previous measurements' bench had not.
        - At the request of others, we took a full-span measurement of the ambient chamber field (with the door covered in foil to rudimentarily complete the chamber faraday cage) with the return of the battery box floating (i.e. with the white banana clip hooked into the battery box, no grounding clip) and grounded (i.e. with the banana clip hooked into the battery box, and also electrically connected to ground). We saw no difference in these results (see pg 4 of the EFM_Results.pdf attachment) so we measured the remaining driven results with the return floating.
        - We used this reference ASD to find a nice quiet / sensitive region to drive. We chose the ~300 Hz region because it was above all of (what we think to be) acoustic noise, but still low enough frequency to be relevant to the most sensitive region of the IFO's DARM sensitivity.

    ST1 ISI Z Drive:
        - Both stages of the BSC ISI are mechanically locked to Stage 0, and HEPI is locked, so no physical motion of the platform is caused by driving the ST1 actuators at ~300 Hz.
        - We had to reset many layers of watchdogs, including the hardware watchdog in the EE HighBay in order to allow for ISI drive to occur.
        - Once able, drove the ISI in Z with a 367.3 Hz size wave (via awggui, with a 360-370 Hz 4th other cheby1 bandpass to be sure we were only driving at 367.3 Hz) in the H1:ISI-ETMY_ST1_ISO_Z_EXC field.
        - We drove at 200 ct_pk and 400 ct_pk at the ISO_Z_EXC point, which I later confirmed with dataviewer and DTT that that corresponds to identical drive to the V1, V2, and V3 actuators, at the level of 12700 and 25300 ct_pk, which is 8111 and 16223 ct_{rms} (as measured via ASD by a fres = 0.125 Hz BW spectrum, with the default Hann window; NENBW = 1.5, ENBW = NENBW*fres = 0.1875).
        - The two amplitudes were to check for / confirm linearity. 

    ESD Shield Drive:
        - With feedthru-to-CL-box ESD cables, the Shield Box, and waveform generator described as above, we drove three sign waves at 383.5, 321.9, and 269.1, to look for frequency dependence, and the first of which at three amplitudes to look for linearity.

Analysis Details
        - I calibrated the DAC output of the ISI into current across the coils by dividing by the following calibration (in matlab in post-processing) derived from D1001575,
             coildriver.c = zpk(-2*pi*136,-2*pi*[32 300],1);
             isiinterface.c = zpk(-2*pi*15.9, -2*pi*0.4, 0.4/15.9);
             actuator.g = 20/2^16 * 1.0 * 0.156; % A / DAC ct
             calibration.isi.c = actuator.g * coildriver.c * isiinterface.c;
        - That results in a calculated current of 3.4 and 6.9 uA_{rms} at 367.3 Hz on each coil.
        - To convert this to the total current through the three vertical coils, I just multiply by 3 to get 10.4 and 20.8 uA_{rms}.
        - Because the ASD I used is not bin-centered, I scaled this up a bit by the ratio of the data-viewer measured peak amplitude (converted to rms amplitude) and the peak amplitude measured in the MASTER_OUT ASD (again converted to rms amplitude). These factors were a small 10% correction to arrive at the numbers you seen in the legend of plot 2 in EFM_Results.pdf.
        - To arrive at the concluding answer above, I took the mean of the to rms amplitude ratios (noting that the SR785 uses a Blackman-Harris window as default, NENBW = 2.0044, fres = 0.25, ENBW = NENBW*fres = 0.5111)

Results Discussion
        - It appears the field scales linearly with both ISI and ESD shield excitation. Good! That's why I report the average in the concluding results.
        - With three data points, it's tough to say, but the lowest of the three frequencies we drove of the ESD shield showing a larger amplitude makes be suspicious that the shield coupling is frequency dependent.

What's Next
        - We intend to bring the field meter down to EX next and do a plethora of further exploratory measurements.
            - Take a more detailed frequency response of the field resulting from the ESD shield driving.
            - Try driving the signal and bias of the ESD
            - Try different DOF excitations on the ISI ST1
            - Try driving ISI ST2 actuators. (probably won't see anything, cause they're smaller than the ST1 actuators.)
            - Try driving OSEM coils. (probably won't see anything).
        - We also intend to project these results to DARM, essentially calibrating LLO's measurements of the shield driving to DARM (LLO aLOG 28675) into electric field units.
            
Images attached to this report
Non-image files attached to this report
H1 SEI
jeffrey.bartlett@LIGO.ORG - posted 09:24, Wednesday 07 March 2018 (40876)
ISI CPS Noise Spectra Checks (FAMIS #6940)
   Posted are the results of the IS CPS noise spectra. All look OK except HAM6. HAM6 is a bit elevated. Since there are many activities at or near HAM6 this is not necessary unexpected. Closing FAMIS #6940. 
Images attached to this report
H1 AOS
jeffrey.bartlett@LIGO.ORG - posted 09:01, Wednesday 07 March 2018 (40873)
Weekly PSL Chiller Checks and Top-off (FAMIS #6565)
   Add 150ml water to Crystal chiller. Added 200ml to Diode chiller. 
   As noted before, the crystal chiller filter is brown, due to 70W install, and will be replaced when the install is finished. The Diode chiller filter is OK. Closing FAMIS task #6565  
LHO VE
chandra.romel@LIGO.ORG - posted 22:19, Tuesday 06 March 2018 - last comment - 12:01, Wednesday 07 March 2018(40869)
CP4 regen bake

(late entry from today's work)

Today we valved in heated gas N2 to allow it to flow through the CP4 reservoir. We learned a few things:

  1. The regen heater has a thermocouple sensor (+ a second spare TC) at the heater elements (TE253B & TE235C), which is used as an over-temperature protection connected to a temperature limit switch inside the Watlow controller. The limit switch works; I was able to trip the heater a few times, mostly when heater is on with no GN2 flow. BTW, it appears TE253B does not work - I haven't looked at the field wiring to see if leads are connected at the heater; we simply switched leads to TE253C inside controller.
  2. I started GN2 flow when the bake enclosure was reading around 90C at TC#1 (supply air). This is when things got fun. The enclosure heater increased to full-on 100%, but all four temps we monitor were not increasing. Turns out the GN2 was absorbing all the excess heat. The regen pipe was warm at the entrance of the enclosure but the exhaust pipe was hot to the touch. The GN2 supply was not nearly as warm - measuring  around 30C at the TC outside the building, just downstream of the heater. I adjusted proportional gain setting in Beckhoff between values of 1 and 6, trying to ramp up the temp. of the GN2 relatively fast to more closely match the enclosure air temp. This process of beginning to warm up GN2 and equalize both systems takes a lot longer than I had time for this afternoon, so I will try again starting early tomorrow morning. For tonight there is no GN2 flow.
  3. We have a bug in the bake enclosure's PLC controls that needs to be worked out with vendor. Read aLOG for more details:  https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=40867

I insulated the exposed regen and exhaust pipes and wrapped the exposed purge valve underneath CP4 with Al foil. Also replaced broken TC#2 that measures air a few feet away from supply near top of enclosure (mounted to regen pipe). 

Comments related to this report
chandra.romel@LIGO.ORG - 08:23, Wednesday 07 March 2018 (40870)

Starting again this morning. Flowing small amount of GN2 to start (1/4 turn on valve ~ 20-40 scfhx100). So far no change on heat output from enclosure. Proportional gain set to 3, cycle time 0.1s and zeros for the I. and D. portions of Beckhoff PID parameters. Regen setpoint at 80C. Bake enclosure currently at 82C at TC#1 and heater at 41%.

chandra.romel@LIGO.ORG - 08:42, Wednesday 07 March 2018 (40871)

The PSI procedure calls for 50 gram/s of GN2 flow rate. 1 kg of GN2 = 30.42 cf, so 50 grams/s = 5476 scfh (our flow meter reads in multiple of x100, so the marker should fall roughly around 55 scfhx100.

chandra.romel@LIGO.ORG - 08:48, Wednesday 07 March 2018 (40872)

Increased flow by opening valve another 1/4 turn (open 1/2 turn total) to achieve 55 scfhx100. Regen temp peaks at around 75C and then falls to 55C and goes back up, with current P(ID) settings. No change on enclosure heater - still at 41%.

NOTE:  flow bounces around between 30-45 schfx100 because of the vaporizer. When it settles for moments, it reads around 20 scfhx100. I will continue to slowly open ball valve, referred to as the "vaporizer feed valve (V-11) in PSI documentation. Also note that the valve they refer to as "regeneration vent valve" (HV107) does not exist at LHO.

Taking detailed notes for future reference and for LLO's upcoming CP regen.

chandra.romel@LIGO.ORG - 09:14, Wednesday 07 March 2018 (40874)

Trend of regen temp (measured just downstream of heater outside in a TC well) and exhaust temp, measured by TC that is routed up the exhaust exit pipe a few feet (modified from original TC well from days of manual/sem-auto overfilling).

Images attached to this comment
chandra.romel@LIGO.ORG - 09:19, Wednesday 07 March 2018 (40875)

Opened up vaporizer feed valve by another 1/4 turn (3/4 turn total). More fluctuations in flow rate. Will continue to monitor as it settles. No change in enclosure heater (41%).

chandra.romel@LIGO.ORG - 09:58, Wednesday 07 March 2018 (40877)

Increased GN2 flow again (now valve is opened one full turn) with fluctuations around 40 scfhx100 or less. Also increased proportional gain setting to 5 to get regen temp closer to setpoint (80C). It was cycling around 60C with a setting of 3.

chandra.romel@LIGO.ORG - 11:20, Wednesday 07 March 2018 (40879)

Opened up vaporizer feed valve another 1/4 turn (1-1/4 turns so far), inching towards 55 scfhx100 flow (around 40 now). Also raised the prop. gain setting to 7 to get regen temp closer to set point of 80C. 

Enclosure heater now at 42% output and supply temp reads 85C. We will need to raise the setpoint today. I contacted the vendor about the bug in code (?) when we raise set point. We're finding we need a hard reboot of the system so the heater doesn't overshoot and push to 100% output. 

chandra.romel@LIGO.ORG - 12:01, Wednesday 07 March 2018 (40880)

Opend vaporizer feed valve another 1/2 turn for a total of two full turns open. Flow is hovering around 40 scfhx100. Increased regen GN2 setpoint to 95C with prop. gain setting at 7. Enclosure heater output is 43%.

LHO VE
kyle.ryan@LIGO.ORG - posted 20:40, Tuesday 06 March 2018 - last comment - 21:33, Tuesday 06 March 2018(40867)
Reboot of CP4 bake-out controller/PLC needed
Heat Profile Summary 

RAMP -> Increase measured temperature towards the SETPOINT value at a rate of 1C / hour 

SOAK -> After measured temperature attains the SETPOINT value, maintain measured temperature at SETPOINT value for time (hours) value entered as "HOLD" 

RAMP -> Decrease measured temperature towards value at a rate of 1C / hour to that seen at the start of the initial RAMP segment. 


We increased the SETPOINT value to 115C before leaving the site tonight.  Once home, I logged on and noticed that all four of the displayed (camera looking at controller display) temperatures had risen significantly from the values I had noted when leaving the site, i.e. had ramped up at a rate much faster than the program limit of 1C / hour should have allowed it to.  In spite of this, the heater output was showing 100%, i.e. was fully on (20 kW)!  The output should have responded and been 0% to prevent such a rapid temperature increase.  I also noticed that the "HOLD" lamp was on.  Thus, the heating profile had somehow advanced to the SOAK segment of the profile and was trying to get the measured temperature to match the SETPOINT value of 115C.  

I phoned Sheila D. in the control room and she agreed to go out the Y-mid station and help us remotely.  Unfortunately, she couldn't get into the building as the mid-stations require a unique key.  When I arrived, I lowered the SETPOINT value to slightly less than that of TC1 (T/C used by control loop) which should have caused the heater output to respond by decreasing down from 100%.  I waited several minutes, but the heater output never changed and the HOLD lamp stayed on.  I ended up power cycling the control unit and restarting the program.  I also lowered the SETPOINT value.  It seems to be working now.

NOTE 
TC3's bimetal junction must be sampling the air even though it is intended to be clamped to the SST of CP4.  I believe this because it changes much too rapidly as should be physically possible while in contact with a large mass and it behaves much like TC1 and TC2 which are intended to be sampling air.  TC4 is confirmed anchored to the lift eye on the side of GV11 and is the only T/C which behaves as if in good thermal contact with a large mass of SST.  I will re-examine TC3 tomorrow.  




Comments related to this report
chandra.romel@LIGO.ORG - 21:33, Tuesday 06 March 2018 (40868)

I also had to reboot the unit by power cycling it on Saturday when raising the set point. After raising the set point, the heater power increased, causing the control and readback T/Cs to ramp up much faster than 1C/hr. I will talk to the vendor about this bug.

H1 SUS (DetChar, ISC, SEI, SUS)
jeffrey.kissel@LIGO.ORG - posted 17:49, Thursday 22 February 2018 - last comment - 16:40, Wednesday 07 March 2018(40675)
Adding Viton Beneath Balance Masses of H1 OPO (an OPOS) Reduces Broadboard Bending Mode Qs by a Factor of 2-3
Á. Fernández, J. Kissel, T. Shaffer

Álvaro, T.J. and I B&K hammered the optical parametric oscillator suspension's (OPOS) fully-payloaded bread board today, both with and without viton beneath its balancing masses. The reduction of bending mode Qs was about a factor of 2 to 3. Not very impressive -- my feeling is that we're either (a) putting viton where there is little bending, and/or (b) the balance masses do not provide enough moving mass at these mode frequencies to really suck out the mode energy through the viton.

I've not been tied close enough to this suspension to know if there is further action / improvement to make or take. Are there specific requirements we're trying to meet? Comment below if you have.
(Note, these results show that traditional, yet often broken, requirement of "Anything attached to the HAM-ISI must have its first bending mode resonances above 150 Hz" has been meet. Also, the addition of viton does not and will not have any affect on what ~1 Hz ISI - OPOS plant interaction issues Arnaud saw in LLO aLOG 37394.)

I attach the transfer function results.

We struck the platform vertically down at the outer edges, in the +Transverse corner and in the +Longitudinal corner (see E1700390 and/or G1300086 for basis definitions), and measured the response with the usual three-axis accelerometer. I only show the vertical response to each vertical excitation. 

Stay tuned for pictures. 
Non-image files attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 09:21, Friday 23 February 2018 (40680)

Adding some pictures of the accelerometer location, hit locations, and some pictures of the added viton. The viton we added was a mixture of some 1/16" thick pieces and some 1/16" thick tie down strips. We used these pieces mainly because it was what we had available. We adding viton to all of the large masses and then tried adding it to some of the smaller masses to try to damp some of the higher frequencies. Since we were hitting a floating suspension, Alvaro had to tap very lightly the floating platform itself, while I would watch one of the stops to make sure it didn't hit.

Attachments are:

1 -- Hammer location one (+ transverse).

2 -- Hammer location two (+ longitudinal).

3 -- Accelerometer location.

4 -- Accelerometer location closer picture.

5-11 -- Various pictures of viton placement on the suspension.

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 16:40, Wednesday 07 March 2018 (40885)SEI, SQZ
I attach the raw data (.pls files), the exported data (.txt files), and the script used to analyze the data.
Non-image files attached to this comment
Displaying reports 48041-48060 of 87790.Go to page Start 2399 2400 2401 2402 2403 2404 2405 2406 2407 End