Displaying reports 14801-14820 of 88171.Go to page Start 737 738 739 740 741 742 743 744 745 End
Reports until 11:28, Friday 26 January 2024
H1 CAL
dana.jones@LIGO.ORG - posted 11:28, Friday 26 January 2024 - last comment - 13:20, Tuesday 30 January 2024(75560)
Detector lock history for prior sensing function measurements

Dana, Louis

We analyzed every measurement of the sensing function taken between the start of O4 and October 27th to see if they were reliable and came up with the following, summarized in the table below:

Report ID GPS time [s] Time locked prior to measurement[h]
20230504T055052Z 1367214670 6+
20230505T012609Z 1367285187 5.2
20230505T174611Z 1367343989 5.2
20230505T200419Z 1367352277 0.2
20230506T182203Z 1367432541 4.7
20230508T180014Z 1367604032 6+
20230509T070754Z 1367651292 5.8
20230510T062635Z 1367735213 3.5
20230517T163625Z 1368376603 6+
20230616T161654Z 1370967432 3.4
20230620T234012Z 1371339630 2.9
20230621T191615Z 1371410193 2.1
20230621T211522Z 1371417340 4.0
20230628T015112Z 1371952290 4.8
20230716T034950Z 1373514608 6+
20230727T162112Z 1374510090 6+
20230802T000812Z 1374970110 2.6
20230817T214248Z 1376343786 6+
20230823T213958Z 1376862016 4.3
20230830T213653Z 1377466631 3.7
20230906T220850Z 1378073348 3.9
20230913T183650Z 1378665428 6+
20230928T193609Z 1379964987 6+
20231004T190945Z 1380481803 4.7
20231018T190729Z 1381691267 6+
20231027T203619Z 1382474197 6+

Ideally, the detector should be in lock state at least three hours before making a sensing function measurement to make sure the thermalization process is complete. However, there were a couple measurements that were made when the detector had only been locked for about two hours (06/21, 08/02), and there was one particularly problematic measurement that was made when the detector had only been locked for about 10 minutes (05/05). This last measurement should certainly not be included in the GPR calculation.

The code used to obtain the detector lock state and history given a report ID is attached below. Note: To run this code, you will need access to pydarm, so run the following command in the terminal before executing the file: source /ligo/groups/cal/local/bin/activate

Non-image files attached to this report
Comments related to this report
louis.dartez@LIGO.ORG - 13:20, Tuesday 30 January 2024 (75630)
report 20230505T200419Z changed to 'invalid' in LHO:75629.
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 SUS
oli.patane@LIGO.ORG - posted 10:28, Friday 26 January 2024 (75571)
BRS Drift Trends - Monthly - FAMIS

Closes FAMIS#26439, last checked 74987

BRS Driftmon (attachment1)
All within range, however in the last day, BRS-X has increased steeply.

Aux BRS Channels (attachment2)
ETMX BRS Temp has declined in temperature over the last day, lining up with the increase in BRS-X Drift.

Images attached to this report
LHO VE
david.barker@LIGO.ORG - posted 10:20, Friday 26 January 2024 - last comment - 11:23, Friday 26 January 2024(75570)
Fri CP1 Fill

Fri Jan 26 10:03:24 2024 INFO: Fill completed in 3min 22secs

Dubious fill. From the discharge line pressure it looks like a reasonable fill. From the TC perspective it was not optimal, TC-B min was only -72C which barely tripped the fill. There is no indication of a steady LN2 flow after the trip.

I've zoom in on the plot to show the TC details.

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 11:23, Friday 26 January 2024 (75574)

Gerardo agreed this does not look like a good fill, we will try again at 12:30 today.

LHO FMCS (PEM)
oli.patane@LIGO.ORG - posted 10:05, Friday 26 January 2024 (75569)
HVAC Fan Vibrometers Check - FAMIS

Closes FAMIS#26278, last checked 75471

Corner Station Fans (attachment1)
MR_FAN5_170_2 became noisier after being turned off and back on last Thursday (attachment2), but is still well below being of concern and has been getting quieter over the course of the week.
All other fans are looking normal and within range.

Outbuilding Fans (attachment3)
All fans are looking normal and within range.

Images attached to this report
H1 PSL
oli.patane@LIGO.ORG - posted 09:52, Friday 26 January 2024 (75568)
PSL Weekly Status - FAMIS

Closes FAMIS#26228, last checked 75219


Laser Status:
    NPRO output power is 1.819W (nominal ~2W)
    AMP1 output power is 68.31W (nominal ~70W)
    AMP2 output power is 138.9W (nominal 135-140W)
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN

