From 4be4dcd2cb4605daba1686296a4e15b53646d759 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:15:09 +0100 Subject: [PATCH 01/60] Update ZOOM-Instrument-Details.md --- .../instrument_details/ZOOM-Instrument-Details.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/doc/processes/instrument_details/ZOOM-Instrument-Details.md b/doc/processes/instrument_details/ZOOM-Instrument-Details.md index 687665da9..6ff78f33b 100644 --- a/doc/processes/instrument_details/ZOOM-Instrument-Details.md +++ b/doc/processes/instrument_details/ZOOM-Instrument-Details.md @@ -7,7 +7,7 @@ The [ZOOM](http://www.isis.stfc.ac.uk/instruments/zoom/zoom8060.html) web page d The ZOOM shutter is due to open in February 2017 (see Zoom plan 28th May 2016). ## Control System ## -ZOOM will use the IBEX control system. +ZOOM uses the IBEX control system. ## ZOOM Equipment ## The equipment listed below is to be used on ZOOM. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -290,8 +290,7 @@ As used on: [LARMOR](LARMOR-Instrument-Details)
{#zoom_noteHitachi} ##### Note: Hitachi ##### -Hitachi L-7100 HPLC pump (no longer supported at ISIS). ~Can't find L-7100 on [Hitachi web-site](http://www.hitachi-hightech.com/global/about/corporate/group/hhs) (may be obsolete). Check existing SECI VI for logic and manual: both VI and manual are located here: `C:\LabVIEW Modules\Drivers\Hitachi L-7100`.~ - * Update (27-06-2019): Hitachi pumps are no longer used. No longer any need to support them. See [#3780](https://github.com/ISISComputingGroup/IBEX/issues/3780). +Hitachi pumps are no longer used. No longer any need to support them. See [#3780](https://github.com/ISISComputingGroup/IBEX/issues/3780). {#zoom_noteHaake} ##### Note: Thermo Scientific (Haake) ##### @@ -371,4 +370,4 @@ Details of [Closed-Cycle Refrigerators](http://www.isis.stfc.ac.uk/sample-enviro {#zoom_note7p5TMagnet} ##### Note: 7.5T Magnet ##### -Model: [7.5T Magnet](https://www.isis.stfc.ac.uk/Pages/75T-Magnet.aspx) \ No newline at end of file +Model: [7.5T Magnet](https://www.isis.stfc.ac.uk/Pages/75T-Magnet.aspx) From b1686a7cf532fdc59a95ce3ac187d57bf1e3a298 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:16:10 +0100 Subject: [PATCH 02/60] Update ZOOM-Instrument-Details.md --- doc/processes/instrument_details/ZOOM-Instrument-Details.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/doc/processes/instrument_details/ZOOM-Instrument-Details.md b/doc/processes/instrument_details/ZOOM-Instrument-Details.md index 6ff78f33b..6c4f02587 100644 --- a/doc/processes/instrument_details/ZOOM-Instrument-Details.md +++ b/doc/processes/instrument_details/ZOOM-Instrument-Details.md @@ -6,9 +6,6 @@ The [ZOOM](http://www.isis.stfc.ac.uk/instruments/zoom/zoom8060.html) web page d The ZOOM shutter is due to open in February 2017 (see Zoom plan 28th May 2016). -## Control System ## -ZOOM uses the IBEX control system. - ## ZOOM Equipment ## The equipment listed below is to be used on ZOOM. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). From c234c77378ed34a8668116283a860ba06701ad5e Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:21:13 +0100 Subject: [PATCH 03/60] Update OFFSPEC-Instrument-Details.md --- .../OFFSPEC-Instrument-Details.md | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md b/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md index bb6383dd6..fae29b67b 100644 --- a/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md +++ b/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md @@ -11,9 +11,6 @@ This page collects information that will be useful for the implementation of the Bench moves so that angle is correct this requires motors at front and back to change positions and the bench to slide in and out. This maintains the distance from the detector to the sample in an arc. -## Control System ## -OFFSPEC will migrate from the SECI control system to the IBEX control system in MMMMMMMM YYYY. - ## OFFSPEC Equipment ## The equipment listed below is used on OFFSPEC. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -64,7 +61,6 @@ The equipment listed below is used on OFFSPEC. Please add new information (e.g.
Older information: -``` Manufacturer | Model | Type | Connection | Driver | Notes | ------------ | ------------- | ------------- | ------------- | ------------- | ------------------------------------------- ISIS | DAE 2 | Detector Electronics | Ethernet | | [see DAE note](#note-dae) @@ -218,16 +214,6 @@ OFFSPEC has the following devices under motion control: 1. Polarizer 1. reflectometer sample stack -## OFFSPEC SECI Configs ## -Document information about OFFSPEC SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -OFFSPEC_place_holder1.conf | - | dd/mm/yyyy | - | -OFFSPEC_place_holder2.conf | - | dd/mm/yyyy | - | - -``` -
## OFFSPEC Genie Scripts ## From 5d31a86e52b3d90973d06704b5c58c7b744303f9 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:22:09 +0100 Subject: [PATCH 04/60] Update MUON-Front-End-Instrument-Details.md --- .../instrument_details/MUON-Front-End-Instrument-Details.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/doc/processes/instrument_details/MUON-Front-End-Instrument-Details.md b/doc/processes/instrument_details/MUON-Front-End-Instrument-Details.md index 0018d3081..64c61142a 100644 --- a/doc/processes/instrument_details/MUON-Front-End-Instrument-Details.md +++ b/doc/processes/instrument_details/MUON-Front-End-Instrument-Details.md @@ -5,9 +5,6 @@ This page contains information pertinent to the automation of the Muon Front End ## Background & Timeline ## The system is due on line September 2016. -## Control System ## -Whilst the Front End control will be undertaken under IBEX, it must integrate with SECI as well as part of the system is to be used on existing instruments. Some of the IOCs will only be controlled from instrument PCs, whilst in some situations only monitoring will be required. - ## Equipment ## | Manufacturer | Model | Type | Connection | Driver | Notes | | --- | --- | --- | --- | --- | --- | @@ -29,4 +26,4 @@ The barn doors and momentum slits control the muon beam delivered to the 3 muon {#muonfe_noteMotion} ##### Note: Motion ##### -There is a project relating to the motion on the South Side Muons in progress, this information may be out of date \ No newline at end of file +There is a project relating to the motion on the South Side Muons in progress, this information may be out of date From f56004a0d87ddb990b56681277c2780fe7ca399b Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:24:28 +0100 Subject: [PATCH 05/60] Update CHIPIR-Instrument-Details.md --- .../instrument_details/CHIPIR-Instrument-Details.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/doc/processes/instrument_details/CHIPIR-Instrument-Details.md b/doc/processes/instrument_details/CHIPIR-Instrument-Details.md index e9598363e..24df191eb 100644 --- a/doc/processes/instrument_details/CHIPIR-Instrument-Details.md +++ b/doc/processes/instrument_details/CHIPIR-Instrument-Details.md @@ -96,9 +96,4 @@ Not required for day 1. Open to suggestions. {#chipir_note-beckhoff} ##### Note: Beckhoff #### -1. Needed prior to migration, should be revisited during migration to move to using more standard motion control under IBEX 1. There are three items, a secondary shutter and 2 filters being controlled by a Beckhoff -1. Initially these will be controlled via SECI, with the Beckhoff managing the reporting and moving of the items in/out of the beam, these will be reported back to IBEX using the standard Beckhoff tagging method -1. A VI will be needed which interacts with the PVs generated by TCIOC - - From 5585e9a8e8c7b89ab19cec9a44224bf6516fe2d8 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:25:28 +0100 Subject: [PATCH 06/60] Update WISH-Instrument-Details.md --- .../instrument_details/WISH-Instrument-Details.md | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/doc/processes/instrument_details/WISH-Instrument-Details.md b/doc/processes/instrument_details/WISH-Instrument-Details.md index 95e04c2f7..d3cefdcd4 100644 --- a/doc/processes/instrument_details/WISH-Instrument-Details.md +++ b/doc/processes/instrument_details/WISH-Instrument-Details.md @@ -4,9 +4,6 @@ This page collects information that will be useful for the implementation of the ## Background & Timeline ## WISH is a long-wavelength diffractometer, on TS2. The [WISH](https://www.isis.stfc.ac.uk/Pages/WISH.aspx) web page describes the background to the instrument. -## Control System ## -WISH has migrated to IBEX from SECI - ## WISH Equipment ## The equipment listed below is used on WISH. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -156,15 +153,3 @@ WISH also tends to borrow things from other instruments. Commonly used equipment 1. IRIS Baratron Gas cell 1. Automatic needle valve - see note on [ticket #6695](https://github.com/ISISComputingGroup/IBEX/issues/6695) for investigation, [ticket #4240](https://github.com/ISISComputingGroup/IBEX/issues/4240) for IOC implementation and [ticket #6777](https://github.com/ISISComputingGroup/IBEX/issues/6777) for OPI. -## WISH SECI Configs ## -Document information about WISH SECI configs here. - -Note: Most of WISH configs revolve around the WISH base config. This has been created as a component in IBEX and subsequent components for each thing that is added to the WISH base config should be added as components (i.e. the Teslatron, Strain Cell, Rotation stages etc.) - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -WISH_base.conf | WISH_base.comp | 01/07/2021 | - | -WISH_base + Oxford Cryostat.conf | WISH_base.comp, Oxford - teslatron.comp | "" | - | - -## WISH Genie Scripts ## -Similarly, Document information about WISH SECI Genie scripts here. From eb8702ab81d6b8d02609da523324dce8d9f0ee14 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:26:45 +0100 Subject: [PATCH 07/60] Update VESUVIO-Instrument-Details.md --- .../VESUVIO-Instrument-Details.md | 41 ------------------- 1 file changed, 41 deletions(-) diff --git a/doc/processes/instrument_details/VESUVIO-Instrument-Details.md b/doc/processes/instrument_details/VESUVIO-Instrument-Details.md index b843cfd1d..8989800c5 100644 --- a/doc/processes/instrument_details/VESUVIO-Instrument-Details.md +++ b/doc/processes/instrument_details/VESUVIO-Instrument-Details.md @@ -73,47 +73,6 @@ Experiments requiring pressure transducer. [Chell CCD100](http://www.chell.co.uk ##### Note: Keithley ##### Experiments requiring source meter. [Keithley 2400 Source Meter](http://uk.tek.com/keithley-source-measure-units/keithley-smu-2400-series-sourcemeter) -## VESUVIO SECI Configs ## -Over the years, VESUVIO is likely to have accumulated a significant collection of SECI configs. Not all of them are current (some may no longer be used, or used only infrequently). We will need to investigate how to convert them to IBEX configs. -The config files are located in the folder `SECI\Configurations\` on the VESUVIO control server and have the extension `.conf`. Sub-configuration files have the extension `.comp` (component). The files with numbers as extensions (`.1`, `.2`, `.3`,etc.) are backups of the configuration and sub-configuration files. - - - -| Configuration Name | Sub-Configurations | Last Accessed | Required | ------------- |-------------------------------------| ------------- | ------------- | -VESUVIO_withTLCCR__31mar2015 | Sub_EVS_Base, Sub_EVS_Eurotherm_CCR | 16/09/2016 | - | -highTfurnace__oct2015 | - | 12/10/2015 | - | -EVS_Huber | Eurotherm | 09/09/2015 | - | -VESUVIO_Nbfurnace__15june2015 | Eurotherm | 15/06/2015 | - | -VESUVIO_emptyInstrument__26mar2015 | Eurotherm | 26/03/2015 | - | -VESUVIO_emptyInstrument__16mar2015 | Eurotherm | 16/03/2015 | - | -EVS Ambient | Eurotherm | 22/08/2014 | - | -tempalooza | Eurotherm | 13/06/2014 | - | -20130425 - EVS Ambient | - | 26/04/2013 | - | -rotating cs + cryo | - | 28/07/2011 | - | -heaters on sample 0 -100C | - | 28/07/2011 | - | -EVS Heated Can | - | 22/07/2011 | - | -EVS Cryostat | - | 22/07/2011 | - | -EVS Ambient + Platinums | - | 22/07/2011 | - | -Calibration | - | 31/03/2011 | - | -U Foil Calibration | - | 14/02/2011 | - | -rotating prisma cs | - | 14/02/2011 | - | -rotating prisma cs + cryo | - | 14/02/2011 | - | -rotating cs | - | 14/02/2011 | - | -rotating ccr | - | 14/02/2011 | - | -Neocera | - | 14/02/2011 | - | -Kelvinox | - | 14/02/2011 | - | -EVS Water Bath | - | 14/02/2011 | - | -EVS Kelvinox | - | 14/02/2011 | - | -EVS CCR | - | 14/02/2011 | - | -EVS Ambient + Cryostat | - | 14/02/2011 | - | -EVS 4K TLCCR | - | 14/02/2011 | - | -ChipIR2 | - | 14/02/2011 | - | -ChipIR | - | 14/02/2011 | - | - -## VESUVIO Genie Scripts ## -Similarly, VESUVIO has built up a significant collection of genie scripts over the years. Again, many scripts are old and may no longer be used regularly. There will be a need to convert some of these scripts to genie-python, but probably not all. - ## Tested IOCs ## | What | When | Notes | From bcc9acf2fd976375e16be13d84dc4143efb6b71d Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:27:27 +0100 Subject: [PATCH 08/60] Update TOSCA-Instrument-Details.md --- .../instrument_details/TOSCA-Instrument-Details.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/doc/processes/instrument_details/TOSCA-Instrument-Details.md b/doc/processes/instrument_details/TOSCA-Instrument-Details.md index 8cde22272..a32fd16a4 100644 --- a/doc/processes/instrument_details/TOSCA-Instrument-Details.md +++ b/doc/processes/instrument_details/TOSCA-Instrument-Details.md @@ -4,9 +4,6 @@ This page collects information that will be useful for the implementation of the ## Background & Timeline ## TOSCA is an indirect geometry spectrometer, on TS1. The [TOSCA](https://www.isis.stfc.ac.uk/Pages/TOSCA.aspx) web page describes the background to the instrument. -## Control System ## -TOSCA will migrate from the SECI control system to the IBEX control system in late October 2018 (prior to Cycle 2018/03). - ## TOSCA Equipment ## The equipment listed below is used on TOSCA. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -80,13 +77,3 @@ TOSCA has the following specialist panels/systems: TOSCA has the following devices under motion control: 1. XY beam scanner (2 axis GALIL motor - this GALIL moves about and is not permanently on TOSCA). - -## TOSCA SECI Configs ## -Document information about TOSCA SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -Standard + Rotation Stage.conf | - | 25/10/2018 | - | - -## TOSCA Genie Scripts ## -Similarly, Document information about TOSCA SECI Genie scripts here. From 1a1e34d9bf89933ec776bf62a2192f78bac2eb50 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:33:12 +0100 Subject: [PATCH 09/60] Update SXD-Instrument-Details.md --- .../instrument_details/SXD-Instrument-Details.md | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/doc/processes/instrument_details/SXD-Instrument-Details.md b/doc/processes/instrument_details/SXD-Instrument-Details.md index 6f55e8c59..9aa753344 100644 --- a/doc/processes/instrument_details/SXD-Instrument-Details.md +++ b/doc/processes/instrument_details/SXD-Instrument-Details.md @@ -114,15 +114,4 @@ SXD has the following specialist panels/systems: SXD has the following devices under motion control: 1. goniometer -1. XYZ stage -## SXD SECI Configs ## -Document information about SXD SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -SXD_place_holder1.conf | - | dd/mm/yyyy | - | -SXD_place_holder2.conf | - | dd/mm/yyyy | - | - -## SXD Genie Scripts ## -Similarly, Document information about SXD SECI Genie scripts here. From 5e973ba012b428528c3d356d405f717a726081d6 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:36:35 +0100 Subject: [PATCH 10/60] Update SURF-Instrument-Details.md --- .../SURF-Instrument-Details.md | 20 ++----------------- 1 file changed, 2 insertions(+), 18 deletions(-) diff --git a/doc/processes/instrument_details/SURF-Instrument-Details.md b/doc/processes/instrument_details/SURF-Instrument-Details.md index c4c9b20fe..e189ee110 100644 --- a/doc/processes/instrument_details/SURF-Instrument-Details.md +++ b/doc/processes/instrument_details/SURF-Instrument-Details.md @@ -60,7 +60,7 @@ Eurotherms are used to control temperature. 1. Grant Water Bath (no longer supported at ISIS) ~(apparently the following Grant water bath: WB27)~ * Update (25-06-2019): Grant water baths are no longer used. No longer any need to support them. See [#4457](https://github.com/ISISComputingGroup/IBEX/issues/4457) 1. Haake Water Bath (no longer supported at ISIS) - 1. ~Haake N6 Water Bath (apparently the following Haake water bath: WB9). Haake has now been taken over by [ThermoFisher](https://www.thermofisher.com/uk/en/home/life-science/lab-equipment/water-baths-circulators-chillers.html). N6 model may be obsolete. Check existing SECI VI for logic and manual.~ + 1. ~Haake N6 Water Bath (apparently the following Haake water bath: WB9). Haake has now been taken over by [ThermoFisher](https://www.thermofisher.com/uk/en/home/life-science/lab-equipment/water-baths-circulators-chillers.html). N6 model may be obsolete. * Update (25-06-2019): Haake water baths are no longer used. No longer any need to support them. See [#4456](https://github.com/ISISComputingGroup/IBEX/issues/4456) 1. See also [Water Baths](https://www.isis.stfc.ac.uk/Pages/Water-Baths.aspx) list @@ -77,7 +77,7 @@ Hitachi L-7100 HPLC pump (no longer supported at ISIS). ~Can't find L-7100 on [ ##### Note: Knauer ##### 1. Knauer K-6 Electric Valve Drive. [Knauer web site](https://www.knauer.net)
- * K-6 model appears to have been superseded. Check existing SECI VI for logic and manual. + * K-6 model appears to have been superseded. * See `C:\LabVIEW Modules\Drivers\Knauer Electric Valve Drive K-6\Documentation` for existing VI. * The Knauer K-6 Electric Valve Drive is (nearly) always used with the [Knauer HPLC pump](#note-knauer-hplc-pump). @@ -111,16 +111,11 @@ Nima Trough: SECI uses a manufacturer supplied VI (see `C:\LabVIEW Modules\Drive ##### Note: Peristaltic Pumps ##### 1. [Watson Marlow 323 Peristaltic Pump](http://www.watson-marlow.com/gb-en/range/watson-marlow/300-tube-pumps/323d/) -1. Check existing SECI VI for logic and manual: VI and manuals are located here: - * `C:\LabVIEW Modules\Drivers\Watson Marlow 323 Pump` ##### Note: Syringe Pumps ##### 1. [WPI Aladdin-1000 Syringe Pump](https://www.wpi-europe.com/products/pumps--microinjection/laboratory-syringe-pumps/al1000-220.aspx) 1. [WPI SP2xx Syringe Pump](https://www.wpi-europe.com/products/pumps--microinjection/laboratory-syringe-pumps.aspx) - check specific model. See also [#3261](https://github.com/ISISComputingGroup/IBEX/issues/3261) 1. The Watson Marlow and WPI Aladdin-1000 syringe pumps are the ones used most frequently on SURF (usually depending on which one is available). -1. Check existing SECI VIs for logic and manual: VIs and manuals are located here: - * `C:\LabVIEW Modules\Drivers\WPI Aladdin-1000 Syringe Pump` - * `C:\LabVIEW Modules\Drivers\WPI SP2XX Pumps` ## SURF Notes ## SURF has the following specialist panels/systems: @@ -141,14 +136,3 @@ SURF has the following devices under motion control: 1. transmission monitor 1. XYZ stage - -## SURF SECI Configs ## -Document information about SURF SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -SURF_place_holder1.conf | - | dd/mm/yyyy | - | -SURF_place_holder2.conf | - | dd/mm/yyyy | - | - -## SURF Genie Scripts ## -Similarly, Document information about SURF SECI Genie scripts here. From 829e158d929d8d6d4b677c793fb8c055ab95de39 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:40:08 +0100 Subject: [PATCH 11/60] Update SANS2D-Instrument-Details.md --- .../SANS2D-Instrument-Details.md | 21 ++++--------------- 1 file changed, 4 insertions(+), 17 deletions(-) diff --git a/doc/processes/instrument_details/SANS2D-Instrument-Details.md b/doc/processes/instrument_details/SANS2D-Instrument-Details.md index c8bdde5bf..e304f362a 100644 --- a/doc/processes/instrument_details/SANS2D-Instrument-Details.md +++ b/doc/processes/instrument_details/SANS2D-Instrument-Details.md @@ -146,18 +146,15 @@ Eurotherms are used to control temperature Orange Cryostat, CCR and Furnace devi 1. See also [#3784](https://github.com/ISISComputingGroup/IBEX/issues/3784) ##### Note: Hitachi ##### -Hitachi L-7100 HPLC pump (no longer supported at ISIS). ~Can't find L-7100 on [Hitachi web-site](http://www.hitachi-hightech.com/global/about/corporate/group/hhs (may be obsolete). Check existing SECI VI for logic and manual.~ - * Update (27-06-2019): Hitachi pumps are being retired. No longer any need to support them. See [#3780](https://github.com/ISISComputingGroup/IBEX/issues/3780) - * SANS2D will not be using Hitachi pumps in future. They will use the [Knauer](#note-knauer-hplc) or Jasco HPLC pumps. +Hitachi pumps are being retired. No longer any need to support them. SANS2D will not be using Hitachi pumps in future. They will use the [Knauer](#note-knauer-hplc) or Jasco HPLC pumps. ##### Note: Knauer ##### 1. Knauer K-6 Electric Valve Drive. [Knauer web site](https://www.knauer.net)
- * K-6 model appears to have been superseded. Check existing SECI VI for logic and manual. + * K-6 model appears to have been superseded. 1. See also [#3781](https://github.com/ISISComputingGroup/IBEX/issues/3781) ##### Note: Knauer HPLC ##### Knauer HPLC 1050 [Knauer HPLC 1050 is discontinued.](https://www.knauer.net/en/discontinued-smartline-pump-1050-successor-azura-p-61l/p14161). -1. Check existing SECI VI for logic and manual. 1. Support for Knauer HPLC 1050 is implemented via the following tickets: [#3262](https://github.com/ISISComputingGroup/IBEX/issues/3262), [#3782](https://github.com/ISISComputingGroup/IBEX/issues/3782), @@ -236,7 +233,7 @@ SANS2D has two baffle trolleys (in the vacuum tank). One for the front baffle, ##### Note: Beamstops ##### SANS2D has beamstops on the front and rear detectors 1. Front Detector: - * has a single beamstop, mounted on the detector trolley. Rotates in the plane of the detector array. The beamstop must not be moved when the detector is rotated (in SECI this requirement is implemented as a software inhibit). + * has a single beamstop, mounted on the detector trolley. Rotates in the plane of the detector array. The beamstop must not be moved when the detector is rotated (in SECI this requirement was implemented as a software inhibit). * has a strip beamstop, mounted on the detector trolley. Moves linearly across the face of the detector array. Primarily used for commissioning purposes (usually "parked" out of the way). 1. Rear Detector: * has three beamstops, mounted on a pillar attached to the detector trolley. Pillar moves linearly across the face of the detector array. The individual beam stops move independently up/down on the pillar. @@ -267,21 +264,11 @@ SANS2D has the following devices under motion control: Specialist requirements: 1. There is a requirement within SANS2D to inhibit the movement of the detectors when they are powered (the CAEN HV is ON) -## SANS2D SECI Configs ## -Document information about SANS2D SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -SANS2D_place_holder1.conf | - | dd/mm/yyyy | - | -SANS2D_place_holder2.conf | - | dd/mm/yyyy | - | - -## SANS2D Genie Scripts ## -Similarly, Document information about SANS2D SECI Genie scripts here. ## SANS2D Baldor Drives ## SANS2D has 5 guides on the front end. Each of these has a significant weight - ~3 tonnes. The motors used to lift the guides are servo motors. Galil controllers cannot provide sufficient power to motors capable of lifting such weights. As a result, some Baldor drives were introduced to provide the power required to lift these guides. They are digital motion controllers that can communicate with a control system and have settings in each controller to drive the motor. -However, ISIS uses them as pseudo dumb power amplifiers only. A Galil drives the axes like a servo - it provides an analogue signal to the Baldor to ask it to drive, but no core power. The Baldor drives the axes. Therefore, from the point of view of SECI or IBEX, the Baldor drives appear as Galil axes. +However, ISIS uses them as pseudo dumb power amplifiers only. A Galil drives the axes like a servo - it provides an analogue signal to the Baldor to ask it to drive, but no core power. The Baldor drives the axes. Therefore, from the point of view of IBEX, the Baldor drives appear as Galil axes. The Baldor drives do need to be set up – but this is done independently. Historically, this entire arrangement caused a lot of problems during commissioning. There is a bespoke homing routine in use with this setup (the need for such a thing has been questioned but, for now, a bespoke homing routine continues in use). From d9e8db85cc2c67bda0048edc43e4e13b259fd2c9 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:43:17 +0100 Subject: [PATCH 12/60] Update SANDALS-Instrument-Details.md --- .../SANDALS-Instrument-Details.md | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/doc/processes/instrument_details/SANDALS-Instrument-Details.md b/doc/processes/instrument_details/SANDALS-Instrument-Details.md index f34319c99..9009d66ef 100644 --- a/doc/processes/instrument_details/SANDALS-Instrument-Details.md +++ b/doc/processes/instrument_details/SANDALS-Instrument-Details.md @@ -42,7 +42,7 @@ _**Note:**_ NIMROD does not have choppers either. {#sandals_noteJaws} ##### Note: Jaws ##### -SANDALS has a single set of jaws controlled by a [Parker controller](https://stfc365.sharepoint.com/sites/ISISExperimentControls/ICP%20Discussions/SANDALS/SANDALS_Parker_Controller.jpg), which is not currently controlled by SECI. There is no requirement to support the Parker system in IBEX, although it would be very convenient if such a thing were possible. +SANDALS has a single set of jaws controlled by a [Parker controller](https://stfc365.sharepoint.com/sites/ISISExperimentControls/ICP%20Discussions/SANDALS/SANDALS_Parker_Controller.jpg), which was not controlled by SECI. There is no requirement to support the Parker system in IBEX, although it would be very convenient if such a thing were possible. It is proposed to replace the Parker controller with a Galil DMC4040 controller (see [#3259](https://github.com/ISISComputingGroup/IBEX/issues/3259)). @@ -104,17 +104,6 @@ Experiments requiring pressure transducer. [Chell CCD100](http://www.chell.co.uk Experiments requiring source meter. [Keithley 2400 Source Meter](http://uk.tek.com/keithley-source-measure-units/keithley-smu-2400-series-sourcemeter).
See also [#1826](https://github.com/ISISComputingGroup/IBEX/issues/1826). -## SANDALS SECI Configs ## -Document information about SANDALS SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -SANDALS_place_holder1.conf | - | dd/mm/yyyy | - | -SANDALS_place_holder2.conf | - | dd/mm/yyyy | - | - -## SANDALS Genie Scripts ## -Similarly, Document information about SANDALS SECI Genie scripts here. - ## SANDALS Notes ## Add any notes about special items of equipment, setup or conditions on SANDALS that might impact the deployment and configuration of IBEX. From 8af39b5a8edd95960c1894a1db93bc136da2e067 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:46:49 +0100 Subject: [PATCH 13/60] Update POLREF-Instrument-Details.md --- .../POLREF-Instrument-Details.md | 23 ++++--------------- 1 file changed, 4 insertions(+), 19 deletions(-) diff --git a/doc/processes/instrument_details/POLREF-Instrument-Details.md b/doc/processes/instrument_details/POLREF-Instrument-Details.md index 50b00fa61..37b7d1305 100644 --- a/doc/processes/instrument_details/POLREF-Instrument-Details.md +++ b/doc/processes/instrument_details/POLREF-Instrument-Details.md @@ -5,9 +5,6 @@ This page collects information that will be useful for the implementation of the ## Background & Timeline ## POLREF is a general purpose polarised neutron reflectometer, on TS2. The [POLREF](https://www.isis.stfc.ac.uk/Pages/polref.aspx) web page describes the background to the instrument. -## Control System ## -POLREF will migrate from the SECI control system to the IBEX control system in MMMMMMMM YYYY. - ## POLREF Equipment ## The equipment listed below is used on POLREF. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -75,9 +72,7 @@ Eurotherms are used to control temperature Orange Cryostat, CCR and Furnace devi ##### Note: Water Baths ##### 1. Julabo Water Bath (apparently the following Julabos: WB23 ) * consult the [Julabo commands](/specific_iocs/temp_controllers/julabo_commands.xlsx) spreadsheet for specific details of which set of commands is used by these water baths. -1. Haake Water Bath (no longer supported at ISIS) - 1. ~Haake N6 Water Bath. Haake has now been taken over by [ThermoFisher](https://www.thermofisher.com/uk/en/home/life-science/lab-equipment/water-baths-circulators-chillers.html). N6 model may be obsolete. Check existing SECI VI for logic and manual~. -1. ~See also [Water Baths](https://www.isis.stfc.ac.uk/Pages/Water-Baths.aspx) list~ +1. Haake Water Baths are no longer supported at ISIS ##### Note: KEPCO ##### 1. [Kepco BOP 100-10MG PSU](http://www.kepcopower.com/bophimod.htm). @@ -89,7 +84,7 @@ Eurotherms are used to control temperature Orange Cryostat, CCR and Furnace devi See also tickets [#1826](https://github.com/ISISComputingGroup/IBEX/issues/1826), [#2695](https://github.com/ISISComputingGroup/IBEX/issues/2695), [#2801](https://github.com/ISISComputingGroup/IBEX/issues/2801) and [#3176](https://github.com/ISISComputingGroup/IBEX/issues/3176). ##### Note: Hitachi ##### -Hitachi L-7100 HPLC pump (no longer supported at ISIS). ~Can't find L-7100 on [Hitachi web-site](http://www.hitachi-hightech.com/global/about/corporate/group/hhs (may be obsolete). Check existing SECI VI for logic and manual.~ +Hitachi pumps are no longer supported at ISIS ##### Note: JASCO HPLC Pump ##### [JASCO HPLC pump](https://jascoinc.com/products/chromatography/hplc/modules/hplc-pumps/) is a new (for ISIS) model of HPLC pump. Jasco pumps are replacing the old Hitachi pumps. @@ -98,10 +93,10 @@ Hitachi L-7100 HPLC pump (no longer supported at ISIS). ~Can't find L-7100 on [ ##### Note: Knauer ##### 1. Knauer K-6 Electric Valve Drive. [Knauer web site](https://www.knauer.net)
- * K-6 model appears to have been superseded. Check existing SECI VI for logic and manual. + * K-6 model appears to have been superseded. ##### Note: Knauer HPLC ##### -Knauer HPLC 1050 [Knauer HPLC 1050 is discontinued.](https://www.knauer.net/en/discontinued-smartline-pump-1050-successor-azura-p-61l/p14161). Check existing SECI VI for logic and manual. +Knauer HPLC 1050 [Knauer HPLC 1050 is discontinued.](https://www.knauer.net/en/discontinued-smartline-pump-1050-successor-azura-p-61l/p14161). ##### Note: LakeShore ##### 1. [Model 327](https://www.lakeshore.com/products/Cryogenic-Temperature-Controllers/Pages/default.aspx). Model 327 is not listed. Is it an obsolete model, or should it be Model-372? @@ -151,13 +146,3 @@ POLREF has the following devices under motion control: **Note:** (from original POLREF notes (may now be obsolete - check with Kathryn)) Note for when the time comes - check with the instrument scientist if the calibration function for the Danfysik is still used (allows for specific hysteresis curves to use between the limits in use), if it is, make sure we capture this functionality again - likely to be some SNL or a genie-python script might be able to do it instead. -## POLREF SECI Configs ## -Document information about POLREF SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -POLREF_place_holder1.conf | - | dd/mm/yyyy | - | -POLREF_place_holder2.conf | - | dd/mm/yyyy | - | - -## POLREF Genie Scripts ## -Similarly, Document information about POLREF SECI Genie scripts here. From c904f0eae3cf24f3d6cd2b8a2a9d6fcf6a2b7013 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:49:18 +0100 Subject: [PATCH 14/60] Update SXD-Instrument-Details.md @LowriJenkins confirms --- doc/processes/instrument_details/SXD-Instrument-Details.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/processes/instrument_details/SXD-Instrument-Details.md b/doc/processes/instrument_details/SXD-Instrument-Details.md index 9aa753344..60fc04e36 100644 --- a/doc/processes/instrument_details/SXD-Instrument-Details.md +++ b/doc/processes/instrument_details/SXD-Instrument-Details.md @@ -65,7 +65,7 @@ See also tickets [#1826](https://github.com/ISISComputingGroup/IBEX/issues/1826) {#sxd_note-kammrath-and-weiss} ##### Note: Kammrath and Weiss ##### -1. The Kammrath-Weiss tensile stress rig is controlled from a dedicated laptop running the manufacturer's software. SECI communicates with the PC to send/read values to/from the manufacturer's software. +1. The Kammrath-Weiss tensile stress rig is controlled from a dedicated laptop running the manufacturer's software. IBEX communicates with the PC to send/read values to/from the manufacturer's software using `LVREMOTE`. 1. [Kammrath and Weiss](https://www.kammrath-weiss.com/en/tensile-compression-modules/).
* See also ticket [#2681](https://github.com/ISISComputingGroup/IBEX/issues/2681) From bc80eb795fcc591a87889d70ac229bfe22b5a2cf Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:53:19 +0100 Subject: [PATCH 15/60] Update GEM-Beamscraper-Jaws.md --- .../jaws/GEM-Beamscraper-Jaws.md | 39 +------------------ 1 file changed, 1 insertion(+), 38 deletions(-) diff --git a/doc/specific_iocs/motor_extensions/jaws/GEM-Beamscraper-Jaws.md b/doc/specific_iocs/motor_extensions/jaws/GEM-Beamscraper-Jaws.md index 3c47824ea..f418cd386 100644 --- a/doc/specific_iocs/motor_extensions/jaws/GEM-Beamscraper-Jaws.md +++ b/doc/specific_iocs/motor_extensions/jaws/GEM-Beamscraper-Jaws.md @@ -2,43 +2,6 @@ The GEM "Beamscraper" jaw set is unique to GEM. The four blades move independently and are all driven by a LinMot. Some calibration is required between the demanded position and the steps sent to the controller. For North/South this calibration is linear, for East/West it is quadratic. -## Control under SECI - -LinMot motor resolution: 0.01953125 mm/steps (Mistakenly labelled as steps/mm in the VI) - -Jaw | Offset | Read Calibration Curve | Write Calibration Curve ----- | -------| ------ | ---------- -North | 2710 | `x + 0.025*x` | `x - 0.025*x` -South | 1530 | `x + 0.025*x` | `x - 0.025*x` -East | 2200 | `(-0.12038 + 0.06452 * x + 0.02998 * x**2)/0.9` | `(x - 0.1*x)` , `((-0.06452 + sqrt(0.06452**2 + 4*0.02998*(0.12038 + x))) / (2*0.02998))` -West | 2200 | `(-0.12038 + 0.06452 * x + 0.02998 * x**2)/0.9` | `(x - 0.1*x)` , `((-0.06452 + sqrt(0.06452**2 + 4*0.02998*(0.12038 + x))) / (2*0.02998))` - -Where there are two equations the first equation calculates the x used in the second equation where there are two. - -The motor resolution/offset values are used as below: - -Read/Write | Axis | Equation ----------- | ---- | -------- -Write | South | `OFF + (x / MRES)` -Write | N/E/W | `OFF - (x / MRES)` -Read | South | `(x - OFF) * MRES)` -Read | N/E/W | `(OFF - x) * MRES)` - -Where x has been calculated from the calibration curves above. - -The setpoints are all set to 5 when home is pressed. There is some tolerance checking, tolerance is set to 1.00, and is based on the presented value. - -The limits for the values that the user can set are: - -Axis | Min | Max ---- | --- | --- -H Gap | 0.2 | 25 -V Gap | 0.2 | 40 -North | 0.1 | 20 -South | 0.1 | 20 -West | 0.1 | 12.5 -East | 0.1 | 12.5 - ## Control under IBEX The calibration curves under IBEX have been simplified to: @@ -61,4 +24,4 @@ Jaw | New Offset | New Motor Resolution South | `-SECI_OFF * SECI_MRES` | `SECI_MRES` N/E/W | `SECI_OFF * SECI_MRES` | `-SECI_MRES` -Tolerance and limits have been included in IBEX, the homing has not. \ No newline at end of file +Tolerance and limits have been included in IBEX, the homing has not. From 6e7b85b1ea1d595fd5f8506bdb5833288b0ebf8f Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:58:46 +0100 Subject: [PATCH 16/60] Update Calibration-Files.md --- doc/system_components/configurations/Calibration-Files.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/doc/system_components/configurations/Calibration-Files.md b/doc/system_components/configurations/Calibration-Files.md index 3baf10297..c1dee074d 100644 --- a/doc/system_components/configurations/Calibration-Files.md +++ b/doc/system_components/configurations/Calibration-Files.md @@ -62,12 +62,6 @@ You will then need to push these files to the common config area and update the If the common calibration file change and they need updating on all instruments, then you can run the [calibration update script which can be found in ibex utils](https://github.com/ISISComputingGroup/ibex_utils/blob/master/installation_and_upgrade/calibration_files_updater.py) -To update those instruments still on SECI use the folder `...\CompGroup\Calibration Files`: - -1. Update files in `Calibration Files\Temperature Sensors\Files` -1. Run the deployment script in `Calibration Files\Temperature Sensors\Deployment Scripts`. - - There should be 1 error per instrument for deleting the network path - ## Calibration file format 1. First lines start with `# ISIS calibration`. From 50650e925055271ddf817228f12a0319adf7e323 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:06:01 +0100 Subject: [PATCH 17/60] Update DAE-Trouble-Shooting.md --- doc/specific_iocs/dae/DAE-Trouble-Shooting.md | 17 ++++++----------- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/doc/specific_iocs/dae/DAE-Trouble-Shooting.md b/doc/specific_iocs/dae/DAE-Trouble-Shooting.md index aa3206456..e0af0f37b 100644 --- a/doc/specific_iocs/dae/DAE-Trouble-Shooting.md +++ b/doc/specific_iocs/dae/DAE-Trouble-Shooting.md @@ -54,9 +54,6 @@ Qxtrm_channel::RDMARead failed rdma2 address 0x40010 nbytes 4(Quixtream: The tim In general if you see an error like this or starting with `NIVISA` you should restart the DAE, then [contact electronics](https://stfc365.sharepoint.com/sites/ISISExperimentControls/ICP%20Discussions/Contact%20details%20for%20other%20groups.docx). -### No log files are produced in `c:\data` even though blocks are set to log. -The reason may be because the isisicp program that writes the datafile hasn't been configured to read values from MySQL for EPICS - the old SECI program used a different route. This is a one off change needed for SECI -> IBEX migration. In `C:\LabVIEW Modules\dae\isisicp.properties` set `isisicp.epicsdb.use = true` to enable this. You will need to restart the `isisicp` process for this to take effect. To do this, just end the `isisicp` process in task manager. - ### DAE doesn't seem to be connected/I want to run without a DAE connected The DAE can be set to run in simulation mode, this must be unset before data will be collected. To set the mode run `g.set_dae_simulation_mode(True)` or `g.set_dae_simulation_mode(False)` to unset. @@ -64,7 +61,7 @@ To change the simulation mode manually, in `icp_config.xml` change the simulate ### Log file for LabVIEW modules DAE -Both SECI and IBEX use the same underlying `isisicp` program (located in `labview modules\dae`) that writes to `C:\Data\Export only\logs\icp\log\icp-log`. There is an [example DAE log in this wiki](DAE-Normal-Log). This is a good place to locate DAE specific issues, not all of the details in this log appear in the ISISDAE IOC log. +IBEX uses `isisicp` program (located in `labview modules\dae`) that writes to `C:\Data\Export only\logs\icp\log\icp-log`. There is an [example DAE log in this wiki](DAE-Normal-Log). This is a good place to locate DAE specific issues, not all of the details in this log appear in the ISISDAE IOC log. ### Error pop up: `*** ICP failed to start - your DAE may be switched OFF or is missing cards ***` The DAE unit may be switched off. This is particularly likely during shut down. Change the DAE into simulation mode as described above. @@ -145,7 +142,7 @@ From an issue in Ticket https://github.com/ISISComputingGroup/IBEX/issues/3099 - [2018-04-09 15:26:49] : Exception occurred. ``` -The issue here is that the default simulated DAE has 2 detector cards in it, but the real DAE has more cards. To fix edit `isisicp.properties` in LabVIEW modules to create more cards. Note this is not an ibex issue - it will also affect DAE simulation mode under SECI. The number of cards on each crate is given by the maximum missing card for the crate (see log), more crates can be added as well as cards. An example from wish with 3 crates, 10, 10 and 12 card per crate is: +The issue here is that the default simulated DAE has 2 detector cards in it, but the real DAE has more cards. To fix edit `isisicp.properties` in LabVIEW modules to create more cards. The number of cards on each crate is given by the maximum missing card for the crate (see log), more crates can be added as well as cards. An example from wish with 3 crates, 10, 10 and 12 card per crate is: ``` isisicp.simulation.detcards.crate0.number = 10 @@ -204,9 +201,9 @@ One cause would be the IOC is trying to call a function in the ISISICP that it c DAE3 is new ethernet based acquisition electronics on ZOOM and MARI, it used `ISISICP` and looks like DAE2 for most purposes. If everything remains in processing, it may be that the `arp` network entries did not get created - these should be done as a system time boot task. Do `arp -a` and see if there is an entry for 192.168.1.101 etc. If not, run `set_dae3_arp.bat` in `c:\labview modules\dae` as as administrator -Note that DAE3 does not ping, so the only way to know if it is there is by running `qxtalk` or the `isisicp` (via ibex or seci) +Note that DAE3 does not ping, so the only way to know if it is there is by running `qxtalk` or the `isisicp` (via ibex) -If IBEX/SECI has either been in simulation mode or not running for a long time previously, then some of the tcp ports used by dae3 may have been grabbed by the operating system as described in `Real DAE complains about missing cards (but was previously working)` above on this page. You will see errors like +If IBEX has either been in simulation mode or not running for a long time previously, then some of the tcp ports used by dae3 may have been grabbed by the operating system as described in `Real DAE complains about missing cards (but was previously working)` above on this page. You will see errors like ``` Quixtream Error: Failed to bind the socket to the local port." ``` @@ -455,12 +452,12 @@ you probably need to follow https://knowledge.ni.com/KnowledgeArticleDetails?id= If you need to recover a system that has filled up its `c:\data` area due to a long event mode run with e.g. noisy detectors then you can use the following. This assumes the scientists do not need the data, you can move the files off instrument but recovery is hard and may not be possible. * log onto NDX computer -* Run `stop_ibex_server` or `kill seci` as appropriate +* Run `stop_ibex_server` * open `c:\data` in windows explorer and sort files by name * look for a very large `eventsYYYYY.tmp` file, make a note of the `YYYYY` number and then select and `shift+delete` this file (you do not want to move it to recycle bin - make sure the prompt says "permanently delete this file" and not "delete this file") * Also now shift+delete `current.run`, `current.runYYYYY`, `data.run`, `data.runYYYYY` * open `c:\data\events` and shift+delete the folder `run_YYYYY` -* start ibex or seci again +* start ibex again Hopefully there is either only one `eventsYYYYY.tmp` file, or the most recent one (largest YYYYY number) is also the largest in size. If there are several files making a decision may need a bit more thought. It is possible that a very large run was done earlier which nearly filled up the disk, then a new one was started that pushed it over the limit while the previous one was ending in the background. Check with the scientists if it is ok to delete this earlier bigger run. You should always delete all YYYYY files corresponding to the run that was in progress when the system filled up, but you may also need to handle an earlier YYYYY number set of files to free up enough disk space. @@ -485,8 +482,6 @@ Check to see if you have any errors similar to the following: If so, you haven't registered your `isisicp.exe` program with the registry. Follow the steps to [Configure DAE for simulation mode on developer's computer](#first_time_install_configure_dae) -If you have done this it may be that the isisicp.exe program is too old. Older versions do not contain a function which is needed by IBEX. Check the file `svn_revision.txt` in `c:\labview modules\dae` - it needs to be 1633 or higher. If it needs updating, ask a SECI specialist to update the program. - ## Multiple VXI devices If you have multiple DAE2 VME crates then you will legitimately have multiple VXI devices in NI MAX. However there are cases when you can get two devices showing in MAX but have only one device in reality. This is usually because of either: From 0c09dcd603765207483c49f1ab5753571c047de9 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:11:04 +0100 Subject: [PATCH 18/60] Update spelling_wordlist.txt --- doc/spelling_wordlist.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/spelling_wordlist.txt b/doc/spelling_wordlist.txt index 8f8e07c12..6e5b9a0c5 100644 --- a/doc/spelling_wordlist.txt +++ b/doc/spelling_wordlist.txt @@ -228,6 +228,7 @@ Ecorr efxclipse EGU Eilidh +Elektronika enablement endian ENGINX From 4d9890e31744c82daf2823d91395cb681fc45d70 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:12:54 +0100 Subject: [PATCH 19/60] Update Deployment-on-an-Instrument-Control-PC.md --- .../deploy/Deployment-on-an-Instrument-Control-PC.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc/deployment/deploy/Deployment-on-an-Instrument-Control-PC.md b/doc/deployment/deploy/Deployment-on-an-Instrument-Control-PC.md index cbf534140..358b61351 100644 --- a/doc/deployment/deploy/Deployment-on-an-Instrument-Control-PC.md +++ b/doc/deployment/deploy/Deployment-on-an-Instrument-Control-PC.md @@ -26,7 +26,6 @@ If you do not have either a D: or O: network drive, then you will need to specif - If you want to install a non-default release you need to set the `SUFFIX` variable in the batch file. For example with `x.y.z` being the current release and `hotfix` being the suffix, it will look for the folder `Releases/x.y.z-hotfix` - Apart from the below points, just follow instructions - most options should be answered `Y` (yes) to, but if you are unsure on a particular machine ask on technical. - Be warned the upgrade runs in 3 steps and so will claim to have finished the upgrade 3 times - - Do not remove any SECI icons from the task list if this is not the first time install 1. Compare screenshots taken earlier to current state @@ -65,7 +64,7 @@ installed on NDX computers. ## Install IBEX for the first time :::{note} -This is unlikely to happen now we've migrated most instruments, and SECI instruments should have a copy of IBEX at the least. +This is unlikely to happen now we've migrated all instruments from SECI. :::
Click to expand From 4ea54412c48e0001a5f1cbc5cca702bd0a1b0b89 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:23:47 +0100 Subject: [PATCH 20/60] Update Experimental-Runs.md --- doc/specific_iocs/dae/Experimental-Runs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/specific_iocs/dae/Experimental-Runs.md b/doc/specific_iocs/dae/Experimental-Runs.md index 07194dbc7..dad6c91be 100644 --- a/doc/specific_iocs/dae/Experimental-Runs.md +++ b/doc/specific_iocs/dae/Experimental-Runs.md @@ -36,7 +36,7 @@ This is from a problem see on IRIS. ## Experiment stuck in `Waiting` state after beginning a run -This issue was encountered on Iris during the transition between Seci and Ibex. SECI was in a waiting state prior to shutdown, then IBEX was left in this waiting state. Usually SECI run control is transient i.e. set by Open GENIE and cleared on a SECI restart, so just restarting SECI would usually clear it. The is now a new PV that you can write to from IBEX to force a resync of run control +There is now a new PV that you can write to from IBEX to force a resync of run control caput %MYPVPREFIX%CS:RC:SYNC:SP 1 @@ -51,4 +51,4 @@ If this has failed: To archive files end a run. Should you have runs ending and read only files, then check on the archive in `INST\instrument\logs\cycle_nn_n`, the log files there will provide some extra information. If the file `exception_copy.log` doesn't exist, or hasn't been updated for a long time, then the script above isn't running the code to clean up old files, or it has hung. -* Problems with the end of run script can be diagnosed by looking at the `post_command_.log'` file in the ICP logs area on the instrument. The ICP log files (in the same area) may also be instructive to check for other issues - for example, if the files are not being set read-only. \ No newline at end of file +* Problems with the end of run script can be diagnosed by looking at the `post_command_.log'` file in the ICP logs area on the instrument. The ICP log files (in the same area) may also be instructive to check for other issues - for example, if the files are not being set read-only. From 9b59552069d14b0999d780f6ad2070dc79ecbc1c Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:29:43 +0100 Subject: [PATCH 21/60] Delete doc/processes/meetings_with_scientists/Demo-notes.md This page deals with demos of IBEX to SECI familiar scientists. Whilst we still do first time demos of IBEX, these are covered by our IBEX training course and so we do not need to duplicate that material by updating this page. --- .../meetings_with_scientists/Demo-notes.md | 184 ------------------ 1 file changed, 184 deletions(-) delete mode 100644 doc/processes/meetings_with_scientists/Demo-notes.md diff --git a/doc/processes/meetings_with_scientists/Demo-notes.md b/doc/processes/meetings_with_scientists/Demo-notes.md deleted file mode 100644 index 123afa216..000000000 --- a/doc/processes/meetings_with_scientists/Demo-notes.md +++ /dev/null @@ -1,184 +0,0 @@ -# First-time demos of IBEX to scientists - -```{note} -All instruments now have IBEX, so this process is unlikely to be needed for existing instruments. - -For existing instruments, use [regular demo documentation](Regular-Demos-of-IBEX-to-Scientists) -``` - -Anyone doing a demo of IBEX should use these notes, so that - -* You are familiar with the scope of the demo (i.e. what should be covered) -* You review it and rehearse it in advance (i.e. you are clear about what you will present) -* You don’t forget to mention any important aspects of the system - * keep a copy of these notes in front of you as you do the demo -* You don’t forget where key files (e.g. demo scripts) are located, etc. -* Instrument scientists get a consistent picture irrespective of where & when the demo is performed. -* If a question takes you “off piste”, you can easily find your way back to the main thread of the demo. -* We can enhance the script in the light of experience (e.g. better answers to questions) - * jot down any important points arising from any demos that you do and add them back into this document for the benefit of others. - -## Overview - -Provide the audience with a quick tour of the IBEX GUI - -* Explain that the GUI is a client application - * It displays data that is provided to it by server applications - * The server applications are called IOCs (Input-Output Controllers) - * IOCs are similar, in some respects, to LabVIEW VIs - * The IOCs run on the control PC (i.e. the NDX... machine) - * The GUI can run on the control PC. It can also run on other client PCs located elsewhere on the network. - -* Highlight the main areas of the GUI - * Dashboard - very similar to the SECI dashboard - * Blocks & Groups - again, very similar to SECI - * System Views - a number of different views of the system. Some views are similar to SECI; others are new. - * Clicking on the list of View buttons (on the left-hand side of the GUI window) changes the view - -* Highlight the IBEX menu - * IBEX - use to switch instrument, restore the default view or exit IBEX - * Configuration - use to edit configurations, load a new configuration or delete a configuration - * Synoptic - use to edit synoptics, load a new synoptic or delete a synoptic. - * IOC - use to start or stop IOCs - * Run Control - use to view and edit run-control settings - * Help - point out the About Box. User should use it to report the server & client version numbers if they encounter problems. - -## Dashboard - -The dashboard is very similar to the SECI dashboard -* It uses the same colour coding as the SECI dashboard -* It displays the same status messages as the SECI dashboard -* Information about the current experiment comes from the DAE set up (we'll touch on this later) -* Beam status information comes from the beam logger IOC - -## Beam Status - -Describe the Beam Status view -* Clicking on the Beam Status button displays the Beam Status view -* The Beam Status view always appears in the main display area -* The Beam Status view comprises 3 panes - * The main pane, taking up most of the display in the Beam Status graph. It shows the Synchrotron current and the currents to TS1 and TS2. You can toggle the display to show graphs for the last hour or last 24 hours. - * The top right pane shows the ISIS MCR news. It is just a simple scrolling window showing the published MCR news. - * The lower right pane shows beam status details. It consists of 3 sections: one for the Synchrotron, one for TS1 and one for TS2. The sections are collapsible, so you can collapse any section that is of no interest to you. - * Beam status information comes from the beam logger IOC, which replaces the old LabVIEW beam logger VI. - * The beam logger IOC is already serving beam status information to all instruments (not just those running IBEX) - * The beam logger IOC actually runs on the accelerator control system - -## IOC Log View - -Describe the IOC Log view -* The IOC Log system provides a unified way of managing status and information messages from the devices attached to the instrument. -* Copies of status and information messages from the DAE are also routed via the IOC Log system. -* The IOC Log messages are primarily intended for diagnosing problems with attached devices. -* The IOC Log view provides you with a convenient means of viewing those messages - * Demonstrate how messages can be filtered and searched (by date/time, severity, etc.) - * Messages are automatically saved to a log on the control PC - * **N.B.** Messages are held in a log which is quite separate from experimental data - -## DAE View - -Describe the DAE view -* The DAE view allows scientists to set up and control the operation of the DAE. -* The DAE view is very similar to the DAE VI in SECI. -* The DAE view comprises 6 tabs. - * Run Summary - Displays run summary information and any recent log messages. - * Experiment Setup - . - * Run Information - . - * Spectra Plots - . - * Diagnostics - . - * Vetos - . - -* As previously noted, copies of status and information messages from the DAE are also routed via the IOC Log system. - -## Blocks & Groups - -Blocks & groups in the new GUI work in the same way as they do in SECI. -* Blocks and groups are displayed at the top (and centre-right) of the GUI window. -* Blocks & groups are part of your configuration. You define blocks & groups by creating and editing configurations. -* In EPICS, an IOC makes information about the status of a device available by publishing *process variables*. In general, an IOC will use many process variables to fully describe the state of a device. Typically, you won't be interested in all of these - just a sub-set. Show how the GUI allows you to select which process variables that are of interest and to define these as *blocks*. -* Once a PV has been defined as a block, show how it can be assigned to a group. -* Make it clear that blocks are automatically logged (just as they are in SECI). Note also that the logging of blocks is independent of the message log. -* Show how blocks can be viewed in the LogPlotter - so the user can always view the history of a block. -* Show how a set of defined blocks & groups can be saved as a configuration. -* Show how a previously saved configuration can be re-loaded. -* Explain what is saved in a configuration: - * groups, blocks, links to settings files, synoptic view -* Demonstrate sub-configurations -* Demonstrate Management Mode. - -## Scripting - -In the new GUI, scripting is built-in. You don't need a separate windows to run a script (although some users prefer to have a separate window). -* Click on the Scripting button to display the Scripting view - * point out the scripting area -* The scripting language is Python -* Python brings a number of advantages over Genie - * *what are they? - we need to enumerate them* -* Python equivalents of the most common Genie commands (e.g. cset) have been created - * demonstrate that, for example, ``cset arg`` becomes ``cset(arg)`` - * it is not difficult to convert a Genie script into a Python script - * display a *before (Genie)* and *after (Python)* script. Emphasize how similar they are. -* Any block (or PV) can be used in a Python script -* Demonstrate running a Python script - * use a script that you prepared earlier: **don't wing it!** - * point out use of Genie-like commands where possible - * show how to pull in data from blocks (or PVs) - * read data from previously saved file if beam is off - * manipulate data in Python - show off what Python can do - * display data in a graph - * copy/paste a graph into MS Word (or similar) - -## Device Support - -EPICS provides support for a wide range of devices. For many devices we can simply download the appropriate driver from the EPICS web-site. Because the source code for these drivers is available, we can, if necessary, adapt an EPICS driver for our specific purposes. -* In EPICS, drivers & IOCs combine to provide control of devices attached an instrument. In addition, we use CSS to create OPIs (graphical user interfaces) for devices. In combination, drivers, IOCs and OPIs provide the functionality of a LabVIEW VI. -* We currently have EPICS drivers for Galil motor controllers, Eurotherms, Julabo water baths, CAEN, Kepco & Thurlby power supplies. We also have controllers for PLCs, jaws-sets, sample changers, rotation stages and goniometers. -* EPICS drivers and controllers for additional devices can be developed as required. -* Adopting EPICS does **not** mean throwing away existing LabVIEW drivers. - * We have created a communication interface, called lvDCOM, to enable EPICS to communicate with LabVIEW VIs. - * Where a device has a complex or specially customised LabVIEW driver, lvDCOM allows us to continue using the LabVIEW VI. Any data that the VI makes available to EPICS can be defined as a block and used in the normal manner. -* Demonstrate an existing EPICS IOC/OPI: for example the Eurotherm IOC & OPI – demonstrate simple operation, ramping, calibration, etc. -* Demonstrate interaction between EPICS and a VI: for example -* Demonstrate starting & stopping of IOCs. Show how startup messages, etc. are captured in the message log. -* Discuss settings files and their relation to IOCs and VIs. - -## Synoptic View or Instrument Overview - -The synoptic view provides an interactive overview of an instrument. -* The synoptic view shows all the devices (or a defined sub-set of devices) attached to an instrument. -* The synoptic view is configurable (via the Synoptic Editor). Show how you can create different views for different instrument setups. -* Incident neutrons are shown coming from the left. -* Each device is represented by its own icon and a small number of key parameters. -* Show how you can drill-down by clicking on each device icon to get more detail. - * Clicking on a device icon displays the device UI, which will display additional controls and information that cannot easily be included on the top-level synoptic display - * Device UIs are sometimes referred to as OPIs (OPIs are analogous to LabVIEW VI screens) - * Demonstrate how some devices (e.g. motors) allow you to drill-down to deeper levels (beware: some of the deeper level screens can get very complex) - * Show how the Up, Next and Prev buttons are used to navigate around the various layers of the synoptic view. - -## Motors View - -The motors view provides a convenient way to view the status of all the motors used on an instrument. -* The motors view is very similar to the *Table of Motors* used in SECI by some instruments. -* Each row corresponds to a single Galil motor controller. The number of rows displayed will depend on the number of Galil controllers attached to the instrument. -* The columns list the Galil controller ports (up to 8 ports per Galil) -* Each entry in the table represents a single Galil controller port (one (or zero) motors per port) - * Each entry identifies the motor by its unique ID number - * Each entry displays the current value of the motor's position and its current set-point. - * A grey entry represents an unused port (no motor is attached, or motor is switched off) - * A pink entry represents a port in use: motor is attached, but stationary - * A green entry represents an active port: motor is attached and is moving -* Show how you can drill-down by clicking on each motor entry to get more detail. - -## EPICS & Extensibility - -EPICS is a framework for creating *distributed* control systems. The ability to have more than one PC controlling different parts of an instrument is inherent to EPICS. -* The default position will continue to be that we will use a single PC to control all of the devices attached an instrument. -* However, there are some situations where it is advantageous to have specialist items of equipment controlled by a separate PC. For example - * the interchangeable cameras on IMAT - * the LARMOR spin-echo system \ No newline at end of file From 5b800be56bd56d3ffe2c9cc5c62f63e5d371ab4e Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:50:01 +0100 Subject: [PATCH 22/60] Update ISISICP---enabling-incremental-event-file-creation.md --- .../dae/ISISICP---enabling-incremental-event-file-creation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/specific_iocs/dae/ISISICP---enabling-incremental-event-file-creation.md b/doc/specific_iocs/dae/ISISICP---enabling-incremental-event-file-creation.md index 3087022c9..29f693e7d 100644 --- a/doc/specific_iocs/dae/ISISICP---enabling-incremental-event-file-creation.md +++ b/doc/specific_iocs/dae/ISISICP---enabling-incremental-event-file-creation.md @@ -7,6 +7,6 @@ To enable incremental mode edit `isisicp.properties` in `C:\labview modules\dae` isisicp.incrementaleventnexus = true isisicp.kafkastream = true ``` -The changes will not take effect until you restart the ISISICP program - make sure you are in SETUP and any runs have finished saving, then kill the `ISISICP` process using task manager (you can restart seci/ibex if you prefer, but that is not necessary) +The changes will not take effect until you restart the ISISICP program - make sure you are in SETUP and any runs have finished saving, then kill the `ISISICP` process using task manager (you can restart ibex if you prefer, but that is not necessary) After this is enabled, you can also run Mantid on any computer and use the Kafka live listener to view and process events live during the run. From 9932192fb261b97c2e2acec20c2cc61db3de55ea Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:55:00 +0100 Subject: [PATCH 23/60] Update Julabo.md --- doc/specific_iocs/temp_controllers/Julabo.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/specific_iocs/temp_controllers/Julabo.md b/doc/specific_iocs/temp_controllers/Julabo.md index 793b82d28..7e4269d25 100644 --- a/doc/specific_iocs/temp_controllers/Julabo.md +++ b/doc/specific_iocs/temp_controllers/Julabo.md @@ -1,6 +1,6 @@ # Julabo -Julabo is a temperature control unit. There are many different versions. The commands for each model are slightly different. When migrating an instrument, care must be taken to check exactly which command set it is using under SECI and to configure an equivalent command set in IBEX. A spreadsheet of LabVIEW settings against command set is in [this spreadsheet](julabo_commands.xlsx). +Julabo is a temperature control unit. There are many different versions. The commands for each model are slightly different. A spreadsheet of previous LabVIEW settings against command set is in [this spreadsheet](julabo_commands.xlsx). The IOC copes with these variations in commands by making 4 commands configurable via macros: - `READ_POWER_CMD_NUMBER` configures the command used to read power. This macro should be the 2-digit number at the end of the read power command in the spreadsheet above (for the relevant model of Julabo). @@ -32,4 +32,4 @@ null modem: depends on Julabo If none of the settings above allow you to connect ## Troubleshooting -The Julabo hardware supports having several different setpoints and can control on any of them, ibex always uses setpoint 1. If the Julabo hardware is set to e.g. use setpoint 2 then ibex will think all is fine and send/read the setpoint 1 ok, but the Julabo hardware will how a different setpoint value (setpoint 2) on its screen. A technician will need to go into the configuration menu on the device and change it to use setpoint 1 \ No newline at end of file +The Julabo hardware supports having several different setpoints and can control on any of them, ibex always uses setpoint 1. If the Julabo hardware is set to e.g. use setpoint 2 then ibex will think all is fine and send/read the setpoint 1 ok, but the Julabo hardware will how a different setpoint value (setpoint 2) on its screen. A technician will need to go into the configuration menu on the device and change it to use setpoint 1 From f3f63205835b5d033834a6106dbd89b3b20511d0 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:56:16 +0100 Subject: [PATCH 24/60] Delete doc/system_components/labview/LabVIEW-memory-warning-in-nagios.md Intro makes clear this is only relevant under SECI --- .../LabVIEW-memory-warning-in-nagios.md | 23 ------------------- 1 file changed, 23 deletions(-) delete mode 100644 doc/system_components/labview/LabVIEW-memory-warning-in-nagios.md diff --git a/doc/system_components/labview/LabVIEW-memory-warning-in-nagios.md b/doc/system_components/labview/LabVIEW-memory-warning-in-nagios.md deleted file mode 100644 index af3601b79..000000000 --- a/doc/system_components/labview/LabVIEW-memory-warning-in-nagios.md +++ /dev/null @@ -1,23 +0,0 @@ -# LabVIEW memory leak - -If nagios is reporting a critical memory usage for LabVIEW (which will only be on a SECI instrument) then you need to do the following: - -first check to see if the nagios service has been acknowledged (has a tick next to it), it it has then these steps have already been followed and you need do nothing - -compose an email with the from address set to "ISIS Experiment Controls" and the following content with `yyyy` replaced by the instrument name e.g. `OFFSPEC` -``` -subject: SECI/LabVIEW memory usage on NDXyyyy computer - -Hi, - -The SECI/LabVIEW memory usage on the NDXyyyy instrument computer is getting very high and the process may crash in the next few days, it would be advisable to restart the SECI control system at the next convenient point - -Regards, - -ISIS Experiment Controls -``` - -Now send this email to the special instrument address alias - -Then acknowledge the service in nagios: click on `LABVIEW memory` for the instrument in the nagios view, then on the right of the next page click on `Acknowledge this service problem` and then give a comment like "emailed scientists" and press `Commit`. If you now return to the nagios service view, you should see a tick mark next to the service name. - From 1cc60d915b8e28dd8bd648434ea2fb5aabab552d Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:57:02 +0100 Subject: [PATCH 25/60] Update POLARIS-Instrument-Details.md --- .../POLARIS-Instrument-Details.md | 26 +++---------------- 1 file changed, 3 insertions(+), 23 deletions(-) diff --git a/doc/processes/instrument_details/POLARIS-Instrument-Details.md b/doc/processes/instrument_details/POLARIS-Instrument-Details.md index c64470b20..7140c0722 100644 --- a/doc/processes/instrument_details/POLARIS-Instrument-Details.md +++ b/doc/processes/instrument_details/POLARIS-Instrument-Details.md @@ -107,26 +107,6 @@ An evacuated furnace cell for measuring resistivity. Controlled by Eurotherms a ##### Note: CS155 Centre Stick ##### Not possible to control this device via software. It connects to the [Spellman](#polaris_noteSpellman) HV-PS. -## POLARIS SECI Configs ## -Document information about POLARIS SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | -----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---------------|----------| - POLARIS Base + Hydrothermal | Chopper, Vacuum, Jaws, Eurotherms Test | 03/02/2017 | - - POLARIS Base + Dilution Fridge | Chopper, Vacuum, Jaws, Oxford - Dilution Fridge | 15/12/2016 | - - POLARIS Base + Sample Changer + Eurotherms_matt | Chopper, Vacuum, Jaws, Eurotherms Test, Sample Changer | 12/12/2016 | - - POLARIS Base + Sample Changer + Eurotherms + Heliox | Chopper, Vacuum, Jaws, Eurotherms Test, Sample Changer, Heliox | 19/09/2016 | - - POLARIS Base | Chopper, Vacuum, Jaws | 30/11/2015 | - - POLARIS Base + Sample Changer + Eurotherms | Chopper, Vacuum, Jaws, Eurotherms Test, Sample Changer | 18/11/2015 | - - POLARIS Base + Sample Changer + Eurotherms + ITC_matt | Chopper, Vacuum, Jaws, Eurotherms Test, Sample Changer | 25/06/2015 | - - POLARIS Base + Eurotherms | Chopper, Vacuum, Jaws, Eurotherms Test | 05/06/2014 | - - POLARIS Base + Keithley (Voltage) + Eurotherms | Chopper, Vacuum, Jaws, Eurotherms Test, Keithley (Voltage) | 02/06/2014 | - - POLARIS Base + Keithley + Eurotherms | Chopper, Vacuum, Jaws, Eurotherms Test, Keithley | 25/03/2013 | - - delete | - | 01/10/2012 | - - POLARIS Base + Sample Changer | Chopper, Vacuum, Jaws, Sample Changer | 14/03/2012 | - - test | - | 10/11/2011 | - - -## POLARIS Genie Scripts ## -Similarly, document information about SECI Genie scripts currently used on POLARIS here. - -## POLARIS Notes ## \ No newline at end of file +s currently used on POLARIS here. + +## POLARIS Notes ## From 3c22b805ac3c059934394fa72800f8de1ed7f9e6 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:58:41 +0100 Subject: [PATCH 26/60] Update PEARL-Instrument-Details.md --- .../instrument_details/PEARL-Instrument-Details.md | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/doc/processes/instrument_details/PEARL-Instrument-Details.md b/doc/processes/instrument_details/PEARL-Instrument-Details.md index 518473813..33e9e6677 100644 --- a/doc/processes/instrument_details/PEARL-Instrument-Details.md +++ b/doc/processes/instrument_details/PEARL-Instrument-Details.md @@ -137,14 +137,3 @@ This is a weird `Servostep` box which contains a Galil 4000 series inside. It lo Compare with similar systems on GEM and POLARIS. There are some inaccessible front end jaws on PEARL controlled by the Galil, these are not used but must be kept open for operation. They are homed to the forward limit and seem to typically be kept about 4/5mm inside that position for running. This should be kept in mind when migrating the Galil. - -## PEARL SECI Configs ## -Document information about PEARL SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -PEARL_place_holder1.conf | - | dd/mm/yyyy | - | -PEARL_place_holder2.conf | - | dd/mm/yyyy | - | - -## PEARL Genie Scripts ## -Similarly, Document information about PEARL SECI Genie scripts here. From d946194af9184c66567e4124f0a68d1733da3f45 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 14:12:49 +0100 Subject: [PATCH 27/60] Update OSIRIS-Instrument-Details.md --- .../instrument_details/OSIRIS-Instrument-Details.md | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/doc/processes/instrument_details/OSIRIS-Instrument-Details.md b/doc/processes/instrument_details/OSIRIS-Instrument-Details.md index 3d7ce9cfe..4f3c985b5 100644 --- a/doc/processes/instrument_details/OSIRIS-Instrument-Details.md +++ b/doc/processes/instrument_details/OSIRIS-Instrument-Details.md @@ -72,15 +72,3 @@ OSIRIS has the following devices under motion control: * single axis, "IN/OUT" device moving between two setpoints. 1. Sample Changer * **N.B.** For the avoidance of doubt: OSIRIS does not currently (September 2018) have a sample changer. There have been discussions about building one but, for the foreseeable future, there is no sample changer. - - -## OSIRIS SECI Configs ## -Over the years, OSIRIS has built up a significant collection of SECI configs. Not all of them are current (some may no longer be used, or used only infrequently). We will need to investigate how to convert them to IBEX configs. The config files are located in the folder `SECI\Configurations\` on the control server and have the extension `.conf`. Sub-configuration files have the extension `.comp` (component). The files with numbers as extensions (`.1`,`.2`,`.3`,etc.) are backups of the configuration and sub-configuration files. The current list of OSIRIS configs is listed on [trac](https://trac.isis.rl.ac.uk/ICP/wiki/OSIRIS). - - -## OSIRIS Genie Scripts ## -Similarly, OSIRIS has built up a significant collection of genie scripts over the years. Again, many scripts are old and may no longer be used regularly. Most runs on OSIRIS are controlled via scripts. There will be a need to convert some of these scripts to genie-python, but probably not all. - -UPDATE (11/01/2016) Franz has explained how the scripts are used: Usually, each time a user arrives to perform an experiment, they would create a new script by modifying an existing one and alter the appropriate parameters. There is NO common set of OSIRIS specific scripts and/or routines that are included in every new script. Therefore a conversion of OSIRIS scripts to Genie-Python couldn't be done en-masse. Although a few examples could be carefully chosen for users to work from. - -The current list of OSIRIS genie scripts is listed on [trac](https://trac.isis.rl.ac.uk/ICP/wiki/OSIRIS). From 681f3eb93154be003db64d44dbfb2d64a42f3d8a Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 14:14:55 +0100 Subject: [PATCH 28/60] Update NIMROD-Instrument-Details.md --- .../NIMROD-Instrument-Details.md | 29 ++----------------- 1 file changed, 3 insertions(+), 26 deletions(-) diff --git a/doc/processes/instrument_details/NIMROD-Instrument-Details.md b/doc/processes/instrument_details/NIMROD-Instrument-Details.md index 2f7b1fa0c..0c5944ad6 100644 --- a/doc/processes/instrument_details/NIMROD-Instrument-Details.md +++ b/doc/processes/instrument_details/NIMROD-Instrument-Details.md @@ -77,8 +77,8 @@ The [MKS PDR2000A](https://www.mksinst.com/f/pdr2000a-2-channel-digital-power-su The [MKS PR4000B](https://www.mksinst.com/f/pr4000b-digital-power-supply) Digital Power Supply and Display module is available with either one or two channels. The single-channel version controls one pressure transducer or one mass flow controller. The two-channel version supports up to two pressure transducers or two mass flow controllers, or one of each. There are [EPICS drivers](http://www.aps.anl.gov/epics/modules/manufacturer.php#MKS%20Instruments) for a variety of MKS devices (although there is a driver for a PR4000B pressure transducer, there does not appear to be one for a PDR2000). -The manual for the MKS PR4000B is here: `\\isis\shares\ISIS_Experiment_Controls\MKS_PR4000B_Controller`.
-The SECI VI for the MKS PDR2000 is here: `C:\LabVIEW Modules\Drivers\MKS PDR2000 Pressure Gauge`. +The manual for the MKS PR4000B is here: `\\isis\shares\ISIS_Experiment_Controls\MKS_PR4000B_Controller`. + **Note:** Please refer to ticket [#3962](https://github.com/ISISComputingGroup/IBEX/issues/3692) when implementing support for the PDR2000 on NIMROD. @@ -86,29 +86,6 @@ The SECI VI for the MKS PDR2000 is here: `C:\LabVIEW Modules\Drivers\MKS PDR2000 NIMROD has the following specialist panels/systems: 1. NIMROD Jaws - calculates jaw settings based on moderator projection. -## NIMROD SECI Configs ## -Document information about NIMROD SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -NIMROD_temp.conf | - | dd/mm/yyyy | - | -NIMROD_SuperStick.conf | - | dd/mm/yyyy | - | -NIMROD_SC.conf | - | dd/mm/yyyy | - | -NIMROD_RB1410637.conf | - | dd/mm/yyyy | - | -NIMROD_RB1410416.conf | - | dd/mm/yyyy | - | -NIMROD_CCR.conf | - | dd/mm/yyyy | - | -NIMROD_Basic.conf | - | dd/mm/yyyy | - | -NiceIceSECI.conf | - | dd/mm/yyyy | - | - -## NIMROD Genie Scripts ## -On NIMROD, normal practice is to adapt an earlier script. There is no library of scripts. Most scripts are similar to those used on SANDALS. It might be useful to create some genie_python scripts to serve as examples. One script that could be converted (to serve as an example) is `fraser10_depwarmup.gcl`. - -Script Name | Notes | Last Accessed | Required | ---------------------------|---------------------------------------------------------|---------------|----------| -`fraser10_depwarmup.gcl` | Convert to use an a template/example for future scripts | dd/mm/yyyy | - | - -The "dry_run" feature used on SANDALS scripts could be handy for NIMROD too. - ## NIMROD Notes ## #### Pumps #### NIMROD tends to use a lot of different pumps (e.g. Oerlikon, Edwards, Pfeiffer). Worth having support for a variety of pumps to make switching between pumps easy. @@ -124,4 +101,4 @@ This has been installed on Galil 4 axis 5 (D) on NIMROD. Motion setpoints have b ![](NIMROD__Oxford_MCP_Camera.jpg) #### Electrochemical Cell Positioner #### -A device is being built to position an electrochemical cell in the beam. This is a single linear axis with continuous positioning. We need not concern ourselves with the cell itself as this will be controlled by the users. \ No newline at end of file +A device is being built to position an electrochemical cell in the beam. This is a single linear axis with continuous positioning. We need not concern ourselves with the cell itself as this will be controlled by the users. From 4ab980b96c2de032fd475bfbe7e94698b7dd374d Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 14:16:06 +0100 Subject: [PATCH 29/60] Update MUSR-Instrument-Details.md --- .../instrument_details/MUSR-Instrument-Details.md | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/doc/processes/instrument_details/MUSR-Instrument-Details.md b/doc/processes/instrument_details/MUSR-Instrument-Details.md index 53462377c..b8de135aa 100644 --- a/doc/processes/instrument_details/MUSR-Instrument-Details.md +++ b/doc/processes/instrument_details/MUSR-Instrument-Details.md @@ -127,17 +127,3 @@ MUSR has the following motion control items: MUSR also has the following system: 1. MUON Script Generator (muongui.exe) - -## MUSR SECI Configs ## -Document information about MUSR SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -EMU_place_holder1.conf | - | dd/mm/yyyy | - | -EMU_place_holder2.conf | - | dd/mm/yyyy | - | - -## MUSR Genie Scripts ## -Similarly, Document information about MUSR SECI Genie scripts here. - -## MUSR configs from EMU -Configurations have been removed that were migrated from SECI + EMU as they are being phased out or have not been in use. Commit `63303d94400cd0270b3c07357a08cbdf5945d8e8` should still contain the configurations before removal. \ No newline at end of file From 2af8504bb0721cb3a566d6515b6b1b77c2eab183 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 14:17:57 +0100 Subject: [PATCH 30/60] Update MERLIN-Instrument-Details.md --- .../instrument_details/MERLIN-Instrument-Details.md | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/doc/processes/instrument_details/MERLIN-Instrument-Details.md b/doc/processes/instrument_details/MERLIN-Instrument-Details.md index c072b9286..1a57d0e3d 100644 --- a/doc/processes/instrument_details/MERLIN-Instrument-Details.md +++ b/doc/processes/instrument_details/MERLIN-Instrument-Details.md @@ -109,14 +109,3 @@ Neocera is used only occasionally. [Neocera LTC-21 Manual](http://www.submm.cal ##### Note: McWhan ##### [McWhan pressure cell](http://www.isis.stfc.ac.uk/sample-environment/high-pressure-and-gas-handling-/clamped-cells/mcwhan-clamped-cell-8653.html). McWhan refers to the design of the cell (not to the manufacturer). Cell cannot be controlled directly from IBEX. It may be possible to report the current pressure via a device such as a Chell pressure transducer. See also [General Clamped Cells](http://www.isis.stfc.ac.uk/sample-environment/high-pressure/clamped-cells/general-clamped-cells/general-clamped-cells14180.html) and [High Pressure Gas Cells](http://www.isis.stfc.ac.uk/sample-environment/sample-containers/high-pressure-gas-cells/high-pressure-gas-cells8936.html). - -## MERLIN SECI Configs ## -MERLIN has a number of SECI configurations, which need to be migrated. - -## MERLIN Genie Scripts ## -The critical OpenGenie scripts, for initialisation and focussing, are in `C:\\OG` (duplicated, more or less, in `C:\\scripts\OG`) - -MERLIN has a number of instrument specific Genie scripts. These need to be migrated to genie_python. - -## MERLIN Notes ## -Add any notes about special items of equipment, setup or conditions on MERLIN that might impact the deployment and configuration of IBEX. From cbc519c92b29a45be12c3f08e66799ebc7688439 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 14:19:17 +0100 Subject: [PATCH 31/60] Update MARI-Instrument-Details.md --- .../instrument_details/MARI-Instrument-Details.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/doc/processes/instrument_details/MARI-Instrument-Details.md b/doc/processes/instrument_details/MARI-Instrument-Details.md index b95961adc..ea7095c24 100644 --- a/doc/processes/instrument_details/MARI-Instrument-Details.md +++ b/doc/processes/instrument_details/MARI-Instrument-Details.md @@ -77,13 +77,5 @@ The temperature control will be handled by a Eurotherm.
[Project Details](https://stfc365.sharepoint.com/sites/ISISProject-1122) and [Project Plan](https://tasks.office.com/stfc365.onmicrosoft.com/en-US/Home/PlanViews/8bdu_4UTBUeZwF_PB8SLIpYAESGr) -## MARI SECI Configs ## -MARI has a number of SECI configurations, which need to be migrated. - -## MARI Genie Scripts ## -Critical OpenGenie scripts for initialisation and focussing. - -MARI has a number of instrument specific Genie scripts. These have now been migrated to genie_python. - ## MARI Notes ## 1. MARI does not currently use a script generator, but there is interest in having one in the future. From a3c20084f29cd3a24f68b5078dd2c22d0eabd2a2 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 14:19:54 +0100 Subject: [PATCH 32/60] Update MAPS-Instrument-Details.md --- .../instrument_details/MAPS-Instrument-Details.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/doc/processes/instrument_details/MAPS-Instrument-Details.md b/doc/processes/instrument_details/MAPS-Instrument-Details.md index e686214d7..4404d4cb9 100644 --- a/doc/processes/instrument_details/MAPS-Instrument-Details.md +++ b/doc/processes/instrument_details/MAPS-Instrument-Details.md @@ -72,13 +72,5 @@ Eurotherms in use on MAPS. Used to control temperature of all top-loading CCRs, ##### Note: Neocera ##### Neocera is used only occasionally. [Neocera LTC-21 Manual](http://www.submm.caltech.edu/~sharc/technical/LTC-21%20manual.pdf) -## MAPS SECI Configs ## -MAPS has a number of SECI configurations, which need to be migrated. - -## MAPS Genie Scripts ## -Critical OpenGenie scripts for initialisation and focussing. - -MAPS has a number of instrument specific Genie scripts. These need to be migrated to genie_python. - ## MAPS Notes ## Add any notes about special items of equipment, setup or conditions on MAPS that might impact the deployment and configuration of IBEX. From f4ab5160be2a5b129e8b3d82c5871cb8e8f162b9 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 14:22:51 +0100 Subject: [PATCH 33/60] Update LOQ-Instrument-Details.md --- .../LOQ-Instrument-Details.md | 38 +------------------ 1 file changed, 1 insertion(+), 37 deletions(-) diff --git a/doc/processes/instrument_details/LOQ-Instrument-Details.md b/doc/processes/instrument_details/LOQ-Instrument-Details.md index 212662578..2649515ca 100644 --- a/doc/processes/instrument_details/LOQ-Instrument-Details.md +++ b/doc/processes/instrument_details/LOQ-Instrument-Details.md @@ -92,7 +92,7 @@ Both the OMEGA™ iBTHX and OMEGA™ PAC devices (see above) have proved unrelia {#loq_note-vacuum-system} ##### Note: Vacuum System ##### 1. There are 2 vacuum gauges on LOQ. Both are TPG300's. One is atop the Galil at the sample position monitoring the collimation, and the other is integrated into the detector tank pumping system. -2. Only the detector tank TPG300 is currently read back in SECI. There are two sensors, one at the pump, and one on the tank. +2. Only the detector tank TPG300 was read back in SECI. There are two sensors, one at the pump, and one on the tank. 3. **It is highly desirable to have the collimation TPG300 integrated into Ibex too.** 4. TPG300 support is implemented via [#216](https://github.com/ISISComputingGroup/IBEX/issues/216) and [#2063](https://github.com/ISISComputingGroup/IBEX/issues/2063) @@ -200,39 +200,3 @@ LOQ has the following devices under motion control: 3. Transmission Monitor (M3) * moves in/out of the beam. -## LOQ SECI Configs ## -Document information about LOQ SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -LOQ_NORMAL_25Hz_Cryostat.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_DurhamRack | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_Flowcell.conf | - | dd/mm/yyyy | see note 1 | -LOQ_NORMAL_25Hz_Furnace.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_Huber_stages.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_Magnet.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_PressuceCell.conf | - | dd/mm/yyyy | N | -LOQ_NORMAL_25Hz_PressureCell.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_Rheometer.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_SampleChanger.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_SampleChanger_eurotherm_controller.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_SampleChanger_eurotherm_controller_2.conf | - | dd/mm/yyyy | ? | -LOQ_NORMAL_25Hz_SampleChanger_NOLIVEVIEW.conf | - | dd/mm/yyyy | see note 2 | -LOQ_NORMAL_25Hz_Shear.conf | - | dd/mm/yyyy | see note 1 | -LOQ_NORMAL_25Hz_StopFlow.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_TJump.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_UnileverCell.conf | - | dd/mm/yyyy | Y | -LOQ_QUIET.conf | - | dd/mm/yyyy | see note 3 | - -##### Note: 1 ##### -Need to establish what devices these relate to! - -##### Note: 2 ##### -This is LOQ_NORMAL_25Hz_SampleChanger.conf without the second time regime. Occasionally used with non-standard detector mapping. - -##### Note: 3 ##### -Configures LOQ for running on internal clock. - -## LOQ Genie Scripts ## -Similarly, Document information about LOQ SECI Genie scripts here. - From 7e4203463b6fab4d9d091d28659e6cc7cf775b6f Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 14:23:52 +0100 Subject: [PATCH 34/60] Update LET-Instrument-Details.md --- .../LET-Instrument-Details.md | 22 ------------------- 1 file changed, 22 deletions(-) diff --git a/doc/processes/instrument_details/LET-Instrument-Details.md b/doc/processes/instrument_details/LET-Instrument-Details.md index d51cd1f1a..ab1cefebe 100644 --- a/doc/processes/instrument_details/LET-Instrument-Details.md +++ b/doc/processes/instrument_details/LET-Instrument-Details.md @@ -99,25 +99,3 @@ LET has the following specialist systems: * LET has two rotation stages; 1. A McLennan rotation stage (same as MERLIN, used with CCRs & Orange Cryostats)) 1. A McLennan-Newport rotation stage (used with the 9T Magnet) - -## LET SECI Configs ## -LET has a number of SECI configurations. Equivalent IBEX configs for the following combinations of equipment are required: - * Eurotherm (for Cryostat or CCR) + rotation stage - * Eurotherm (for Cryostat or CCR) + ORC + rotation stage - * Eurotherm (for Cryostat or CCR) + dilution fridge (Triton) + rotation stage - * Eurotherm (for Cryostat or CCR) + dilution fridge (Triton)+ ORC + rotation stage - * Eurotherm (for Cryostat or CCR) + dilution fridge (Heliox) + rotation stage - * Eurotherm (for Cryostat or CCR) + dilution fridge (Heliox)+ ORC + rotation stage - * 9T Magnet + McLennan-Newport rotation stage - -## LET Genie Scripts ## -LET has a number of instrument specific Genie scripts. The key scripts to be migrated to genie_python are: - -Script| Purpose | Notes | ------------- | ------------- | ------------------------------------------- -`park_choppers`| It parks the choppers, of course | Needed because LET has 4 choppers -`set_ei5` | Sets chopper speed/phase | This is the LET version of `set_ei`. It is **not** the same as `set_ei` used on other excitations instruments. It would be helpful if `set_ei5` could be extended to better support vetoes and wiring tables. Ignore the older versions `set_ei1` - `set_ei4`. -`mono` | | - -On LET user scripts are usually created by modifying an old user script. Create a template genie_python script (based on an old user script) which can be used in future. - From 15a4275a73e253925117a9f853e89983d46e9b48 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 14:25:53 +0100 Subject: [PATCH 35/60] Update 2T-3D-Vector-magnet.md --- doc/specific_iocs/cryogenics/2T-3D-Vector-magnet.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/specific_iocs/cryogenics/2T-3D-Vector-magnet.md b/doc/specific_iocs/cryogenics/2T-3D-Vector-magnet.md index 36e9f3e7a..49e801435 100644 --- a/doc/specific_iocs/cryogenics/2T-3D-Vector-magnet.md +++ b/doc/specific_iocs/cryogenics/2T-3D-Vector-magnet.md @@ -37,7 +37,7 @@ IP address : DHCP reserved and visible on front screen when connected to ISIS ne ### Rotation Stage -Standard unit controlled by a Galil axis on both SECI and IBEX instruments. Details: +Standard unit controlled by a Galil axis. Details: * +- 370 degrees * Motor with encoder @@ -64,4 +64,4 @@ The Lakeshore 336 is an Ethernet device and should therefore be connected to the ### Schematic of system -![Schematic of system](3d_vector_magnet_schematic.png) \ No newline at end of file +![Schematic of system](3d_vector_magnet_schematic.png) From d43962d21193d3cbe32b9054bebf044a726cc536 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 14:30:53 +0100 Subject: [PATCH 36/60] Update ARGUS-Instrument-Details.md --- .../ARGUS-Instrument-Details.md | 32 +------------------ 1 file changed, 1 insertion(+), 31 deletions(-) diff --git a/doc/processes/instrument_details/ARGUS-Instrument-Details.md b/doc/processes/instrument_details/ARGUS-Instrument-Details.md index cf70a3173..9d2ec1da3 100644 --- a/doc/processes/instrument_details/ARGUS-Instrument-Details.md +++ b/doc/processes/instrument_details/ARGUS-Instrument-Details.md @@ -1,12 +1,10 @@ # ARGUS This page collects information that will be useful for the implementation of the IBEX control system on ARGUS. + ## Background & Timeline ## ARGUS is a general purpose muon spectrometer at ISIS, on TS1. The [ARGUS](https://www.isis.stfc.ac.uk/Pages/argus.aspx) web page describes the background to the instrument. -## Control System ## -ARGUS will migrate from the SECI control system to the IBEX control system in MMMMMMMM YYYY. - ## ARGUS Equipment ## The equipment listed below is used on ARGUS. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -112,31 +110,3 @@ Low temperature experiments?[Neocera LTC-21 Manual](http://www.submm.caltech.edu Support for McLennan devices is well established (see [#1099](https://github.com/ISISComputingGroup/IBEX/issues/1099) and [#1100](https://github.com/ISISComputingGroup/IBEX/issues/1100) and subsequent tickets. * muon instruments don't use motors in their sample environment -## ARGUS SECI Configs ## -Document information about ARGUS SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -ARGUS_place_holder1.conf | - | dd/mm/yyyy | - | -ARGUS_place_holder2.conf | - | dd/mm/yyyy | - | - -## ARGUS Genie Scripts ## -Similarly, Document information about ARGUS SECI Genie scripts here. - -## ARGUS Notes ## -ARGUS has the following specialist panels: -1. serial port commands - individual commands via serial port (cf. SDTEST) -1. ARGUS [zero field controller](/specific_iocs/magnets/Zero-field-controller) -1. CHRONUS Danfysik -1. MUON [Zero field controller (magnetselected.vi)](/specific_iocs/magnets/Zero-field-controller) -1. ARGUS Leiden Dilution Fridge -1. ARGUS Danfysik -1. ARGUS [Zero field controller](/specific_iocs/magnets/Zero-field-controller) - -## Obsolete ARGUS Equipment & SECI Configs ## -The equipment listed below is referenced in SECI config files on ARGUS. It is highly likely that the config files are no longer relevant (they are old, dating from 2011 or 2012), therefore, the references are to devices that are obsolete or simply not used on ARGUS. - -Manufacturer | Model | Type | Connection | Driver | Notes | ------------- | ------------- | ------------- | ------------- | ------------- | ------------------------------------------- -GALIL | [DMC2280](http://www.galilmc.com/products/dmc-22x0.php) | Motion Controller | Ethernet | [EPICS](http://www.aps.anl.gov/epics/modules/manufacturer.php#Galil%20Motion%20Control) | | -McLennan | PM600 | Motion Controller | RS-232 | [EPICS](http://www.aps.anl.gov/epics/modules/manufacturer.php#McLennan%20Servo%20Supplies) | [see McLennan note](#argus_note-mclennan) From c66428fbdd4905e07959e43d14c188ee6dc830bf Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 14:34:15 +0100 Subject: [PATCH 37/60] Update Triton.md --- doc/specific_iocs/cryogenics/Triton.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/specific_iocs/cryogenics/Triton.md b/doc/specific_iocs/cryogenics/Triton.md index 863d017ad..520453861 100644 --- a/doc/specific_iocs/cryogenics/Triton.md +++ b/doc/specific_iocs/cryogenics/Triton.md @@ -2,7 +2,7 @@ ## Naming -Technically, "Triton" refers to the gas handling apparatus. This is what IBEX and SECI talk to. When setting up a triton, scientists may refer to it as a "Kelvinox". This is the technical name for the dilution insert, which is controlled by the triton gas handling apparatus. +Technically, "Triton" refers to the gas handling apparatus. This is what IBEX talks to. When setting up a triton, scientists may refer to it as a "Kelvinox". This is the technical name for the dilution insert, which is controlled by the triton gas handling apparatus. To avoid confusion: all dilution fridges currently in use at ISIS are controlled by Triton gas handling systems, with one exception: the ICE fridge used on the muon beamlines. From a26b1bb5c3068e124be67a6122324e2987d7bf2d Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 16:44:55 +0100 Subject: [PATCH 38/60] Remove SECI from instrument details pages --- .../ARGUS-Instrument-Details.md | 32 +------------ .../CHIPIR-Instrument-Details.md | 5 --- .../CRISP-Instrument-Details.md | 17 ++----- .../EMMA-Instrument-Details.md | 15 +------ .../EMU-Instrument-Details.md | 12 ----- .../ENGIN-X-Instrument-Details.md | 10 +---- .../GEM-Instrument-Details.md | 45 ------------------- .../HIFI-Instrument-Details.md | 21 --------- .../HRPD-Instrument-Details.md | 26 +---------- .../INES-Instrument-Details.md | 34 +------------- .../INTER-Instrument-Details.md | 33 +++----------- .../IRIS-Instrument-Details.md | 12 ----- .../LET-Instrument-Details.md | 22 --------- .../LOQ-Instrument-Details.md | 38 +--------------- .../MAPS-Instrument-Details.md | 8 ---- .../MARI-Instrument-Details.md | 8 ---- .../MERLIN-Instrument-Details.md | 11 ----- .../MUON-Front-End-Instrument-Details.md | 5 +-- .../MUSR-Instrument-Details.md | 14 ------ .../NIMROD-Instrument-Details.md | 29 ++---------- .../OFFSPEC-Instrument-Details.md | 14 ------ .../OSIRIS-Instrument-Details.md | 12 ----- .../PEARL-Instrument-Details.md | 11 ----- .../POLARIS-Instrument-Details.md | 26 ++--------- .../POLREF-Instrument-Details.md | 23 ++-------- .../SANDALS-Instrument-Details.md | 13 +----- .../SANS2D-Instrument-Details.md | 21 ++------- .../SURF-Instrument-Details.md | 20 +-------- .../SXD-Instrument-Details.md | 13 +----- .../TOSCA-Instrument-Details.md | 13 ------ .../VESUVIO-Instrument-Details.md | 41 ----------------- .../WISH-Instrument-Details.md | 15 ------- .../ZOOM-Instrument-Details.md | 8 +--- 33 files changed, 36 insertions(+), 591 deletions(-) diff --git a/doc/processes/instrument_details/ARGUS-Instrument-Details.md b/doc/processes/instrument_details/ARGUS-Instrument-Details.md index cf70a3173..9d2ec1da3 100644 --- a/doc/processes/instrument_details/ARGUS-Instrument-Details.md +++ b/doc/processes/instrument_details/ARGUS-Instrument-Details.md @@ -1,12 +1,10 @@ # ARGUS This page collects information that will be useful for the implementation of the IBEX control system on ARGUS. + ## Background & Timeline ## ARGUS is a general purpose muon spectrometer at ISIS, on TS1. The [ARGUS](https://www.isis.stfc.ac.uk/Pages/argus.aspx) web page describes the background to the instrument. -## Control System ## -ARGUS will migrate from the SECI control system to the IBEX control system in MMMMMMMM YYYY. - ## ARGUS Equipment ## The equipment listed below is used on ARGUS. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -112,31 +110,3 @@ Low temperature experiments?[Neocera LTC-21 Manual](http://www.submm.caltech.edu Support for McLennan devices is well established (see [#1099](https://github.com/ISISComputingGroup/IBEX/issues/1099) and [#1100](https://github.com/ISISComputingGroup/IBEX/issues/1100) and subsequent tickets. * muon instruments don't use motors in their sample environment -## ARGUS SECI Configs ## -Document information about ARGUS SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -ARGUS_place_holder1.conf | - | dd/mm/yyyy | - | -ARGUS_place_holder2.conf | - | dd/mm/yyyy | - | - -## ARGUS Genie Scripts ## -Similarly, Document information about ARGUS SECI Genie scripts here. - -## ARGUS Notes ## -ARGUS has the following specialist panels: -1. serial port commands - individual commands via serial port (cf. SDTEST) -1. ARGUS [zero field controller](/specific_iocs/magnets/Zero-field-controller) -1. CHRONUS Danfysik -1. MUON [Zero field controller (magnetselected.vi)](/specific_iocs/magnets/Zero-field-controller) -1. ARGUS Leiden Dilution Fridge -1. ARGUS Danfysik -1. ARGUS [Zero field controller](/specific_iocs/magnets/Zero-field-controller) - -## Obsolete ARGUS Equipment & SECI Configs ## -The equipment listed below is referenced in SECI config files on ARGUS. It is highly likely that the config files are no longer relevant (they are old, dating from 2011 or 2012), therefore, the references are to devices that are obsolete or simply not used on ARGUS. - -Manufacturer | Model | Type | Connection | Driver | Notes | ------------- | ------------- | ------------- | ------------- | ------------- | ------------------------------------------- -GALIL | [DMC2280](http://www.galilmc.com/products/dmc-22x0.php) | Motion Controller | Ethernet | [EPICS](http://www.aps.anl.gov/epics/modules/manufacturer.php#Galil%20Motion%20Control) | | -McLennan | PM600 | Motion Controller | RS-232 | [EPICS](http://www.aps.anl.gov/epics/modules/manufacturer.php#McLennan%20Servo%20Supplies) | [see McLennan note](#argus_note-mclennan) diff --git a/doc/processes/instrument_details/CHIPIR-Instrument-Details.md b/doc/processes/instrument_details/CHIPIR-Instrument-Details.md index e9598363e..24df191eb 100644 --- a/doc/processes/instrument_details/CHIPIR-Instrument-Details.md +++ b/doc/processes/instrument_details/CHIPIR-Instrument-Details.md @@ -96,9 +96,4 @@ Not required for day 1. Open to suggestions. {#chipir_note-beckhoff} ##### Note: Beckhoff #### -1. Needed prior to migration, should be revisited during migration to move to using more standard motion control under IBEX 1. There are three items, a secondary shutter and 2 filters being controlled by a Beckhoff -1. Initially these will be controlled via SECI, with the Beckhoff managing the reporting and moving of the items in/out of the beam, these will be reported back to IBEX using the standard Beckhoff tagging method -1. A VI will be needed which interacts with the PVs generated by TCIOC - - diff --git a/doc/processes/instrument_details/CRISP-Instrument-Details.md b/doc/processes/instrument_details/CRISP-Instrument-Details.md index fa582ca75..832c9f1a2 100644 --- a/doc/processes/instrument_details/CRISP-Instrument-Details.md +++ b/doc/processes/instrument_details/CRISP-Instrument-Details.md @@ -71,8 +71,6 @@ Eurotherms are used to control temperature Orange Cryostat, CCR and Furnace devi CRISP uses two types of water bath 1. Julabo (which model(s)?) 1. Grant Water Bath - * Update (25-06-2019): Grant water baths are no longer used. No longer any need to support them. See [#4457](https://github.com/ISISComputingGroup/IBEX/issues/4457) -1. Haake N6 Water Bath. Haake has now been taken over by [ThermoFisher](https://www.thermofisher.com/uk/en/home/life-science/lab-equipment/water-baths-circulators-chillers.html). N6 model may be obsolete. Check existing SECI VI for logic and manual. * Update (25-06-2019): Haake water baths are no longer used. No longer any need to support them. See [#4456](https://github.com/ISISComputingGroup/IBEX/issues/4456) {#crisp_noteKeithley} @@ -86,16 +84,16 @@ CRISP uses two types of water bath {#crisp_noteHitachi} ##### Note: Hitachi ##### -Hitachi L-7100 HPLC pump. Can't find L-7100 on Hitachi web-site (may be obsolete). Check existing SECI VI for logic and manual. +Hitachi pumps are no longer supported in ISIS {#crisp_noteKnauer} ##### Note: Knauer ##### Knauer K-6 Electric Valve Drive. [Knauer web site](https://www.knauer.net)
-K-6 model appears to have been superseded. Check existing SECI VI for logic and manual. +K-6 model appears to have been superseded. {#crisp_noteKnauerHPLC} ##### Note: Knauer HPLC ##### -Knauer HPLC 1050 [Knauer HPLC 1050 is discontinued.](https://www.knauer.net/en/discontinued-smartline-pump-1050-successor-azura-p-61l/p14161). Check existing SECI VI for logic and manual. +Knauer HPLC 1050 [Knauer HPLC 1050 is discontinued.](https://www.knauer.net/en/discontinued-smartline-pump-1050-successor-azura-p-61l/p14161). {#crisp_noteNimaTrough} ##### Note: Nima Trough ##### @@ -120,16 +118,7 @@ Thurlby EX355P PSU - see [#155](https://github.com/ISISComputingGroup/IBEX/issue ##### Note: He3 Monitor ##### He3 Monitor is an obsolete piece of equipment. It is no longer used. No need to support it. -## CRISP SECI Configs ## -Document information about CRISP SECI configs here. -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -CRISP_place_holder1.conf | - | dd/mm/yyyy | - | -CRISP_place_holder2.conf | - | dd/mm/yyyy | - | - -## CRISP Genie Scripts ## -Similarly, Document information about CRISP SECI Genie scripts here. ## CRISP Notes ## CRISP has the following specialist panels: diff --git a/doc/processes/instrument_details/EMMA-Instrument-Details.md b/doc/processes/instrument_details/EMMA-Instrument-Details.md index dfa24a0d4..4b550b88e 100644 --- a/doc/processes/instrument_details/EMMA-Instrument-Details.md +++ b/doc/processes/instrument_details/EMMA-Instrument-Details.md @@ -6,9 +6,6 @@ EMMA is an instrument at ISIS, on TS1 and used primarily for test purposes. The Instrument scientist contact is **Jeffrey Sykora**. -## Control System ## -EMMA will migrate from the SECI control system to the IBEX control system in summer 2017. - ## EMMA Equipment ## The equipment listed below is used on EMMA. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -67,7 +64,7 @@ The Fermi chopper control crates (located in the EMMA rack) look like this: ##### Note: Fermi Chopper Lift ##### The Fermi chopper is lifted into position by a Galil controlled motor.
The Fermi chopper must not be operated when it is not in the beam (i.e. in the parked/upper position) -There is a hardware interlock to prevent the Fermi chopper from being operated in the parked position. This interlock is implemented in the Galil controller, via a Galil program (described in the [EMMA chopper lifter - Handover](https://stfc365.sharepoint.com/:w:/r/sites/ISISExperimentControls/ICP%20Discussions/EMMA/EMMA%20chopper%20lifter%20-%20Handover.docx?d=wafc19324e3354636b5ab702a140668aa&csf=1&web=1&e=A6BnDe) document). In SECI a simple VI is used to provide a GUI, which passes parameters to the Galil program, so that the user can control the Fermi Chopper lift. IBEX should provide a similar capability via an IOC and OPI. +There is a hardware interlock to prevent the Fermi chopper from being operated in the parked position. This interlock is implemented in the Galil controller, via a Galil program (described in the [EMMA chopper lifter - Handover](https://stfc365.sharepoint.com/:w:/r/sites/ISISExperimentControls/ICP%20Discussions/EMMA/EMMA%20chopper%20lifter%20-%20Handover.docx?d=wafc19324e3354636b5ab702a140668aa&csf=1&web=1&e=A6BnDe) document). {#emma_noteJaws} ##### Note: Jaws ##### @@ -81,13 +78,11 @@ The vacuum system ([TPG300](https://stfc365.sharepoint.com/:i:/r/sites/ISISExper {#emma_noteYZTable} ##### Note: Y-Z Table ##### Driven by Galil controlled motors. -In SECI, Y-Z Table has its own GUI. No particular reason for this; it could be merged with the Rotation Stage UI.
[Photograph of Y-Z table](https://stfc365.sharepoint.com/sites/ISISExperimentControls/ICP%20Discussions/EMMA/EMMA_Y_Z_Table_2017_06_05.jpg). {#emma_noteRotationStage} ##### Note: Rotation Stage ##### Driven by Galil controlled motors. -In SECI, Rotation Stage has its own GUI. No particular reason for this; it could be merged with the Y-Z Table UI.
[Photograph of Rotation Stage](https://stfc365.sharepoint.com/sites/ISISExperimentControls/ICP%20Discussions/EMMA/EMMA_Rotation_Stage_2017_06_05.jpg). It sits on top of the Y-Z table when in use. {#emma_noteCAENHT} @@ -116,14 +111,6 @@ For the future - it's on the wish list. Desired models are: 1. [Tektronix Oscilloscope DPO7000](http://www.tek.com/oscilloscope/dpo7000-digital-phosphor-oscilloscope) 1. [Tektronix Oscilloscope MSO4054](http://www.tek.com/oscilloscope/mdo4000c-mixed-domain-oscilloscope) -## EMMA SECI Configs ## -Document information about EMMA SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | -----------------------------------------------------------|----------------------------------------------------------------|---------------|----------| - -## EMMA Genie Scripts ## -Similarly, Document information about EMMA SECI Genie scripts here. ## EMMA Notes ## Add any notes about special items of equipment, setup or conditions on EMMA that might impact the deployment and configuration of IBEX. diff --git a/doc/processes/instrument_details/EMU-Instrument-Details.md b/doc/processes/instrument_details/EMU-Instrument-Details.md index 687ce0e1e..79e074aaf 100644 --- a/doc/processes/instrument_details/EMU-Instrument-Details.md +++ b/doc/processes/instrument_details/EMU-Instrument-Details.md @@ -4,9 +4,6 @@ This page collects information that will be useful for the implementation of the ## Background & Timeline ## EMU is a new 96-detector muon spin rotation spectrometer which is optimised for zero field and longitudinal field measurements at ISIS, on TS1. The [EMU](https://www.isis.stfc.ac.uk/Pages/EMU.aspx) web page describes the background to the instrument. -## Control System ## -EMU will migrate from the SECI control system to the IBEX control system in MMMMMMMM YYYY. - ## EMU Equipment ## The equipment listed below is used on EMU. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -119,16 +116,7 @@ Aeroflex has been through a complicated series of sales in recent years. The Ae There appears to be no driver for the Aeroflex 2023A in `C:\LabVIEW Modules\`. However, there is a driver for an Aeroflex 2030 in `C:\LabVIEW Modules\Drivers\Aeroflex 2030`. -## EMU SECI Configs ## -Document information about EMU SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ------------------------------------|----------------------------------------------------|---------------|----------| -EMU_place_holder1.conf | - | dd/mm/yyyy | - | -EMU_place_holder2.conf | - | dd/mm/yyyy | - | -## EMU Genie Scripts ## -Similarly, Document information about EMU SECI Genie scripts here. ### Booster heater issues Scientists initially raised concerns about intermittent invalid alarms and it appears this is due to communication failures to a mercury (see [#6286](https://github.com/ISISComputingGroup/IBEX/issues/6286)). diff --git a/doc/processes/instrument_details/ENGIN-X-Instrument-Details.md b/doc/processes/instrument_details/ENGIN-X-Instrument-Details.md index cef1c1f4f..ad4a84d53 100644 --- a/doc/processes/instrument_details/ENGIN-X-Instrument-Details.md +++ b/doc/processes/instrument_details/ENGIN-X-Instrument-Details.md @@ -123,7 +123,7 @@ The Stress Rig is driven from its own PC (fitted with a GPIB card). IBEX commun {#enginx_noteHuber} ##### Note: Huber ##### -2-degree of freedom Eulerian cradle. The Huber can be driven from a Galil. Gareth has created a VI to control this via SECI. +2-degree of freedom Eulerian cradle. The Huber can be driven from a Galil. {#enginx_noteTheodolite} ##### Note: Theodolite ##### @@ -163,11 +163,3 @@ ENGIN-X are consider whether it would be useful to use a high-performance GigE c ## ENGIN-X Notes ## * For each run, ENGIN-X generates .log and .txt files from the NeXus data file. The .txt files are "3-column" files (as opposed to the "2-column" data files used on other instruments. We need to determine if these "3-column" files are still required in the future and, if so, document how these "3-column" files are generated. * OpenGENIE is currently used to analyse ENGIN-X data. In due course, the ENGIN-X team should consider migrating to Mantid. - -## ENGIN-X SECI Configs ## -Document information about ENGIN-X SECI configs here. - -## ENGIN-X Genie Scripts ## -Similarly, Document information about ENGIN-X SECI Genie scripts here. -* ENGIN-X currently has one large master OpenGENIE script, which is used in (almost?) all runs. This script has to be migrated to genie_python (or to a library of genie_python methods). -* ENGIN-X also uses a position compensation script (to compensate for the movement of the target position as the sample is stretched on the stress rig). diff --git a/doc/processes/instrument_details/GEM-Instrument-Details.md b/doc/processes/instrument_details/GEM-Instrument-Details.md index 120e68c7b..900f8f6a0 100644 --- a/doc/processes/instrument_details/GEM-Instrument-Details.md +++ b/doc/processes/instrument_details/GEM-Instrument-Details.md @@ -93,48 +93,3 @@ Furnaces are controlled via a temperature controller (e.g. Eurotherm), so nothin {#gem_noteMcLennan} ##### Note: McLennan ##### [see Collimator note](#gem_noteCollimator) - -## GEM SECI Configs ## - -Configuration Name | Sub-Configurations | Last Accessed | Required | -----------------------------------------------------------|----------------------------------------------------------------|---------------|----------| -`gem_heliox.conf` | - | 14/11/2016 | - -`gem_sample_changer_matt.conf` | Choppers | 20/05/2016 | - -`gem_ccr_matt.conf` | Choppers | 28/04/2016 | - -`gem_sample_changer_Alex.conf` | Choppers | 24/02/2016 | - -`gem_lowT_furnace_matt.conf` | Choppers | 04/12/2015 | - -`gem_kelvinox_matt.conf` | - | 01/10/2015 | - -`GEM_CRYOSTAT.conf` | Choppers | 24/07/2015 | - -`gem_furnace_matt.conf` | Choppers, Furnace Pressure | 15/06/2015 | - -`gem_polaris_sample_changer_matt.conf` | Choppers | 26/04/2015 | - -`gem_furnace_ramp.conf` | Furnace Pressure | 03/04/2015 | - -`gem_furnace.conf` | Furnace Pressure | 02/04/2015 | - -`gem_3eurotherms.conf` | - | 20/03/2015 | - -`gem_sample_changer.conf` | Choppers | 18/03/2015 | - -`GEM_CRYOSTAT_matt.conf` | - | 02/06/2014 | - -`gem_ccr.conf` | Choppers | 02/04/2014 | - -`gem_8t cryo.conf` | GEM_Base, Choppers | 18/12/2013 | - -`5 Axis.conf` | - | 20/07/2013 | - -`gem_sample_changer_+_3_Eurotherms.conf` | 3_Eurotherms | 18/03/2013 | - -`gem_tizrcell_matt.conf` | - | 16/10/2012 | - -`gem_3eurotherms_pressure.conf` | - | 12/10/2012 | - -`gem_ambient.conf` | - | 04/10/2011 | - -`gem_3eurotherms_baritron.conf` | - | 16/04/2011 | - -`gem_express.conf` | - | 23/02/2011 | - -`gem_gazcell.conf` | - | 16/02/2011 | - -`gem_cryo + eurotherm.conf` | - | 15/02/2011 | - -`gem_7t cryomagnet.conf` | - | 15/02/2011 | - -`Dave.conf` | - | 15/02/2011 | - -`gem_kelvinox.conf` | - | 27/01/2011 | - -`gem_cryo + ilm.conf` | - | 27/01/2011 | - -`gem_cryo + ilm + SC.conf` | - | 27/01/2011 | - -`gem_cryo + heliox.conf` | - | 27/01/2011 | - -`gem_8t cryo + rotation.conf` | - | 27/01/2011 | - -`gem_8t cryo + kelvinox.conf` | - | 27/01/2011 | - -`gem_10t cryomagnet.conf` | - | 27/01/2011 | - - -## GEM Genie Scripts ## -Similarly, Document information about GEM SECI Genie scripts here. - -## GEM Notes ## -Add any notes about special items of equipment, setup or conditions on GEM that might impact the deployment and configuration of IBEX. diff --git a/doc/processes/instrument_details/HIFI-Instrument-Details.md b/doc/processes/instrument_details/HIFI-Instrument-Details.md index df0223bce..a9c1e6aa6 100644 --- a/doc/processes/instrument_details/HIFI-Instrument-Details.md +++ b/doc/processes/instrument_details/HIFI-Instrument-Details.md @@ -4,9 +4,6 @@ This page collects information that will be useful for the implementation of the ## Background & Timeline ## HIFI is high magnetic-field muon instrument at ISIS, on TS1. The [HIFI](https://www.isis.stfc.ac.uk/Pages/HIFI.aspx) web page describes the background to the instrument. -## Control System ## -HIFI will migrate from the SECI control system to the IBEX control system in MMMMMMMM YYYY. - ## HIFI Equipment ## The equipment listed below is used on HIFI. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -65,8 +62,6 @@ There appears to be no driver for the Aeroflex 2023A in `C:\LabVIEW Modules\`. H * no information on specific Julabo Water Baths - maybe HIFI uses water baths from the pool? * consult the [Julabo commands](/specific_iocs/temp_controllers/julabo_commands.xlsx) spreadsheet for specific details of which set of commands are used individual water baths. 1. Haake Water Bath is now obsolete (replaced by Julabo, according to instrument scientist) - * ~Haake Water Bath (apparently the following Haake water bath: WB9)~ - * ~Haake N6 Water Bath. Haake has now been taken over by [ThermoFisher](https://www.thermofisher.com/uk/en/home/life-science/lab-equipment/water-baths-circulators-chillers.html). N6 model may be obsolete. Check existing SECI VI for logic and manual (see `C:\LabVIEW Modules\Drivers\Haake N6`).~ 1. See also [Water Baths](https://www.isis.stfc.ac.uk/Pages/Water-Baths.aspx) list {#hifi_note-neocera} @@ -103,21 +98,8 @@ See also `C:\LabVIEW Modules\Drivers\Caen`. ##### Note: Metrolab ##### 1. [PT2025 NMR Precision Teslameter](https://www.metrolab.com/products/pt2025/) * The PT2025 is now obsolete. Replaced by model PT2026. - * See `C:\LabVIEW Modules\Instruments\HIFI\Metrolab PT2025 NMR` for SECI VI * See `\\isis\shares\ISIS_Experiment_Controls\Metrolab PT2025 Teslameter` for the technical manual. - -## HIFI SECI Configs ## -Document information about HIFI SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -HIFI_place_holder1.conf | - | dd/mm/yyyy | - | -HIFI_place_holder2.conf | - | dd/mm/yyyy | - | - -## HIFI Genie Scripts ## -Similarly, Document information about HIFI SECI Genie scripts here. - ## HIFI Notes ## HIFI has the following specialist panels: 1. MUSR RF Kit @@ -132,6 +114,3 @@ HIFI has the following specialist panels: 1. HIFI Metrolab PT2025 (NMR Readout) 1. MUON FrontEnd Magnet Monitoring 1. MUON Jaws - -HIFI also has the following system: -1. MUON Script (generator) \ No newline at end of file diff --git a/doc/processes/instrument_details/HRPD-Instrument-Details.md b/doc/processes/instrument_details/HRPD-Instrument-Details.md index d2e631a2e..f02b5c47f 100644 --- a/doc/processes/instrument_details/HRPD-Instrument-Details.md +++ b/doc/processes/instrument_details/HRPD-Instrument-Details.md @@ -1,10 +1,11 @@ # HRPD This page collects information that will be useful for the implementation of the IBEX control system on HRPD. + ## Background & Timeline ## HRPD, the High Resolution Powder Diffractometer is an instrument on TS1 at ISIS. It is the highest resolution neutron powder diffractometer of its type in the world. The [HRPD](http://www.isis.stfc.ac.uk/instruments/hrpd/hrpd.html) web page describes the background to the instrument. -There is a proposal to re-build HRPD at some point in the next 3-5 years. +HRPD is currently being rebuilt as HRPD-X ## HRPD Equipment ## The equipment listed below is used on HRPD. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -102,26 +103,3 @@ See [magnets at ISIS](http://www.isis.stfc.ac.uk/sample-environment/high-magneti {#hrpd_noteRamanSpect} ##### Note: mini-Raman Spectrometer ##### 1. [B&W Tek i-Raman Plus](http://bwtek.com/products/i-raman-plus/) A Raman Spectrometer is something that HRPD would like to use at a future date (TBD). See also SXD. - -## HRPD SECI Configs ## -HRPD has numerous heritage SECI configurations only two of which are now used routinely. - -1. One is used for day-to-day operation with samples at RT, in cryostats or furnace (`HRPD_Eurotherms_2.conf`). -1. The second is used with the sample changer (`HRPD_Sample_Changer_new_oct16.conf`). - -All located in `C:\\Program Files (x86)\STFC ISIS Facility\SECI\Configurations` - -The HRPD team would probably wish to have separate configurations for experiments involving: - -1. High-pressure devices (incl. various pressure transducers) -1. Gas handling -1. Magnets -1. In-situ light scattering (laser control, spectrometer data acquisition) - -## HRPD Genie Scripts ## -The critical OpenGenie scripts, for initialisation and focussing, are in `C:\\OG` (duplicated, more or less, in `C:\\scripts\OG`) - -HRPD has a large collection of Genie scripts accumulated over the years, each of results from a specific user running a specific operation. A number of editable seed scripts are kept in (`C:\\scripts\keep`). These might appropriately be converted to genie_python. - -## HRPD Notes ## -Add any notes about special items of equipment, setup or conditions on HRPD that might impact the deployment and configuration of IBEX. diff --git a/doc/processes/instrument_details/INES-Instrument-Details.md b/doc/processes/instrument_details/INES-Instrument-Details.md index 846a05b3f..b67864c4e 100644 --- a/doc/processes/instrument_details/INES-Instrument-Details.md +++ b/doc/processes/instrument_details/INES-Instrument-Details.md @@ -4,9 +4,6 @@ This page collects information that will be useful for the implementation of the ## Background & Timeline ## INES is a powder diffractometer instrument at ISIS, on TS1. The [INES](https://www.isis.stfc.ac.uk/Pages/ines.aspx) web page describes the background to the instrument. -## Control System ## -INES will migrate from the SECI control system to the IBEX control system in late October 2018 (prior to Cycle 2018/03). - ## INES Equipment ## The equipment listed below is used on INES. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -29,7 +26,7 @@ INES uses DAE-2. INES has 2 fixed monitors. {#ines_noteShutter} ##### Note: Shutter ##### INES shares a shutter with TOSCA. INES needs to know the status of the TOSCA shutter.
-INES also has a secondary shutter. The status of the secondary shutter cannot currently (September 2018) be read (it requires the installation of an appropriate electronic device to provide a signal). At the present time, INES has no need to monitor the secondary shutter via IBEX (for the same reasons, the secondary shutter cannot be monitored with SECI). +INES also has a secondary shutter. The status of the secondary shutter cannot currently (September 2018) be read (it requires the installation of an appropriate electronic device to provide a signal). At the present time, INES has no need to monitor the secondary shutter via IBEX. {#ines_noteChopper} ##### Note: Choppers ##### @@ -60,36 +57,7 @@ Eurotherms are used to control temperature in the vacuum tank. See also tickets [#1826](https://github.com/ISISComputingGroup/IBEX/issues/1826), [#2695](https://github.com/ISISComputingGroup/IBEX/issues/2695), [#2801](https://github.com/ISISComputingGroup/IBEX/issues/2801) and [#3176](https://github.com/ISISComputingGroup/IBEX/issues/3176). 1. Keithley 2410 is used only rarely (for neutron instrumentation projects) -## INES SECI Configs ## -Document information about INES SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -5_Axis | - | 14/02/2011 | - | -AncientCharm | - | 14/02/2011 | - | -Blank | - | 18/02/2011 | - | -Eurotherms & Keithley | Keithley | 06/06/2014 | Yes | -Eurotherms | - | 19/05/2014 | Yes | -Goniometer | - | 01/07/2011 | Yes | -INES Base | - | 28/04/2014 | Yes | -practice | - | 14/02/2011 | - | -Sample_Changer | - | 01/07/2011 | Yes | -TEST | - | 19/08/2010 | - | -Tomography | - | 24/05/2011 | - | - -## INES Genie Scripts ## -Similarly, Document information about INES SECI Genie scripts here. - ## INES Notes ## -INES has the following specialist panels: -1. INES IV - 1. This is a SECI VI, customised for INES. We should check what information it displays that is not already included in the standard IBEX dashboard. A new OPI may be required. -1. GEM Jaws - 1. **Note:** GEM has been upgraded and now has new jaws. "GEM Jaws" may refer to the old GEM jaws VI. - 1. Check if the behaviour of the standard jaws OPI meets the needs of INES. -1. Walter SE `Rotacq2` - 1. This refers to an old rotation stage, which is no longer used. - INES has the following devices under motion control: 1. Goniometer 1. INES has 2 goniometers: one large, one small. diff --git a/doc/processes/instrument_details/INTER-Instrument-Details.md b/doc/processes/instrument_details/INTER-Instrument-Details.md index a1af8c197..5bf4a22c0 100644 --- a/doc/processes/instrument_details/INTER-Instrument-Details.md +++ b/doc/processes/instrument_details/INTER-Instrument-Details.md @@ -80,7 +80,7 @@ See also tickets [#1826](https://github.com/ISISComputingGroup/IBEX/issues/1826) {#inter_noteHitachi} ##### Note: Hitachi ##### -Hitachi L-7100 HPLC pump (no longer supported at ISIS). ~Can't find L-7100 on [Hitachi web-site](http://www.hitachi-hightech.com/global/about/corporate/group/hhs (may be obsolete). Check existing SECI VI for logic and manual.~ +Hitachi pumps are no longer supported at ISIS {#inter_note-linkam} ##### Note: Linkam ##### @@ -90,12 +90,12 @@ See also [Linkam T95 controller](http://www.linkam.co.uk/t95-system-controllers/ {#inter_note-knauer} ##### Note: Knauer ##### Knauer K-6 Electric Valve Drive. [Knauer web site](https://www.knauer.net)
-K-6 model appears to have been superseded. Check existing SECI VI for logic and manual. +K-6 model appears to have been superseded. 1. Support now implemented (28-03-2019). See [#3781](https://github.com/ISISComputingGroup/IBEX/issues/3781). {#inter_note-knauer-HPLC} ##### Note: Knauer HPLC ##### -Knauer HPLC 1050 [Knauer HPLC 1050 is discontinued.](https://www.knauer.net/en/discontinued-smartline-pump-1050-successor-azura-p-61l/p14161). Check existing SECI VI for logic and manual. +Knauer HPLC 1050 [Knauer HPLC 1050 is discontinued.](https://www.knauer.net/en/discontinued-smartline-pump-1050-successor-azura-p-61l/p14161). 1. Support now implemented (04-01-2019). See [#3262](https://github.com/ISISComputingGroup/IBEX/issues/3262). {#inter_note-jasco-hplc-pump} @@ -115,9 +115,8 @@ Knauer HPLC 1050 [Knauer HPLC 1050 is discontinued.](https://www.knauer.net/en/d {#inter_note-nima-trough} ##### Note: Nima Trough ##### -Nima Trough: SECI uses a manufacturer supplied VI (see `C:\LabVIEW Modules\Drivers\Nima Trough`). We may need to do the same in IBEX (via lvDCOM). +Nima Trough: * **Note:** NIMA Technologies Ltd now seems to be part of [Biolin Scientific](https://www.biolinscientific.com/ksvnima).
- * The NIMA trough is used regularly on SURF. The manufacturer supplied VI is used to view graphs showing information about thin films. * The manufacturer has made additional software available for download. A copy of this software is located in `\\isis\shares\ISIS_Experiment_Controls\NIMA Trough\Nima_TR8.1.zip`. * Support now implemented (25-05-2019). See [#3783](https://github.com/ISISComputingGroup/IBEX/issues/3783) @@ -165,11 +164,10 @@ Thurlby EX355P PSU - see [#155](https://github.com/ISISComputingGroup/IBEX/issue ##### Note: Vacuum Chamber ##### 1. Vacuum chamber – specialist setup using HV and vacuum with some safety trips integrated (instrument scientists says this is be a high priority to enable in IBEX). - * Check SECI VI. * Is the vacuum chamber related to the INTER High Voltage VI (listed below)? ## INTER Mirror Guides ## -INTER is due to get new mirror guides (prior to Cycle 2019/01). These will be operational (under SECI) before INTER is migrated to IBEX. There is a [sketch showing the three mirror guide sections](https://stfc365.sharepoint.com/sites/ISISExperimentControls/ICP%20Discussions/INTER/Defined%20Axis%20and%20Rotations.pdf) (MG1 - MG3). MG1 is fixed; it requires no control. MG2 and MG3 are moveable and, therefore, do require control. +INTER is due to get new mirror guides (prior to Cycle 2019/01). There is a [sketch showing the three mirror guide sections](https://stfc365.sharepoint.com/sites/ISISExperimentControls/ICP%20Discussions/INTER/Defined%20Axis%20and%20Rotations.pdf) (MG1 - MG3). MG1 is fixed; it requires no control. MG2 and MG3 are moveable and, therefore, do require control. There will be, essentially, 3 modes of operation: 1. **no bounce:** all three sections centred in height around the incident beam height to allow straight through beam on sample @@ -178,27 +176,6 @@ There will be, essentially, 3 modes of operation: In modes 2 and 3 several beamline components need to track: intermediate slit (S1b), slit 2, sample monitor, sample height, slit 3 and detector. -In May 2019, SECI was updated to handle the new mirror guides. IBEX will need to replicate the new functionality in SECI. The is a document [describing the SECI changes](https://stfc365.sharepoint.com/sites/ISISExperimentControls/ICP%20Discussions/INTER/INTER%20SECI%20changes.docx). - -## INTER SECI Configs ## -Document information about INTER SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | --------------------------------------|----------------------------------------------------|---------------|----------| -INTER_place_holder1.conf | - | dd/mm/yyyy | - | -INTER_place_holder2.conf | - | dd/mm/yyyy | - | - -## INTER Genie Scripts ## -Similarly, Document information about INTER SECI Genie scripts here. - -## INTER Notes ## -INTER has the following specialist panels: -1. INTER Front Panel -1. INTER KEYENCE LK-G -1. INTER Galil DIO -1. INTER High Voltage -1. OFFSPEC Piezo Stage -1. SURF Galil DIO INTER has the following devices under motion control: 1. FOM diff --git a/doc/processes/instrument_details/IRIS-Instrument-Details.md b/doc/processes/instrument_details/IRIS-Instrument-Details.md index 097b170d9..84ae2a8a7 100644 --- a/doc/processes/instrument_details/IRIS-Instrument-Details.md +++ b/doc/processes/instrument_details/IRIS-Instrument-Details.md @@ -12,9 +12,6 @@ This page collects information that will be useful for the implementation of the IRIS is a long established instrument at ISIS, on TS1. The [IRIS](http://www.isis.stfc.ac.uk/instruments/iris/iris4691.html) web page describes the background to the instrument. A schematic layout of IRIS is shown in ​[this diagram](http://www.isis.stfc.ac.uk/images/instruments/iris-/iris-schematic4923.jpg).
IRIS shares a port with [OSIRIS](http://www.isis.stfc.ac.uk/instruments/osiris/osiris4667.html). We may need to have a way of sharing information between the IRIS and OSIRIS control systems. It might also be worth migrating IRIS and ​OSIRIS to IBEX at the same time. -## Control System ## -IRIS will migrate from the SECI control system to the IBEX control system. - ## IRIS Equipment ## The equipment listed below is used on IRIS. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -127,15 +124,6 @@ _no comment (as yet)_ ##### Note: CryoValve Controller ##### Due to be superseded by the Exchange Gas Controller. -## IRIS SECI Configs ## -Over the years, IRIS has built up a significant collection of SECI configs. Not all of them are current (some may no longer be used, or used only infrequently). We will need to investigate how to convert them to IBEX configs. The current list of IRIS configs is listed on [trac](https://trac.isis.rl.ac.uk/ICP/wiki/IRIS). -The config files are located in the folder `SECI\Configurations\` on the control server and have the extension `.conf`. Sub-configuration files have the extension `.comp` (component). The files with numbers as extensions (`.1`, `.2`, `.3`,etc.) are backups of the configuration and sub-configuration files. - -## IRIS Genie Scripts ## -Similarly, IRIS has built up a significant collection of genie scripts over the years. Again, many scripts are old and may no longer be used regularly. Most runs on IRIS are controlled via scripts. There will be a need to convert some of these scripts to genie-python, but probably not all. - -The current list of IRIS genie scripts is listed on [trac](https://trac.isis.rl.ac.uk/ICP/wiki/IRIS). - ## Tested IOCs ## | What | When | Notes | diff --git a/doc/processes/instrument_details/LET-Instrument-Details.md b/doc/processes/instrument_details/LET-Instrument-Details.md index d51cd1f1a..ab1cefebe 100644 --- a/doc/processes/instrument_details/LET-Instrument-Details.md +++ b/doc/processes/instrument_details/LET-Instrument-Details.md @@ -99,25 +99,3 @@ LET has the following specialist systems: * LET has two rotation stages; 1. A McLennan rotation stage (same as MERLIN, used with CCRs & Orange Cryostats)) 1. A McLennan-Newport rotation stage (used with the 9T Magnet) - -## LET SECI Configs ## -LET has a number of SECI configurations. Equivalent IBEX configs for the following combinations of equipment are required: - * Eurotherm (for Cryostat or CCR) + rotation stage - * Eurotherm (for Cryostat or CCR) + ORC + rotation stage - * Eurotherm (for Cryostat or CCR) + dilution fridge (Triton) + rotation stage - * Eurotherm (for Cryostat or CCR) + dilution fridge (Triton)+ ORC + rotation stage - * Eurotherm (for Cryostat or CCR) + dilution fridge (Heliox) + rotation stage - * Eurotherm (for Cryostat or CCR) + dilution fridge (Heliox)+ ORC + rotation stage - * 9T Magnet + McLennan-Newport rotation stage - -## LET Genie Scripts ## -LET has a number of instrument specific Genie scripts. The key scripts to be migrated to genie_python are: - -Script| Purpose | Notes | ------------- | ------------- | ------------------------------------------- -`park_choppers`| It parks the choppers, of course | Needed because LET has 4 choppers -`set_ei5` | Sets chopper speed/phase | This is the LET version of `set_ei`. It is **not** the same as `set_ei` used on other excitations instruments. It would be helpful if `set_ei5` could be extended to better support vetoes and wiring tables. Ignore the older versions `set_ei1` - `set_ei4`. -`mono` | | - -On LET user scripts are usually created by modifying an old user script. Create a template genie_python script (based on an old user script) which can be used in future. - diff --git a/doc/processes/instrument_details/LOQ-Instrument-Details.md b/doc/processes/instrument_details/LOQ-Instrument-Details.md index 212662578..2649515ca 100644 --- a/doc/processes/instrument_details/LOQ-Instrument-Details.md +++ b/doc/processes/instrument_details/LOQ-Instrument-Details.md @@ -92,7 +92,7 @@ Both the OMEGA™ iBTHX and OMEGA™ PAC devices (see above) have proved unrelia {#loq_note-vacuum-system} ##### Note: Vacuum System ##### 1. There are 2 vacuum gauges on LOQ. Both are TPG300's. One is atop the Galil at the sample position monitoring the collimation, and the other is integrated into the detector tank pumping system. -2. Only the detector tank TPG300 is currently read back in SECI. There are two sensors, one at the pump, and one on the tank. +2. Only the detector tank TPG300 was read back in SECI. There are two sensors, one at the pump, and one on the tank. 3. **It is highly desirable to have the collimation TPG300 integrated into Ibex too.** 4. TPG300 support is implemented via [#216](https://github.com/ISISComputingGroup/IBEX/issues/216) and [#2063](https://github.com/ISISComputingGroup/IBEX/issues/2063) @@ -200,39 +200,3 @@ LOQ has the following devices under motion control: 3. Transmission Monitor (M3) * moves in/out of the beam. -## LOQ SECI Configs ## -Document information about LOQ SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -LOQ_NORMAL_25Hz_Cryostat.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_DurhamRack | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_Flowcell.conf | - | dd/mm/yyyy | see note 1 | -LOQ_NORMAL_25Hz_Furnace.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_Huber_stages.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_Magnet.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_PressuceCell.conf | - | dd/mm/yyyy | N | -LOQ_NORMAL_25Hz_PressureCell.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_Rheometer.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_SampleChanger.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_SampleChanger_eurotherm_controller.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_SampleChanger_eurotherm_controller_2.conf | - | dd/mm/yyyy | ? | -LOQ_NORMAL_25Hz_SampleChanger_NOLIVEVIEW.conf | - | dd/mm/yyyy | see note 2 | -LOQ_NORMAL_25Hz_Shear.conf | - | dd/mm/yyyy | see note 1 | -LOQ_NORMAL_25Hz_StopFlow.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_TJump.conf | - | dd/mm/yyyy | Y | -LOQ_NORMAL_25Hz_UnileverCell.conf | - | dd/mm/yyyy | Y | -LOQ_QUIET.conf | - | dd/mm/yyyy | see note 3 | - -##### Note: 1 ##### -Need to establish what devices these relate to! - -##### Note: 2 ##### -This is LOQ_NORMAL_25Hz_SampleChanger.conf without the second time regime. Occasionally used with non-standard detector mapping. - -##### Note: 3 ##### -Configures LOQ for running on internal clock. - -## LOQ Genie Scripts ## -Similarly, Document information about LOQ SECI Genie scripts here. - diff --git a/doc/processes/instrument_details/MAPS-Instrument-Details.md b/doc/processes/instrument_details/MAPS-Instrument-Details.md index e686214d7..4404d4cb9 100644 --- a/doc/processes/instrument_details/MAPS-Instrument-Details.md +++ b/doc/processes/instrument_details/MAPS-Instrument-Details.md @@ -72,13 +72,5 @@ Eurotherms in use on MAPS. Used to control temperature of all top-loading CCRs, ##### Note: Neocera ##### Neocera is used only occasionally. [Neocera LTC-21 Manual](http://www.submm.caltech.edu/~sharc/technical/LTC-21%20manual.pdf) -## MAPS SECI Configs ## -MAPS has a number of SECI configurations, which need to be migrated. - -## MAPS Genie Scripts ## -Critical OpenGenie scripts for initialisation and focussing. - -MAPS has a number of instrument specific Genie scripts. These need to be migrated to genie_python. - ## MAPS Notes ## Add any notes about special items of equipment, setup or conditions on MAPS that might impact the deployment and configuration of IBEX. diff --git a/doc/processes/instrument_details/MARI-Instrument-Details.md b/doc/processes/instrument_details/MARI-Instrument-Details.md index b95961adc..ea7095c24 100644 --- a/doc/processes/instrument_details/MARI-Instrument-Details.md +++ b/doc/processes/instrument_details/MARI-Instrument-Details.md @@ -77,13 +77,5 @@ The temperature control will be handled by a Eurotherm.
[Project Details](https://stfc365.sharepoint.com/sites/ISISProject-1122) and [Project Plan](https://tasks.office.com/stfc365.onmicrosoft.com/en-US/Home/PlanViews/8bdu_4UTBUeZwF_PB8SLIpYAESGr) -## MARI SECI Configs ## -MARI has a number of SECI configurations, which need to be migrated. - -## MARI Genie Scripts ## -Critical OpenGenie scripts for initialisation and focussing. - -MARI has a number of instrument specific Genie scripts. These have now been migrated to genie_python. - ## MARI Notes ## 1. MARI does not currently use a script generator, but there is interest in having one in the future. diff --git a/doc/processes/instrument_details/MERLIN-Instrument-Details.md b/doc/processes/instrument_details/MERLIN-Instrument-Details.md index c072b9286..1a57d0e3d 100644 --- a/doc/processes/instrument_details/MERLIN-Instrument-Details.md +++ b/doc/processes/instrument_details/MERLIN-Instrument-Details.md @@ -109,14 +109,3 @@ Neocera is used only occasionally. [Neocera LTC-21 Manual](http://www.submm.cal ##### Note: McWhan ##### [McWhan pressure cell](http://www.isis.stfc.ac.uk/sample-environment/high-pressure-and-gas-handling-/clamped-cells/mcwhan-clamped-cell-8653.html). McWhan refers to the design of the cell (not to the manufacturer). Cell cannot be controlled directly from IBEX. It may be possible to report the current pressure via a device such as a Chell pressure transducer. See also [General Clamped Cells](http://www.isis.stfc.ac.uk/sample-environment/high-pressure/clamped-cells/general-clamped-cells/general-clamped-cells14180.html) and [High Pressure Gas Cells](http://www.isis.stfc.ac.uk/sample-environment/sample-containers/high-pressure-gas-cells/high-pressure-gas-cells8936.html). - -## MERLIN SECI Configs ## -MERLIN has a number of SECI configurations, which need to be migrated. - -## MERLIN Genie Scripts ## -The critical OpenGenie scripts, for initialisation and focussing, are in `C:\\OG` (duplicated, more or less, in `C:\\scripts\OG`) - -MERLIN has a number of instrument specific Genie scripts. These need to be migrated to genie_python. - -## MERLIN Notes ## -Add any notes about special items of equipment, setup or conditions on MERLIN that might impact the deployment and configuration of IBEX. diff --git a/doc/processes/instrument_details/MUON-Front-End-Instrument-Details.md b/doc/processes/instrument_details/MUON-Front-End-Instrument-Details.md index 0018d3081..64c61142a 100644 --- a/doc/processes/instrument_details/MUON-Front-End-Instrument-Details.md +++ b/doc/processes/instrument_details/MUON-Front-End-Instrument-Details.md @@ -5,9 +5,6 @@ This page contains information pertinent to the automation of the Muon Front End ## Background & Timeline ## The system is due on line September 2016. -## Control System ## -Whilst the Front End control will be undertaken under IBEX, it must integrate with SECI as well as part of the system is to be used on existing instruments. Some of the IOCs will only be controlled from instrument PCs, whilst in some situations only monitoring will be required. - ## Equipment ## | Manufacturer | Model | Type | Connection | Driver | Notes | | --- | --- | --- | --- | --- | --- | @@ -29,4 +26,4 @@ The barn doors and momentum slits control the muon beam delivered to the 3 muon {#muonfe_noteMotion} ##### Note: Motion ##### -There is a project relating to the motion on the South Side Muons in progress, this information may be out of date \ No newline at end of file +There is a project relating to the motion on the South Side Muons in progress, this information may be out of date diff --git a/doc/processes/instrument_details/MUSR-Instrument-Details.md b/doc/processes/instrument_details/MUSR-Instrument-Details.md index 53462377c..b8de135aa 100644 --- a/doc/processes/instrument_details/MUSR-Instrument-Details.md +++ b/doc/processes/instrument_details/MUSR-Instrument-Details.md @@ -127,17 +127,3 @@ MUSR has the following motion control items: MUSR also has the following system: 1. MUON Script Generator (muongui.exe) - -## MUSR SECI Configs ## -Document information about MUSR SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -EMU_place_holder1.conf | - | dd/mm/yyyy | - | -EMU_place_holder2.conf | - | dd/mm/yyyy | - | - -## MUSR Genie Scripts ## -Similarly, Document information about MUSR SECI Genie scripts here. - -## MUSR configs from EMU -Configurations have been removed that were migrated from SECI + EMU as they are being phased out or have not been in use. Commit `63303d94400cd0270b3c07357a08cbdf5945d8e8` should still contain the configurations before removal. \ No newline at end of file diff --git a/doc/processes/instrument_details/NIMROD-Instrument-Details.md b/doc/processes/instrument_details/NIMROD-Instrument-Details.md index 2f7b1fa0c..0c5944ad6 100644 --- a/doc/processes/instrument_details/NIMROD-Instrument-Details.md +++ b/doc/processes/instrument_details/NIMROD-Instrument-Details.md @@ -77,8 +77,8 @@ The [MKS PDR2000A](https://www.mksinst.com/f/pdr2000a-2-channel-digital-power-su The [MKS PR4000B](https://www.mksinst.com/f/pr4000b-digital-power-supply) Digital Power Supply and Display module is available with either one or two channels. The single-channel version controls one pressure transducer or one mass flow controller. The two-channel version supports up to two pressure transducers or two mass flow controllers, or one of each. There are [EPICS drivers](http://www.aps.anl.gov/epics/modules/manufacturer.php#MKS%20Instruments) for a variety of MKS devices (although there is a driver for a PR4000B pressure transducer, there does not appear to be one for a PDR2000). -The manual for the MKS PR4000B is here: `\\isis\shares\ISIS_Experiment_Controls\MKS_PR4000B_Controller`.
-The SECI VI for the MKS PDR2000 is here: `C:\LabVIEW Modules\Drivers\MKS PDR2000 Pressure Gauge`. +The manual for the MKS PR4000B is here: `\\isis\shares\ISIS_Experiment_Controls\MKS_PR4000B_Controller`. + **Note:** Please refer to ticket [#3962](https://github.com/ISISComputingGroup/IBEX/issues/3692) when implementing support for the PDR2000 on NIMROD. @@ -86,29 +86,6 @@ The SECI VI for the MKS PDR2000 is here: `C:\LabVIEW Modules\Drivers\MKS PDR2000 NIMROD has the following specialist panels/systems: 1. NIMROD Jaws - calculates jaw settings based on moderator projection. -## NIMROD SECI Configs ## -Document information about NIMROD SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -NIMROD_temp.conf | - | dd/mm/yyyy | - | -NIMROD_SuperStick.conf | - | dd/mm/yyyy | - | -NIMROD_SC.conf | - | dd/mm/yyyy | - | -NIMROD_RB1410637.conf | - | dd/mm/yyyy | - | -NIMROD_RB1410416.conf | - | dd/mm/yyyy | - | -NIMROD_CCR.conf | - | dd/mm/yyyy | - | -NIMROD_Basic.conf | - | dd/mm/yyyy | - | -NiceIceSECI.conf | - | dd/mm/yyyy | - | - -## NIMROD Genie Scripts ## -On NIMROD, normal practice is to adapt an earlier script. There is no library of scripts. Most scripts are similar to those used on SANDALS. It might be useful to create some genie_python scripts to serve as examples. One script that could be converted (to serve as an example) is `fraser10_depwarmup.gcl`. - -Script Name | Notes | Last Accessed | Required | ---------------------------|---------------------------------------------------------|---------------|----------| -`fraser10_depwarmup.gcl` | Convert to use an a template/example for future scripts | dd/mm/yyyy | - | - -The "dry_run" feature used on SANDALS scripts could be handy for NIMROD too. - ## NIMROD Notes ## #### Pumps #### NIMROD tends to use a lot of different pumps (e.g. Oerlikon, Edwards, Pfeiffer). Worth having support for a variety of pumps to make switching between pumps easy. @@ -124,4 +101,4 @@ This has been installed on Galil 4 axis 5 (D) on NIMROD. Motion setpoints have b ![](NIMROD__Oxford_MCP_Camera.jpg) #### Electrochemical Cell Positioner #### -A device is being built to position an electrochemical cell in the beam. This is a single linear axis with continuous positioning. We need not concern ourselves with the cell itself as this will be controlled by the users. \ No newline at end of file +A device is being built to position an electrochemical cell in the beam. This is a single linear axis with continuous positioning. We need not concern ourselves with the cell itself as this will be controlled by the users. diff --git a/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md b/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md index bb6383dd6..fae29b67b 100644 --- a/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md +++ b/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md @@ -11,9 +11,6 @@ This page collects information that will be useful for the implementation of the Bench moves so that angle is correct this requires motors at front and back to change positions and the bench to slide in and out. This maintains the distance from the detector to the sample in an arc. -## Control System ## -OFFSPEC will migrate from the SECI control system to the IBEX control system in MMMMMMMM YYYY. - ## OFFSPEC Equipment ## The equipment listed below is used on OFFSPEC. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -64,7 +61,6 @@ The equipment listed below is used on OFFSPEC. Please add new information (e.g.
Older information: -``` Manufacturer | Model | Type | Connection | Driver | Notes | ------------ | ------------- | ------------- | ------------- | ------------- | ------------------------------------------- ISIS | DAE 2 | Detector Electronics | Ethernet | | [see DAE note](#note-dae) @@ -218,16 +214,6 @@ OFFSPEC has the following devices under motion control: 1. Polarizer 1. reflectometer sample stack -## OFFSPEC SECI Configs ## -Document information about OFFSPEC SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -OFFSPEC_place_holder1.conf | - | dd/mm/yyyy | - | -OFFSPEC_place_holder2.conf | - | dd/mm/yyyy | - | - -``` -
## OFFSPEC Genie Scripts ## diff --git a/doc/processes/instrument_details/OSIRIS-Instrument-Details.md b/doc/processes/instrument_details/OSIRIS-Instrument-Details.md index 3d7ce9cfe..4f3c985b5 100644 --- a/doc/processes/instrument_details/OSIRIS-Instrument-Details.md +++ b/doc/processes/instrument_details/OSIRIS-Instrument-Details.md @@ -72,15 +72,3 @@ OSIRIS has the following devices under motion control: * single axis, "IN/OUT" device moving between two setpoints. 1. Sample Changer * **N.B.** For the avoidance of doubt: OSIRIS does not currently (September 2018) have a sample changer. There have been discussions about building one but, for the foreseeable future, there is no sample changer. - - -## OSIRIS SECI Configs ## -Over the years, OSIRIS has built up a significant collection of SECI configs. Not all of them are current (some may no longer be used, or used only infrequently). We will need to investigate how to convert them to IBEX configs. The config files are located in the folder `SECI\Configurations\` on the control server and have the extension `.conf`. Sub-configuration files have the extension `.comp` (component). The files with numbers as extensions (`.1`,`.2`,`.3`,etc.) are backups of the configuration and sub-configuration files. The current list of OSIRIS configs is listed on [trac](https://trac.isis.rl.ac.uk/ICP/wiki/OSIRIS). - - -## OSIRIS Genie Scripts ## -Similarly, OSIRIS has built up a significant collection of genie scripts over the years. Again, many scripts are old and may no longer be used regularly. Most runs on OSIRIS are controlled via scripts. There will be a need to convert some of these scripts to genie-python, but probably not all. - -UPDATE (11/01/2016) Franz has explained how the scripts are used: Usually, each time a user arrives to perform an experiment, they would create a new script by modifying an existing one and alter the appropriate parameters. There is NO common set of OSIRIS specific scripts and/or routines that are included in every new script. Therefore a conversion of OSIRIS scripts to Genie-Python couldn't be done en-masse. Although a few examples could be carefully chosen for users to work from. - -The current list of OSIRIS genie scripts is listed on [trac](https://trac.isis.rl.ac.uk/ICP/wiki/OSIRIS). diff --git a/doc/processes/instrument_details/PEARL-Instrument-Details.md b/doc/processes/instrument_details/PEARL-Instrument-Details.md index 518473813..33e9e6677 100644 --- a/doc/processes/instrument_details/PEARL-Instrument-Details.md +++ b/doc/processes/instrument_details/PEARL-Instrument-Details.md @@ -137,14 +137,3 @@ This is a weird `Servostep` box which contains a Galil 4000 series inside. It lo Compare with similar systems on GEM and POLARIS. There are some inaccessible front end jaws on PEARL controlled by the Galil, these are not used but must be kept open for operation. They are homed to the forward limit and seem to typically be kept about 4/5mm inside that position for running. This should be kept in mind when migrating the Galil. - -## PEARL SECI Configs ## -Document information about PEARL SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -PEARL_place_holder1.conf | - | dd/mm/yyyy | - | -PEARL_place_holder2.conf | - | dd/mm/yyyy | - | - -## PEARL Genie Scripts ## -Similarly, Document information about PEARL SECI Genie scripts here. diff --git a/doc/processes/instrument_details/POLARIS-Instrument-Details.md b/doc/processes/instrument_details/POLARIS-Instrument-Details.md index c64470b20..7140c0722 100644 --- a/doc/processes/instrument_details/POLARIS-Instrument-Details.md +++ b/doc/processes/instrument_details/POLARIS-Instrument-Details.md @@ -107,26 +107,6 @@ An evacuated furnace cell for measuring resistivity. Controlled by Eurotherms a ##### Note: CS155 Centre Stick ##### Not possible to control this device via software. It connects to the [Spellman](#polaris_noteSpellman) HV-PS. -## POLARIS SECI Configs ## -Document information about POLARIS SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | -----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---------------|----------| - POLARIS Base + Hydrothermal | Chopper, Vacuum, Jaws, Eurotherms Test | 03/02/2017 | - - POLARIS Base + Dilution Fridge | Chopper, Vacuum, Jaws, Oxford - Dilution Fridge | 15/12/2016 | - - POLARIS Base + Sample Changer + Eurotherms_matt | Chopper, Vacuum, Jaws, Eurotherms Test, Sample Changer | 12/12/2016 | - - POLARIS Base + Sample Changer + Eurotherms + Heliox | Chopper, Vacuum, Jaws, Eurotherms Test, Sample Changer, Heliox | 19/09/2016 | - - POLARIS Base | Chopper, Vacuum, Jaws | 30/11/2015 | - - POLARIS Base + Sample Changer + Eurotherms | Chopper, Vacuum, Jaws, Eurotherms Test, Sample Changer | 18/11/2015 | - - POLARIS Base + Sample Changer + Eurotherms + ITC_matt | Chopper, Vacuum, Jaws, Eurotherms Test, Sample Changer | 25/06/2015 | - - POLARIS Base + Eurotherms | Chopper, Vacuum, Jaws, Eurotherms Test | 05/06/2014 | - - POLARIS Base + Keithley (Voltage) + Eurotherms | Chopper, Vacuum, Jaws, Eurotherms Test, Keithley (Voltage) | 02/06/2014 | - - POLARIS Base + Keithley + Eurotherms | Chopper, Vacuum, Jaws, Eurotherms Test, Keithley | 25/03/2013 | - - delete | - | 01/10/2012 | - - POLARIS Base + Sample Changer | Chopper, Vacuum, Jaws, Sample Changer | 14/03/2012 | - - test | - | 10/11/2011 | - - -## POLARIS Genie Scripts ## -Similarly, document information about SECI Genie scripts currently used on POLARIS here. - -## POLARIS Notes ## \ No newline at end of file +s currently used on POLARIS here. + +## POLARIS Notes ## diff --git a/doc/processes/instrument_details/POLREF-Instrument-Details.md b/doc/processes/instrument_details/POLREF-Instrument-Details.md index 50b00fa61..37b7d1305 100644 --- a/doc/processes/instrument_details/POLREF-Instrument-Details.md +++ b/doc/processes/instrument_details/POLREF-Instrument-Details.md @@ -5,9 +5,6 @@ This page collects information that will be useful for the implementation of the ## Background & Timeline ## POLREF is a general purpose polarised neutron reflectometer, on TS2. The [POLREF](https://www.isis.stfc.ac.uk/Pages/polref.aspx) web page describes the background to the instrument. -## Control System ## -POLREF will migrate from the SECI control system to the IBEX control system in MMMMMMMM YYYY. - ## POLREF Equipment ## The equipment listed below is used on POLREF. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -75,9 +72,7 @@ Eurotherms are used to control temperature Orange Cryostat, CCR and Furnace devi ##### Note: Water Baths ##### 1. Julabo Water Bath (apparently the following Julabos: WB23 ) * consult the [Julabo commands](/specific_iocs/temp_controllers/julabo_commands.xlsx) spreadsheet for specific details of which set of commands is used by these water baths. -1. Haake Water Bath (no longer supported at ISIS) - 1. ~Haake N6 Water Bath. Haake has now been taken over by [ThermoFisher](https://www.thermofisher.com/uk/en/home/life-science/lab-equipment/water-baths-circulators-chillers.html). N6 model may be obsolete. Check existing SECI VI for logic and manual~. -1. ~See also [Water Baths](https://www.isis.stfc.ac.uk/Pages/Water-Baths.aspx) list~ +1. Haake Water Baths are no longer supported at ISIS ##### Note: KEPCO ##### 1. [Kepco BOP 100-10MG PSU](http://www.kepcopower.com/bophimod.htm). @@ -89,7 +84,7 @@ Eurotherms are used to control temperature Orange Cryostat, CCR and Furnace devi See also tickets [#1826](https://github.com/ISISComputingGroup/IBEX/issues/1826), [#2695](https://github.com/ISISComputingGroup/IBEX/issues/2695), [#2801](https://github.com/ISISComputingGroup/IBEX/issues/2801) and [#3176](https://github.com/ISISComputingGroup/IBEX/issues/3176). ##### Note: Hitachi ##### -Hitachi L-7100 HPLC pump (no longer supported at ISIS). ~Can't find L-7100 on [Hitachi web-site](http://www.hitachi-hightech.com/global/about/corporate/group/hhs (may be obsolete). Check existing SECI VI for logic and manual.~ +Hitachi pumps are no longer supported at ISIS ##### Note: JASCO HPLC Pump ##### [JASCO HPLC pump](https://jascoinc.com/products/chromatography/hplc/modules/hplc-pumps/) is a new (for ISIS) model of HPLC pump. Jasco pumps are replacing the old Hitachi pumps. @@ -98,10 +93,10 @@ Hitachi L-7100 HPLC pump (no longer supported at ISIS). ~Can't find L-7100 on [ ##### Note: Knauer ##### 1. Knauer K-6 Electric Valve Drive. [Knauer web site](https://www.knauer.net)
- * K-6 model appears to have been superseded. Check existing SECI VI for logic and manual. + * K-6 model appears to have been superseded. ##### Note: Knauer HPLC ##### -Knauer HPLC 1050 [Knauer HPLC 1050 is discontinued.](https://www.knauer.net/en/discontinued-smartline-pump-1050-successor-azura-p-61l/p14161). Check existing SECI VI for logic and manual. +Knauer HPLC 1050 [Knauer HPLC 1050 is discontinued.](https://www.knauer.net/en/discontinued-smartline-pump-1050-successor-azura-p-61l/p14161). ##### Note: LakeShore ##### 1. [Model 327](https://www.lakeshore.com/products/Cryogenic-Temperature-Controllers/Pages/default.aspx). Model 327 is not listed. Is it an obsolete model, or should it be Model-372? @@ -151,13 +146,3 @@ POLREF has the following devices under motion control: **Note:** (from original POLREF notes (may now be obsolete - check with Kathryn)) Note for when the time comes - check with the instrument scientist if the calibration function for the Danfysik is still used (allows for specific hysteresis curves to use between the limits in use), if it is, make sure we capture this functionality again - likely to be some SNL or a genie-python script might be able to do it instead. -## POLREF SECI Configs ## -Document information about POLREF SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -POLREF_place_holder1.conf | - | dd/mm/yyyy | - | -POLREF_place_holder2.conf | - | dd/mm/yyyy | - | - -## POLREF Genie Scripts ## -Similarly, Document information about POLREF SECI Genie scripts here. diff --git a/doc/processes/instrument_details/SANDALS-Instrument-Details.md b/doc/processes/instrument_details/SANDALS-Instrument-Details.md index f34319c99..9009d66ef 100644 --- a/doc/processes/instrument_details/SANDALS-Instrument-Details.md +++ b/doc/processes/instrument_details/SANDALS-Instrument-Details.md @@ -42,7 +42,7 @@ _**Note:**_ NIMROD does not have choppers either. {#sandals_noteJaws} ##### Note: Jaws ##### -SANDALS has a single set of jaws controlled by a [Parker controller](https://stfc365.sharepoint.com/sites/ISISExperimentControls/ICP%20Discussions/SANDALS/SANDALS_Parker_Controller.jpg), which is not currently controlled by SECI. There is no requirement to support the Parker system in IBEX, although it would be very convenient if such a thing were possible. +SANDALS has a single set of jaws controlled by a [Parker controller](https://stfc365.sharepoint.com/sites/ISISExperimentControls/ICP%20Discussions/SANDALS/SANDALS_Parker_Controller.jpg), which was not controlled by SECI. There is no requirement to support the Parker system in IBEX, although it would be very convenient if such a thing were possible. It is proposed to replace the Parker controller with a Galil DMC4040 controller (see [#3259](https://github.com/ISISComputingGroup/IBEX/issues/3259)). @@ -104,17 +104,6 @@ Experiments requiring pressure transducer. [Chell CCD100](http://www.chell.co.uk Experiments requiring source meter. [Keithley 2400 Source Meter](http://uk.tek.com/keithley-source-measure-units/keithley-smu-2400-series-sourcemeter).
See also [#1826](https://github.com/ISISComputingGroup/IBEX/issues/1826). -## SANDALS SECI Configs ## -Document information about SANDALS SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -SANDALS_place_holder1.conf | - | dd/mm/yyyy | - | -SANDALS_place_holder2.conf | - | dd/mm/yyyy | - | - -## SANDALS Genie Scripts ## -Similarly, Document information about SANDALS SECI Genie scripts here. - ## SANDALS Notes ## Add any notes about special items of equipment, setup or conditions on SANDALS that might impact the deployment and configuration of IBEX. diff --git a/doc/processes/instrument_details/SANS2D-Instrument-Details.md b/doc/processes/instrument_details/SANS2D-Instrument-Details.md index c8bdde5bf..e304f362a 100644 --- a/doc/processes/instrument_details/SANS2D-Instrument-Details.md +++ b/doc/processes/instrument_details/SANS2D-Instrument-Details.md @@ -146,18 +146,15 @@ Eurotherms are used to control temperature Orange Cryostat, CCR and Furnace devi 1. See also [#3784](https://github.com/ISISComputingGroup/IBEX/issues/3784) ##### Note: Hitachi ##### -Hitachi L-7100 HPLC pump (no longer supported at ISIS). ~Can't find L-7100 on [Hitachi web-site](http://www.hitachi-hightech.com/global/about/corporate/group/hhs (may be obsolete). Check existing SECI VI for logic and manual.~ - * Update (27-06-2019): Hitachi pumps are being retired. No longer any need to support them. See [#3780](https://github.com/ISISComputingGroup/IBEX/issues/3780) - * SANS2D will not be using Hitachi pumps in future. They will use the [Knauer](#note-knauer-hplc) or Jasco HPLC pumps. +Hitachi pumps are being retired. No longer any need to support them. SANS2D will not be using Hitachi pumps in future. They will use the [Knauer](#note-knauer-hplc) or Jasco HPLC pumps. ##### Note: Knauer ##### 1. Knauer K-6 Electric Valve Drive. [Knauer web site](https://www.knauer.net)
- * K-6 model appears to have been superseded. Check existing SECI VI for logic and manual. + * K-6 model appears to have been superseded. 1. See also [#3781](https://github.com/ISISComputingGroup/IBEX/issues/3781) ##### Note: Knauer HPLC ##### Knauer HPLC 1050 [Knauer HPLC 1050 is discontinued.](https://www.knauer.net/en/discontinued-smartline-pump-1050-successor-azura-p-61l/p14161). -1. Check existing SECI VI for logic and manual. 1. Support for Knauer HPLC 1050 is implemented via the following tickets: [#3262](https://github.com/ISISComputingGroup/IBEX/issues/3262), [#3782](https://github.com/ISISComputingGroup/IBEX/issues/3782), @@ -236,7 +233,7 @@ SANS2D has two baffle trolleys (in the vacuum tank). One for the front baffle, ##### Note: Beamstops ##### SANS2D has beamstops on the front and rear detectors 1. Front Detector: - * has a single beamstop, mounted on the detector trolley. Rotates in the plane of the detector array. The beamstop must not be moved when the detector is rotated (in SECI this requirement is implemented as a software inhibit). + * has a single beamstop, mounted on the detector trolley. Rotates in the plane of the detector array. The beamstop must not be moved when the detector is rotated (in SECI this requirement was implemented as a software inhibit). * has a strip beamstop, mounted on the detector trolley. Moves linearly across the face of the detector array. Primarily used for commissioning purposes (usually "parked" out of the way). 1. Rear Detector: * has three beamstops, mounted on a pillar attached to the detector trolley. Pillar moves linearly across the face of the detector array. The individual beam stops move independently up/down on the pillar. @@ -267,21 +264,11 @@ SANS2D has the following devices under motion control: Specialist requirements: 1. There is a requirement within SANS2D to inhibit the movement of the detectors when they are powered (the CAEN HV is ON) -## SANS2D SECI Configs ## -Document information about SANS2D SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -SANS2D_place_holder1.conf | - | dd/mm/yyyy | - | -SANS2D_place_holder2.conf | - | dd/mm/yyyy | - | - -## SANS2D Genie Scripts ## -Similarly, Document information about SANS2D SECI Genie scripts here. ## SANS2D Baldor Drives ## SANS2D has 5 guides on the front end. Each of these has a significant weight - ~3 tonnes. The motors used to lift the guides are servo motors. Galil controllers cannot provide sufficient power to motors capable of lifting such weights. As a result, some Baldor drives were introduced to provide the power required to lift these guides. They are digital motion controllers that can communicate with a control system and have settings in each controller to drive the motor. -However, ISIS uses them as pseudo dumb power amplifiers only. A Galil drives the axes like a servo - it provides an analogue signal to the Baldor to ask it to drive, but no core power. The Baldor drives the axes. Therefore, from the point of view of SECI or IBEX, the Baldor drives appear as Galil axes. +However, ISIS uses them as pseudo dumb power amplifiers only. A Galil drives the axes like a servo - it provides an analogue signal to the Baldor to ask it to drive, but no core power. The Baldor drives the axes. Therefore, from the point of view of IBEX, the Baldor drives appear as Galil axes. The Baldor drives do need to be set up – but this is done independently. Historically, this entire arrangement caused a lot of problems during commissioning. There is a bespoke homing routine in use with this setup (the need for such a thing has been questioned but, for now, a bespoke homing routine continues in use). diff --git a/doc/processes/instrument_details/SURF-Instrument-Details.md b/doc/processes/instrument_details/SURF-Instrument-Details.md index c4c9b20fe..e189ee110 100644 --- a/doc/processes/instrument_details/SURF-Instrument-Details.md +++ b/doc/processes/instrument_details/SURF-Instrument-Details.md @@ -60,7 +60,7 @@ Eurotherms are used to control temperature. 1. Grant Water Bath (no longer supported at ISIS) ~(apparently the following Grant water bath: WB27)~ * Update (25-06-2019): Grant water baths are no longer used. No longer any need to support them. See [#4457](https://github.com/ISISComputingGroup/IBEX/issues/4457) 1. Haake Water Bath (no longer supported at ISIS) - 1. ~Haake N6 Water Bath (apparently the following Haake water bath: WB9). Haake has now been taken over by [ThermoFisher](https://www.thermofisher.com/uk/en/home/life-science/lab-equipment/water-baths-circulators-chillers.html). N6 model may be obsolete. Check existing SECI VI for logic and manual.~ + 1. ~Haake N6 Water Bath (apparently the following Haake water bath: WB9). Haake has now been taken over by [ThermoFisher](https://www.thermofisher.com/uk/en/home/life-science/lab-equipment/water-baths-circulators-chillers.html). N6 model may be obsolete. * Update (25-06-2019): Haake water baths are no longer used. No longer any need to support them. See [#4456](https://github.com/ISISComputingGroup/IBEX/issues/4456) 1. See also [Water Baths](https://www.isis.stfc.ac.uk/Pages/Water-Baths.aspx) list @@ -77,7 +77,7 @@ Hitachi L-7100 HPLC pump (no longer supported at ISIS). ~Can't find L-7100 on [ ##### Note: Knauer ##### 1. Knauer K-6 Electric Valve Drive. [Knauer web site](https://www.knauer.net)
- * K-6 model appears to have been superseded. Check existing SECI VI for logic and manual. + * K-6 model appears to have been superseded. * See `C:\LabVIEW Modules\Drivers\Knauer Electric Valve Drive K-6\Documentation` for existing VI. * The Knauer K-6 Electric Valve Drive is (nearly) always used with the [Knauer HPLC pump](#note-knauer-hplc-pump). @@ -111,16 +111,11 @@ Nima Trough: SECI uses a manufacturer supplied VI (see `C:\LabVIEW Modules\Drive ##### Note: Peristaltic Pumps ##### 1. [Watson Marlow 323 Peristaltic Pump](http://www.watson-marlow.com/gb-en/range/watson-marlow/300-tube-pumps/323d/) -1. Check existing SECI VI for logic and manual: VI and manuals are located here: - * `C:\LabVIEW Modules\Drivers\Watson Marlow 323 Pump` ##### Note: Syringe Pumps ##### 1. [WPI Aladdin-1000 Syringe Pump](https://www.wpi-europe.com/products/pumps--microinjection/laboratory-syringe-pumps/al1000-220.aspx) 1. [WPI SP2xx Syringe Pump](https://www.wpi-europe.com/products/pumps--microinjection/laboratory-syringe-pumps.aspx) - check specific model. See also [#3261](https://github.com/ISISComputingGroup/IBEX/issues/3261) 1. The Watson Marlow and WPI Aladdin-1000 syringe pumps are the ones used most frequently on SURF (usually depending on which one is available). -1. Check existing SECI VIs for logic and manual: VIs and manuals are located here: - * `C:\LabVIEW Modules\Drivers\WPI Aladdin-1000 Syringe Pump` - * `C:\LabVIEW Modules\Drivers\WPI SP2XX Pumps` ## SURF Notes ## SURF has the following specialist panels/systems: @@ -141,14 +136,3 @@ SURF has the following devices under motion control: 1. transmission monitor 1. XYZ stage - -## SURF SECI Configs ## -Document information about SURF SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -SURF_place_holder1.conf | - | dd/mm/yyyy | - | -SURF_place_holder2.conf | - | dd/mm/yyyy | - | - -## SURF Genie Scripts ## -Similarly, Document information about SURF SECI Genie scripts here. diff --git a/doc/processes/instrument_details/SXD-Instrument-Details.md b/doc/processes/instrument_details/SXD-Instrument-Details.md index 6f55e8c59..60fc04e36 100644 --- a/doc/processes/instrument_details/SXD-Instrument-Details.md +++ b/doc/processes/instrument_details/SXD-Instrument-Details.md @@ -65,7 +65,7 @@ See also tickets [#1826](https://github.com/ISISComputingGroup/IBEX/issues/1826) {#sxd_note-kammrath-and-weiss} ##### Note: Kammrath and Weiss ##### -1. The Kammrath-Weiss tensile stress rig is controlled from a dedicated laptop running the manufacturer's software. SECI communicates with the PC to send/read values to/from the manufacturer's software. +1. The Kammrath-Weiss tensile stress rig is controlled from a dedicated laptop running the manufacturer's software. IBEX communicates with the PC to send/read values to/from the manufacturer's software using `LVREMOTE`. 1. [Kammrath and Weiss](https://www.kammrath-weiss.com/en/tensile-compression-modules/).
* See also ticket [#2681](https://github.com/ISISComputingGroup/IBEX/issues/2681) @@ -114,15 +114,4 @@ SXD has the following specialist panels/systems: SXD has the following devices under motion control: 1. goniometer -1. XYZ stage -## SXD SECI Configs ## -Document information about SXD SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -SXD_place_holder1.conf | - | dd/mm/yyyy | - | -SXD_place_holder2.conf | - | dd/mm/yyyy | - | - -## SXD Genie Scripts ## -Similarly, Document information about SXD SECI Genie scripts here. diff --git a/doc/processes/instrument_details/TOSCA-Instrument-Details.md b/doc/processes/instrument_details/TOSCA-Instrument-Details.md index 8cde22272..a32fd16a4 100644 --- a/doc/processes/instrument_details/TOSCA-Instrument-Details.md +++ b/doc/processes/instrument_details/TOSCA-Instrument-Details.md @@ -4,9 +4,6 @@ This page collects information that will be useful for the implementation of the ## Background & Timeline ## TOSCA is an indirect geometry spectrometer, on TS1. The [TOSCA](https://www.isis.stfc.ac.uk/Pages/TOSCA.aspx) web page describes the background to the instrument. -## Control System ## -TOSCA will migrate from the SECI control system to the IBEX control system in late October 2018 (prior to Cycle 2018/03). - ## TOSCA Equipment ## The equipment listed below is used on TOSCA. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -80,13 +77,3 @@ TOSCA has the following specialist panels/systems: TOSCA has the following devices under motion control: 1. XY beam scanner (2 axis GALIL motor - this GALIL moves about and is not permanently on TOSCA). - -## TOSCA SECI Configs ## -Document information about TOSCA SECI configs here. - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -Standard + Rotation Stage.conf | - | 25/10/2018 | - | - -## TOSCA Genie Scripts ## -Similarly, Document information about TOSCA SECI Genie scripts here. diff --git a/doc/processes/instrument_details/VESUVIO-Instrument-Details.md b/doc/processes/instrument_details/VESUVIO-Instrument-Details.md index b843cfd1d..8989800c5 100644 --- a/doc/processes/instrument_details/VESUVIO-Instrument-Details.md +++ b/doc/processes/instrument_details/VESUVIO-Instrument-Details.md @@ -73,47 +73,6 @@ Experiments requiring pressure transducer. [Chell CCD100](http://www.chell.co.uk ##### Note: Keithley ##### Experiments requiring source meter. [Keithley 2400 Source Meter](http://uk.tek.com/keithley-source-measure-units/keithley-smu-2400-series-sourcemeter) -## VESUVIO SECI Configs ## -Over the years, VESUVIO is likely to have accumulated a significant collection of SECI configs. Not all of them are current (some may no longer be used, or used only infrequently). We will need to investigate how to convert them to IBEX configs. -The config files are located in the folder `SECI\Configurations\` on the VESUVIO control server and have the extension `.conf`. Sub-configuration files have the extension `.comp` (component). The files with numbers as extensions (`.1`, `.2`, `.3`,etc.) are backups of the configuration and sub-configuration files. - - - -| Configuration Name | Sub-Configurations | Last Accessed | Required | ------------- |-------------------------------------| ------------- | ------------- | -VESUVIO_withTLCCR__31mar2015 | Sub_EVS_Base, Sub_EVS_Eurotherm_CCR | 16/09/2016 | - | -highTfurnace__oct2015 | - | 12/10/2015 | - | -EVS_Huber | Eurotherm | 09/09/2015 | - | -VESUVIO_Nbfurnace__15june2015 | Eurotherm | 15/06/2015 | - | -VESUVIO_emptyInstrument__26mar2015 | Eurotherm | 26/03/2015 | - | -VESUVIO_emptyInstrument__16mar2015 | Eurotherm | 16/03/2015 | - | -EVS Ambient | Eurotherm | 22/08/2014 | - | -tempalooza | Eurotherm | 13/06/2014 | - | -20130425 - EVS Ambient | - | 26/04/2013 | - | -rotating cs + cryo | - | 28/07/2011 | - | -heaters on sample 0 -100C | - | 28/07/2011 | - | -EVS Heated Can | - | 22/07/2011 | - | -EVS Cryostat | - | 22/07/2011 | - | -EVS Ambient + Platinums | - | 22/07/2011 | - | -Calibration | - | 31/03/2011 | - | -U Foil Calibration | - | 14/02/2011 | - | -rotating prisma cs | - | 14/02/2011 | - | -rotating prisma cs + cryo | - | 14/02/2011 | - | -rotating cs | - | 14/02/2011 | - | -rotating ccr | - | 14/02/2011 | - | -Neocera | - | 14/02/2011 | - | -Kelvinox | - | 14/02/2011 | - | -EVS Water Bath | - | 14/02/2011 | - | -EVS Kelvinox | - | 14/02/2011 | - | -EVS CCR | - | 14/02/2011 | - | -EVS Ambient + Cryostat | - | 14/02/2011 | - | -EVS 4K TLCCR | - | 14/02/2011 | - | -ChipIR2 | - | 14/02/2011 | - | -ChipIR | - | 14/02/2011 | - | - -## VESUVIO Genie Scripts ## -Similarly, VESUVIO has built up a significant collection of genie scripts over the years. Again, many scripts are old and may no longer be used regularly. There will be a need to convert some of these scripts to genie-python, but probably not all. - ## Tested IOCs ## | What | When | Notes | diff --git a/doc/processes/instrument_details/WISH-Instrument-Details.md b/doc/processes/instrument_details/WISH-Instrument-Details.md index 95e04c2f7..d3cefdcd4 100644 --- a/doc/processes/instrument_details/WISH-Instrument-Details.md +++ b/doc/processes/instrument_details/WISH-Instrument-Details.md @@ -4,9 +4,6 @@ This page collects information that will be useful for the implementation of the ## Background & Timeline ## WISH is a long-wavelength diffractometer, on TS2. The [WISH](https://www.isis.stfc.ac.uk/Pages/WISH.aspx) web page describes the background to the instrument. -## Control System ## -WISH has migrated to IBEX from SECI - ## WISH Equipment ## The equipment listed below is used on WISH. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -156,15 +153,3 @@ WISH also tends to borrow things from other instruments. Commonly used equipment 1. IRIS Baratron Gas cell 1. Automatic needle valve - see note on [ticket #6695](https://github.com/ISISComputingGroup/IBEX/issues/6695) for investigation, [ticket #4240](https://github.com/ISISComputingGroup/IBEX/issues/4240) for IOC implementation and [ticket #6777](https://github.com/ISISComputingGroup/IBEX/issues/6777) for OPI. -## WISH SECI Configs ## -Document information about WISH SECI configs here. - -Note: Most of WISH configs revolve around the WISH base config. This has been created as a component in IBEX and subsequent components for each thing that is added to the WISH base config should be added as components (i.e. the Teslatron, Strain Cell, Rotation stages etc.) - -Configuration Name | Sub-Configurations | Last Accessed | Required | ----------------------------------------|----------------------------------------------------|---------------|----------| -WISH_base.conf | WISH_base.comp | 01/07/2021 | - | -WISH_base + Oxford Cryostat.conf | WISH_base.comp, Oxford - teslatron.comp | "" | - | - -## WISH Genie Scripts ## -Similarly, Document information about WISH SECI Genie scripts here. diff --git a/doc/processes/instrument_details/ZOOM-Instrument-Details.md b/doc/processes/instrument_details/ZOOM-Instrument-Details.md index 687665da9..6c4f02587 100644 --- a/doc/processes/instrument_details/ZOOM-Instrument-Details.md +++ b/doc/processes/instrument_details/ZOOM-Instrument-Details.md @@ -6,9 +6,6 @@ The [ZOOM](http://www.isis.stfc.ac.uk/instruments/zoom/zoom8060.html) web page d The ZOOM shutter is due to open in February 2017 (see Zoom plan 28th May 2016). -## Control System ## -ZOOM will use the IBEX control system. - ## ZOOM Equipment ## The equipment listed below is to be used on ZOOM. Please add new information (e.g. new items of equipment, new notes, information about drivers, etc. to this table). @@ -290,8 +287,7 @@ As used on: [LARMOR](LARMOR-Instrument-Details)
{#zoom_noteHitachi} ##### Note: Hitachi ##### -Hitachi L-7100 HPLC pump (no longer supported at ISIS). ~Can't find L-7100 on [Hitachi web-site](http://www.hitachi-hightech.com/global/about/corporate/group/hhs) (may be obsolete). Check existing SECI VI for logic and manual: both VI and manual are located here: `C:\LabVIEW Modules\Drivers\Hitachi L-7100`.~ - * Update (27-06-2019): Hitachi pumps are no longer used. No longer any need to support them. See [#3780](https://github.com/ISISComputingGroup/IBEX/issues/3780). +Hitachi pumps are no longer used. No longer any need to support them. See [#3780](https://github.com/ISISComputingGroup/IBEX/issues/3780). {#zoom_noteHaake} ##### Note: Thermo Scientific (Haake) ##### @@ -371,4 +367,4 @@ Details of [Closed-Cycle Refrigerators](http://www.isis.stfc.ac.uk/sample-enviro {#zoom_note7p5TMagnet} ##### Note: 7.5T Magnet ##### -Model: [7.5T Magnet](https://www.isis.stfc.ac.uk/Pages/75T-Magnet.aspx) \ No newline at end of file +Model: [7.5T Magnet](https://www.isis.stfc.ac.uk/Pages/75T-Magnet.aspx) From e7764d65b7e2ed02b07de9a3f5c4fbdb78659169 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 15:47:27 +0100 Subject: [PATCH 39/60] attempt to fix cross references on OFFSPEC docs --- .../OFFSPEC-Instrument-Details.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md b/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md index fae29b67b..a9eed6fa6 100644 --- a/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md +++ b/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md @@ -83,7 +83,7 @@ Nima Trough | ??? | Trough | ??? | | [see Nima Trough note](#note-nima-trough) [KEPCO](http://www.kepcopower.com/bop.htm) | BOP 100-10MG | Bi-Polar Power Supply | RS232 | #187 |[see Kepco note](#note-kepco) [KEPCO](http://www.kepcopower.com/bop.htm) | BIT 4886 | I/F card | GPIB, RS-232 | |[see Kepco note](#note-kepco) [KEPCO](http://www.kepcopower.com/bop.htm) | BOP 50-2M-4886 | Bi-Polar Power Supply | RS232 | |[see Kepco note](#note-kepco) -Delta-Elektronika | SM300-5 | PSU | ??? | | [see Delta Elektronika note](#note-delta-elektronika ) +Delta-Elektronika | SM300-5 | PSU | ??? | | [see Delta Elektronika note](#note-delta-elektronika) Thurlby | EX355P | PSU | ??? | | [see Thurlby note](#note-thurlby) Thurlby | TGA1240 | Arbitrary Waveform Generator | ??? | | [see Thurlby note](#note-thurlby) Thurlby | TSX3510P | PSU | ??? | | [see Thurlby note](#note-thurlby) @@ -95,18 +95,23 @@ Watson Marlow | 323 | Peristaltic Pump | ??? | | [see Peristaltic Pumps note](#n WPI | Aladdin-1000 | Syringe Pump | ??? | | [see Syringe Pumps note](#note-syringe-pumps) WPI | SP2xx | Syringe Pump | ??? | | [see Syringe Pumps note](#note-syringe-pumps) +{#note-dae} ##### Note: DAE ##### See multi-detector and single-detector below. +{#note-chopper} ##### Note: Choppers ##### OFFSPEC has a Mk3 chopper.
+{#note-jaws} ##### Note: Jaws ##### Provide information about OFFSPEC jaws. +{#note-vacuum} ##### Note: Vacuum System ##### TPG300 support is implemented via [#216](https://github.com/ISISComputingGroup/IBEX/issues/216) and [#2063](https://github.com/ISISComputingGroup/IBEX/issues/2063) +{#note-eurotherm} ##### Note: Eurotherm ##### [Eurotherms](http://www.facilities.rl.ac.uk/isis/computing/ICPdiscussions/OFFSPEC/OFFSPEC_Eurotherms.jpg) are used to control temperature Orange Cryostat, CCR and Furnace devices. @@ -122,6 +127,7 @@ OFFSPEC uses Julabo water baths & re-circulating coolers 1. [Kepco BIT 4886](http://www.kepcopower.com/bit.htm) is an interface card for Kepco bi-polar ([BOP](http://www.kepcopower.com/bop.htm)) power supplies. 1. [KEPCO BOP 50-2M-4886 PSU](http://www.kepcopower.com/bophimod.htm).
See also [#188](https://github.com/ISISComputingGroup/IBEX/issues/188) & [#200](https://github.com/ISISComputingGroup/IBEX/issues/200) +{#note-keithley} ##### Note: Keithley ##### 1. [Keithley 2400 Series Source Meter](https://uk.tek.com/keithley-source-measure-units/keithley-smu-2400-series-sourcemeter).
See also tickets [#1826](https://github.com/ISISComputingGroup/IBEX/issues/1826), [#2695](https://github.com/ISISComputingGroup/IBEX/issues/2695), [#2801](https://github.com/ISISComputingGroup/IBEX/issues/2801) and [#3176](https://github.com/ISISComputingGroup/IBEX/issues/3176). @@ -129,20 +135,24 @@ See also tickets [#1826](https://github.com/ISISComputingGroup/IBEX/issues/1826) ##### Note: Hitachi ##### Hitachi L-7100 HPLC pump (no longer supported at ISIS). ~Can't find L-7100 on [Hitachi web-site](http://www.hitachi-hightech.com/global/about/corporate/group/hhs (may be obsolete). Check existing SECI VI for logic and manual.~ +{#note-jasco-hplc-pump} ##### Note: JASCO HPLC Pump ##### [JASCO HPLC pump](https://jascoinc.com/products/chromatography/hplc/modules/hplc-pumps/) is a new (for ISIS) model of HPLC pump. * See `C:\LabVIEW Modules\Drivers\Jasco PU-4180 HPLC Pump\Documentation` for documentation. * See also [#3743](https://github.com/ISISComputingGroup/IBEX/issues/3743) & [#3923](https://github.com/ISISComputingGroup/IBEX/issues/3923) +{#note-knauer} ##### Note: Knauer ##### 1. Knauer K-6 Electric Valve Drive. [Knauer web site](https://www.knauer.net)
* K-6 model appears to have been superseded. Check existing SECI VI for logic and manual. * Support now implemented (28-03-2019). See [#3781](https://github.com/ISISComputingGroup/IBEX/issues/3781). +{#note-knauerHPLC} ##### Note: Knauer HPLC ##### Knauer HPLC 1050 [Knauer HPLC 1050 is discontinued.](https://www.knauer.net/en/discontinued-smartline-pump-1050-successor-azura-p-61l/p14161). Check existing SECI VI for logic and manual. 1. Support now implemented (04-01-2019). See [#3262](https://github.com/ISISComputingGroup/IBEX/issues/3262). +{#note-nima-trough} ##### Note: Nima Trough ##### Nima Trough: SECI used a manufacturer supplied VI. We may need to do the same in IBEX (via lvDCOM).
* **Note:** NIMA Technologies Ltd now seems to be part of [Biolin Scientific](https://www.biolinscientific.com/ksvnima).
@@ -150,9 +160,11 @@ Nima Trough: SECI used a manufacturer supplied VI. We may need to do the same i * The manufacturer has made additional software available for download. A copy of this software is located in `\\isis\shares\ISIS_Experiment_Controls\NIMA Trough\Nima_TR8.1.zip`. * Support now implemented (25-05-2019). See [#3783](https://github.com/ISISComputingGroup/IBEX/issues/3783) +{#note-delta-elektronika} ##### Note: Delta-Elektronika ##### 1. Delta-Elektronika SM300-5 is a DC power supply. It is listed on page for [Delta-Elektronika SM1500 series](http://www.delta-elektronika.nl/en/products/dc-power-supplies-1500w-sm1500-series.html) products. +{#note-thurlby} ##### Note: Thurlby ##### [Thurlby Thandar Instruments](https://www.aimtti.com/) 1. [Thurlby Thandar Instruments EX355P PSU](https://www.aimtti.com/product-category/dc-power-supplies/aim-ex-rseries) @@ -162,24 +174,29 @@ Nima Trough: SECI used a manufacturer supplied VI. We may need to do the same i 1. [Thurlby TGA1240 Arbitrary Waveform Generator](https://www.aimtti.com/product-category/arbitrary-generators/aim-tga1240series) 1. [Thurlby TSX3510P DC Power Supply](https://www.aimtti.com/product-category/dc-power-supplies/aim-tsxseries) +{#note-oxford-instruments} ##### Note: Oxford Instruments ##### 1. Support for OI ITC503 created as part of [#2593](https://github.com/ISISComputingGroup/IBEX/issues/2593) 1. Support for Mercury Temperature Controller was created as part of [#2840](https://github.com/ISISComputingGroup/IBEX/issues/2840) +{#note-linkam} ##### Note: Linkam ##### There are VIs for this.
See also [Linkam T95 controller](http://www.linkam.co.uk/t95-system-controllers/) and tickets [#1106](https://github.com/ISISComputingGroup/IBEX/issues/1106), [#1496](https://github.com/ISISComputingGroup/IBEX/issues/1496), [#1509](https://github.com/ISISComputingGroup/IBEX/issues/1509). +{#note-peristaltic-pumps} ##### Note: Peristaltic Pumps ##### 1. [Watson Marlow 323 Peristaltic Pump](http://www.watson-marlow.com/gb-en/range/watson-marlow/300-tube-pumps/323d/) * Support now implemented (14-08-2019). See [#3786](https://github.com/ISISComputingGroup/IBEX/issues/3786) +{#note-syringe-pumps} ##### Note: Syringe Pumps ##### 1. [WPI Aladdin-1000 Syringe Pump](https://www.wpi-europe.com/products/pumps--microinjection/laboratory-syringe-pumps/al1000-220.aspx) * Support now implemented (20-06-2019). See [#3787](https://github.com/ISISComputingGroup/IBEX/issues/3787) 1. [WPI SP2xx Syringe Pump](https://www.wpi-europe.com/products/pumps--microinjection/laboratory-syringe-pumps.aspx) - check specific model. * Support now implemented (05-07-2018). See [#3261](https://github.com/ISISComputingGroup/IBEX/issues/3261) +{#note-tektronix} ##### Note: Tektronix ##### 1. Tektronix Function Generator: [AFG 3021B](https://www.tek.com/datasheet/afg3000-series) * See also [#237](https://github.com/ISISComputingGroup/IBEX/issues/237) From c5f4cbd35de85726b88340a87ad0dc957735586d Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 16:44:38 +0100 Subject: [PATCH 40/60] Remove SECI from specific IOC docs --- .../cryogenics/2T-3D-Vector-magnet.md | 6 +-- .../cryogenics/Mercury-Heliox.md | 2 +- doc/specific_iocs/cryogenics/MercuryiTC.md | 2 +- doc/specific_iocs/cryogenics/Triton.md | 2 +- .../jaws/GEM-Beamscraper-Jaws.md | 39 +------------------ doc/specific_iocs/motors/McLennan-motors.md | 4 +- doc/specific_iocs/plcs/SANS2D-vacuum-PLC.md | 2 +- doc/specific_iocs/temp_controllers/Julabo.md | 4 +- 8 files changed, 12 insertions(+), 49 deletions(-) diff --git a/doc/specific_iocs/cryogenics/2T-3D-Vector-magnet.md b/doc/specific_iocs/cryogenics/2T-3D-Vector-magnet.md index 36e9f3e7a..478d55c34 100644 --- a/doc/specific_iocs/cryogenics/2T-3D-Vector-magnet.md +++ b/doc/specific_iocs/cryogenics/2T-3D-Vector-magnet.md @@ -37,7 +37,7 @@ IP address : DHCP reserved and visible on front screen when connected to ISIS ne ### Rotation Stage -Standard unit controlled by a Galil axis on both SECI and IBEX instruments. Details: +Standard unit controlled by a Galil axis. Details: * +- 370 degrees * Motor with encoder @@ -50,7 +50,7 @@ When this magnet was last installed on ZOOM, one of the slit axes was used for t ### Needle Valve -This is a motorised valve which is controlled via an analogue output from a Galil on SECI instruments (POLREF at least) and a Thurlby-Thandar Instruments EX355P benchtop PSU on IBEX instruments (LARMOR and ZOOM at least). There are two front panel VIs for this purpose, one for each scenario: `Vector-control-v16isis.vi` for the TTi-EX355P controlled valve and `Vector-control-v16isis-Galil-Valve.vi` for analogue output controlled valve. Both are in the SourceSafe location mentioned above: `\LabVIEW Modules\Drivers\Scientific Instruments\3D Magnet\Source Code\`. +This is a motorised valve. Historically this has been controlled via an analogue output from a Galil on POLREF and a Thurlby-Thandar Instruments EX355P benchtop PSU on LARMOR and ZOOM. There are two front panel VIs for this purpose, one for each scenario: `Vector-control-v16isis.vi` for the TTi-EX355P controlled valve and `Vector-control-v16isis-Galil-Valve.vi` for analogue output controlled valve. Both are in the SourceSafe location mentioned above: `\LabVIEW Modules\Drivers\Scientific Instruments\3D Magnet\Source Code\`. If the PSU is to be used, first it will need to be configured via its own setup VI located in `\LabVIEW Modules\Drivers\Thurlby EX355P\TH EX355P - System Functions.llb\TH EX355P - Setup Dialog.vi`, with the port from the `settings.txt` file mentioned above. It will then be possible to check the communication to the PSU via its own front panel VI here: `\LabVIEW Modules\Drivers\Thurlby EX355P\TH EX355P - System Functions.llb\TH EX355P - Front Panel 1.vi`. This VI and the main magnet VI cannot be run simultaneously. @@ -64,4 +64,4 @@ The Lakeshore 336 is an Ethernet device and should therefore be connected to the ### Schematic of system -![Schematic of system](3d_vector_magnet_schematic.png) \ No newline at end of file +![Schematic of system](3d_vector_magnet_schematic.png) diff --git a/doc/specific_iocs/cryogenics/Mercury-Heliox.md b/doc/specific_iocs/cryogenics/Mercury-Heliox.md index c2785e046..d358b5996 100644 --- a/doc/specific_iocs/cryogenics/Mercury-Heliox.md +++ b/doc/specific_iocs/cryogenics/Mercury-Heliox.md @@ -155,7 +155,7 @@ Example ramp (260mK-1.8K in steps of 20mK) demonstrating these instabilities (no ![](mercury_heliox_ramp_example.PNG) -There is nothing the driver does in either SECI or IBEX which can affect the stability. Consult cryogenics to check outer cryostat performance, PID parameters, flow rates etc. +There is nothing the driver does in IBEX which can affect the stability. Consult cryogenics to check outer cryostat performance, PID parameters, flow rates etc. ### Regeneration starts when I set temperature setpoint = 0 diff --git a/doc/specific_iocs/cryogenics/MercuryiTC.md b/doc/specific_iocs/cryogenics/MercuryiTC.md index 73c8a3cb6..5003ed228 100644 --- a/doc/specific_iocs/cryogenics/MercuryiTC.md +++ b/doc/specific_iocs/cryogenics/MercuryiTC.md @@ -39,7 +39,7 @@ There is a section on each below as well as how to set the communication setting {#mercury_itc_setup} #### Setup -To activate a card you must set the related IOC macro (note that this is different from in SECI where there was a separate VI to talk to each individual card e.g. Mercury_1_Temp_4 to talk to the 4th card as a temperature card). The following macros set the for the possible IOC slot: +To activate a card you must set the related IOC macro. The following macros set the for the possible IOC slot: | Macro | IOC Name | | ---- | -------- | diff --git a/doc/specific_iocs/cryogenics/Triton.md b/doc/specific_iocs/cryogenics/Triton.md index 863d017ad..520453861 100644 --- a/doc/specific_iocs/cryogenics/Triton.md +++ b/doc/specific_iocs/cryogenics/Triton.md @@ -2,7 +2,7 @@ ## Naming -Technically, "Triton" refers to the gas handling apparatus. This is what IBEX and SECI talk to. When setting up a triton, scientists may refer to it as a "Kelvinox". This is the technical name for the dilution insert, which is controlled by the triton gas handling apparatus. +Technically, "Triton" refers to the gas handling apparatus. This is what IBEX talks to. When setting up a triton, scientists may refer to it as a "Kelvinox". This is the technical name for the dilution insert, which is controlled by the triton gas handling apparatus. To avoid confusion: all dilution fridges currently in use at ISIS are controlled by Triton gas handling systems, with one exception: the ICE fridge used on the muon beamlines. diff --git a/doc/specific_iocs/motor_extensions/jaws/GEM-Beamscraper-Jaws.md b/doc/specific_iocs/motor_extensions/jaws/GEM-Beamscraper-Jaws.md index 3c47824ea..f418cd386 100644 --- a/doc/specific_iocs/motor_extensions/jaws/GEM-Beamscraper-Jaws.md +++ b/doc/specific_iocs/motor_extensions/jaws/GEM-Beamscraper-Jaws.md @@ -2,43 +2,6 @@ The GEM "Beamscraper" jaw set is unique to GEM. The four blades move independently and are all driven by a LinMot. Some calibration is required between the demanded position and the steps sent to the controller. For North/South this calibration is linear, for East/West it is quadratic. -## Control under SECI - -LinMot motor resolution: 0.01953125 mm/steps (Mistakenly labelled as steps/mm in the VI) - -Jaw | Offset | Read Calibration Curve | Write Calibration Curve ----- | -------| ------ | ---------- -North | 2710 | `x + 0.025*x` | `x - 0.025*x` -South | 1530 | `x + 0.025*x` | `x - 0.025*x` -East | 2200 | `(-0.12038 + 0.06452 * x + 0.02998 * x**2)/0.9` | `(x - 0.1*x)` , `((-0.06452 + sqrt(0.06452**2 + 4*0.02998*(0.12038 + x))) / (2*0.02998))` -West | 2200 | `(-0.12038 + 0.06452 * x + 0.02998 * x**2)/0.9` | `(x - 0.1*x)` , `((-0.06452 + sqrt(0.06452**2 + 4*0.02998*(0.12038 + x))) / (2*0.02998))` - -Where there are two equations the first equation calculates the x used in the second equation where there are two. - -The motor resolution/offset values are used as below: - -Read/Write | Axis | Equation ----------- | ---- | -------- -Write | South | `OFF + (x / MRES)` -Write | N/E/W | `OFF - (x / MRES)` -Read | South | `(x - OFF) * MRES)` -Read | N/E/W | `(OFF - x) * MRES)` - -Where x has been calculated from the calibration curves above. - -The setpoints are all set to 5 when home is pressed. There is some tolerance checking, tolerance is set to 1.00, and is based on the presented value. - -The limits for the values that the user can set are: - -Axis | Min | Max ---- | --- | --- -H Gap | 0.2 | 25 -V Gap | 0.2 | 40 -North | 0.1 | 20 -South | 0.1 | 20 -West | 0.1 | 12.5 -East | 0.1 | 12.5 - ## Control under IBEX The calibration curves under IBEX have been simplified to: @@ -61,4 +24,4 @@ Jaw | New Offset | New Motor Resolution South | `-SECI_OFF * SECI_MRES` | `SECI_MRES` N/E/W | `SECI_OFF * SECI_MRES` | `-SECI_MRES` -Tolerance and limits have been included in IBEX, the homing has not. \ No newline at end of file +Tolerance and limits have been included in IBEX, the homing has not. diff --git a/doc/specific_iocs/motors/McLennan-motors.md b/doc/specific_iocs/motors/McLennan-motors.md index 6e21099cc..7d6832a3c 100644 --- a/doc/specific_iocs/motors/McLennan-motors.md +++ b/doc/specific_iocs/motors/McLennan-motors.md @@ -21,12 +21,12 @@ Instructions on how to convert a **LabVIEW Mclennan ini file** are at the end of ## Behaviour ### Motor Resolution -The motor resolution is set with the *MSTP***n** IOC macros and in units of `steps/mm` (same as in SECI/LabVIEW), this will be inverted by the IOC internally as the EPICS motor record `MRES` field uses the inverse `mm/step`. +The motor resolution is set with the *MSTP***n** IOC macros and in units of `steps/mm`, this will be inverted by the IOC internally as the EPICS motor record `MRES` field uses the inverse `mm/step`. ### Encoder Resolution The encoder ratio rather than encoder resolution is set with the *ERES***n** IOC macros, this is a string like `400/4096` and bears no direct relation to the EPICS motor record `ERES`. As the Mclennan driver pretends to be open loop (no encoder present as per `MSTA` field) whatever mode it is running in, the motor record `ERES` is not actually used and is set to `0` in the `st.cmd` and will then display as the same value as motor record `MRES` when later viewed. So ignore the encoder resolution value displayed on the motor record screen. -The encoder ratio written `M/E` is providing `motor_steps_per_revolution / encoder_steps_per_revolution`, in SECI/LabVIEW this was referred to as `Numerator / Demoninator`. So `actual_position_steps = encoder_steps_readback * encoder_ratio`. For closed loop (encoder feedback) controller mode to work this ratio needs to be correct so that `commanded_motor_steps_moved = encoder_steps_moved * encoder_ratio`, if the ratio isn't right the motor will fail to get position leading to many retries and an error. It is possible to work out the ratio by e.g. going to motor console (PuTTY/hterm), doing a small MR relative move and comparing command position (CP) and actual position (AP). `dbior` command on an ioc window now shows these values, as does the `QP` command at the motor low level serial interface. The Raw encoder steps is `IP` or `Input Position` which is scaled by encoder ratio to give actual (AP) position. If encoder and motor move in opposite directions, add a minus sign to encoder ratio. +The encoder ratio written `M/E` is providing `motor_steps_per_revolution / encoder_steps_per_revolution`, in the past (e.g. under SECI/LabVIEW) this was referred to as `Numerator / Demoninator`. So `actual_position_steps = encoder_steps_readback * encoder_ratio`. For closed loop (encoder feedback) controller mode to work this ratio needs to be correct so that `commanded_motor_steps_moved = encoder_steps_moved * encoder_ratio`, if the ratio isn't right the motor will fail to get position leading to many retries and an error. It is possible to work out the ratio by e.g. going to motor console (PuTTY/hterm), doing a small MR relative move and comparing command position (CP) and actual position (AP). `dbior` command on an ioc window now shows these values, as does the `QP` command at the motor low level serial interface. The Raw encoder steps is `IP` or `Input Position` which is scaled by encoder ratio to give actual (AP) position. If encoder and motor move in opposite directions, add a minus sign to encoder ratio. ### Velocity The McLennan motor velocity is set with the *VELO***n** IOC macros, the value set is in `mm/second`, same units as EPICS motor record uses. diff --git a/doc/specific_iocs/plcs/SANS2D-vacuum-PLC.md b/doc/specific_iocs/plcs/SANS2D-vacuum-PLC.md index a0b5e975b..0ebfec4d1 100644 --- a/doc/specific_iocs/plcs/SANS2D-vacuum-PLC.md +++ b/doc/specific_iocs/plcs/SANS2D-vacuum-PLC.md @@ -2,7 +2,7 @@ ## Vacuum Status -Currently, we get a tank vacuum status from the PLC. This was not available in SECI. There are 4 different states, ATMOSPHERE, AT VACUUM, VAC DOWN, VENTING, but if we cannot get a state the PV goes into major alarm and has the string ERROR: STATUS UNKNOWN. This is displayed on the OPI in both the regular and advanced tab. +Currently, we get a tank vacuum status from the PLC. There are 4 different states, ATMOSPHERE, AT VACUUM, VAC DOWN, VENTING, but if we cannot get a state the PV goes into major alarm and has the string ERROR: STATUS UNKNOWN. This is displayed on the OPI in both the regular and advanced tab. ## Front beamstop inhibit diff --git a/doc/specific_iocs/temp_controllers/Julabo.md b/doc/specific_iocs/temp_controllers/Julabo.md index 793b82d28..7e4269d25 100644 --- a/doc/specific_iocs/temp_controllers/Julabo.md +++ b/doc/specific_iocs/temp_controllers/Julabo.md @@ -1,6 +1,6 @@ # Julabo -Julabo is a temperature control unit. There are many different versions. The commands for each model are slightly different. When migrating an instrument, care must be taken to check exactly which command set it is using under SECI and to configure an equivalent command set in IBEX. A spreadsheet of LabVIEW settings against command set is in [this spreadsheet](julabo_commands.xlsx). +Julabo is a temperature control unit. There are many different versions. The commands for each model are slightly different. A spreadsheet of previous LabVIEW settings against command set is in [this spreadsheet](julabo_commands.xlsx). The IOC copes with these variations in commands by making 4 commands configurable via macros: - `READ_POWER_CMD_NUMBER` configures the command used to read power. This macro should be the 2-digit number at the end of the read power command in the spreadsheet above (for the relevant model of Julabo). @@ -32,4 +32,4 @@ null modem: depends on Julabo If none of the settings above allow you to connect ## Troubleshooting -The Julabo hardware supports having several different setpoints and can control on any of them, ibex always uses setpoint 1. If the Julabo hardware is set to e.g. use setpoint 2 then ibex will think all is fine and send/read the setpoint 1 ok, but the Julabo hardware will how a different setpoint value (setpoint 2) on its screen. A technician will need to go into the configuration menu on the device and change it to use setpoint 1 \ No newline at end of file +The Julabo hardware supports having several different setpoints and can control on any of them, ibex always uses setpoint 1. If the Julabo hardware is set to e.g. use setpoint 2 then ibex will think all is fine and send/read the setpoint 1 ok, but the Julabo hardware will how a different setpoint value (setpoint 2) on its screen. A technician will need to go into the configuration menu on the device and change it to use setpoint 1 From c8b974e35d455373a2aad3d3661ef3241f305d43 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 12:58:46 +0100 Subject: [PATCH 41/60] Update Calibration-Files.md --- doc/system_components/configurations/Calibration-Files.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/doc/system_components/configurations/Calibration-Files.md b/doc/system_components/configurations/Calibration-Files.md index 3baf10297..c1dee074d 100644 --- a/doc/system_components/configurations/Calibration-Files.md +++ b/doc/system_components/configurations/Calibration-Files.md @@ -62,12 +62,6 @@ You will then need to push these files to the common config area and update the If the common calibration file change and they need updating on all instruments, then you can run the [calibration update script which can be found in ibex utils](https://github.com/ISISComputingGroup/ibex_utils/blob/master/installation_and_upgrade/calibration_files_updater.py) -To update those instruments still on SECI use the folder `...\CompGroup\Calibration Files`: - -1. Update files in `Calibration Files\Temperature Sensors\Files` -1. Run the deployment script in `Calibration Files\Temperature Sensors\Deployment Scripts`. - - There should be 1 error per instrument for deleting the network path - ## Calibration file format 1. First lines start with `# ISIS calibration`. From 5382a1f12d17225738bec990f4d58c473506a697 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:06:01 +0100 Subject: [PATCH 42/60] Update DAE-Trouble-Shooting.md --- doc/specific_iocs/dae/DAE-Trouble-Shooting.md | 17 ++++++----------- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/doc/specific_iocs/dae/DAE-Trouble-Shooting.md b/doc/specific_iocs/dae/DAE-Trouble-Shooting.md index aa3206456..e0af0f37b 100644 --- a/doc/specific_iocs/dae/DAE-Trouble-Shooting.md +++ b/doc/specific_iocs/dae/DAE-Trouble-Shooting.md @@ -54,9 +54,6 @@ Qxtrm_channel::RDMARead failed rdma2 address 0x40010 nbytes 4(Quixtream: The tim In general if you see an error like this or starting with `NIVISA` you should restart the DAE, then [contact electronics](https://stfc365.sharepoint.com/sites/ISISExperimentControls/ICP%20Discussions/Contact%20details%20for%20other%20groups.docx). -### No log files are produced in `c:\data` even though blocks are set to log. -The reason may be because the isisicp program that writes the datafile hasn't been configured to read values from MySQL for EPICS - the old SECI program used a different route. This is a one off change needed for SECI -> IBEX migration. In `C:\LabVIEW Modules\dae\isisicp.properties` set `isisicp.epicsdb.use = true` to enable this. You will need to restart the `isisicp` process for this to take effect. To do this, just end the `isisicp` process in task manager. - ### DAE doesn't seem to be connected/I want to run without a DAE connected The DAE can be set to run in simulation mode, this must be unset before data will be collected. To set the mode run `g.set_dae_simulation_mode(True)` or `g.set_dae_simulation_mode(False)` to unset. @@ -64,7 +61,7 @@ To change the simulation mode manually, in `icp_config.xml` change the simulate ### Log file for LabVIEW modules DAE -Both SECI and IBEX use the same underlying `isisicp` program (located in `labview modules\dae`) that writes to `C:\Data\Export only\logs\icp\log\icp-log`. There is an [example DAE log in this wiki](DAE-Normal-Log). This is a good place to locate DAE specific issues, not all of the details in this log appear in the ISISDAE IOC log. +IBEX uses `isisicp` program (located in `labview modules\dae`) that writes to `C:\Data\Export only\logs\icp\log\icp-log`. There is an [example DAE log in this wiki](DAE-Normal-Log). This is a good place to locate DAE specific issues, not all of the details in this log appear in the ISISDAE IOC log. ### Error pop up: `*** ICP failed to start - your DAE may be switched OFF or is missing cards ***` The DAE unit may be switched off. This is particularly likely during shut down. Change the DAE into simulation mode as described above. @@ -145,7 +142,7 @@ From an issue in Ticket https://github.com/ISISComputingGroup/IBEX/issues/3099 - [2018-04-09 15:26:49] : Exception occurred. ``` -The issue here is that the default simulated DAE has 2 detector cards in it, but the real DAE has more cards. To fix edit `isisicp.properties` in LabVIEW modules to create more cards. Note this is not an ibex issue - it will also affect DAE simulation mode under SECI. The number of cards on each crate is given by the maximum missing card for the crate (see log), more crates can be added as well as cards. An example from wish with 3 crates, 10, 10 and 12 card per crate is: +The issue here is that the default simulated DAE has 2 detector cards in it, but the real DAE has more cards. To fix edit `isisicp.properties` in LabVIEW modules to create more cards. The number of cards on each crate is given by the maximum missing card for the crate (see log), more crates can be added as well as cards. An example from wish with 3 crates, 10, 10 and 12 card per crate is: ``` isisicp.simulation.detcards.crate0.number = 10 @@ -204,9 +201,9 @@ One cause would be the IOC is trying to call a function in the ISISICP that it c DAE3 is new ethernet based acquisition electronics on ZOOM and MARI, it used `ISISICP` and looks like DAE2 for most purposes. If everything remains in processing, it may be that the `arp` network entries did not get created - these should be done as a system time boot task. Do `arp -a` and see if there is an entry for 192.168.1.101 etc. If not, run `set_dae3_arp.bat` in `c:\labview modules\dae` as as administrator -Note that DAE3 does not ping, so the only way to know if it is there is by running `qxtalk` or the `isisicp` (via ibex or seci) +Note that DAE3 does not ping, so the only way to know if it is there is by running `qxtalk` or the `isisicp` (via ibex) -If IBEX/SECI has either been in simulation mode or not running for a long time previously, then some of the tcp ports used by dae3 may have been grabbed by the operating system as described in `Real DAE complains about missing cards (but was previously working)` above on this page. You will see errors like +If IBEX has either been in simulation mode or not running for a long time previously, then some of the tcp ports used by dae3 may have been grabbed by the operating system as described in `Real DAE complains about missing cards (but was previously working)` above on this page. You will see errors like ``` Quixtream Error: Failed to bind the socket to the local port." ``` @@ -455,12 +452,12 @@ you probably need to follow https://knowledge.ni.com/KnowledgeArticleDetails?id= If you need to recover a system that has filled up its `c:\data` area due to a long event mode run with e.g. noisy detectors then you can use the following. This assumes the scientists do not need the data, you can move the files off instrument but recovery is hard and may not be possible. * log onto NDX computer -* Run `stop_ibex_server` or `kill seci` as appropriate +* Run `stop_ibex_server` * open `c:\data` in windows explorer and sort files by name * look for a very large `eventsYYYYY.tmp` file, make a note of the `YYYYY` number and then select and `shift+delete` this file (you do not want to move it to recycle bin - make sure the prompt says "permanently delete this file" and not "delete this file") * Also now shift+delete `current.run`, `current.runYYYYY`, `data.run`, `data.runYYYYY` * open `c:\data\events` and shift+delete the folder `run_YYYYY` -* start ibex or seci again +* start ibex again Hopefully there is either only one `eventsYYYYY.tmp` file, or the most recent one (largest YYYYY number) is also the largest in size. If there are several files making a decision may need a bit more thought. It is possible that a very large run was done earlier which nearly filled up the disk, then a new one was started that pushed it over the limit while the previous one was ending in the background. Check with the scientists if it is ok to delete this earlier bigger run. You should always delete all YYYYY files corresponding to the run that was in progress when the system filled up, but you may also need to handle an earlier YYYYY number set of files to free up enough disk space. @@ -485,8 +482,6 @@ Check to see if you have any errors similar to the following: If so, you haven't registered your `isisicp.exe` program with the registry. Follow the steps to [Configure DAE for simulation mode on developer's computer](#first_time_install_configure_dae) -If you have done this it may be that the isisicp.exe program is too old. Older versions do not contain a function which is needed by IBEX. Check the file `svn_revision.txt` in `c:\labview modules\dae` - it needs to be 1633 or higher. If it needs updating, ask a SECI specialist to update the program. - ## Multiple VXI devices If you have multiple DAE2 VME crates then you will legitimately have multiple VXI devices in NI MAX. However there are cases when you can get two devices showing in MAX but have only one device in reality. This is usually because of either: From d5ef97017184fdfbb67ee0193a4f45bf676cdffe Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:12:54 +0100 Subject: [PATCH 43/60] Update Deployment-on-an-Instrument-Control-PC.md --- .../deploy/Deployment-on-an-Instrument-Control-PC.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc/deployment/deploy/Deployment-on-an-Instrument-Control-PC.md b/doc/deployment/deploy/Deployment-on-an-Instrument-Control-PC.md index cbf534140..358b61351 100644 --- a/doc/deployment/deploy/Deployment-on-an-Instrument-Control-PC.md +++ b/doc/deployment/deploy/Deployment-on-an-Instrument-Control-PC.md @@ -26,7 +26,6 @@ If you do not have either a D: or O: network drive, then you will need to specif - If you want to install a non-default release you need to set the `SUFFIX` variable in the batch file. For example with `x.y.z` being the current release and `hotfix` being the suffix, it will look for the folder `Releases/x.y.z-hotfix` - Apart from the below points, just follow instructions - most options should be answered `Y` (yes) to, but if you are unsure on a particular machine ask on technical. - Be warned the upgrade runs in 3 steps and so will claim to have finished the upgrade 3 times - - Do not remove any SECI icons from the task list if this is not the first time install 1. Compare screenshots taken earlier to current state @@ -65,7 +64,7 @@ installed on NDX computers. ## Install IBEX for the first time :::{note} -This is unlikely to happen now we've migrated most instruments, and SECI instruments should have a copy of IBEX at the least. +This is unlikely to happen now we've migrated all instruments from SECI. :::
Click to expand From 398f1a80da1e72c4babc5f3598073cf922c2e22c Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:23:47 +0100 Subject: [PATCH 44/60] Update Experimental-Runs.md --- doc/specific_iocs/dae/Experimental-Runs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/specific_iocs/dae/Experimental-Runs.md b/doc/specific_iocs/dae/Experimental-Runs.md index 07194dbc7..dad6c91be 100644 --- a/doc/specific_iocs/dae/Experimental-Runs.md +++ b/doc/specific_iocs/dae/Experimental-Runs.md @@ -36,7 +36,7 @@ This is from a problem see on IRIS. ## Experiment stuck in `Waiting` state after beginning a run -This issue was encountered on Iris during the transition between Seci and Ibex. SECI was in a waiting state prior to shutdown, then IBEX was left in this waiting state. Usually SECI run control is transient i.e. set by Open GENIE and cleared on a SECI restart, so just restarting SECI would usually clear it. The is now a new PV that you can write to from IBEX to force a resync of run control +There is now a new PV that you can write to from IBEX to force a resync of run control caput %MYPVPREFIX%CS:RC:SYNC:SP 1 @@ -51,4 +51,4 @@ If this has failed: To archive files end a run. Should you have runs ending and read only files, then check on the archive in `INST\instrument\logs\cycle_nn_n`, the log files there will provide some extra information. If the file `exception_copy.log` doesn't exist, or hasn't been updated for a long time, then the script above isn't running the code to clean up old files, or it has hung. -* Problems with the end of run script can be diagnosed by looking at the `post_command_.log'` file in the ICP logs area on the instrument. The ICP log files (in the same area) may also be instructive to check for other issues - for example, if the files are not being set read-only. \ No newline at end of file +* Problems with the end of run script can be diagnosed by looking at the `post_command_.log'` file in the ICP logs area on the instrument. The ICP log files (in the same area) may also be instructive to check for other issues - for example, if the files are not being set read-only. From db46cb9ee7cc86762ff396d62aa5aba155d634be Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:50:01 +0100 Subject: [PATCH 45/60] Update ISISICP---enabling-incremental-event-file-creation.md --- .../dae/ISISICP---enabling-incremental-event-file-creation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/specific_iocs/dae/ISISICP---enabling-incremental-event-file-creation.md b/doc/specific_iocs/dae/ISISICP---enabling-incremental-event-file-creation.md index 3087022c9..29f693e7d 100644 --- a/doc/specific_iocs/dae/ISISICP---enabling-incremental-event-file-creation.md +++ b/doc/specific_iocs/dae/ISISICP---enabling-incremental-event-file-creation.md @@ -7,6 +7,6 @@ To enable incremental mode edit `isisicp.properties` in `C:\labview modules\dae` isisicp.incrementaleventnexus = true isisicp.kafkastream = true ``` -The changes will not take effect until you restart the ISISICP program - make sure you are in SETUP and any runs have finished saving, then kill the `ISISICP` process using task manager (you can restart seci/ibex if you prefer, but that is not necessary) +The changes will not take effect until you restart the ISISICP program - make sure you are in SETUP and any runs have finished saving, then kill the `ISISICP` process using task manager (you can restart ibex if you prefer, but that is not necessary) After this is enabled, you can also run Mantid on any computer and use the Kafka live listener to view and process events live during the run. From 7cf45fe5bdb384b6d5ff32893b5a768fbf882f86 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 16:13:46 +0100 Subject: [PATCH 46/60] systems/external --- ...am-Status,-Shutter,-accelerator-and-moderator-information.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/systems/external/Beam-Status,-Shutter,-accelerator-and-moderator-information.md b/doc/systems/external/Beam-Status,-Shutter,-accelerator-and-moderator-information.md index 5a7c1e763..26d1f9ab7 100644 --- a/doc/systems/external/Beam-Status,-Shutter,-accelerator-and-moderator-information.md +++ b/doc/systems/external/Beam-Status,-Shutter,-accelerator-and-moderator-information.md @@ -71,7 +71,7 @@ A "Beam current" block may not be showing the accelerator beam current, it may b ## Value shows zero in IBEX but non-zero with `db_access` on MERECKX -If the third column in `params.txt` contains a `z` (e.g. `tz`) then this means that the parameter will be monitored for a stale (non updating) state and if this is detected it will send 0 as the value to IBEX/SECI. At time of writing this had only been requested for the decoupled methane, sending 0 when the value is uncertain means they will go into a WAITING state as they run control on methane temperature and it is important that they are not collecting data when a methane charge-change happens. In future the value could be EPICS alarmed, but for SECI instruments we need to send 0 +If the third column in `params.txt` contains a `z` (e.g. `tz`) then this means that the parameter will be monitored for a stale (non updating) state and if this is detected it will send 0 as the value to IBEX. At time of writing this had only been requested for the decoupled methane, sending 0 when the value is uncertain means they will go into a WAITING state as they run control on methane temperature and it is important that they are not collecting data when a methane charge-change happens. In future the value could be EPICS alarmed, but for SECI instruments we needed to send 0. You may be able to confirm a value is not updating by running `db_access` on it a few times with a reasonable time delay in-between, but some values are quite stable or fluctuate only a bit so this may be difficult to determine. You can view the typical value and variation in an accelerator parameter by following the links on values at [http://beamlog.nd.rl.ac.uk/status.xml](http://beamlog.nd.rl.ac.uk/status.xml) From dc2af65685e3411a9c027395ad5b77fe03985850 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 14:27:42 +0100 Subject: [PATCH 47/60] Update Webserver.md Believe these are being removed as part of today's SECI technical debt day --- doc/systems/Webserver.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/doc/systems/Webserver.md b/doc/systems/Webserver.md index 535423cba..b85de00c7 100644 --- a/doc/systems/Webserver.md +++ b/doc/systems/Webserver.md @@ -7,10 +7,7 @@ NDAEXTWEB3 is a central Windows 2019 server, which is hosted on the FIT Hyper-V * The [old IBEX web dashboard (JSON_Bourne)](/webdashboard/Web-Dashboard) * The [Automation application](/processes/git_and_github/Automation-Application) * [MCR news](https://www.isis.stfc.ac.uk/Pages/MCR-News.aspx) -* The SECI web dashboard * The central proxy created [here](https://github.com/ISISComputingGroup/IBEX/issues/5112) -* WAP access to SECI web dashboard - Most of these services can be started and stopped by the [IIS Manager](https://www.iis.net/). To access the IIS Manager, select IIS in the Server Manager, then click on Manage in the top right hand corner of that screen. From f05be9bb8bb3fae5aad2f7cdd4a7e8c3b26d48f2 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:11:04 +0100 Subject: [PATCH 48/60] Update spelling_wordlist.txt --- doc/spelling_wordlist.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/spelling_wordlist.txt b/doc/spelling_wordlist.txt index 8f8e07c12..6e5b9a0c5 100644 --- a/doc/spelling_wordlist.txt +++ b/doc/spelling_wordlist.txt @@ -228,6 +228,7 @@ Ecorr efxclipse EGU Eilidh +Elektronika enablement endian ENGINX From fb3624ffc574de20a531e21c6eef198db0d4e63f Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:29:43 +0100 Subject: [PATCH 49/60] Delete doc/processes/meetings_with_scientists/Demo-notes.md This page deals with demos of IBEX to SECI familiar scientists. Whilst we still do first time demos of IBEX, these are covered by our IBEX training course and so we do not need to duplicate that material by updating this page. --- doc/Overview.md | 1 - .../meetings_with_scientists/Demo-notes.md | 184 ------------------ 2 files changed, 185 deletions(-) delete mode 100644 doc/processes/meetings_with_scientists/Demo-notes.md diff --git a/doc/Overview.md b/doc/Overview.md index 467ff9d64..08c0b9c60 100644 --- a/doc/Overview.md +++ b/doc/Overview.md @@ -34,7 +34,6 @@ overview/Links-and-Resources ## Documentation & Processes - [How to edit this documentation](Editing-the-Wiki) -- [How to demonstrate IBEX](processes/meetings_with_scientists/Demo-notes): Some notes on what to show someone when demonstrating IBEX for the first time - [Notes from Retrospectives](processes/Retrospective-Notes): Notes from Sprint Retrospective meetings are recorded here. - [Decision Log](processes/Decision-Log): A place to write down decisions made. - [Documentation](processes/dev_processes/Project-Documentation): Documentation of the project and processes _(including why we have 3 wikis)_ diff --git a/doc/processes/meetings_with_scientists/Demo-notes.md b/doc/processes/meetings_with_scientists/Demo-notes.md deleted file mode 100644 index 123afa216..000000000 --- a/doc/processes/meetings_with_scientists/Demo-notes.md +++ /dev/null @@ -1,184 +0,0 @@ -# First-time demos of IBEX to scientists - -```{note} -All instruments now have IBEX, so this process is unlikely to be needed for existing instruments. - -For existing instruments, use [regular demo documentation](Regular-Demos-of-IBEX-to-Scientists) -``` - -Anyone doing a demo of IBEX should use these notes, so that - -* You are familiar with the scope of the demo (i.e. what should be covered) -* You review it and rehearse it in advance (i.e. you are clear about what you will present) -* You don’t forget to mention any important aspects of the system - * keep a copy of these notes in front of you as you do the demo -* You don’t forget where key files (e.g. demo scripts) are located, etc. -* Instrument scientists get a consistent picture irrespective of where & when the demo is performed. -* If a question takes you “off piste”, you can easily find your way back to the main thread of the demo. -* We can enhance the script in the light of experience (e.g. better answers to questions) - * jot down any important points arising from any demos that you do and add them back into this document for the benefit of others. - -## Overview - -Provide the audience with a quick tour of the IBEX GUI - -* Explain that the GUI is a client application - * It displays data that is provided to it by server applications - * The server applications are called IOCs (Input-Output Controllers) - * IOCs are similar, in some respects, to LabVIEW VIs - * The IOCs run on the control PC (i.e. the NDX... machine) - * The GUI can run on the control PC. It can also run on other client PCs located elsewhere on the network. - -* Highlight the main areas of the GUI - * Dashboard - very similar to the SECI dashboard - * Blocks & Groups - again, very similar to SECI - * System Views - a number of different views of the system. Some views are similar to SECI; others are new. - * Clicking on the list of View buttons (on the left-hand side of the GUI window) changes the view - -* Highlight the IBEX menu - * IBEX - use to switch instrument, restore the default view or exit IBEX - * Configuration - use to edit configurations, load a new configuration or delete a configuration - * Synoptic - use to edit synoptics, load a new synoptic or delete a synoptic. - * IOC - use to start or stop IOCs - * Run Control - use to view and edit run-control settings - * Help - point out the About Box. User should use it to report the server & client version numbers if they encounter problems. - -## Dashboard - -The dashboard is very similar to the SECI dashboard -* It uses the same colour coding as the SECI dashboard -* It displays the same status messages as the SECI dashboard -* Information about the current experiment comes from the DAE set up (we'll touch on this later) -* Beam status information comes from the beam logger IOC - -## Beam Status - -Describe the Beam Status view -* Clicking on the Beam Status button displays the Beam Status view -* The Beam Status view always appears in the main display area -* The Beam Status view comprises 3 panes - * The main pane, taking up most of the display in the Beam Status graph. It shows the Synchrotron current and the currents to TS1 and TS2. You can toggle the display to show graphs for the last hour or last 24 hours. - * The top right pane shows the ISIS MCR news. It is just a simple scrolling window showing the published MCR news. - * The lower right pane shows beam status details. It consists of 3 sections: one for the Synchrotron, one for TS1 and one for TS2. The sections are collapsible, so you can collapse any section that is of no interest to you. - * Beam status information comes from the beam logger IOC, which replaces the old LabVIEW beam logger VI. - * The beam logger IOC is already serving beam status information to all instruments (not just those running IBEX) - * The beam logger IOC actually runs on the accelerator control system - -## IOC Log View - -Describe the IOC Log view -* The IOC Log system provides a unified way of managing status and information messages from the devices attached to the instrument. -* Copies of status and information messages from the DAE are also routed via the IOC Log system. -* The IOC Log messages are primarily intended for diagnosing problems with attached devices. -* The IOC Log view provides you with a convenient means of viewing those messages - * Demonstrate how messages can be filtered and searched (by date/time, severity, etc.) - * Messages are automatically saved to a log on the control PC - * **N.B.** Messages are held in a log which is quite separate from experimental data - -## DAE View - -Describe the DAE view -* The DAE view allows scientists to set up and control the operation of the DAE. -* The DAE view is very similar to the DAE VI in SECI. -* The DAE view comprises 6 tabs. - * Run Summary - Displays run summary information and any recent log messages. - * Experiment Setup - . - * Run Information - . - * Spectra Plots - . - * Diagnostics - . - * Vetos - . - -* As previously noted, copies of status and information messages from the DAE are also routed via the IOC Log system. - -## Blocks & Groups - -Blocks & groups in the new GUI work in the same way as they do in SECI. -* Blocks and groups are displayed at the top (and centre-right) of the GUI window. -* Blocks & groups are part of your configuration. You define blocks & groups by creating and editing configurations. -* In EPICS, an IOC makes information about the status of a device available by publishing *process variables*. In general, an IOC will use many process variables to fully describe the state of a device. Typically, you won't be interested in all of these - just a sub-set. Show how the GUI allows you to select which process variables that are of interest and to define these as *blocks*. -* Once a PV has been defined as a block, show how it can be assigned to a group. -* Make it clear that blocks are automatically logged (just as they are in SECI). Note also that the logging of blocks is independent of the message log. -* Show how blocks can be viewed in the LogPlotter - so the user can always view the history of a block. -* Show how a set of defined blocks & groups can be saved as a configuration. -* Show how a previously saved configuration can be re-loaded. -* Explain what is saved in a configuration: - * groups, blocks, links to settings files, synoptic view -* Demonstrate sub-configurations -* Demonstrate Management Mode. - -## Scripting - -In the new GUI, scripting is built-in. You don't need a separate windows to run a script (although some users prefer to have a separate window). -* Click on the Scripting button to display the Scripting view - * point out the scripting area -* The scripting language is Python -* Python brings a number of advantages over Genie - * *what are they? - we need to enumerate them* -* Python equivalents of the most common Genie commands (e.g. cset) have been created - * demonstrate that, for example, ``cset arg`` becomes ``cset(arg)`` - * it is not difficult to convert a Genie script into a Python script - * display a *before (Genie)* and *after (Python)* script. Emphasize how similar they are. -* Any block (or PV) can be used in a Python script -* Demonstrate running a Python script - * use a script that you prepared earlier: **don't wing it!** - * point out use of Genie-like commands where possible - * show how to pull in data from blocks (or PVs) - * read data from previously saved file if beam is off - * manipulate data in Python - show off what Python can do - * display data in a graph - * copy/paste a graph into MS Word (or similar) - -## Device Support - -EPICS provides support for a wide range of devices. For many devices we can simply download the appropriate driver from the EPICS web-site. Because the source code for these drivers is available, we can, if necessary, adapt an EPICS driver for our specific purposes. -* In EPICS, drivers & IOCs combine to provide control of devices attached an instrument. In addition, we use CSS to create OPIs (graphical user interfaces) for devices. In combination, drivers, IOCs and OPIs provide the functionality of a LabVIEW VI. -* We currently have EPICS drivers for Galil motor controllers, Eurotherms, Julabo water baths, CAEN, Kepco & Thurlby power supplies. We also have controllers for PLCs, jaws-sets, sample changers, rotation stages and goniometers. -* EPICS drivers and controllers for additional devices can be developed as required. -* Adopting EPICS does **not** mean throwing away existing LabVIEW drivers. - * We have created a communication interface, called lvDCOM, to enable EPICS to communicate with LabVIEW VIs. - * Where a device has a complex or specially customised LabVIEW driver, lvDCOM allows us to continue using the LabVIEW VI. Any data that the VI makes available to EPICS can be defined as a block and used in the normal manner. -* Demonstrate an existing EPICS IOC/OPI: for example the Eurotherm IOC & OPI – demonstrate simple operation, ramping, calibration, etc. -* Demonstrate interaction between EPICS and a VI: for example -* Demonstrate starting & stopping of IOCs. Show how startup messages, etc. are captured in the message log. -* Discuss settings files and their relation to IOCs and VIs. - -## Synoptic View or Instrument Overview - -The synoptic view provides an interactive overview of an instrument. -* The synoptic view shows all the devices (or a defined sub-set of devices) attached to an instrument. -* The synoptic view is configurable (via the Synoptic Editor). Show how you can create different views for different instrument setups. -* Incident neutrons are shown coming from the left. -* Each device is represented by its own icon and a small number of key parameters. -* Show how you can drill-down by clicking on each device icon to get more detail. - * Clicking on a device icon displays the device UI, which will display additional controls and information that cannot easily be included on the top-level synoptic display - * Device UIs are sometimes referred to as OPIs (OPIs are analogous to LabVIEW VI screens) - * Demonstrate how some devices (e.g. motors) allow you to drill-down to deeper levels (beware: some of the deeper level screens can get very complex) - * Show how the Up, Next and Prev buttons are used to navigate around the various layers of the synoptic view. - -## Motors View - -The motors view provides a convenient way to view the status of all the motors used on an instrument. -* The motors view is very similar to the *Table of Motors* used in SECI by some instruments. -* Each row corresponds to a single Galil motor controller. The number of rows displayed will depend on the number of Galil controllers attached to the instrument. -* The columns list the Galil controller ports (up to 8 ports per Galil) -* Each entry in the table represents a single Galil controller port (one (or zero) motors per port) - * Each entry identifies the motor by its unique ID number - * Each entry displays the current value of the motor's position and its current set-point. - * A grey entry represents an unused port (no motor is attached, or motor is switched off) - * A pink entry represents a port in use: motor is attached, but stationary - * A green entry represents an active port: motor is attached and is moving -* Show how you can drill-down by clicking on each motor entry to get more detail. - -## EPICS & Extensibility - -EPICS is a framework for creating *distributed* control systems. The ability to have more than one PC controlling different parts of an instrument is inherent to EPICS. -* The default position will continue to be that we will use a single PC to control all of the devices attached an instrument. -* However, there are some situations where it is advantageous to have specialist items of equipment controlled by a separate PC. For example - * the interchangeable cameras on IMAT - * the LARMOR spin-echo system \ No newline at end of file From 931b48d449d6e802a40d75318f87a6205d46c6d7 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 13:56:16 +0100 Subject: [PATCH 50/60] Delete doc/system_components/labview/LabVIEW-memory-warning-in-nagios.md Intro makes clear this is only relevant under SECI --- .../LabVIEW-memory-warning-in-nagios.md | 23 ------------------- 1 file changed, 23 deletions(-) delete mode 100644 doc/system_components/labview/LabVIEW-memory-warning-in-nagios.md diff --git a/doc/system_components/labview/LabVIEW-memory-warning-in-nagios.md b/doc/system_components/labview/LabVIEW-memory-warning-in-nagios.md deleted file mode 100644 index af3601b79..000000000 --- a/doc/system_components/labview/LabVIEW-memory-warning-in-nagios.md +++ /dev/null @@ -1,23 +0,0 @@ -# LabVIEW memory leak - -If nagios is reporting a critical memory usage for LabVIEW (which will only be on a SECI instrument) then you need to do the following: - -first check to see if the nagios service has been acknowledged (has a tick next to it), it it has then these steps have already been followed and you need do nothing - -compose an email with the from address set to "ISIS Experiment Controls" and the following content with `yyyy` replaced by the instrument name e.g. `OFFSPEC` -``` -subject: SECI/LabVIEW memory usage on NDXyyyy computer - -Hi, - -The SECI/LabVIEW memory usage on the NDXyyyy instrument computer is getting very high and the process may crash in the next few days, it would be advisable to restart the SECI control system at the next convenient point - -Regards, - -ISIS Experiment Controls -``` - -Now send this email to the special instrument address alias - -Then acknowledge the service in nagios: click on `LABVIEW memory` for the instrument in the nagios view, then on the right of the next page click on `Acknowledge this service problem` and then give a comment like "emailed scientists" and press `Commit`. If you now return to the nagios service view, you should see a tick mark next to the service name. - From c28c4be15d818d1c5b74391462491b2f9dea9345 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Mon, 1 Sep 2025 16:58:43 +0100 Subject: [PATCH 51/60] actually fix offspect cross-references --- .../instrument_details/OFFSPEC-Instrument-Details.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md b/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md index a9eed6fa6..f99c98a4c 100644 --- a/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md +++ b/doc/processes/instrument_details/OFFSPEC-Instrument-Details.md @@ -122,6 +122,7 @@ OFFSPEC uses Julabo water baths & re-circulating coolers 1. [Julabo FL300](https://www.julabo.com/en/products/recirculating-coolers/fl300-recirculating-cooler) 1. Julabo Water Bath (which models?) +{#note-Kepco} ##### Note: KEPCO ##### 1. [Kepco BOP 100-10MG PSU](http://www.kepcopower.com/bophimod.htm).
See also [#3005](https://github.com/ISISComputingGroup/IBEX/issues/3005) 1. [Kepco BIT 4886](http://www.kepcopower.com/bit.htm) is an interface card for Kepco bi-polar ([BOP](http://www.kepcopower.com/bop.htm)) power supplies. @@ -210,10 +211,10 @@ OFFSPEC has the following specialist panels/systems: 1. OFFSPEC Delft System 1. OFFSPEC ISIS Sample Environment 1. OFFSPEC Linkam - * [see Linkam note](#noteLinkam) + * [see Linkam note](#note-linkam) 1. OFFSPEC Newport Piezo Stage 1. OFFSPEC BH (KEPCO 100-10MG & Keithley 2400) - * [see Kepco note](#noteKepco) & [see Keithley note](#noteKeithley) + * [see Kepco note](#note-Kepco) & [see Keithley note](#note-keithley) 1. OFFSPEC Delft RF 1. OFFSPEC PI Motion Stage 1. POLREF Danfysik From 1f159e110e475c88a7492857927e08fd09e6e5d1 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Tue, 2 Sep 2025 08:36:18 +0100 Subject: [PATCH 52/60] change in response to review --- .../instrument_details/POLARIS-Instrument-Details.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/doc/processes/instrument_details/POLARIS-Instrument-Details.md b/doc/processes/instrument_details/POLARIS-Instrument-Details.md index 7140c0722..06c64d22d 100644 --- a/doc/processes/instrument_details/POLARIS-Instrument-Details.md +++ b/doc/processes/instrument_details/POLARIS-Instrument-Details.md @@ -106,7 +106,3 @@ An evacuated furnace cell for measuring resistivity. Controlled by Eurotherms a {#polaris_noteHVCentreStick} ##### Note: CS155 Centre Stick ##### Not possible to control this device via software. It connects to the [Spellman](#polaris_noteSpellman) HV-PS. - -s currently used on POLARIS here. - -## POLARIS Notes ## From f1390618a0e79cd1782ca14c2a04278b8749f62c Mon Sep 17 00:00:00 2001 From: George Ryall Date: Tue, 2 Sep 2025 08:37:01 +0100 Subject: [PATCH 53/60] Update doc/specific_iocs/cryogenics/Triton.md Co-authored-by: Tom Willemsen --- doc/specific_iocs/cryogenics/Triton.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/specific_iocs/cryogenics/Triton.md b/doc/specific_iocs/cryogenics/Triton.md index 520453861..ff89f6fa3 100644 --- a/doc/specific_iocs/cryogenics/Triton.md +++ b/doc/specific_iocs/cryogenics/Triton.md @@ -4,7 +4,7 @@ Technically, "Triton" refers to the gas handling apparatus. This is what IBEX talks to. When setting up a triton, scientists may refer to it as a "Kelvinox". This is the technical name for the dilution insert, which is controlled by the triton gas handling apparatus. -To avoid confusion: all dilution fridges currently in use at ISIS are controlled by Triton gas handling systems, with one exception: the ICE fridge used on the muon beamlines. +To avoid confusion: all dilution fridges currently in use at ISIS are controlled by Triton gas handling systems. ## Connection From a705a34bb1525c973ce3843c41f7c1cb90e2261b Mon Sep 17 00:00:00 2001 From: George Ryall Date: Tue, 2 Sep 2025 08:38:28 +0100 Subject: [PATCH 54/60] Update doc/specific_iocs/dae/Experimental-Runs.md Co-authored-by: Tom Willemsen --- doc/specific_iocs/dae/Experimental-Runs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/specific_iocs/dae/Experimental-Runs.md b/doc/specific_iocs/dae/Experimental-Runs.md index dad6c91be..6ec56304a 100644 --- a/doc/specific_iocs/dae/Experimental-Runs.md +++ b/doc/specific_iocs/dae/Experimental-Runs.md @@ -51,4 +51,4 @@ If this has failed: To archive files end a run. Should you have runs ending and read only files, then check on the archive in `INST\instrument\logs\cycle_nn_n`, the log files there will provide some extra information. If the file `exception_copy.log` doesn't exist, or hasn't been updated for a long time, then the script above isn't running the code to clean up old files, or it has hung. -* Problems with the end of run script can be diagnosed by looking at the `post_command_.log'` file in the ICP logs area on the instrument. The ICP log files (in the same area) may also be instructive to check for other issues - for example, if the files are not being set read-only. +* Problems with the end of run script can be diagnosed by looking at the `post_command_.log` file in the ICP logs area on the instrument. The ICP log files (in the same area) may also be instructive to check for other issues - for example, if the files are not being set read-only. From 50a108f29d8ff8a39179d72cce69c6e1b76345a8 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Tue, 2 Sep 2025 08:39:15 +0100 Subject: [PATCH 55/60] Update doc/systems/external/Beam-Status,-Shutter,-accelerator-and-moderator-information.md Co-authored-by: Tom Willemsen --- ...am-Status,-Shutter,-accelerator-and-moderator-information.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/systems/external/Beam-Status,-Shutter,-accelerator-and-moderator-information.md b/doc/systems/external/Beam-Status,-Shutter,-accelerator-and-moderator-information.md index 26d1f9ab7..2308d14d1 100644 --- a/doc/systems/external/Beam-Status,-Shutter,-accelerator-and-moderator-information.md +++ b/doc/systems/external/Beam-Status,-Shutter,-accelerator-and-moderator-information.md @@ -69,7 +69,7 @@ If something does appear to have gone wrong with this service (e.g. values are n A "Beam current" block may not be showing the accelerator beam current, it may be showing the effective beam current from the DAE. Blocks read from the accelerator will all be referring to global PV names starting AC: and TG: so if the block refers to an IN: it will be something on the local instrument. The DAE:BEAMCURRENT value is the effective DAE beam current, but if the dae is not counting (SETUP, WAITING, PAUSED) then this value will be zero. If the DAE is vetoing this value will vary between 0 and something else depending on what % of frames are being vetoed. If the chopper is being run at a lower frequency, the value will be lower too as the DAE is seeing less pulses and hence a lower effective beam current. -## Value shows zero in IBEX but non-zero with `db_access` on MERECKX +## Value shows zero in IBEX but non-zero with `db_access` on MERCKX If the third column in `params.txt` contains a `z` (e.g. `tz`) then this means that the parameter will be monitored for a stale (non updating) state and if this is detected it will send 0 as the value to IBEX. At time of writing this had only been requested for the decoupled methane, sending 0 when the value is uncertain means they will go into a WAITING state as they run control on methane temperature and it is important that they are not collecting data when a methane charge-change happens. In future the value could be EPICS alarmed, but for SECI instruments we needed to send 0. From bfce906baa14f95a54dea975f62b9230b9dcbd30 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Tue, 2 Sep 2025 08:40:42 +0100 Subject: [PATCH 56/60] Update MUON-Front-End-Instrument-Details.md --- .../instrument_details/MUON-Front-End-Instrument-Details.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/doc/processes/instrument_details/MUON-Front-End-Instrument-Details.md b/doc/processes/instrument_details/MUON-Front-End-Instrument-Details.md index 64c61142a..902f22528 100644 --- a/doc/processes/instrument_details/MUON-Front-End-Instrument-Details.md +++ b/doc/processes/instrument_details/MUON-Front-End-Instrument-Details.md @@ -23,7 +23,3 @@ The system is due on line September 2016. {#muonfe_noteMomentumSlits} ## Barndoors and Momentum Slits ## The barn doors and momentum slits control the muon beam delivered to the 3 muon instruments: HIFI, muSR and EMU. The control of these devices is described on the [Barndoors & Momentum-Slits](/specific_iocs/motor_extensions/jaws/Barndoors-and-Momentum-Slits-on-MUON-Front-End) page. - -{#muonfe_noteMotion} -##### Note: Motion ##### -There is a project relating to the motion on the South Side Muons in progress, this information may be out of date From 102f3f8d4dc245559348d5b130f04c6fb3374989 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Tue, 2 Sep 2025 13:53:11 +0100 Subject: [PATCH 57/60] Update SXD-Instrument-Details.md in response to review feedback --- doc/processes/instrument_details/SXD-Instrument-Details.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/processes/instrument_details/SXD-Instrument-Details.md b/doc/processes/instrument_details/SXD-Instrument-Details.md index 60fc04e36..0cbda4aa1 100644 --- a/doc/processes/instrument_details/SXD-Instrument-Details.md +++ b/doc/processes/instrument_details/SXD-Instrument-Details.md @@ -65,7 +65,7 @@ See also tickets [#1826](https://github.com/ISISComputingGroup/IBEX/issues/1826) {#sxd_note-kammrath-and-weiss} ##### Note: Kammrath and Weiss ##### -1. The Kammrath-Weiss tensile stress rig is controlled from a dedicated laptop running the manufacturer's software. IBEX communicates with the PC to send/read values to/from the manufacturer's software using `LVREMOTE`. +1. The Kammrath-Weiss tensile stress rig is controlled from a dedicated laptop running the manufacturer's software. IBEX communicates with the PC to send/read values to/from the manufacturer's software using [`LVREMOTE`](https://github.com/ISISComputingGroup/EPICS-LVREMOTE). 1. [Kammrath and Weiss](https://www.kammrath-weiss.com/en/tensile-compression-modules/).
* See also ticket [#2681](https://github.com/ISISComputingGroup/IBEX/issues/2681) From b049f01ba7c4511c9795eed7826617d8356cf0e6 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Tue, 2 Sep 2025 15:43:00 +0100 Subject: [PATCH 58/60] Update Experimental-Runs.md final response to feedback --- doc/specific_iocs/dae/Experimental-Runs.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc/specific_iocs/dae/Experimental-Runs.md b/doc/specific_iocs/dae/Experimental-Runs.md index 6ec56304a..89e828e45 100644 --- a/doc/specific_iocs/dae/Experimental-Runs.md +++ b/doc/specific_iocs/dae/Experimental-Runs.md @@ -36,9 +36,7 @@ This is from a problem see on IRIS. ## Experiment stuck in `Waiting` state after beginning a run -There is now a new PV that you can write to from IBEX to force a resync of run control - - caput %MYPVPREFIX%CS:RC:SYNC:SP 1 +There is now a new PV that you can write to from IBEX to [force a resync of run control](https://isiscomputinggroup.github.io/ibex_developers_manual/system_components/Run-control.html#troubleshooting) ## Experimental Files not being Archived and so not Appearing in the Journal From b99304d20e810f7b7897cae5465552406a048f83 Mon Sep 17 00:00:00 2001 From: George Ryall Date: Tue, 2 Sep 2025 17:43:58 +0100 Subject: [PATCH 59/60] Update Experimental-Runs.md --- doc/specific_iocs/dae/Experimental-Runs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/specific_iocs/dae/Experimental-Runs.md b/doc/specific_iocs/dae/Experimental-Runs.md index 89e828e45..8013f6206 100644 --- a/doc/specific_iocs/dae/Experimental-Runs.md +++ b/doc/specific_iocs/dae/Experimental-Runs.md @@ -36,7 +36,7 @@ This is from a problem see on IRIS. ## Experiment stuck in `Waiting` state after beginning a run -There is now a new PV that you can write to from IBEX to [force a resync of run control](https://isiscomputinggroup.github.io/ibex_developers_manual/system_components/Run-control.html#troubleshooting) +There is now a new PV that you can write to from IBEX to [force a resync of run control](system_components/Run-control.html#troubleshooting) ## Experimental Files not being Archived and so not Appearing in the Journal From 86e17ca6ccbb996e470c0bbf1ddd50be2cfca7b7 Mon Sep 17 00:00:00 2001 From: Tom Willemsen Date: Wed, 3 Sep 2025 08:45:18 +0100 Subject: [PATCH 60/60] fix link --- doc/specific_iocs/dae/Experimental-Runs.md | 2 +- doc/system_components/Run-control.md | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/specific_iocs/dae/Experimental-Runs.md b/doc/specific_iocs/dae/Experimental-Runs.md index 8013f6206..eb7f9b5c3 100644 --- a/doc/specific_iocs/dae/Experimental-Runs.md +++ b/doc/specific_iocs/dae/Experimental-Runs.md @@ -36,7 +36,7 @@ This is from a problem see on IRIS. ## Experiment stuck in `Waiting` state after beginning a run -There is now a new PV that you can write to from IBEX to [force a resync of run control](system_components/Run-control.html#troubleshooting) +There is now a new PV that you can write to from IBEX to [force a resync of run control](#force_runcontrol_resync). ## Experimental Files not being Archived and so not Appearing in the Journal diff --git a/doc/system_components/Run-control.md b/doc/system_components/Run-control.md index f5e2621a4..19b16fcf4 100644 --- a/doc/system_components/Run-control.md +++ b/doc/system_components/Run-control.md @@ -32,4 +32,7 @@ On LOQ a separate :DC: instance is also created, this calls a procedure to put i ## Troubleshooting +{#force_runcontrol_resync} +### Force a re-sync of runcontrol + If the system gets stuck in a WAITING state with no blocks being outside of runcontrol limits, then you can force a resync of the system with e.g. for OFFSPEC `caput IN:OFFSPEC:CS:RC:SYNC:SP 1`