- Justin to LVEA, laser safe transition.
- John to LVEA, soft close GV6 and GV8, per WP4380.
- Bubba and crew to LVEA, remove HAM01 door, per WP4379.
- Mitchell and Andres to LVEA, AOS/ACB assembly work.
- Corey to MX, store items.
- Filiberto and Aaron to Y-End, inspection of installation.
- Justin to LVEA, supervise locksmith.
- Luis and Frank to X-End, PEM cable work.
- Justin to LVEA, laser hazard transition.
- Thomas to LVEA, alignment of OLs.
- Mitchell to LVEA, AOS/ACB assembly work.
- Dave from CR, lots of reboots per WP 4382.
- Karen and Chris to LVEA, HAM4 cleanroom, clean area per WP4384.
- Filiberto and Aaron to X-End, Install GigE camera on A1-C, port VP5, per WP4386.
Mark B. and Kiwamu.
Yesteday afternoon, Kiwamu reported that the MC2 guardian was giving an error in line 104 the SUS.py script. This was a call to a method from sustools.py in the definition of the ALIGNED state:
self.optic.lockGainWrite(1.0,[],[], [P,Y])
This could never have worked - all arguments to lockGainWrite other than the first are keyword arguments, and the non-empty list should be of strings. I changed it and a similar instance (line 120) to
self.optic.lockGainWrite(1.0,chans=['P','Y'])
That solved the initial problem and exposed a second: there was no file ^/sus/h1/burtfiles/h1susmc2_misaligned_offsets.snap .
I created one by copying h1susmc2_aligned_offsets.snap and manally putting in new offsets suggested by Kiwamu.
I committed the fixed SUS.py and added and committed everything else in the ^/sus/h1/burtfiles and ^/sus/common/guardian directories.
References: aLOG 6683, https://dcc.ligo.org/L1200282, https://dcc.ligo.org/T1200470, https://dcc.ligo.org/D1000313-V9
Attached shows the relative position of ALSX, ALSY and POP (from L1200282) together with two top periscope mirror profiles (equidistant from three beams and centered on ALSY, the latter is supposed to be the current configuration). Green and red circles show the beam diameter obtained from T1200470 and D1000313-V9 (V10 doesn't have the beam profile information).
With the "centered on ALSY" configuration POP is close to the edge of the mirror. Today HAM1 incursion team will move everything such that periscope and downstream will be equidistant from three beams though we have only the ALSX for the moment,. They'll also try to find POP in HAM1 again with the new alignment.
I installed the following IPC links: ASC to ISCEX: PZT1X_PIT PZT2X_PIT, PZT1X_YAW PZT2X_YAW (all four are being received) ASC to ISCEY: PZT1Y_PIT PZT2Y_PIT, PZT1Y_YAW PZT2Y_YAW (all four are being received) ASC to SUSTMSX: TMSX_PIT, TMSX_YAW (not being received yet) ASC to SUSTMSY: TMSY_PIT, TMSY_YAW (not being received yet) (links for ASC to ETMs and ITMs were already installed.) checked in h1asc.mdl: SVN revision 6769 h1iscex.mdl: SVN revision 6770 h1iscey.mdl: SVN revision 6770 We are still getting some IPC errors.
J. Kissel, S. Ballmer, D. Barker I've completed the install of the new IPC communication between the ASC front-end model and the TMS and HTTS models for green / REFL alignment control. This required - (as Stefan mentions above) Adding RFM IPC parts to the ASC model to send to the end-station SUS computers, H1:ASC_TMSX_PIT_SUSTMSX H1:ASC_TMSX_YAW_SUSTMSX H1:ASC_TMSY_PIT_SUSTMSY H1:ASC_TMSY_YAW_SUSTMSY - (as Stefan *didn't* mention above) Adding SHMEM IPC parts to the ASC model to send to the HTTS core on the same front-end H1:ASC_RM1_PIT_SUSHTTS H1:ASC_RM1_YAW_SUSHTTS H1:ASC_RM2_PIT_SUSHTTS H1:ASC_RM2_YAW_SUSHTTS - Modifying the ASC and OAF IOP model parameters to turn on the RFM capability (Set "rfm_dma=1") - Installing all of the above mentioned channel into the respective receiver models, and hooking them up to the already-present place holders in the ISC input bus creator, h1sustmsx --> H1:ASC_TMSX_PIT_SUSTMSX, H1:ASC_TMSX_YAW_SUSTMSX h1sustmsy --> H1:ASC_TMSY_PIT_SUSTMSY, H1:ASC_TMSY_YAW_SUSTMSY h1sushtts --> H1:ASC_RM1_PIT_SUSHTTS, H1:ASC_RM1_YAW_SUSHTTS, H1:ASC_RM2_PIT_SUSHTTS, H1:ASC_RM2_YAW_SUSHTTS - Re-compiling, Re-installing, Re-starting, and Re-storing all of the following models: h1iopasc0 h1iopoaf0 h1asc h1sustmsx h1sustmsy h1sushtts All of the modified models mentioned above have been committed to the userapps repository. Taking down H1 SUS TMSX naturally trips the watchdog on HPI and ISI ETMX, so Hugh and I made sure to ramp down all offsets before getting started. After restoring, Hugh has brought up HPI ETMX and ISI ETMX, and I've restored the alignment of both SUS ETMX and SUS TMSX. No one is using the RMs just yet, so they have not been restored -- and indeed, they do not yet have a good safe.snap, so they will need a complete restore from scratch. Bummer.
The attached plot shows the XEND pump down and transition to BT operation. 30 days are shown.
Over the Christmas break we operated on the main turbo only. On Jan 6 the transition to the main ion pump and 80K pumps was made.
After isolating the main turbo the beam tube valve was opened for HIFO X work.
You can see that the the pressure has come to ~4e-8 torr in the BSC chamber (pt510). The two gauges on the 80K pump and the beam tube are both below 2e-8 torr.
In summary the transition from turbo only to final configuration has bought us slightly more than a factor of 10 improvement in pressure.
The LVEA transition is shown in this alog https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=9119
For reference, guidance related to opening to the beam tube is here: https://dcc.ligo.org/LIGO-T1300802
After the alignment of PR3 (see alog 9146), I aligned PR2 and PRM to get PRX flashing with the infrared light. The resultant alignment sliders are shown in the attached.
I could lock PRX quite smoothly, but it seems that some optics are oscillating in pitch by a non-negligible amount. Due to this, the intracavity field spatially wobbles by almost its beam size in pitch according to the CCD camera attached on BS's chamber. In this condition, the intracavity power observed by the POP_A QPD fluctuates more than 10%. We need to identify which optic is the culprit by using the oplevs and witness sensors. It seems to me that it is hopeless to try locking PRMI without improving this wobbliness.
An additional note:
The spatial beam motion was observed by introducing an intentional misalignment in ITMY and BS to let the ITMY reflection beam hit the BS baffle which is monitored by the BS CCD camera.
Greg G, Thomas V I tricked Greg into helping me and we successfully installed and aligned the ETMX optical lever; it will need to be calibrated it next but that will not require the closure of a gate valve. At the first shot of alignment, there was some clipping on the edge of the viewport so we had to modify the transmitter mount which took a bit more time than I expected. Note: We adjusted the height of the receiver pylon to line up the viewport to the optical lever enclosure, but this did not take into account what will be needed for the photon calibrator receiver so we might have to revisit this in the future.
Green arm transmission was first found on the Swiss cheese baffle while scanning PR3.
After centering the beam on the POP hole in the baffle (PIT was already good, YAW was off by 86urad), we looked inside HAM1 and found that the beam was already coming in that chamber. The beam was hitting somewhere on the green/IR separator M10, and some scattering or maybe specular reflection was hitting the beam duct of IR POP path, but nothing seemed to be hitting the green steering mirror M11.
Turning PR3 by +10urad in YAW and the beam was already blocked on the mirror holder of M11.
Turning PR3 by -10urad in YAW and the beam was nowhere to be found in HAM1, and we couldn't identify where the beam is blocked in HAM2, but it kind of seems from one of the GigE cameras that the beam might be blocked by one of the MC towers.
See attached if this helps.
Right now PR3 is set to the "neutral" position where the beam is centered in the baffle hole, but probably that's not the right thing to do (because the space between MC1 and MC3 tower gives us a tight aperture in YAW). We'll go in HAM1 tomorrow to find a right solution.
One positive thing is that it seemed as if we're locked to 00 mode.
However, refl power is supposed to drop to 45%-ish in an ideal case, we're only getting 90% or so, and our mode matching cannot be that bad (see earlier alog), so the alignment is far from ideal (Kiwamu and Sheila confirmed that no dither was used for aligning it).
I went back to the end station to look into why the frequency comparator readback has not been reliable. There was 1MHz oscillation on the readout of the PD that is similar in size to our beatnote, which was confusing the frequency comparator. The oscillation goes away when the noise eater is on, and the frequency readback works well. For now I have left it on, although this isn't a long term solution.
In alog 6669 I came to the opposite conclusion, that the nosie eater had to be off to avoid oscillations at 1 MHz that confuse the frequency comparator. A high pass in the path to the frequency comparator might take care of the problem.
Cyrus created a new EPICS gateway between the H1-AUX and H1-FE VLANS to permit the DAQ EDCU to acquire the new PSL Centroid EPICS channels created by Chris W. The new gateway is called h1aux-h1fe (client on h1aux, server on h1fe). The DAQ EDCU quickly connected to the new channels and became GREEN.
Today we were frought with more fiber pulling issues. After sorting user errors with the profile math yesterday, today the fiber puller was cranky. The latest problem this afternoon was that a piece of the mechanics on the bottom stage of the puller pulled out of place (a problem that has been seen before). It will (again) take a few hours of their time to fix tomorrow.
Meanwhile at EY, Jason and I repositioned the UIM and PUM in prep for the rewelding scheduled for later this week. When we went to position the test mass, Jason discovered that the HR return beam was very faint and the autocollimator could not get a reading off of it. LLO reported this finding when they did their ETM. We will pull the First Contact thin alignment sheet down a bit and try see if that improves the visability. Otherwise, we may entertain the idea of sighting off of the AR surface for pointing which has a much better return for the 670nm autocol beam.
Oh, and the cookie cutter for repositioning the ETMy QUAD upper structure on the ISI appears to have been machined incorrectly. I have time to fix it.
Fire Department on site doing maintenance Installation and alignment of the GigE cameras at the HAM2 and HAM3 spools – Kiwamu Centering SR2 BOSEMs at LVEA – Jeff B. Baffle work at LVEA West bay – Mitchell Electrician working at H1 electronics room Work at End X – Sheila/Koji/Alexas Turning Off aLOG, SVN, and awiki services due to hardware problems – Jonathan Work on H1 PSL diode room – R. Savage Cable pulling from Electronics room to HAM2 – Luis aLOG, SVN, and awiki services have been turned ON – Jonathan Remove the HAM1 viewport covers and/or camera cans – Keita/Kiwamu/Sheila/Koji/Alexa Soft-close GV20 at End X- Kyle Removing yellow cover from viewports on HAM1, HAM2 and HAM3 – Stefan Fix to the ETMX, ETMXY, TMSX and TMSY models – Jeff K. Hardware cabling at End X - Richard
In anticipation of some new changes to the ASC_MASTER library part, I updated it to the latest version from LLO. This includes pitch and yaw outputs for RM1,RM2,OM1,OM2. I updated our h1asc.mdl accordingly, recompiled and restarted it. SVN version number 6759.
I modified ASC_MASTER library part to route initial green arm alignment signals in and out. This added six new inputs (green arm signals) and twelve new output signals (controls for TMS, PZT1, PZT2, both pitch and yaw). ASC_MASTER.mdl was checked in to SVN: revision 6761 I also updated h1asc.mdl to deal with the additional in and outputs. For now I connected the twelve RFM IPCs to ISCEX/Y and SUSTMSX/Y. The inputs are still grounded, because the sending models have to be updated first. h1asc.mdl was checked into SVN: revision 6762 The model was compiled, installed and restarted.
I am in the process of updating the ISCEX and ISCEY models to receive the newly sent alignment dither signals for the PZTs. ALS_END.mdl was updated, and checked into SVN: revision 6763 I am in the process of editing h1iscex.mdl and h1iscey.mdl More tomorrow.
Back on 23 December, Keita found the need to tilt the HEPI to pitch the TMS. Attached is a plot showing the T240 signal going back 30 days from now. The time keita tilted the HEPI is pretty obvious in the middle of the trends when tilted axes of the T240s are affected. Much of the period since 23 Dec has the ISI off (tripped from T240 saturations) and so not the source of the increase in these T240 signals.
As I've logged before, the ETMX ISI has not managed to stay engaged for more than a few hours since this time. Notice too on these trends, the signals with the largest amplification has a regular hit of the rail. The second plot I've attached is a single channel of 15 days. Notice the rail hit every 24 hours; this is to the minute as best I can tell from a 15 day dv trend. I am suspicious that this is real given the periodicity.
Finally, the last plot zooms in to 8 days of this channel and I've added a channel indicating the HEPI tilt. Notice in the middle of the plot where on 2 & 3 Jan I'm mucking about with tilts and ISI. The noise of the T240 is reduced when there is no tilt applied.
Duplicated this situation at ITMY. We removed the HEPI position loops and took the ISI to damping only and then tilted the HEPI -12000 counts in the same method as the ETMX. Attached is the nominally affected channels. Upper right trace is the offset. There is no large difference between the periods of offset and no offset; certainly not to the extent it is seen on the ETM. Fabrice is currently repeating this measurement at ETMX while ISC has relenquished control.
For the record, the following are the nominal values used for the large ion pump controllers (listed in the order queried by the MultiVac firmware Flow 7): Torr Spare 7000V 200mA 200watt Protect 10mA STEP 5000V 1.0 x 10-3amps 3000V 4.0 x 10-5amps (StPt 1) 1.0 x 10-5torr (not used?) (StPt 2) 1.0 x 10-6torr (not used?) 1.0 x 10-10 1.7 x 10-9 8.0 x 10-7 2.0 x 10-4
Correction: 1 x 10-3 amps (should be) 3 x 10-3 amps