Displaying report 1-1 of 1.
Reports until 12:40, Tuesday 06 May 2025
H1 CDS
david.barker@LIGO.ORG - posted 12:40, Tuesday 06 May 2025 - last comment - 13:06, Tuesday 06 May 2025(84286)
CDS Maintenance Summary: Tuesday 6th May 2025

WP12510 Add Geist environment sensors

Jonathan, Dave:

Last Friday I started five EPICS IOCs for the four new out-building sensors and one for the existing MSR sensor.

Yesterday I installed the MX and MY Geist watchdog 1250 sensor units in the CDS VEA racks (details in forthcoming alog).

Today we added the new EPICS Channels to the EDC+DAQ. A new H1EPICS_ENV.ini file was created, it is generated by running generate_env_ini.py

This new INI was added to the edcumaster.txt file.

WP12511 Add h1daqfw2 EPICS LOAD MON channels to DAQ

Jonathan, Dave:

A new H1EPICS_CDSMON.ini was created with the addition of h1daqfw2's channels.

New JAC Slow Controls channels

Daniel, Dave:

A previous slow controls upgraded generated new INI channels for the JAC system. Back then we elected to not add them to the DAQ immediately, rather wait for the next target-of-opportunity, which was today.

DAQ restart

Jonathan, Erik, Dave:

The DAQ was restarted to install the new channels for:

No major issues, GDS0 needed a second restart. Due to vent activities we did not take the trend writers offline for this restart, rather just restarted the EDC following the 0-leg restart.

Jonathan tested his new restart-less frame writer during this restart.

EDC channel count 59188 + 84 = 59,272 

Comments related to this report
jonathan.hanks@LIGO.ORG - 13:06, Tuesday 06 May 2025 (84287)

This daqd restart was used as a test of h1daqfw2's ability to adjust on the fly. It went well. As expected the new code saw the changes and adjusted.

Amoung the changes were additions to the system monitoring channels.  We did the restart towards the end of the hour.  Normally that would mean losing close to an hours worth of trend data.  In this case the framewriter adjusts its channel list on the fly.  Below you can see two channels dumped from a 1hr minute trend frame.  The ...H1DAQFW1... was an old pre-existing channel, ...H1DAQFW2... channel was new.  You can see that the new channel was added midway with a zero fill of the data before it existed, while the older channel was not impact (or thrown away with the daqd restart).

In addition, over the weekend I figured it wouldn't take too much work to put a minimal nds1 interface onto the framewriter.  So both Erik and I were able to take some simple measurements through the daqd restart without interruption.  I did have some issues with streaming the data from the edc (the bit we restarted).  This functionality is very much not ready for control room use, but did work as a proof of principle.

Dump of a old and a new channel from a frame generated while the other frame writers were being restarted:

root@h1daqfw2:/frames/trend/minute/14305# framecpp_dump_channel --channel H1:CDS-MONITOR_H1DAQFW1_CPU_LOAD_PERCENT.mean H-H1_M-1430589600-3600.gwf
Frame file: H-H1_M-1430589600-3600.gwf
DEBUG: Processing channel: H1:CDS-MONITOR_H1DAQFW1_CPU_LOAD_PERCENT.mean
DEBUG: Trying as ADC
DEBUG: Is a ADC
Name:     
Compress: 266 (Endianness: Little Scheme: 10)
Type:     2
NData:    60
NBytes:   416
Data: 6.28729164004326, 4.17406255081296, 3.57833329414328, 3.60958333561818, 3.66750004241864, 3.67500002260009, 3.71916669532657, 3.74739585369825, 3.8817708991468, 3.82260420769453, 5.55906248788039, 3.87937504226963, 3.93562503432234, 3.91968751251698, 3.82739583849907, 3.62052083040277, 3.62010418747862, 3.69833336497347, 3.68625002404054, 3.66718753005068, 5.32447914779186, 3.67375002975265, 3.71656252965331, 3.73489584351579, 3.89322916989525, 3.90125003928939, 3.93125004768372, 3.86749999498328, 3.91406253824631, 3.71927081222336, 5.44343745956818, 3.61781248822808, 3.68937503372629, 3.71395837391416, 3.7930208645761, 3.76812503834565, 3.7355208667616, 3.62187499354283, 3.70145832026998, 3.80020837162932, 5.48312501261632, 3.90666671544313, 3.92562501778205, 3.9627083795766, 3.95802086566885, 3.92802087018887, 3.80010416110357, 3.63791664664944, 3.62510419090589, 3.62989583437641, 5.31531244814396, 2.30302085528771, 0.95135415866971, 3.71520840749145, 3.72906252816319, 3.93354169155161, 4.05625004221996, 2.55833331122994, 2.94218750347694, 4.27510416905085
root@h1daqfw2:/frames/trend/minute/14305#
root@h1daqfw2:/frames/trend/minute/14305# framecpp_dump_channel --channel H1:CDS-MONITOR_H1DAQFW2_CPU_LOAD_PERCENT.mean H-H1_M-1430589600-3600.gwf 
Frame file: H-H1_M-1430589600-3600.gwf
DEBUG: Processing channel: H1:CDS-MONITOR_H1DAQFW2_CPU_LOAD_PERCENT.mean
DEBUG: Trying as ADC
DEBUG: Is a ADC
Name:     
Compress: 266 (Endianness: Little Scheme: 10)
Type:     2
NData:    60
NBytes:   96
Data: 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1.34916668335597, 4.81020835687717, 4.67812503005068, 4.78708336452643, 4.95833332886299, 4.98052083601554, 4.76249999230107, 4.90572916567326
root@h1daqfw2:/frames/trend/minute/14305#
Displaying report 1-1 of 1.