Displaying reports 14781-14800 of 88171.Go to page Start 736 737 738 739 740 741 742 743 744 End
Reports until 22:53, Friday 26 January 2024
H1 ISC (ISC, SUS)
keita.kawabe@LIGO.ORG - posted 22:53, Friday 26 January 2024 - last comment - 16:02, Wednesday 31 January 2024(75575)
HAM6 work Jan/26/2024: Alignment of the laser into the new OMC, day 3 (Rahul, Koji, Betsy, Keita)

OMCS was touching.
Rahul made OMCS transfer functions and found that something was touching. He, Koji and Betsy went to the floor to center the OSEMs. T1 was touching, which was fixed. Depth of OSEMs were adjusted, too.

Something is funny about OM3 damping.

Rahul also made TFs for OMs and thought that they were fine. However, OM3 PIT damping was oscillating at 1.75Hz. I flipped the sign of H1:SUS-OM3_M1_DAMP_P_GAIN (nominally -1, now +1) and it damped fine. I hate this.

1st attachment red shows the OLTF of OM3 P damping loop at around the offending resonance. This was of course measured with the flipped damping gain, and the OLTF looks absolutely strange. The 1st UGF is ~1.73Hz with -42deg phase, and the 2nd UGF is ~1.77Hz with -180deg phase.

If you draw a Nyquist diagram, you will find that this is a stable TF. OTOH, with the "correct" damping gain, this will become unstable. So we know why this works and why the correct sign doesn't, but we don't know what changed and why. 

Alignment converges.

With the OMC suspended without any biases, we adjusted OM1/2/3 biases to align the beam into the OMC (i.e. centering both of the OMC QPDs).

At some point we found that the ASC-AS_C was totally off-centered, used SRM to recenter, and continued the alignment.

2nd attachment shows the status as of now. Both of the OMC QPDs are reasonably centered, ASC-AS_C too. BOSEM DAC output for OM1 is ~11k max. OM2 and OM3 are at ~7k max  and ~9k max, respectively. These are OK though OM1 is not super.

Current status of the LVEA etc.

It's laser hazard. SQZ manager was set to DOWN. Koji closed small HAM5 GV and HAM7 -X curtain.

Remaining work (Monday).

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 16:02, Wednesday 31 January 2024 (75647)ISC, SUS

OM3 damping mystery solved, everything back to normal.

The sign of the OM3 P damping gain got back to the nominal -1 (negative 1) after yesterday's boot fest (alog 75627) and OM3 was happily damping everything.

Turns out that the problem was a rogue filter in all of OM3 M1 COILOUTF channels, stealing about 7dB and ~61deg at 1Hz, 12dB and ~73deg at 2Hz, which was fixed after booting things.

In the attached ndscope screen, at 2024/Jan/26 17:25:11 UTC, OM3 M1 BIO status request was changed from 2 (nominal, hardware LPF ON) to 1 (cannot be used for OMs as hardware LPF seems to be always ON). I don't know how this happened.

FM1 in OM3 M1 COUIOUTF was turned on, that's a digital LPF used when hardware LPF is off, but the hardware filter is always on, causing mismatch. The same filter was turned on for OM2, but it was set back to normal after ~30 minutes. After rebooting things yesterday, state request for OM3 coils got back to normal.

Today I made OM3 P damping TF and it made sense (attached dtt, red is now, blue is when COILOUTF was in a bad state). Taking into account the sign flip between the red and blue, clearly the blue is delayed about 60deg at 1Hz and maybe 80deg-ish at 2Hz.

The blue showed a huge L coupling, which went away in today's data, I don't know why. (Green trace is the L2L OLTF just to show you where the L peak is.) I haven't bothered to change the state request back to 1, flip the damping gain and repeat the measurement just to see if  the L coupling comes back.

I don't know how this happened.

Images attached to this comment
H1 CAL
anthony.sanchez@LIGO.ORG - posted 18:22, Friday 26 January 2024 - last comment - 09:15, Tuesday 27 February 2024(75595)
PCAL End X Tx Module maintenance.

