SUS PI code change WP6018

Carl, Terra, Jim, Dave:

New code was installed for h1susitmpi, h1omc, h1susprocpi, h1susetmxpi, h1susetmypi. The model changes went in normally, but the DAQ restart was problematic. The data concentrator error'ed on duplicate channels for H1:SUS-PI_PROC_COMPUTE_MODE9_PLL_SIG_OUT. This was surprising as I had ran my script to check for duplicates prior to the DAQ restart. We reconfigured the DAQ sans h1susprocpi to get the DAQ running again while we investigated the problem. Jim found the problem, in the sys/common/models/PLL_MASTER.mdl file, a testpoint part was named SIG_OUT in addition to a filter module at that level which was named SIG, and the filtermodule has a testpoint also called SIG_OUT. This common part had 32 such duplicates, MODE9 was just the first to be reported.

Terra fixed the models, we restarted h1susprocpi, reintroduced it to the DAQ and restarted the DAQ.

I extended the script check_daq_channel_list_for_duplications.bsh to check both INI files and PAR files.

DAQ Restarts

Jim, Dave:

h1tw0 has become fragile lately (not so h1tw1). We discovered that if we restart the DAQ while h1tw0 is in the midst of writing the raw minute files, this can corrupt the file system requiring an fsck to fix. Today we were careful to only restart the DAQ while h1tw1 was inbetween file writes. This has worked and h1tw0 has not crashed.

In two of today's DAQ restarts we needed to restart the mx-stream on a handfull of frontends.

GDS code upgrade WP6012

Jim:

New GDS code was installed, details in Jim's alog.

New LSC code

Jenne, Dave:

Jenne's new h1lsc code was installed. This added some channels to the commissioning frame (eight channels at 2048Hz).

Radio receiver spectrum analyser work

Carlos, Jordan:

The RF analyser was attached to the FLIR camera windows server, code was installed and tested.

New DAQ frame writer WP6016

Carlos, Dave, Jonathan, Jim:

we installed a new frame writer called h1fw2. It is a standard front end computer using a spare Myricom 10GE card. New SFP and RAM (48GB) were purchased for the unit. This is a dual boot machine (Ubuntu 12 and Debian 8). It has a 1TB internal HDD which we are using for testing. Jim and Jonathan did some Deb8 work on it. We determined 48GB is not sufficient for it to write all the frame types.

As the system is currently configured:

h1fw0 is writing commissioning and science frames (no trends). It is now 100% stable, has been running for 6 days.

h1fw1 is writing all frames. It is unstable, restarting on average every 2 hours.

h1fw2 is writing commissioning and science frames (no trends) to its local disk.

All three have been running for about two hours now. I've extended the DAQ overview MEDM to show all three and check their frames are identical. It would be good to run three writers for O2, if the frames were not identical a trio of writers could indicate which is the incorrect frame.