Displaying reports 921-940 of 82959.Go to page Start 43 44 45 46 47 48 49 50 51 End
Reports until 15:14, Monday 19 May 2025
H1 TCS
thomas.shaffer@LIGO.ORG - posted 15:14, Monday 19 May 2025 (84364)
TCS Chiller Sock Filters Replaced

FAMIS 31406

The sock filters had slight discolorization, but there were floating string-like particulate in both reservoirs (pic1 & pic2). This isn't a new finding, but I was hoping after the last flush in October that it would have reduced the amount of floaters over time as they were filtered out, but this doesn't seem to be the case.

Images attached to this report
H1 ISC
elenna.capote@LIGO.ORG - posted 14:39, Monday 19 May 2025 - last comment - 14:49, Monday 19 May 2025(84450)
HAM1 POP and REFL power budgets

Sheila and I used the thorlabs power meters to do a quick power budget along the POP and REFL paths. Just as a note, this alog from Craig and others in 2022 still holds and is probably the best authority for the REFL path.

Attached is a handy cartoon with the naming convention for HAM1, see D1000313.

POP path measurements:

POP path measurements were taken in "single bounce" 10 W input. So PRM misaligned, ITMX aligned. 9.4 W was incident on IM4 trans.

Expected power to HAM1 = 9.4 W * 0.977 (IFI transmission) * 0.031 (PRM transmission) * 0.5 * 0.5 (two passes of the BS) * 229e-6 (PR2 transmission) = 16.3 uW (this assumes the reflection off the ITM is 1)

The POP beam then sees a 90/10 split at M12 (air/vac) and a 50/50 split at M15 (LSC/ASC).

Location Measured Expected (how calculated) Ratio Measured/Expected
After periscope 15 uW 16.3 uW (9.4 * 0.977 * 0.031 * 0.5 * 0.5 * 229e-6) 0.92
reflection of M12 (90/10 splitter for air/vac) 14 uW 14.7 uW (9.4 * 0.977 *0.031 * 0.5 * 0.5 * 229e-6 * 0.9) 0.95
transmission of M15 (just before POP ASC diode) 0.65 uW 0.81 uW (9.4 * 0.977 * 0.031 * 0.5 * 0.5 * 229e-6 * 0.1 * 0.5) 0.8

The beam is hard to see until after the lens so these were the only measurements possible.

REFL path measurements:

These measurements were taken in two sets, with the first set at 10 W input with PRM misaligned and the second set at 2 W input with PRM aligned and ITMX misaligned.

Set 1 is single bounce with PRM misaligned and 9.4 W on IM4 trans.

Expected power to HAM1 = 9.4 W * 0.977 * 0.031 * 0.5 *0.5 * 0.031 * 0.977 (double pass of beam splitter, PRM and IFI) = 2.15 mW (this assumes that the backward throughput of the IFI is the same as the forward throughput)

Location Measured Expected (how calculated) Ratio Measured/Expected
Before M14 (beam just coming to HAM1) 2.05 mW 2.15 mW (9.4 * 0.977 *0.031 *0.5 * 0.5 * 0.031 * 0.977) 0.95
reflection of M14 (90/10 splitter) 1.9 mW 1.94 mW (9.4 * 0.977 * 0.031 *0.5 * 0.5 * 0.031 * 0.977 * 0.9) 0.98
transmission of M17 (first 50/50) 0.1 mW 0.11 mW (9.4 * 0.977 * 0.031 *0.5 * 0.5 * 0.031 * 0.977 * 0.1 * 0.5) 0.91
transmission of M1 (second 50/50) 40 uW

53.9 uW (9.4 * 0.977 * 0.031 *0.5 * 0.5 * 0.031 * 0.977 * 0.1 * 0.5 * 0.5)

0.74

Set 2 is single bounce with PRM aligned and 2 W input, so 1.9 W on IM4 trans.

Expected power to HAM1 = 1.9 W * 0.977 (IFI throughput) * 0.97 (PRM reflection) * 0.977 (IFI throughput)= 1.76 mW