Rick and I cleaned the optics out here at End X.
Noted a drop in MAX Diffracted Power between M5 and the Wedged Beam Splitter from 1.1W to 1.08 W.
This may be due to the laser being turned off and not thermalized.

We would like to come back to End X and adjust the AOM alignment and we are leaving PCAL in a LASER SAFE status, LASER OFF and Key out.

Comments related to this report
anthony.sanchez@LIGO.ORG - 09:15, Tuesday 27 February 2024 (75988)

The results of our TX module maintenance is recorded on the DCC spreadsheet:  T2400029
https://dcc.ligo.org/LIGO-T2400029

 

LHO VE
janos.csizmazia@LIGO.ORG - posted 17:18, Friday 26 January 2024 (75594)
1-26 vent vacuum diary
Today's activities:
- HAM3 was prepared for door removal: the AIP was valved out, and the Annulus system was vented with N2
- EX was fully prepared for pumpdown, which happens next week
- RGA at EX was finished, it's totally leak tight - although its Ion-pump needs some troubleshooting
- There was a solution found for the filters' installation to the Hepta headers: the ISO-fitting will be done with a unique part (https://ancorp.com/product/4500060/), as the more standard claw clamps cannot be fit there
- The 2nd bellows for the relay tube was located - it needs class-A C+B
- Dew points were measured at the corner and at EX, all is good: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=75590
H1 CDS
david.barker@LIGO.ORG - posted 17:01, Friday 26 January 2024 (75593)
Restart of h1seih16 and h1oaf0 following CER work completion

Marc, Erik, Corey, Betsy, Jim, Dave:

h1seih16 and h1oaf0 were power cycled to recover them from this afternoon's crashes. Sequence is (* applies to h1seih16 only)

  1. stop all models
  2. fence from Dolphin fabric
  3. power down fe computer
  4. * power down AI chassis
  5. power down IO Chassis
  6. power up IO Chassis
  7. power up fe computer
  8. * power up AI chassis

Everything restarted with no issues.

Jim has requested that no watchdogs be untripped on the h1seih16 system. The first DAC (HAM6 ISI+HPI) is still in its DACKILL state because the SWWD is untripped. The second DAC (HAM1 HPI) has zero drive because the h1hpiham1 model is untripped.

Latched IPC and DAQ-CRC errors have been cleared.

H1 PEM (ISC, PEM, TCS)
marc.pirello@LIGO.ORG - posted 16:45, Friday 26 January 2024 - last comment - 11:39, Thursday 01 February 2024(75592)
CER Accelerometer Chassis Installed

Replaced the Endevco Accelerometer Power Conditioners with LIGO Accelerometer Power Conditioners. WP11653

Order in the rack:

U19 - Accelerometer Power Conditioner S2300062

U16-U17 AA Chassis S1300101

U14 - Accelerometer Power Conditioner S2300063

U13 - Accelerometer Power Conditioner S2300065

U12 - Accelerometer Power Conditioner S2300069

U11 - Accelerometer Power Conditioner S2300064

Still have EX, EY, MX, MY, FCES to complete.

M. Pirello, J. Jimerson. R. Schofield

Comments related to this report
marc.pirello@LIGO.ORG - 16:28, Tuesday 30 January 2024 (75636)

Mid Y, we were not able to connect power, we installed the chassis and will revist.

Installed Accelerometer Chassis at EX, cables connected and chassis powered up.  One of the Acelerometer cable connectors is loose and will be repaired later this week but it is functional.

Signal Order Asbuilt:

Slot = Cable Number = Accelerometer Number

1 = 4 = PEM EY BSC10

2 = 7 = PEM EY EBAY

3 = empty = empty

4 = 1 = PEM EY OPLEV

5 = empty = empty

6 = empty = PEM EY BSC6

7 = 6 =Black Cable

8 = 2 = PEM EY BSC10

9 = 3 = PEM EY TRN

10 = 5 = PEM EY BSC ACC X

We have no slot 10 on the new chassis therefore we moved cable 5 to slot 5, and moved the PEM EY BSC ACC X cable to match on the back.

Once we matched the cables we rearranged the signals to match the numbering on the front, i.e. cable 1 goes to slot 1, cable 2 goes to slot 2, etc...

