From f1f8eeb05bcf03f4a8ad065e4d4ef29a305e3f14 Mon Sep 17 00:00:00 2001 From: Freddie Akeroyd Date: Mon, 19 May 2025 16:33:02 +0100 Subject: [PATCH 1/6] Add hexagin docs --- doc/specific_iocs/CAEN-Hexagon.md | 10 ++++++++++ doc/specific_iocs/dae/CAEN-Hexagon.md | 2 ++ 2 files changed, 12 insertions(+) create mode 100644 doc/specific_iocs/CAEN-Hexagon.md create mode 100644 doc/specific_iocs/dae/CAEN-Hexagon.md diff --git a/doc/specific_iocs/CAEN-Hexagon.md b/doc/specific_iocs/CAEN-Hexagon.md new file mode 100644 index 000000000..cb3f32ffd --- /dev/null +++ b/doc/specific_iocs/CAEN-Hexagon.md @@ -0,0 +1,10 @@ +# CAEN Hexagon (MUX Data Acquisition Electronics) + +The CAEN hexagon is the data acquisition used on MUX. It is currently controlled by the CAENMCA IOC, of which they run two instances for the two hexagons. They also run their DAE in simulation mode to log sample environment data, then the CAEN syncs run number with the DAE and writes its own data files. + +Data is publicsed to the ususal archive, but to the "autoreduced" subfolder + + + + + diff --git a/doc/specific_iocs/dae/CAEN-Hexagon.md b/doc/specific_iocs/dae/CAEN-Hexagon.md new file mode 100644 index 000000000..582fb44ad --- /dev/null +++ b/doc/specific_iocs/dae/CAEN-Hexagon.md @@ -0,0 +1,2 @@ +# CAEN Hexagon + From 45fba8cfc4af4c1626f2a323c731311306b9e6fb Mon Sep 17 00:00:00 2001 From: Freddie Akeroyd Date: Mon, 19 May 2025 16:37:46 +0100 Subject: [PATCH 2/6] Update --- doc/specific_iocs/CAEN-Hexagon.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/doc/specific_iocs/CAEN-Hexagon.md b/doc/specific_iocs/CAEN-Hexagon.md index cb3f32ffd..6d04caf79 100644 --- a/doc/specific_iocs/CAEN-Hexagon.md +++ b/doc/specific_iocs/CAEN-Hexagon.md @@ -1,10 +1,8 @@ # CAEN Hexagon (MUX Data Acquisition Electronics) -The CAEN hexagon is the data acquisition used on MUX. It is currently controlled by the CAENMCA IOC, of which they run two instances for the two hexagons. They also run their DAE in simulation mode to log sample environment data, then the CAEN syncs run number with the DAE and writes its own data files. - -Data is publicsed to the ususal archive, but to the "autoreduced" subfolder - - +The CAEN hexagon is the data acquisition used on MUX. It is currently controlled by the CAENMCA IOC, of which they run two instances for the two hexagons. They also run their DAE in simulation mode to log sample environment data, then the CAEN syncs run number with the DAE and writes its own data files. So you will have the ususal log and nxs file as per an instrument plus some extra bin and nxs files from the hexagon. The hexagon raw files currently have a rather strange timestamp. +Data is publicised to the ususal archive, but to the "autoreduced" subfolder +scripting currently has some extra `begin_hexagons` and `end_hexagons` commands defined in the local python to start/stop acquision - this also begibns a ususal run, so do not use normal begin command From 0b0eb85238798f31bf1234d24f2b0493fd6bc3a3 Mon Sep 17 00:00:00 2001 From: Freddie Akeroyd Date: Mon, 19 May 2025 16:41:29 +0100 Subject: [PATCH 3/6] Update --- doc/specific_iocs/CAEN-Hexagon.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/specific_iocs/CAEN-Hexagon.md b/doc/specific_iocs/CAEN-Hexagon.md index 6d04caf79..0b333b16a 100644 --- a/doc/specific_iocs/CAEN-Hexagon.md +++ b/doc/specific_iocs/CAEN-Hexagon.md @@ -1,8 +1,8 @@ # CAEN Hexagon (MUX Data Acquisition Electronics) -The CAEN hexagon is the data acquisition used on MUX. It is currently controlled by the CAENMCA IOC, of which they run two instances for the two hexagons. They also run their DAE in simulation mode to log sample environment data, then the CAEN syncs run number with the DAE and writes its own data files. So you will have the ususal log and nxs file as per an instrument plus some extra bin and nxs files from the hexagon. The hexagon raw files currently have a rather strange timestamp. +The CAEN hexagon is the data acquisition used on MUX. It is currently controlled by the CAENMCA IOC, of which they run two instances for the two hexagons. They also run their DAE in simulation mode to log sample environment data, then the CAEN syncs run number with the DAE and writes its own data files. So you will have the usual log and nxs file as per an instrument plus some extra bin and nxs files from the hexagon. The hexagon raw files currently have a rather strange timestamp. -Data is publicised to the ususal archive, but to the "autoreduced" subfolder +Data is published to the usual archive, but to the `autoreduced` subfolder -scripting currently has some extra `begin_hexagons` and `end_hexagons` commands defined in the local python to start/stop acquision - this also begibns a ususal run, so do not use normal begin command +scripting currently has some extra `begin_hexagons` and `end_hexagons` commands defined in the local python to start/stop acquisition - this also begins a usual run, so do not use normal begin commands From 82fb699d000a578e22a12c1f1ff53a6f81702645 Mon Sep 17 00:00:00 2001 From: Freddie Akeroyd Date: Thu, 29 May 2025 11:25:09 +0100 Subject: [PATCH 4/6] Update CAEN-Hexagon.md --- doc/specific_iocs/CAEN-Hexagon.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/specific_iocs/CAEN-Hexagon.md b/doc/specific_iocs/CAEN-Hexagon.md index 0b333b16a..f76a27e8e 100644 --- a/doc/specific_iocs/CAEN-Hexagon.md +++ b/doc/specific_iocs/CAEN-Hexagon.md @@ -1,8 +1,8 @@ # CAEN Hexagon (MUX Data Acquisition Electronics) -The CAEN hexagon is the data acquisition used on MUX. It is currently controlled by the CAENMCA IOC, of which they run two instances for the two hexagons. They also run their DAE in simulation mode to log sample environment data, then the CAEN syncs run number with the DAE and writes its own data files. So you will have the usual log and nxs file as per an instrument plus some extra bin and nxs files from the hexagon. The hexagon raw files currently have a rather strange timestamp. +The CAEN hexagon is the data acquisition used on MUX. It is currently controlled by the CAENMCA IOC (`CAENMCA_01`). There are two hexagon hardware boxes, but are controlled from a single IOC so they are stopped and started at the same time. They also run their DAE in simulation mode to log sample environment data, then the CAEN syncs run number with the DAE and writes its own data files. So you will have the usual log and nxs file as per an instrument plus some extra bin and nxs files from the hexagon. The hexagon raw `.bin` files currently have a rather strange timestamp due to a clock issue in the hardware. -Data is published to the usual archive, but to the `autoreduced` subfolder +Data is published to the usual instrument network archive, but to the `autoreduced` subfolder -scripting currently has some extra `begin_hexagons` and `end_hexagons` commands defined in the local python to start/stop acquisition - this also begins a usual run, so do not use normal begin commands +scripting currently has some extra `begin_hexagons` and `end_hexagons` commands defined in the local python to start/stop acquisition - this also begins a usual run, so do not use normal begin commands. Do not use `begin` and `end` - this will just start a simulated DAE run, use the special hexagon commands mentioned previously. From cf64aadaae8a0c53891974dca038b1be6dbfecc8 Mon Sep 17 00:00:00 2001 From: Freddie Akeroyd Date: Thu, 29 May 2025 11:31:49 +0100 Subject: [PATCH 5/6] Update CAEN-Hexagon.md --- doc/specific_iocs/CAEN-Hexagon.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/specific_iocs/CAEN-Hexagon.md b/doc/specific_iocs/CAEN-Hexagon.md index f76a27e8e..55a9abe64 100644 --- a/doc/specific_iocs/CAEN-Hexagon.md +++ b/doc/specific_iocs/CAEN-Hexagon.md @@ -6,3 +6,8 @@ Data is published to the usual instrument network archive, but to the `autoreduc scripting currently has some extra `begin_hexagons` and `end_hexagons` commands defined in the local python to start/stop acquisition - this also begins a usual run, so do not use normal begin commands. Do not use `begin` and `end` - this will just start a simulated DAE run, use the special hexagon commands mentioned previously. +## Troubleshooting + +Sometimes the hexagon loses connection with the IOC, this can be due to a hexagin spontaneous reboot or it may have hung. If you see errors like `exception in pollerTask: CAENMCA::GetData(): Generic error` then +- try an IOC restrart +- try a hexagon power cycle then an IOC restart From 033125bb8cbb81929be48ceab832f62052446e7b Mon Sep 17 00:00:00 2001 From: Freddie Akeroyd Date: Thu, 29 May 2025 11:36:24 +0100 Subject: [PATCH 6/6] Update CAEN-Hexagon.md --- doc/specific_iocs/CAEN-Hexagon.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/specific_iocs/CAEN-Hexagon.md b/doc/specific_iocs/CAEN-Hexagon.md index 55a9abe64..625ab24ae 100644 --- a/doc/specific_iocs/CAEN-Hexagon.md +++ b/doc/specific_iocs/CAEN-Hexagon.md @@ -8,6 +8,6 @@ scripting currently has some extra `begin_hexagons` and `end_hexagons` commands ## Troubleshooting -Sometimes the hexagon loses connection with the IOC, this can be due to a hexagin spontaneous reboot or it may have hung. If you see errors like `exception in pollerTask: CAENMCA::GetData(): Generic error` then -- try an IOC restrart +Sometimes the hexagon loses connection with the IOC, this can be due to a hexagon spontaneous reboot or it may have hung. If you see errors like `exception in pollerTask: CAENMCA::GetData(): Generic error` then +- try an IOC restart - try a hexagon power cycle then an IOC restart