Location Measured Expected (how calculated) Ratio Measured/Expected
before M2 (third 50/50 splitter) 64 mW** 44 mW (1.9 W * 0.977 * 0.97 * 0.977 * 0.1 * 0.5 * 0.5) 1.45
before M6 (LSC/ASC splitter) 14 mW 22 mW (1.9 W * 0.977 * 0.97 * 0.977 * 0.1 * 0.5 * 0.5 * 0.5) 0.64
transmission M6 (50/50 LSC/ASC splitter) 7 mW 11 mW (1.9 W * 0.977 * 0.97 * 0.977 * 0.1 * 0.5 * 0.5 * 0.5 * 0.5) 0.64
reflection of M18 (50/50 LSC A/B splitter) 3.5 mW 5.5 mW (1.9 W * 0.977 * 0.97 * 0.977 * 0.1 * 0.5 * 0.5 * 0.5 * 0.5 * 0.5) 0.64
transmission of M18 (50/50 LSC A/B splitter) 3.5 mW 5.5 mW (1.9 W * 0.977 * 0.97 * 0.977 * 0.1 * 0.5 * 0.5 * 0.5 * 0.5 * 0.5) 0.64

** we made this first measurement as a quick check to see what power was going to the other side of the table, but clearly something is wrong with it! Maybe I transposed a number?

While there is clearly a discrepancy between what light we measure vs expect at M6, all the splitting ratios after seems to make sense. Craig calculated what the true splitting ratios for M14, M17 and M1 in alog 63510. None of these optics have changed. The splitting ratios are as follows:

M14 trans = 0.0756

M17 trans = 0.5072

M1 trans = 0.5295

If I update the calculations of the REFL path using those numbers, I get the following, with bolded values noting which ones have changed:

Location Measured Expected (how calculated) Ratio Measured/Expected
Before M14 (beam just coming to HAM1) 2.05 mW 2.15 mW (9.4 * 0.977 * 0.031 *0.5 * 0.5 * 0.031 * 0.977) 0.95
reflection of M14 (90/10 splitter) 1.9 mW 1.99 mW (9.4 * 0.977* 0.031 *0.5 * 0.5 * 0.031 * 0.977 * (1-0.0756)) 0.95
transmission of M17 (first 50/50) 0.1 mW 0.083 mW (9.4 * 0.977 * 0.031 *0.5 * 0.5 * 0.031 * 0.977 * 0.0756 * 0.5072) 1.2
transmission of M1 (second 50/50) 40 uW

43.8 uW (9.4 * 0.977 * 0.031 *0.5 * 0.5 * 0.031 * 0.977 * 0.0756 * 0.5072 * 0.5295)

0.91

 

Location Measured Expected (how calculated) Ratio Measured/Expected
before M2 (third 50/50 splitter) 64 mW** 35.7 mW (1.9 * 0.977 * 0.97 *0.977 * (0.0756) * 0.5072 * 0.5295) 1.8
before M6 (LSC/ASC splitter) 14 mW 17.8 mW (1.9 * 0.977 * 0.97 *0.977 * (0.0756) * 0.5072 * 0.5295 * 0.5) 0.79
transmission M6 (50/50 LSC/ASC splitter) 7 mW 8.9 mW (1.9 * 0.977 * 0.97 *0.977 * (0.0756) * 0.5072 * 0.5295 * 0.5 * 0.5) 0.79
reflection of M18 (50/50 LSC A/B splitter) 3.5 mW 4.46 mW (1.9 * 0.977 * 0.97 *0.977 * (0.0756) * 0.5072 * 0.5295 * 0.5 * 0.5 * 0.5) 0.78
transmission of M18 (50/50 LSC A/B splitter) 3.5 mW 4.46 mW (1.9 * 0.977 * 0.97 *0.977 * (0.0756) * 0.5072 * 0.5295 * 0.5 * 0.5 * 0.5) 0.78

 

Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 14:49, Monday 19 May 2025 (84470)