Slot = Cable Number = Accelerometer Number

1 = 1 =  PEM EY OPLEV

2 = 2 = PEM EY BSC10

3 = 3 =  PEM EY TRN

4 = 4 = PEM EY BSC10 (this cable had a loose connector, but registered as an accelerometer)

5 = 5 = PEM EY BSC ACC X (this cable did not register as an accelerometer)

6 = 6 = Black Cable (this cable is unlabeled)

7 = 7 = PEM EY EBAY

8 = empty (This needs AA and signal)

9 = empty (This needs AA and signal)

J. Jimerson, M. Pirello

marc.pirello@LIGO.ORG - 17:01, Wednesday 31 January 2024 (75652)

Further investigation into EY Accelerometers

Slot = Cable Number = Accelerometer Number

1 = 1 =  PEM EY OPLEV

2 = 2 = PEM EY BSC10_Y (Should be BSC10_ACC_X)

3 = 3 =  PEM EY TRN (should be BSC10_ACC_Y)

4 = 4 = PEM EY BSC10_Z 

5 = 5 = PEM EY BSC ACC X (should be TRN_TBL_ACC_Y)

6 = 6 = Black Cable (this cable is unlabeled) * same issue as EX

7 = 7 = PEM EY EBAY

8 = empty (This needs AA and signal)

9 = empty (This needs AA and signal)

Same as EX, CH2 moves to CH3, CH3 moves to CH5, CH5 moves to CH2.

marc.pirello@LIGO.ORG - 11:39, Thursday 01 February 2024 (75674)PEM

Removed S2300069 from CS PEM rack, this is not supposed to be installed here.

LHO General
corey.gray@LIGO.ORG - posted 16:09, Friday 26 January 2024 (75580)
Fri (Afternoon) Ops DAY Shift Summary

TITLE: 01/26 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

Afternoon shift's main item of note  is the CRASH of the OAF front end as well as the SEIH16 model; recovery of this would be made after the shift (after CER accelerometer work).

OMC aligning (from the Control Room) has also been ongoing through the afternoon by Keita/Koji/Rahul.
LOG:

LHO VE (VE)
gerardo.moreno@LIGO.ORG - posted 16:04, Friday 26 January 2024 (75590)
Corner Station and EX Purge Air Dew Point Measurements

Measured the purge air dew point at the corner station during "lunch break", no people in chamber, measured -42.0 degrees C.

Travis measured the purge air dew point at EX, all ports closed, purge valve closed, no usage from vacuum volume.  Measured at purge valve area -41.3 degrees C.

Images attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 14:27, Friday 26 January 2024 - last comment - 14:59, Friday 26 January 2024(75583)
h1oaf0 models stopped

all the models on h1oaf0 have stopped running. At time of writing it looks like a possible timing glitch caused by in-rack work in the CER. We will hold off on restarts until the rack wiring work is completed because there are ongoing alignment measurements.

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 14:47, Friday 26 January 2024 (75585)

Soon after we lost h1seih16 models

Images attached to this comment
david.barker@LIGO.ORG - 14:48, Friday 26 January 2024 (75586)

Initially I thought these were just timing glitches, but logging onto the front ends and scanning the IO Chassis cards using lspci shows that many cards are missing. This suggests +24V DC power issues.

david.barker@LIGO.ORG - 14:52, Friday 26 January 2024 (75587)

For example, h1seih16 is showing the first Adnaco backplane (timing_card, ADC0, DAC0) but is missing the second Adnaco (ADC1, ADC2, ADC3, DAC1). The third is empty, the fourth has the Contec card and is seen.

corey.gray@LIGO.ORG - 14:59, Friday 26 January 2024 (75588)PEM

Plan is to let Marc finish the accelerometer work he was doing in the CER (WP11653:  replacing accelerometer power conditioners) at the time of these model crashes before starting any model-recovery.

LHO VE
david.barker@LIGO.ORG - posted 13:32, Friday 26 January 2024 (75581)
Fri CP1 Fill, part deux

Fri Jan 26 12:33:45 2024 INFO: Fill completed in 3min 42secs

Second time was a charm, Gerardo confirmed a good fill curbside.

