I ran the script that Hugo prepared for me at around 7:34:30 in UTC or 0:34:30 in PDT. I confirmed that it successfully switched the blend filter for Z in ETMX ISI to the one he wanted to test. I am leaving it in this configuration as requested by Hugo.
Those who perform X arm comissioning tomorrow should not forget to switch it back to the nominal configuration by running:
/ligo/svncommon/SeiSVN/seismic/BSC-ISI/H1/Common/Misc/Test_Configuration_Scripts/Switch_To_Comm.py
Note:
before running the script, I steered ETMX to an angle which is far enough from the aligned value so that it does not interfer with the corner locking but still gives an OK centering for oplev. This resulted in (PIT bias, YAW bias) = (403, 86).
Alexa, Sheila, Kiwamu,
We are concluding that the DRMI seems to have a high rate of the SRC mode hops when the arm cavities are present. At this point, it is unclear why.
(A comparison test with and without arm cavities)
We locked the DRMI while holding the arm cavities at a off resonance point (750 Hz away from resonance in IR) by ALSs. The number of the mode hop was as high as once a second or so. As usual, a SRCL offset of -800 cnts could help reducing the mode hops and also aligning the DRMI helped it as well. However we could not completely get rid of the mode hops at the end. So we quickly switched back to a simple DRMI by misaligning ETMs to determin whether if it is an issue only when the arms are resent. Indeed, the simple DRMI locked and stayed without a mode hop. So the arm cavities really increase the rate of the mode hops.
Note that there was a good DRMI stretch starting at Oct-29 7:00 UTC.
We also tried engaging the ASC loop that had been tuned up for a simple DRMI. This did not look very promising as it was not able to reduce the number of mode hops. It may have been a situation where the ASC was not able to correctly work because of too many hoppings. We don't know what exactly was going on yet.
(Some ETM suspension adjustment for DIFF loop)
The roll mode rang up tonight as well in ETMY. We decided to use only ETMX until the roll mode settles down. Also we changed the L3 gain from 0.8 to 1.1 in ETMX because we saw an oscillation at the cross over frequency at around 2-ish Hz when the gain was at 0.8 and ETMY was disabled. We could not push the UGF of the DIFF loop to 10 Hz because of saturation in the ETMX ESD supposedly due to the roll mode dominating the rms. We decreased the overall LSC UGF by a factor of 2 or so in order to avoid the saturation.
At some point, we were suffering by an issue of the X arm being misaligned as the LSC feedback got bigger. This turned out to be a bad L2P decoupling in the L2 stage which Sheila turned off (alog 14428) because the filter was thought to be bad. We have no idea what has changed since then, but it was obvious tonight that the L2P decoupling filter really helped the decoupling and improved the stability of the DIFF loop a lot. We now enabled it.
(SR3 opelv damping loop was off)
When locking the DRMI, we noticed that a pitch mode of an optic was too large that it was inducing more mode hop in the SRC. We identified it to be SR3 whose oplev pitch loop had been switched off. So we switched it back on and this helped the stability of the DRMI.
Sheila, Patrick, Daniel, Alexa, Chris, Kiwamu, Evan
Before we started commissioning tonight, we had to recover from some maintenance day activities.
Alexa, Kiwamu,
In response to Keita's alog about the PR2 baffle, we took a peek at the PR2 baffle by opening some of the viewports on HAM3 and HAM2 spool.
Conclusions:
(PR2 baffle check out)
We opened up a viewport on the East side of HAM3 which the leftmost one with an illuminator attached on. This was the only available viewport to open up. We removed the illuminator and looked at the baffle through the viewport. We confirmed that there was no cross bar structure on the side of the baffle unit as shown in the DCC document (D1000328). We could not see the top part of the baffle where it supposed to have a cross bar structure. We took some pictures and I attach them to this entry.
(Peek at the aperture position)
Then we tried a different zooming in the PR2 digital camera in order to have a better view so that we can determine if the aperture hole is in the middle of the baffle unit or not. With a help of flash light illuminating the PR2 baffle from the HAM2 East side viewport, we could clearly see the edge on both right and left sides of the unit as well as the edge of the aperture. It looked like the hole is centered with respect to the right and left edges of the unit. We took several pictures of it via the digital camera so that one can evaluate the position later if necessary.
(MC2 scraper baffle check out)
Then we opened up another viewport on the West side of HAM3 in order to see both MC2 and PR2 baffles. Though, the MC2 baffle was completely occulting the PR2 baffle and therefore we could not see it. We could still confirm that the MC2 baffle has a cross bar structure on the side as shown in the design document (D1000327).
The baffle hole seems to be centered in the baffle frame within 3mm from the picture. Good.
The distance from the left baffle hole edge to the left inner edge of the baffle frame is about 52 pixels, it's 56 pixels for the right, i.e. about 2 pixels offset to the left, which corresponds to 2 or 3mm.
Keita
The hole diameter is also good (i.e. the ratio of baffle frame width to the hole diameter on the picture reasonably agrees with the spec).
Switch between the first attachment and the second to see if you agree with my assessment of the edges.
Nominal | Image | |
Baffle diameter | 2.756" | 53px |
Baffle height | 8.34" | 160px |
Baffle width | 8.74" | 165px |
Diam/Width | 0.315 | 0.321 |
Height/Width | 0.954 | 0.970 |
Center offset | none | 2px to the left ~ 3mm |
Similar to what was rolled-out earlier today for the Suspensions (see LHO aLOG entry 14657), I've now svn'd up the latest HAM-ISI & HEPI MEDM Overview screens, which includes the embedded Guardian mini control-panel providing access to requestable states, as was developed at LLO (see LLO aLOG entry 15010). The following MEDM screens were updated:- /opt/rtcds/userapps/release/isi/common/medm/hamisi/ U ISI_CUST_CHAMBER_OVERVIEW_LARGE.adl U ISI_CUST_CHAMBER_OVERVIEW.adl /opt/rtcds/userapps/release/hpi/common/medm/hepitemplate/ U HPI_CUST_CHAMBER_OVERVIEW.adl Screen-shots of the updated HAM-ISI & HEPI MEDM Overview screens are attached below.
added 802 channels removed 524 channels
I've scheduled a RH-X test to run from around 2:45AM for 5 hours.
We reported last week that the pitch RMS motions of the bottom masses was dominated by 0.5 Hz features on all BSC units. We are looking at the coherence between ISI, Suspension top mass and optical levers to find out how to reduce the bottom masses angular motion.
Plots:
The first figure attached shows coherence plots, the second figure shows transfer functions plots:
- in the top left, from "ISI longitudinal" to "SUS top mass longitudinal"
- in the top right, from "ISI longitudinal" to "SUS top mass pitch"
- in the bottom left, from "SUS top mass longitudinal" to "Optical Lever pitch"
- in the bottom right, from "SUS top mass pitch" to "Optical lever pitch"
Comments:
At 0.5 Hz,
- the coherence between ISI longitudinal and SUS top mass motion is not very high. We'll add more ISI channels to see how they contribute to the suspension point motion.
- the coherence betwen the suspension top mass and the optical levers is above 0.9 (above .99 in some instances). The BS longitudinal to pitch transfer functions show a Q around 20. The pitch to pitch transfer functions show similar Qs for all units. We can compare this to damping models.
Corrections:
- I used one hour of data starting on Monday Oct 27, 3 am PT.
- I fixed the axis labels and plots titles
SUS and LSC model changes. Jeff K
many sus models and LSC were changed. New IPC added between them. susaux models at end stations also changed.
HEPI Pump Controller. Hugh R
new EPICS databases started on EX and EY HEPI pump controllers. MEDM changed accordingly.
DAQ FW1 file system increase. Jim, Dave, Dan
h1ldasgw1 file system grown to use two raids.
Patch and Restart Workstations. Cyrus
All CDS workstations patched and restarted
Beckhoff changes. Patrick
Beckhoff systems for C1 (PLC1,3) X1 (PLC3) and Y1 (PLC3) modified.
DAQ reconfigured. Dave
DAQ reconfigured for Beckhoff and HEPI pump controller and susaux(ex,ey) changes. Restarted twice, needed start_streamers on various frontend after second restart.
Installing SUS DRIFTMON. Jim, Dave
Installing a test version of driftmon which doesn't require additional EPICS records. Testing NDS2 data collection parameters.
Beckhoff INI generator continues to write duplicate channels H1:PCL-ERROR_[CODE,FLAG] from both end stations. Would be nice if someone could fix this, I have to hand edit the ini files to prevent DAQ lockup on restart.
Aidan. Alastair
Following a successful install of the HWSY correction, we realigned the HWSX optical system to accomodate a change in the green leakage field from four weeks ago (probably due to changes in alignment of the BS and SR3). We coarsely matched the ALS and 800nm optical axes through the irises. We fine-tuned the centering of the probe beam to the ITM by observing the location of the center of the intensity relative to the center of the shadow from the BS and tweaking the alignment of the upper periscope mirror to get the intensity distribution concentric with the shadow.
We will run RH tests in the morning to try to ascertain the exact location of the centers of the ITMs in the HWS coordinates.
However: when I turned on the HWS-Y SLED, the HWS-X sensor started going haywire. By reviewing the camera stream from HWS-X itself, it became clear that some of the HWS-Y probe beam is making it into the HWS-X camera. We haven't yet figured out what this leakage path is. We can still run the sensors one at a time as diagnostics. Only HWS-X is currently running.
And: we're seeing glitches in the frames from HWS-X that have been seen before. They manifest as part of the image being transpose with another part of the image. This is clearly a digital issue (probably access of the framegrabber). It has really only been observed when we try to access both cameras from the framegrabber.
Images of the HWS-X camera stream, with and without the HWS-Y probe beam turned on, are attached.
WP 4916
Dan Moraru
The file system for writing frames on h1fw1 has been expanded by attaching a second SATABOY raid similar to h1fw0. This will provide a look back capability similar to h1fw0 as data is written over the coming weeks. The current look back capability of h1fw0 is:
Data | Hours |
---|---|
Commisioning frames | 356 |
Science Frames | 74 |
Minute Trends | 106 |
Second Trends | 851 |
8:15 Jodi and guest to LVEA
8:15 RichardM to LVEA to check ITMX HEPI L4C
9:00 Mitch to LVEA
9:15 Hugh to EX/EY hooking up HEPI Pressure sensors, back at 11:00
10:15 Betsy to LVEA
11:00 Karen to EY
13:30 Betsy back out to LVEA
14:30 JeffB and Andres to LVEA, moving 3IFO sus
15:00 Kyle to EY work wit Rai, back 16:00
I have tried to use the Guardian to isolate HAM2 ISI seven times today and it has never succeeded. Three times early ~8am, twice at 1250, and twice at 1500. Everytime I use the command script it succeeds. Another thing I've noticed the Guardian does differently from the old Command script: The Guardian loads the reference location at the intermediate points whereas the command script does all 6 dofs at the end.
Attached is the GS-13 Spectra after switching to the 100mHz Blends on X Y & Z. Again, it doesn't appear to be a better controller.
The ITMY RH is on at 4W for beam location of the HWS beam.
The default NDS server has been restored to h1nds1. This applies to all new logins, shells, or processes that use NDS, all currently running processes are unaffected and will continue to use h1nds0.
Work under permit 4919 and possible missed stuff from 4917: corner station quit IOC C:/SlowControls: svn update H1ECATC1: PLC3: 'Update from source' C:/SlowControls/Target/H1ECATC1/H1ECATC1.tsm: PLC1 rescan project, PLC3 rescan project; Actions -> Generate mappings, Check configuration; Save Copy C:/SlowControls/Target/H1ECATC1/H1ECATC1.tsm to C:/SlowControls/Scripts/Configuration/H1ECATC1/SYS/H1ECatC1.tsm. svn commit C:/SlowControls/Target/H1ECATC1/PLC3/PLC3.pro: rebuild all, save Copy C:/SlowControls/Target/H1ECATC1/PLC3/PLC3.pro to C:/SlowControls/TwinCAT/Source/Interferometer/Corner/Plc3.pro C:/SlowControls/TwinCAT/Source/Current/Interferometer/Corner/Plc3.pro: Export EXP. svn commit Plc3.pro and Plc3.exp. C:/SlowControls/Target/H1ECATC1/H1ECATC1.tsm: PLC3 rescan project; Actions -> Generate mappings, Check configuration; Save. Copy C:/SlowControls/Target/H1ECATC1/H1ECATC1.tsm to C:/SlowControls/Scripts/Configuration/H1ECATC1/SYS/H1ECatC1.tsm. svn commit H1ECATC1: SYS, PLC1, PLC3: 'Stop', 'Update from source', 'Compile': Compile failed. C:/SlowControls: svn update H1ECATC1: SYS, PLC1, PLC3: 'Stop', 'Update from source', 'Compile', 'Activate and run': TwinCAT PLC Control has stopped working Restart computer quit IOC H1ECATC1: SYS, PLC1. PLC3: 'Stop', 'Update from source', 'Compile': TwinCAT PLC Control has stopped working H1ECATC1: SYS, PLC1. PLC2. PLC3: 'Stop', 'Update from source', 'Compile': TwinCAT PLC Control has stopped working, 'Activate and run': TwinCAT PLC Control has stopped working At this point I don't know what is going on. Going into deeper investigation...
I got the corner station back, now end X is down...'mystery errors' in IOC.
All appear to be back. Burtrestores done to 6:10 am for all PLCs for the corner station, end X and end Y.
I'm currently injecting a 50mHz, 2 micro-radian ampltiude sinusoid into ITMY YAW (via the top stage). HWSY is now within a few mm of the conjugate plane of ITMY. The HWS code is running and will measure the apparent tilt at the HWS from the injection oscillation. I will use this to calibrate the magnificiation of the HWSY optical system.
Injection stopped.
I upgraded the guardian core and cdsutils (python ezca) installs:
I restarted most of the nodes, except for the following:
jameson.rollins@opsws2:~/src/cdsutils/trunk 0$ guardctrl list | grep -v 1095
node s k m vers state message
---- - - - ---- ----- -------
ALS_COMM o - - - - -
H1ECATC1PLC2 * E 1076 INIT
H1ECATX1PLC2 * E 1076 INIT
H1ECATY1PLC2 * E 1076 INIT
H1ISCEX * E 1076 INIT
H1ISCEY * E 1076 INIT
H1LSC * E 1076 INIT
H1LSCAUX * E 1076 INIT
HPI_HAM2 * * M 1083 ROBUST_ISOLATED
IAS_INPUT o - - - - -
IAS_MICH o - - - - -
IAS_PRC o - - - - -
IAS_SRC o - - - - -
IAS_TEST o - - - - -
IAS_XARM o - - - - -
IAS_YARM o - - - - -
IFO_ALIGN o - - - - -
ISC_LOCK o - - - - -
ISI_HAM2 * P 1083 WATCHDOG_TRIPPED_FULL_SHUTDOWN WATCHDOG TRIP: FULL_SHUTDOWN (4)
LSC * E 1076 INIT
LSC_PRMI_VAR_FINESSE * E 1083 DOWN MISALIGN PRM
LSC_PRX * P 1083 FAULT check LSC input matrix, ITMY not MISALIGNED
LSC_PRY * P 1080 FAULT PRM not ALIGNED, ITMX not MISALIGNED
SEI_HAM2 * P 1083 ISOLATED
SUS_MC1 * * E 1080 ALIGNED
SUS_MC3 * * E 1080 ALIGNED
SUS_PR3 * * E 1080 ALIGNED
SUS_PRM * * M 1083 ALIGNED
The non-running nodes (s='o') had various errors on restart, so I shut them down until they can be fixed. I shut down all the IAS nodes since I was told they're not in use. The HAM2 nodes were not restarted because Hugh was in the middle of doing some SEI work on HAM2. The nodes starting with "H1" are the "CSDEF" nodes (not sure what the status of those is). I'll restart these nodes when I'm sure it's ok.
I noticed that there are a couple of "hidden" nodes, that are not listed in the Guardian overview screen:
H1ECATC1PLC2 * E 1076 INIT
H1ECATX1PLC2 * E 1076 INIT
H1ECATY1PLC2 * E 1076 INIT
H1ISCEX * E 1076 INIT
H1ISCEY * E 1076 INIT
H1LSC * E 1076 INIT
H1LSCAUX * E 1076 INIT
LSC * E 1076 INIT
LSC_PRMI_VAR_FINESSE * E 1083 DOWN MISALIGN PRM
LSC_PRX * P 1083 FAULT check LSC input matrix, ITMY not MISALIGNED
LSC_PRY * P 1080 FAULT PRM not ALIGNED, ITMX not MISALIGNED
We should be very careful about these. If they're being used, they should be on the overview. If they're not being used, they should be shut down. Do not leave running nodes off of the overview screen
I should note that a bug was fixed in the cdsutils avg function. The standard deviation calculations were bogus, off by some unknown but large factor. This new version fixes that issue so that the standard deviation calculations returned with the "stdev" option are now correct.
We have reverted the cdsutils to cdsutils-329 (the version installed here since september), we did this by changing the link in /ligo/apps/linux-x86_64
The guardians were failing when they called the new avg function, we tried using the new cds utils function from the command line but it doesn't seem to be working.
We had about a half hour of DRMI locked at 10 W with the ETMs misaligned, starting at 7:00 UTC october 29. Durring this time there were only a handfull of mode hops (the ASC loops were on).
I had a look at some coherences with the ISI GS13s, the plot is attached. There is a good amount of coherence between AS90 and the BS GS13 (both X and Y, which is hard to see on the plot) from 4Hz, to 90 Hz. This seems most likely to be some coupling (clippping, scattering) from the suspension cage, because the optic should have a good deal of isolation due to the suspension at those frequencies.
HAM5 Y also shows coherence at high frequencies.