PMC:
    It has been locked 5 days, 19 hr 23 minutes
    Reflected power = 18.55W
    Transmitted power = 108.4W
    PowerSum = 127.0W

FSS:
    It has been locked for 10 days 1 hr and 27 min
    TPD[V] = 0.5292V

ISS:
    The diffracted power is around 1.9%
    Last saturation event was 10 days 1 hours and 59 minutes ago


Possible Issues:
    PMC reflected power is high
    FSS TPD is low
    ISS diffracted power is low

LHO VE
janos.csizmazia@LIGO.ORG - posted 08:49, Friday 26 January 2024 (75566)
1-25 vent vacuum diary
Late entry.
Activities at 1-25:
- The RGA was completely rebuilt at EX, and the RGA tree was already leak checked. Currently it is pumped, and it is already at the E-9 Torr region
- The 12" 3IFO feedthrough was replaced with a blank on BSC5 at EX
- The spare roughing stations were completely finished
So far, everything went as scheduled.
H1 ISC (SUS)
koji.arai@LIGO.ORG - posted 00:59, Friday 26 January 2024 (75565)
Remaining HAM6/OMC work

Mechanical

Electrical tests:

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.

H1 ISC (ISC, SUS)
keita.kawabe@LIGO.ORG - posted 17:53, Thursday 25 January 2024 - last comment - 18:18, Thursday 25 January 2024(75557)
HAM6 work Jan/25/2024: Alignment of the laser into the new OMC, day 2 (Dana, Koji, Rahul, Keita)

Summary:

We restarted the alignment work. The angle and/or the position of the new OMC relative to the cage is significantly different from the old one, and we had to mechanicaly rebalance not just the OMC, but OM3 and OM2 too, and rotate the cage of OM3. We'll see if these were good enough tomorrow.

1. Rebalancing the OMC

Yesterday, we rebalanced the OMC, the beam was on both of OMC QPDs but we didn't have time to touch up OM1 and OM2 to center the beam on OMC QPDs.  This morning we centered the QPDs and relieved the PIT offset of the OM3 as much as I could by using OM1 and OM2. Then we did another push of the balance mass, recentered the QPDs, and relieved PIT offsets of OM1/2/3 such that everybody kind of equally suffer. We ended up doing four iterations of this in total.

Following is the PIT/YAW offset slider values (ASC output to OM1/OM2 due to earlier WFS centering was already folded into these numbers).

Note1: OMn (n=1/2/3) sliders are not calibrated. Due to different EUL2OSEM matrix, OM2 apparent "range" for the sliders is about a factor of 1.7 larger than OM1 and OM3 (i.e. if you compare OM1 and OM2 coil output, the latter has a factor of 1.7 smaller output than the former given the same slider offset).

Note2: By "centering", we really mean centering w/o offsets. Since the position of the QPDs relative to the cavity mode differs from one assembly to another, there's no reason to assume that the good QPD offsets for the new OMC will be the same as the old one.

  OM1 PIT/YAW OM2 PIT/YAW OM3 PIT/YAW

Offsets that worked for the Old OMC with WFS centering ON yesterday (note: OM2 was railing periodically.)

1023/-403 -1440/-3751 230/-930

New OMC before rebalancing yesterday (note: OMC QPDs couldn't be centered at all no matter what. OM2 was railing periodically.)

1663/-519 -2388/-2948 3200/0
After the 4th round of OMC rebalancing. QPDs are nicely centered. 973/-64 713/-1649

-70/1269

2. Beam height measurement, beam centering on OMs

At this point Koji measured the beam height at OM1, OM2 and OM3.

The beam was about 3/64" or about 1mm too high on OM1 (it was 5mm higher than 4" in the past) but it was too low on OM2 by ~16/64" or about 6mm. It quickly went up from OM2 to OM3 where the beam height was about 2/64" or about 0.8mm too low. The beam was clearing the input hole of the OMC shroud cleanly, and the OMCR beam was level.

These meant that OM2 was excessively tilted up and OM3 excessively down, both mechanically. Koji and I agreed that this is most likely due to the difference in angle for the old and the new OMC.

1/4" mis-centering on OM2 sounded too much to ignore to me, so we decided to bring the beam up at OM2 by using OM1 bias, and mechanically relieve the PIT of OM2/OM3 and YAW of OM3.