Images attached to this report
H1 PEM (ISC, PEM, TCS)
marc.pirello@LIGO.ORG - posted 13:00, Friday 26 January 2024 (75579)
Installed 24 port power strip to PEM/TCS rack for 24V rail.

Replaced the 6 port +24V  DC power strip with a 24 port DC power strip in the TCS / PEM racks per WP11649

H1 CDS
david.barker@LIGO.ORG - posted 12:29, Friday 26 January 2024 (75578)
Power cycle h1oaf0 and TCS Beckhoff CER chassis

Marc, Oli, Dave:

For Marc's change over to a bigger +24V power strip in the OAF/TCS CER rack, I powered down the h1oaf0 frontend to permit its IO Chassis to be power cycled.

Sequence was

All is looking good from a CDS perspective.

Images attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 11:09, Friday 26 January 2024 - last comment - 11:42, Friday 26 January 2024(75572)
FMCS IOC stable after power cycle and code upgrade

FRS30184

Patrick, Jonathan, Erik, Dave:

A summary and follow up on the recent FMCS EPICS IOC freeze ups.

Timeline (all times local)

Sat 13 Jan 15:57 FMCS IOC flatlining started. After restart IOC would run anywhere from 1 to 14 hours before flatlining again

Tue 16 Jan 23:12 FMCS IOC running under systemd control, auto-restart code running which restarts IOC if flatlined for 10 mins

Wed 17 Jan 10:48 fmcs-epics-cds machine power cycled

Thu 18 Jan 11:25 After power cycle, IOC ran 25 hours with no flatline, previous longest run 14 hours [Power cycle of computer fixed it]

Thu 18 Jan 11:25 Patrick installed new version of the FMCS IOC code. This added new diagnostic EPICS channels.

Thu 18 Jan 14:58 systemd control of FMCS IOC under puppet configuration management

Tue 23 Jan 10:33 DAQ+EDC restarted to trend new FMCS diagnostic channels

Summary:

After running for many years error free, and 90 days after the last computer reboot, the FMCS IOC code became unstable. At random times it would stop updating its EPICS values, flatlining them at their last value.

The code at this point was started manually and ran in a screen environment.

To facilitate the auto restart of the code while the problem was being investigated, the IOC code was moved to a procServ environment and put under systemd control. A script running on cdsmanager monitored the FMCS channel H0:FMC-EX_CY_H2O_SUP_DEGF every minute. If its value did not change for 10 minutes, the systemd fmcs_ioc.service was restarted on fmcs-epics-cds.

A soft reboot of fmcs-epics-cds did not fix the problem. We then tried a hard power down, wait 30 seconds, then power back on. This appeared to fix the immediate problem.

We decided to upgrade the software to see if this would prevent future occurances, in 90+ days time.

At time of writing, +8 days after upgrade, there have been zero flatline instances.

Comments related to this report
david.barker@LIGO.ORG - 11:42, Friday 26 January 2024 (75576)

One caveat to the new FMCS code is that we have not directly verified it records when the fire pumps run. However the new code's diagnostics channels do permit a verification that the fire pump bacnet device it functioning correctly.

The fire pump status is a binary device. The new code does not allow binary records to directly read device data, so Patrick created intermediate analog input records to read the bacnet devices. These records are defined in the EPICS db file fmcs_bacnet_bi_to_ai.db

For the firepumps, the AI record device names are:

    field(INP, "@bacnet12075 3 5 85")
    field(INP, "@bacnet12075 3 6 85")
 

In backnet-speak, the device string is @bacnet<dev_id> <data_type> <dev_chan_num> <chan_type>

In this case fire_pump_1 reads channel 5, fire_pump_2 reads channel 6. Device 12075 only reads the two fire pump operational status.

The new code provides diagnostic channels for bacnet devices, in this case the three channels:

H0:FMC-BACNET_12075_TX

H0:FMC-BACNET_12075_RX

H0:FMC-BACNET_12075_ER

Trending these channels since they were added to the DAQ Tue morning shows: zero errors, TX and RX numbers increasing linearly in step, they are almost but not quite identical to each other.