Following up to add that Sheila and I recently checked the POP calibration in 82656, and it appeared we were missing about 15% of the power we expected on POP. Based on the measurements above, I can convince myself that it is possible we could have had that discrepancy, due to extra loss in the path into/on HAM1. However, these measurements do not exactly recreate that scenario because before we had a 95/5 at M12 and an HR at M15.

H1 SUS
oli.patane@LIGO.ORG - posted 14:36, Monday 19 May 2025 (84468)
Checking ASDs of OSEMINF_OUTs on RMs

Jeff, Oli

Following up on one of Jeff's followup tasks about the signs of RM1 and RM2 (84462):

"(II) Measure the amplitude spectral density of each individual OSEMs well above the data rate we typically store them; look to see if there's no giant noise features. If there is -- debug that (usually a reboot of the satamp is the first step.)"

I ran ASD measurements for RM1 and RM2 at OSEMINF_OUT for each OSEM (with the comb60 filter turned off), and we verified they all look good(attachment1). To further check and compare them, we reran the same template (and filter) setup but for OM1 and OM2(attachment2). Since doors are currently being put on and the HAM1 ISI isn't isolated yet, we can see that the RM OSEM spectrum are very noisy below 30 Hz due to seismic noise, and other noises caused by the immediate environment are causing peaks at several different frequencies for thre RMs as compared to the OMs, but overall all four suspensions' OSEMs asymptote the same way and there aren't any noise features that seem to be of concern.

Images attached to this report
H1 DAQ
jonathan.hanks@LIGO.ORG - posted 13:55, Monday 19 May 2025 - last comment - 16:28, Monday 19 May 2025(84466)
WP 12455 Replace failed power supply on h1daqframes-1

As per WP 12455 Dave and Jonathan replaced the power supply on h1daqframes-1.  Due to the available space in the rack we decided to power off the system so that we could move it safely and replace the power supply.

We did some double checking to verify which machines where hooked together.  We followed the physical connections and cross checked them with the names and numbers for interfaces on each machine.  This was good as the labels on the front of the system where wrong.  This is the frame disk associated with h1daqfw1.

We powered down h1daqfw1, verified that the link to h1daqframes-1 had gone dark.  After that we powered off h1daqframes-1 pushed it forwared enought to replace the power supply, pushed it back in th place and restarted it.

After the disk server was back we restarted h1daqfw1 as well.

Dave will fix the labeling.

Comments related to this report
david.barker@LIGO.ORG - 16:26, Monday 19 May 2025 (84472)

Labels are now good. MSR-RACK09 U02-U03 (bottom unit) is h1daqframes-1. MSR-RACK09 U04-U05 (next to bottom unit) is h1daqframes-0.

david.barker@LIGO.ORG - 16:28, Monday 19 May 2025 (84473)

Closed FRS27399

H1 SUS (ISC)
jeffrey.kissel@LIGO.ORG - posted 13:35, Monday 19 May 2025 - last comment - 14:37, Monday 19 May 2025(84462)
Physical Check of Actuation Sign for RM1 and RM2 as they Currently Stand; OK for doors, but we've got work to do.
R. Kumar, C. Compton, J. Kissel
(Using Cartoon from other files of D1000313-v19)
(Following sign conventions from T1200015)

Given the sign confusion of the RMs (LHO:84289), I wanted a physical, with-our-eyeballs, confirmation of how the RMs deflect the beam under different alignment offsets given the current state of the system while we still had doors off HAM1. Using the REFL beam as our optical lever, we drove +/-20000 [ct] alignment offsets into each suspensions H1:SUS-RM[1,2]_M1_OPTICALIGN_[P,Y]_OFFSET, and watched the displaced beam downstream of the optic. Rahul was in chamber with the card and his eyeballs, Camilla was chamberside in view of the card as a second set of eyeballs to confirm, and I was driving with a CDS laptop and taking notes. Detailed blow-by-blow and raw convention-free data can be found in the attached text file.