We're done with the 1st round of mechanical relieving. We adjusted OM2 PIT. We adjusted OM3 PIT and rotated OM3 cage for YAW while making sure that the beam is at least partially visible on both of the QPDs. After centering QPDA, the following shows the numbers as of now.

  OM1 OM2 OM3
PIT/YAW offset 0/-64 213/-1649 200/-539

Beam height (relative to the nominal height of 4")

3/64" -2/64" -2/64"

Overall, this looks to be a good improvement, but the beam is still hitting QPDB at the edge. We still have to see if it's possible at all to center both QPDs without further mechanical relief.

3. PZT and DCPD electronics are working

Koji scanned the OMC PZT and saw flashing on the DCPD A as well as B. PZT as well as the DCPD preamp are working.


Remaining tasks:

Center the OMC QPDs using mostly OM2 and OM3. If further mechanical relief is required, do.

After the OMC QPDs are centered, confirm that OMCR path is still reasonably level. Center the beam on the OMCR DCPD.

Center the AS_A and AS_B.

I don't know how to confirm that the OMC transmission will still hit the viewport for the camera. We'll try to use the card and the viewer combined.

Check the grounding.

Comments related to this report
koji.arai@LIGO.ORG - 18:18, Thursday 25 January 2024 (75563)

While Keita was working on the beam alignment, I swept the OMC PZT2 to see if the DCPDs can see something. Yes, they did see the OMC flashing.
The attached image is the response of DCPD_A and _B as well as DCPD_SUM, while PZT2 was swept.
The calibration of the numbers are unknown, so it's not quantitative but at least the PDs are connected and A&B were identically responding.

Note that the function of PZT1 is not yet confirmed.

Images attached to this comment
H1 General
oli.patane@LIGO.ORG - posted 16:17, Thursday 25 January 2024 (75561)
Ops DAY Shift End

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: SQZ laser was turned back on and LVEA moved back to Laser Hazard, work continued at HAM6, wind fence repair was started, HAM3 was cleaned in preparation for opening.
LOG:

16:35UTC Team going into LVEA to check on the status of the TCS water leak
17:30 Squeezer laser okay to get turned back on; gets turned on
18:19 LVEA transition to LASER HAZARD

Start Time System Name Location Lazer_Haz Task Time End
18:19 site site LVEA YES LVEA is LASER HAZARD !! Ongoing
22:17 OMC Betsy LVEA yes See if HAM6 peeps need help Ongoing
15:30 FAC Randy LVEA NB n Craning 18:14
15:30 FAC Karen OpticsLab,VacPrep n Tech clean 16:07
16:07 FAC Kim,Karen LVEA n Tech clean HAM 6/7 17:36
16:35 SYS TJ,Betsy,Fil LVEA NO TCS Water Leak Recovery Check 16:54
16:51 FAC Ken MechRoom n Replacing lights 00:22
16:54 VAC Jordan LVEA n Purge air measurement 17:09
17:09 VAC Gerardo, Jordan EX n RGA installation and swapping parts 22:48
17:29 EE Fil,Camilla LVEA n Turn on SQZ laser 17:44
17:34 FAC Chris LVEA yes Helping clean top of HAM3 18:43
17:36 FAC Kim,Karen LVEA yes Tech clean HAM3 19:06
17:44 FAC Jim,Ryan S LVEA n Helping move cleanroom 17:58
17:50 FAC Eric LVEA n Also helping move cleanroom 18:07
18:10 PEM Robert EX n Clean up for yesterday's work (didn't go yet) 18:30
18:22 SQZ Camilla LVEA yes Transitioning LVEA to laser hazard 18:22
18:59 FAC Randy,Mitch,Jim EY n Fixing wind fence 23:16
19:07 SUS Ibrahim LVEA yes Cleaning the outside of sus storage containers 19:51
19:31 OMC Rahul, Koji LVEA yes HAM6 work 19:59
19:33 PEM Robert EX n Clean up for yesterday's work 23:33
19:34   Camilla, Betsy VacPrepLab n   19:51
19:35 PCAL Tony PCal Lab yes(local) RespRat(responsivity ratio measurement) 20:59
20:57 EE Fil EY n Measuring cables 23:52
21:01 TCS TJ LVEA yes Looking for plumbing 21:31
21:03 Health Camilla MY n Getting healthier 21:32
21:15 SUS Ibrahim LVEA yes Cleaning the outside of storage containers pt2 22:05
21:41 Tour Sheila, Alan, interns LVEA yes Tour of LVEA 22:36
21:41 CDS Erik EY n Replace failed power supply 22:08
22:16   Camilla OpticsLab n Looking for stuff 23:31
22:23 FAC Tyler EX n Meet with Jordan 23:07
22:48 VAC Jordan, Janos LVEA yes Looking for parts 23:08
22:53   Jason LVEA yes Check Faro 00:13
23:45   Ibrahim LVEA yes HAM6 express delivery 00:10
H1 CDS
david.barker@LIGO.ORG - posted 13:46, Thursday 25 January 2024 - last comment - 16:23, Thursday 25 January 2024(75558)
h1susauxey front end computer has a failed power supply

