Displaying report 1-1 of 1.
Reports until 14:41, Tuesday 24 June 2025
H1 CDS
david.barker@LIGO.ORG - posted 14:41, Tuesday 24 June 2025 - last comment - 16:42, Tuesday 24 June 2025(85296)
CDS Maintenance Summary: Tuesday 24th June 2025

WP12623 h1asc add fast channels to DAQ

Elenna, Dave:

A new h1asc model was rev-locked and installed. Four new fast DQ channels were added to the DAQ (channel, rate):

> H1:ASC-DC6_P_IN1_DQ, 256
> H1:ASC-DC6_P_OUT_DQ, 512
> H1:ASC-DC6_Y_IN1_DQ, 256
> H1:ASC-DC6_Y_OUT_DQ, 512

DAQ restart needed.

WP12570 Restart Digivideo Cameras with latest pylon

Patrick, Jonathan, Dave:

Jonathan updated pylon on h1digivideo[4,5,6] and restarted all the camera servers on these machines. This should fix the bug of stuck open files accumulating when the camera connection is interrupted.

No DAQ restart needed.

Add PID SMOO channels to vacuum SDF

Dave:

Prior to today's h0vacly restart I added the missing CP PID-control SMOO channels to the vacuum SDF monitor.req and safe.snap files. SDF was restarted 08:29. No DAQ restart needed.

WP12577, 12608, 12615 Upgrade LY Vacuum Controls

Janos, Gerardo, Patrick, Jonathan, Erik, Dave:

Patrick installed a new h0vacly system this morning. Main items are:

Pleae see Patrick's alog for details.

A extended DAQ restart was required, renaming Ion Pump raw minute trend files for uninterrupted lookback and construcing new PT100 (HAM1) raw minute trends following the upgrade of h0vaclx last Tuesday (17th June 2025).

DAQ Restart

Jonathan, Erik, Patrick, Dave:

Immediately following the restart of h1asc at 11:52, the DAQ was restarted using the following procedure:

  1. both trend writers were turned off, allowing raw minute trend file changes on a static system
  2. ip_copy_scripts.bsh was ran on both TWs, for each Ion Pump channel which is being renamed, this copied the old file into the correct directory for the new file, preserving recent lookbacks.
  3. Erik ran his script to merge the previous HAM1 PT100 data sets into the new channel name.
  4. A new H0EPICS_VACLY.ini was generated
  5. 0-leg was restarted, followed by a EDC restart on h1susauxb123
  6. 1-leg was restarted, requiring a second restart of GDS1.

It was at this late point that I remembered that the temporary H1 version of PT100B is no longer needed, and indeed this channel has no data following the removal of the PT100B Volts channel from h0vacly. However since it is still in the EDC, we need to continue running the temporary IOC until the next DAQ restart. I've removed it from edcumaster.txt as a reminder.

GPS Leap Seconds Updates

Jonathan, Erik, Dave:

Erik's FAMIS task reminded us that the leapseonds files expiration date of 30 June 2025 is rapidly approaching. Although no leap seconds are to be applied, the files need to be updated to reset their expiration dates. Please see Erik and Jonathan's alog for more details.

DNS testing 

Erik:

ns1 (backup DNS server) was used by Erik to see if we can reproduce the error whereby loss of connection to GC caused internal CDS name resolution issues. It did not.

Comments related to this report
david.barker@LIGO.ORG - 16:42, Tuesday 24 June 2025 (85304)

Vacuum Ion Pump channel name changes (old-name, new-name)

 

H0:VAC-FCES_IP23_II123_AIP_IC_VOLTS H0:VAC-FCES_IPFCC9_IIC9_AIP_IC_VOLTS
H0:VAC-FCES_IP23_II123_AIP_IC_VOLTS_ERROR H0:VAC-FCES_IPFCC9_IIC9_AIP_IC_VOLTS_ERROR
H0:VAC-FCES_IP23_II123_AIP_IC_MA H0:VAC-FCES_IPFCC9_IIC9_AIP_IC_MA
H0:VAC-FCES_IP23_II123_AIP_IC_MA_ERROR H0:VAC-FCES_IPFCC9_IIC9_AIP_IC_MA_ERROR
H0:VAC-FCES_IP23_II123_AIP_IC_LOGMA H0:VAC-FCES_IPFCC9_IIC9_AIP_IC_LOGMA
H0:VAC-FCES_IP23_II123_AIP_IC_LOGMA_ERROR H0:VAC-FCES_IPFCC9_IIC9_AIP_IC_LOGMA_ERROR
H0:VAC-FCES_IP23_VI123_AIP_PRESS_TORR H0:VAC-FCES_IPFCC9_VIC9_AIP_PRESS_TORR
H0:VAC-FCES_IP23_VI123_AIP_PRESS_TORR_ERROR H0:VAC-FCES_IPFCC9_VIC9_AIP_PRESS_TORR_ERROR
H0:VAC-FCES_IP24_II124_AIP_IC_VOLTS H0:VAC-FCES_IPFCD1_IID1_AIP_IC_VOLTS
H0:VAC-FCES_IP24_II124_AIP_IC_VOLTS_ERROR H0:VAC-FCES_IPFCD1_IID1_AIP_IC_VOLTS_ERROR
H0:VAC-FCES_IP24_II124_AIP_IC_MA H0:VAC-FCES_IPFCD1_IID1_AIP_IC_MA
H0:VAC-FCES_IP24_II124_AIP_IC_MA_ERROR H0:VAC-FCES_IPFCD1_IID1_AIP_IC_MA_ERROR
H0:VAC-FCES_IP24_II124_AIP_IC_LOGMA H0:VAC-FCES_IPFCD1_IID1_AIP_IC_LOGMA
H0:VAC-FCES_IP24_II124_AIP_IC_LOGMA_ERROR H0:VAC-FCES_IPFCD1_IID1_AIP_IC_LOGMA_ERROR
H0:VAC-FCES_IP24_VI124_AIP_PRESS_TORR H0:VAC-FCES_IPFCD1_VID1_AIP_PRESS_TORR
H0:VAC-FCES_IP24_VI124_AIP_PRESS_TORR_ERROR H0:VAC-FCES_IPFCD1_VID1_AIP_PRESS_TORR_ERROR
H0:VAC-FCES_IP25_CS187_STATUS H0:VAC-FCES_IPFCH8A_CSH8A_STATUS
H0:VAC-FCES_IP25_II187_IC_VOLTS H0:VAC-FCES_IPFCH8A_IIH8A_IC_VOLTS
H0:VAC-FCES_IP25_II187_IC_VOLTS_ERROR H0:VAC-FCES_IPFCH8A_IIH8A_IC_VOLTS_ERROR
H0:VAC-FCES_IP25_II187_IC_AMPS H0:VAC-FCES_IPFCH8A_IIH8A_IC_AMPS
H0:VAC-FCES_IP25_II187_IC_AMPS_ERROR H0:VAC-FCES_IPFCH8A_IIH8A_IC_AMPS_ERROR
H0:VAC-FCES_IP25_VI187_PRESS_TORR H0:VAC-FCES_IPFCH8A_VIH8A_PRESS_TORR
H0:VAC-FCES_IP25_VI187_PRESS_TORR_ERROR H0:VAC-FCES_IPFCH8A_VIH8A_PRESS_TORR_ERROR

 

Displaying report 1-1 of 1.