Conclusions (all statements made with "Today," preceding the statement):
(0) We checked that 
  On the actuation side,
    (a) H1:SUS-RM[1,2]_M1_OPTICALIGN_[P,Y]_GAINs are all positive, at +1.0;
    (b) The sign of the pitch and yaw elements of the EUL2OSEM matrices for both RM1 and RM2 match convention;
    (c) There's no sneaky sign flop in the *filters* of the COILOUTF banks, i.e, in none of the "LPM1" or "AntiLPM1" filter modules (see (1) below for statement on sign of gains)
  On the sensor side
    (d) The raw ADC counts for both RM1 and RM2 are positive, as expected after the cable swap, and per a normal OSEM sensor;
    (e) The sign of the OSEMINF bank gains are all positive values close to +1.0, as expected for a standard OSEM sensor chain;
    (f) There's no sneaky sign flip in the *filters* of the OSEMINF banks, i.e. in none of the "10:0.4", "to_um," or "comb60" filter modules
    (g) The sign of pitch and yaw elements of the OSEM2EUL matrices are the correct transpose (in the mathematical sense) of the EUL2OSEM matrices, so they match convention

(1) the COILOUTF gains are set as they were reverted to their "been like this forever value" on May 6th LHO:84289, with 
    (a) RM1 obeying convention (UL, LL, UR, LR = +, -, -, +) and 
    (b) RM2 disobeying convention (UL, LL, UR, LR = +, -, -, +).

(2) RM1 displaces the beam per convention, with a
    (a) positive pitch offset displacing the downstream beam down and 
    (b) positive yaw offset displacing the beam in +Y (IFO Cartesian coordinates) i.e. rotating RM1 in +RZ, or +yaw,
    at RM2,

(3) RM2 displaces the beam against convention, 
    (a) positive pitch offset displacing the downstream beam up and 
    (b) positive yaw offset displacing the beam also +Y (IFO Cartesian coordinates) i.e. rotating RM2 in -RZ, or -yaw,
    at M5, 

(4) Under these displacements, 
    (a) the RM1 OSEM sensor sign agrees with the physical displacement: 
        (i) positive requested pitch shows up as more positive pitch OSEM sensor value, 
        (ii) positive requested yaw shows up as more positive yaw OSEM sensor value, 
    (b) the RM2 OSEM sensor signs disagrees with the physical displacement: 
        (i) positive requested pitch displaces the beam up (negative pitch), so the optic has physically tilted up in negative pitch, but the OSEM reads this as positive pitch
        (ii) positive request yaw displaces the beam in -RZ (negative yaw), so the optic has physically rotated in negative yaw, but the OSEM reads this as positive yaw.