Fil, Jonathan, Erik, Dave:

At EY Fil found h1susauxey has its front panel FAIL LED lit. He tracked the issue down to a failed power supply. This is a redundant dual power supply system.

Strangely this system is not beeping, which is the default behaviour if a power supply unit is inserted but not operational.

The IPMI shell confirms that the system has correctly identified the failure:

ipmi sensor output:

  OK     | (2751) PS1 Status        |           Presence detected           |
  Fail   | (2818) PS2 Status        |     Power Supply Failure detected     |
 

Comments related to this report
david.barker@LIGO.ORG - 13:48, Thursday 25 January 2024 (75559)
david.barker@LIGO.ORG - 16:23, Thursday 25 January 2024 (75562)

Erik replaced the failed power supply with a good spare, status is good

h1susauxey:   OK     | (2751) PS1 Status        |           Presence detected           |
h1susauxey:   OK     | (2818) PS2 Status        |           Presence detected           |
 

H1 TCS
camilla.compton@LIGO.ORG - posted 11:23, Thursday 25 January 2024 - last comment - 09:23, Thursday 01 February 2024(75550)
CO2X Laser Swap

TJ, Jason, Camilla, Fil.

WP11612, FRS25384, swapping because current CO2X laser was slowly deteriorating, details in 75249.

Removed: Access 50LT 20706.21015D. Installed 20306-20419D, which was refurbished/re-gassed in March 2020. Table layout: T1200007.

Still to do after the CO2X cooling line issue is solved:

Images attached to this report
Non-image files attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 09:09, Friday 26 January 2024 (75567)

FRS 30283 Created for this issue. 

corey.gray@LIGO.ORG - 09:23, Thursday 01 February 2024 (75667)EPO

Tagging EPO for Thermal Compensation System (TCS) photos.

LHO VE
david.barker@LIGO.ORG - posted 10:10, Thursday 25 January 2024 (75555)
Thu CP1 Fill

Thu Jan 25 10:02:32 2024 INFO: Fill completed in 2min 30secs

Images attached to this report
H1 SQZ
daniel.sigg@LIGO.ORG - posted 10:04, Wednesday 24 January 2024 - last comment - 11:34, Thursday 25 January 2024(75537)
SQZ PMC work

Naoki Vicky Daniel

We physically placed the PMC, the RF photodetector, and a bunch of steering mirrors into the empty space on SQZT0. Everything seems to fit as planned. No beams yet!

We also installed the Thorlabs PDA100A that serves as the PMC_TRANS monitor. It is installed along the seed path. There is a 50:50 splitter that reduces the seed power by 2. We installed a one-side AR coated wedge in the path of the beam dump to get about 19mW of light that we steered onto the PDA100A.

The slow controls system was upgraded to add new channels associated with the PMC and update some channels names. There is no longer a FIBR_REJECTED PD, instead we added a FIBR_INPUT PD that monitors the fiber power from squeezer laser in the beat note box.We no longer have a monitor for light in the wrong polarization at the laser locking beat note. Instead, we have to use the beat note strength to optmize the input polarization.

Comments related to this report
victoriaa.xu@LIGO.ORG - 13:38, Wednesday 24 January 2024 (75546)

Some photos here. Here is the PMC TRANS PD path and aligment, including the beam dumps. Here's a photo of PMC + RFPD fitting into the table, to-be aligned afterwards. The SHG beam path clears the back of the PMC, so that's good.

Images attached to this comment
victoriaa.xu@LIGO.ORG - 13:41, Wednesday 24 January 2024 (75547)

We also installed a longpass filter onto the SEED_LAUNCH_PD (FEL0850, cuts-on above 850nm), so we can now open the SQZT0 table lights without changing the measured seed launch power.

daniel.sigg@LIGO.ORG - 11:34, Thursday 25 January 2024 (75556)

Updated medm

Images attached to this comment
Displaying reports 14801-14820 of 88171.Go to page Start 737 738 739 740 741 742 743 744 745 End