H1 SYS
betsy.weaver@LIGO.ORG - posted 20:11, Thursday 25 January 2024 - last comment - 09:21, Thursday 01 February 2024(75564)
Vent work progress update

So far, the O4 break vent & commissioning work is proceeding as planned, with only minor hiccups.  Yesterday's TCS water leak caused a pause to the HAM6 in-chamber OMC alignment work, but we were able to resume this morning pretty quickly with only a short amount of time down.

The attached snapshot shows the planned schedule outline with green checkmarks next to the items completed so far on the left hand side.  On the right is a running log of the activities which have taken place daily (for ease of viewing all in one place).

Teams currently on:

 

Non-image files attached to this report
Comments related to this report
betsy.weaver@LIGO.ORG - 14:26, Friday 26 January 2024 (75582)
Images attached to this comment
corey.gray@LIGO.ORG - 09:21, Thursday 01 February 2024 (75666)EPO

Tagging EPO for FARO Alignment, baffle, Output Mode Cleaner photos.

LHO VE
janos.csizmazia@LIGO.ORG - posted 18:10, Wednesday 24 January 2024 - last comment - 15:57, Friday 26 January 2024(75552)
1-24 vent vacuum diary
Today's activities:
- 3 viewports have been taken off at EX for baffle works. These have been inspected, and found intact in every aspect - the inspection report is in the comment section
- These viewports have been already taken back, as the works were already finished
- The EX RGA is being rebuilt after many leaks have been found - it is in progress, will be finished tomorrow
- The new Hepta header elbow pieces have been staged at all stations
Comments related to this report
gerardo.moreno@LIGO.ORG - 15:57, Friday 26 January 2024 (75589)

Measured dew point at corner station, result of -42.6 degrees C.

Images attached to this comment
LHO VE
janos.csizmazia@LIGO.ORG - posted 17:29, Tuesday 23 January 2024 - last comment - 16:10, Friday 26 January 2024(75526)
1-23 vent vacuum diary
Today's activities:
- The RGA tree at EX was leak-checked, and multiple flanges were leaky, possibly because of some overheating during a bakeout in the past. The gaskets will be redone, and the all-metal angle valve will be also replaced
- EX was vented
- The VPW vacuum chamber was opened, after the 2 stuck screw was removed
- Both 2 spare roughing stations are entirely finished
- All the Hepta header filter works were finished in the LVEA
Comments related to this report
gerardo.moreno@LIGO.ORG - 16:10, Friday 26 January 2024 (75591)VE

Measured the purge air dew point at the corner station with no usage from other groups, no people in chamber, measured -41.3 degrees C.

Measured the purge air dew point at EX, no open ports, before vent, measurement was done at the purge valve area, measured -45.4 degrees C.

Images attached to this comment
H1 DetChar (PEM, SEI)
dana.jones@LIGO.ORG - posted 10:49, Friday 19 January 2024 - last comment - 11:46, Friday 26 January 2024(75474)
Detector duty factor vs. microseism levels

Dana, Jenne

We looked at how the microseism levels have impacted the detector duty factor since the start of aLIGO to see if our ability to maintain lock during microseisms has gotten better or worse. The attached figure shows the fraction of time the detector maintained lock over the course of a week as a function of the average microseism level over that same week for each week in O4a, as well as each week in (1) O1, (2) O2, (3) O3a, and (4) O3b.

According to the data, it seems we may be slightly worse off in terms of our ability to maintain lock during high levels of microseisms in O4 than we were in O3, but it seems we are better off now than we were in O1 and O2. However, it is difficult to directly compare the data between observing runs given that during certain runs the average level of microseisms seemed consistently higher than in others. There were also certainly other sources of lockloss besisdes microseisms. But it can at least be said that maintaining lock during microseisms does not appear to be a bigger issue now than it used to be.

Note: The two large data gaps present in O2 were removed.

Images attached to this report
Comments related to this report
dana.jones@LIGO.ORG - 11:46, Friday 26 January 2024 (75577)

This is the code I used to produce the attached figure and some additional figures in case anyone would like to repeat this study in the future.

Non-image files attached to this comment
Displaying reports 14781-14800 of 88171.Go to page Start 736 737 738 739 740 741 742 743 744 End