In each of the attach trends of the test -- RM1 PIT, RM1 YAW, RM2 PIT, and RM2 YAW -- that show
    - The digitally requested alignment offset
    - The OSEMINF raw ADC channels (just to show that these are all positive now, after the cable work discussed in LHO:84027; you can't actually see the displacement)
    - The projected Euler basis OSEM sensors
    - The REFL WFS DC QPD signals (these didn't turn out to be that useful because we didn't take care to let the beam settle at each alignment, and predicting what the sign of the measured beam spot downstream of the WFS lens is not straight-forward)

All of the above conclude that
There are no sign issues in the sensor or actuator chains for RM1
Given the combination of (1)(b) and (3)(a) + (3)(b), we conclude that
There is *no* magnet polarity problems, and we *could* make RM2 actuators obey actuation convention without any hardware change.

Instead, from (4)(b)
There remains a sign issue with the OSEM *sensor* chain for RM2.

And yet, even in the face of the *difference* in RM sensor sign, (3)(a) vs. (3)(b), 
With what *very* low level "does it work or not" MEDM screen viewing that we've done, *both* RMs "need" the same *positive*, +1, damping loop gain which disobeys convention.
So -- 
   - Why do the RM2 sensors readout opposite from physical displacement? 
and
   - Why don't RM1's damping loops work with a -1.0 damping gain?

From here we need to:
(I) Compare the *phase* of now vs. old "damping loop OFF" "health check" transfer functions. If these show a sign change after the cable swap changed the OSEM sensor sign, good.
(II) Measure the amplitude spectral density of each individual OSEMs well above the data rate we typically store them; look to see if there's no giant noise features. If there is -- debug that (usually a reboot of the satamp is the first step.)
(III) If/once there's no gross electronics noise, after the dust settles in the chamber, with doors on, turn on the damping loops with +1 gain. 
(IV) Measure the open loop gain transfer functions (drive M1_DAMP_EXC, measure TF of IN1/IN2), and confirm stability and appropriate amount of gain; they should look like they did when I improved the damping loop filters back in 2022. LHO:63656. Debug further if they don't.
Images attached to this report
Non-image files attached to this report
Comments related to this report
oli.patane@LIGO.ORG - 14:37, Monday 19 May 2025 (84469)

Looked into (II) here: 84468

H1 SUS (SUS)
ryan.crouch@LIGO.ORG - posted 12:52, Monday 19 May 2025 (84459)
OPLEV charge measurements, ETMX, ETMY

* Not a great measurement, low coherence and large error bars*

I took the OPLEV charge measurements for ETMX and ETMY this afternoon. There were more overflows than typical on both ETMs during the measurements, ground motion was also elevated due to highish (~20mph) winds.

ETMX's charge is close to +/- 50 [V] on all DOF, ETMY's charge is under +/-50[V] on most DOFs except for UL_Y, and maybe LL_P.

Images attached to this report
H1 SYS
betsy.weaver@LIGO.ORG - posted 12:24, Monday 19 May 2025 - last comment - 15:13, Monday 02 June 2025(84464)
HAM1 closeout final chamber checks
For chamber closeout finalization, this morning I 

* placed a 3" contam control wafer on the center of the HAM1 table today
* took a few last pics, removed the stowed 3x septum covers (missed removing the 4th one from the septum, thanks vac good eye, pic 4)
* looked around for left behind tools
* retraced the beam path to look for errand in-the-way cables (none observed)
* inspected under and around lower area of table for left goods (none found)
* cleaned up last tool pans to get ready for doors
* particle counts were <50 all sizes, zero most often
* purposefully coiled the to-be-used in post O4 next vent cable with the peek connector not grounding to anything - it sits in the PSL side door well below the table

* all subsytems have signed for doors, so we are putting doors on.
Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 15:13, Monday 02 June 2025 (84723)EPO

Tagging for epo

H1 ISC
camilla.compton@LIGO.ORG - posted 12:24, Monday 19 May 2025 (84463)
Final Check of Beams through HAM1 Viewports

Betsy, Sheila, Camilla. WP 12551

After the VAC team installed the +Y door, we got the PSL ALS and REFL beams (opened beam divertor) out of the VPs. All look good. 
Attached photo of PSL ALS beam, with expected green arm beams added on from 84338 photo.
Attached photo of REFL beam, with expected POP beam added on from 84361 photo.
Images attached to this report
H1 SUS
oli.patane@LIGO.ORG - posted 11:11, Monday 19 May 2025 (84455)
PM1 COILOUTF filters fixed

When we first put together everything for PM1, we just copied all the filters over from RM1(84457). It turns out that the coil drivers for RM1 and RM2 both have had ECRs completed (ECR:E2200307, IIET:24501) that changed the frequency response for the coil drivers, a change which the PM1 coil drivers do not have.

After some troubleshooting (84454), we figured this all out, and so I just went in and updated the COILOUTF filters for PM1 to be what they are supposed to be, which is identical to the filters used in the other HAMA driver top masses that haven't had the ECRs done to them, like the ZMs. Filters have been loaded in.

Filter Before (matching RMs) After (matching ZMs)
LPM1 (not used) zpk([52.32;50.77],[0.5;3174],1,"n") zpk([9.99999;20.9999],[0.9;211.883],1,"n")
AntiLPM1 zpk([0.5;3174],[52.32;50.77],1,"n") zpk([0.9;211.883],[9.99999;20.9999],1,"n")

 

Images attached to this report
H1 SUS
jeffrey.kissel@LIGO.ORG - posted 11:08, Monday 19 May 2025 - last comment - 14:25, Monday 19 May 2025(84454)
PM1 HAM-A Coil Driver Does NOT Have ECR E2100430 Mods to its Low Pass Filter
J. Kissel, R. Kumar, O. Patane, F. Clara

We're debugging why high-frequency asymptote/slope/frequency response of PM1's transfer functions do not match RM1's -- see RED (PM1) and BLACK (RM1) from the attachments of LHO:84397.
I immediately suspected coil driver compensation filters in COILOUTF banks did not match the analog HAM-A driver's low pass filter *state.* 
In the modern era all HAM-A driver's low pass filters are to be jumpered ON since we don't have binary input/ouput remote control of them. And when instantiating a new HTTS suspension, because there's no MEDM interface to set it, and you have to "caput" the channel (H1:SUS-RM1_BIO_M1_STATEREQ) to 2.0 via the command line. 
When we forget to do this, we errantly see the analog response of the driver in the health check transfer functions rather than the expected "falls as 1/f^2 above the resonances."

We confirmed (via trend) that I *did* set this correctly when I original brought the infrastructure online see LHO:84457 comment to LHO:83293 on Mar 20 2025. 
We also confirmed that it's still the case today -- see attached screenshot, with magneta box around the CD state.

We also confirmed that the LED status lights of the LP filter are green / ON, which report that, internally, indeed the HAM-A driver's LP filter switch is in the "Run" state, which is LP ON, see attached photo of SUS-C4, U-heights 3 (for PM1),4 (for RM2), 5 (for RM1) (per page 14 of D0902810-v11).

HOWEVER 
(1) In taking that picture, I noticed that all the HAM-A drivers in that rack had a sticker mentioning ECR E2100430 *except* for PM1's driver in U3. 
In that ECR -- which is for modifying the OMs -- is better described in T2100410, the low pass filter response was changed from a z:p = [10,20]:[1,200] to z:p = [0.5,3174]:[52.32, 50.77].
There are later ECRs E2200307 and E2400048 that demand the *rest* of the HAM-A drivers should be modified with these same changes.
Tickets IIET:20650 (for OMs) IIET:24501 (for IMs, RMs, and OFI), confirm that these modifications have been done at LHO for those suspensions.

(2) IIET:30349 (for the A+ SUS), suggests that no such modifications have been done at LHO (and partially implemented at LLO).
Rahul confirms with a pictures from SUS-M1 that the ZM1 ZM2 ZM3 and the OPO, and SUS-C8 for ZM4 ZM5 ZM6 that there are no stickers referencing any ECR E2100430, E2200307, and what it *should* reference, E2400048.
From this we conclude that E2400048 has NOT been implemented here at LHO.
 
(3) Finally - even though ECRs demand that essentially ALL HAM-A drivers should now have this LP filter change -- there exists NO version of D1100117 that has the the change in components or callout of new frequency response. This is likely why this change got overlooked when setting up PM1's HAMA driver.

So, from the lack of sticker, lack of updated circuit drawing, and odd health check transfer function response --  we conclude frequency response PM1's HAM-A driver has frequency response is still the z:p = [10,20]:[1,200] response.

When I set up PM1, I copied RM1's COILOUTF frequency response. 
RM1's COILOUTF is *correctly* was compensating the z:p = [0.5,3174]:[52.32, 50.77] analog response. 
However, that will NOT correctly compensate the unmondified PM1 driver's z:p = [10,20]:[1,200] response.

*sigh* For now, we'll update the COILOUTF filters, and then discuss later when / if we want to modify the driver.

Images attached to this report
Comments related to this report
rahul.kumar@LIGO.ORG - 11:33, Monday 19 May 2025 (84460)SUS

I am attaching two pictures as a reference to Jeff's comments above ("there are no stickers referencing any ECR E2100430, E2200307, and what it *should* reference, E2400048"), please see them below,

1. Picture01- SUS-M1 for ZM1 ZM2 ZM3 taken at the MER

2. Picture02 - SUS-M1 for ZM4-5-6 taken at the CER (see slot U11 and U12).

Images attached to this comment
daniel.sigg@LIGO.ORG - 13:32, Monday 19 May 2025 (84465)

Yikes! E2200307 also mentions to eliminate the binary switching for the IMs and use jumpers like all the others. Since the binary IO chassis for the IMs are still in the rack, I suspect this hasn't been completed. We should go ahead and install the jumpers for the IMs and remove the binary IO chassis.

jeffrey.kissel@LIGO.ORG - 14:25, Monday 19 May 2025 (84467)
The COILOUTF filters have been updated to compensate the current, z:p = [10,20]:[1,200], frequency response -- see LHO:84455.
H1 SUS (SUS)
edgard.bonilla@LIGO.ORG - posted 10:46, Monday 19 May 2025 (84458)
Exported 'production' SUS models into the SVN for use in python

Original (and more detailed) post: SWG:12283

I have added two scripts and a folder to the Common/MatlabTools of the Sus SVN. The folder is called ExportedModels and it contains exported [A,B,C,D] matrices for making state-space models for 13 suspension types (HLTS_model, QUAD_model, HAUX_model, etc.). It also contains a SUS_projections struct that contains a summary of the OSEM to euler bais changes for most suspensions, also organized by suspension type.

Instructions to navigate the structs can be found in export_SUS_production_models.m, and export_SUS_projection_matrices.m; both inside Common/MatlabTools/

The idea is that these two can be imported into other programming languages (I'm thinking python right now) for analysis, scripting or any other things that people might want.

___

The use I have in mind right now is for OSEM calibration using ISI drives, following the work we're doing with Oli [see LHO:84296]. But could be handy for something else.

LHO VE
david.barker@LIGO.ORG - posted 10:18, Monday 19 May 2025 (84456)
Mon CP1 Fill

Mon May 19 10:06:14 2025 INFO: Fill completed in 6min 11secs

 

Images attached to this report
H1 PSL
ryan.short@LIGO.ORG - posted 09:28, Monday 19 May 2025 (84451)
PSL 10-Day Trends

FAMIS 31086

The PMC was left unlocked over the weekend, and when Oli relocked it this morning, it came back with higher transmitted power but about the same reflected, and the ISS diffracted power is lower too. As things are still settling, PMC TRANS is coming down and the ISS diffraction is coming up. However, this has also made the (already poorly calibrated) rotation stage downstream unhappy as the higher power out of the PMC is causing the stage to not exactly provide the power requested (e.g 2.2W vs 2.0W) and the LASER_PWR Guardian is reporting "Power not the same as requested." As the HAM1 team is currently using the beam for alignment checks and doesn't particularly care about the extra 200mW, I'll leave things alone for now.

Images attached to this report
H1 PSL
sheila.dwyer@LIGO.ORG - posted 20:02, Friday 16 May 2025 - last comment - 11:33, Monday 19 May 2025(84446)
PMC left unlocked

I left 10W out of the rotation stage, with the stage de-engergized this evening and the light pipe closed.  I've just now unlocked the PMC (LOCK off, RAMP off) so that we won't have 10W on the light pipe shutter all weekend. 

 

Comments related to this report
jason.oberling@LIGO.ORG - 11:33, Monday 19 May 2025 (84461)ISC, OpsInfo

This is a reminder that whenever the PMC is unlocked, especially for an extended period of time, the FSS and ISS should also be disengaged; otherwise, the respective autolockers will continue to try to engage these systems despite not having the means to do so (because they have no light, since the PMC is unlocked).  If there are ever any questions as to how to properly and safely disengage the PSL stabilization systems, CONTACT ME.  It does not matter if I'm offsite for any reason (RDO, vacation, sick, etc.).

From the 10-day trends Ryan posted this morning, neither the ISS nor the FSS were properly disengaged, so were left trying to lock all weekend.  For the FSS see the plot H1:PSL-FSS_NPRO_XTALTEMP in this set of plots.  It's clear from this plot that the FSS autolocker was doing a temperature search while trying to lock the RefCav, which means the NPRO PZT was also ramping.  Since there was no light in the FSS path the RefCav could not lock, so the search continued all weekend.

For the ISS, see the plot H1:PSL-ISS_DIFFRACTION_AVG in this set of plots.  The ISS diffraction should be completely flat if it is off, but the series of downward spikes indicate the ISS was trying to lock and failing to do so, since there was no light on the ISS PDs (my guess is it kept lowering the diffraction percentage to try to increase light on the ISS PDs, and unlocking when the diffraction hit 0% to start the process again).  This can also be seen in the behavior of the PMC reflected power (1st attached picture), which was moving around substantially all weekend as the ISS was trying and failing to lock; can also see the ISS diffracted power moving between 0% and 40%.  A zoomed in portion is also attached, in which it's seen that the ISS diffraction was moving from zero to ~20% (but as high as 50%) in a roughly 15 second period; note the changes in PMC Refl during this time (the small spikes in PMC Trans are not the PMC trying to lock, it's small flashes of resonance as the temperature of the PMC changes combined with the FSS actuating on the laser frequency).

While not strictly necessary, it's good practice to also close the PSL external shutter if the stabilization systems are going to be disabled for an extended period.

I don't think that this will compromise the performance of the ISS or FSS, but this does represent unnecessary wear on the mechanical components that are the actuators for both of these stabilization subsystems.  I should have caught that the PSL was left in this state, but did not pay attention to the alog during my RDO weekend and therefore did not catch this.  For this I apologize.

Images attached to this comment
H1 SUS
jeffrey.kissel@LIGO.ORG - posted 10:10, Tuesday 11 March 2025 - last comment - 10:25, Monday 19 May 2025(83293)
H1SUSPM1 HTTS MEDM and Filter File Infrastructure Populated
J. Kissel

Today Dave installed all the simulink front-end code infrastructure that Oli and I built for PM1 (see LHO:83214), Oli created a generic MEDM macro for PM1 and attached a call to that file with the generic HTTS MEDM screen to the sitemap yesteday. 

That meant I had everything in place for me to completely fill out the PM1 infrastructure:
- Populated OSEM2EUL, SENSALIGN, and EUL2OSEM matrices with generic HTTS values
- Populated OSEMINF filter banks with standard OSEM calibration filters and turned them ON with a gain of 1.0 for now
- Populated the DAMP filter with standard (recently improved) HTTS damping filters
- Populated the COILOUTF filter bank with HAM-A coil driver frequency response compensation, and turned the filters on with magnet polarity compensating gains of UL LL UR LR = +1, -1, -1, +1'
- Populated and turned on the RMS filtering to support the watchdog trigger signals, and set the threshold to 150 [urad_RMS] as is the case for other HTTS
- Turned on the on-diagonal elements of the DRIVEALIGN matrix
- Set the calibration gain of the OPTICALIGN alignment offsets to 1.0, which is not the right number, but standard for HTTS. Turn the offset ON.

Then monitored and accepted all the settings in the h1sushtts_safe.snap, expect the OPTICALIGN offsets.
The committed the safe.snap and filter file to the userapps repo.

All we need now is PM1 itself!
Comments related to this report
jeffrey.kissel@LIGO.ORG - 10:25, Monday 19 May 2025 (84457)
Expanding on the digital setup of the coil driver signal chain:
- Populated the COILOUTF filter bank with HAM-A coil driver frequency response compensation, and turned the filters on with magnet polarity compensating gains of UL LL UR LR = +1, -1, -1, +1'
 - I copied the COILOUTF frequency response from RM1, which has 
       FM1    LPM1        zpk([52.32;50.77],[0.5;3174],1,"n")
       FM6    AntiLPM1    zpk([0.5;3174],[52.32;50.77],1,"n")
 - I set the H1:SUS-PM1_BIO_M1_STATEREQ to 2.0 to ensure the response of the HAM-A driver's low-pass (which is always jumpered to ON) is correctly compensated with only FM6 ON via "caget" on the command line.

     
Displaying reports 921-940 of 82959.Go to page Start 43 44 45 46 47 48 49 50 51 End