ISISComputingGroup · rerpha · Sep 1, 2025 · Sep 1, 2025 · Sep 1, 2025 · Sep 1, 2025
diff --git a/doc/FAQ.rst b/doc/FAQ.rst
@@ -29,15 +29,10 @@ How do I install IBEX Client?
 
 To install IBEX Client - see :ref:`installing_ibex_client`.
 
-Can I run IBEX and SECI at the same time?
------------------------------------------
-
-In a word - No.  Running two control programs on any system is a bad idea - which program has control?  If you were to run IBEX and SECI on the same system, the two would contend for control of individual devices.  It would not be clear which device was controlled by which program.  The results would be unpredictable.
-
 Which version of Python does IBEX use?
 --------------------------------------
 
-IBEX currently uses Python 3.11.2. 
+IBEX currently uses Python 3.12
 
 Where can I learn about Python?
 -------------------------------
@@ -67,11 +62,6 @@ How do I stop IBEX Server?
 
 To stop IBEX Server - see :ref:`stopping_ibex_server`.
 
-Can I switch from running IBEX to SECI and vice-versa?
-------------------------------------------------------
-
-Yes, it is possible to switch from running IBEX to SECI or to switch from SECI to IBEX, but you have to be careful. See :doc:`obsolete/Switching-Between-IBEX-and-SECI` for details.
-
 Can I write scripts to control my experiment?
 ---------------------------------------------
 

diff --git a/doc/Key-Concepts-in-IBEX.rst b/doc/Key-Concepts-in-IBEX.rst
@@ -166,7 +166,7 @@ A veto is a hardware signal that can, on a frame by frame basis, tell the DAE no
 
 * ISIS 50Hz veto: vetoes frames when accelerator not running at 50Hz (e.g. during beam run up or diagnostics) 
 
-  * Used on IRIS/OSIRIS, but they also use ISISFREQ SECI block 
+  * Used on IRIS/OSIRIS, but they also use ISISFREQ block
 
 .. _concept_timing:
 

diff --git a/doc/Obsolete.md b/doc/Obsolete.md
diff --git a/doc/concepts/Blocks.rst b/doc/concepts/Blocks.rst
@@ -1,7 +1,7 @@
 Blocks
 ######
 
-The IBEX concept of a block is similar to SECI, in that it is a relevant piece of information chosen by the scientist that will be displayed on the instrument dashboard and, if required, can be logged into the datafile.
+The concept of a block is that a relevant piece of information chosen by the scientist that will be displayed on the instrument dashboard and, if required, can be logged into the datafile.
 
 In IBEX, a block is, to all intents and purposes, an alias to a process variable.  For example, the block ``Chop1Freq`` on LARMOR is defined to be the process variable ``IN:LARMOR:CS:SB:Chop1Freq``.  It is much simpler to refer to a block than to refer to a process variable.  Utilities like genie_python know about blocks, and you can use commands such as ``cset`` to access ``Chop1Freq``. However, you can access blocks using the name ``IN:LARMOR:CS:SB:Chop1Freq``  with any standard EPICS tool.
 

diff --git a/doc/index.md b/doc/index.md
@@ -44,7 +44,6 @@ How-To
 IBEX-File-Paths-page
 Instrument-Specific-Guidance
 Device-Specific-Guidance
-Obsolete
 ```
 
 ## Further information & Links

diff --git a/doc/inst_specific/Engin-X-Sample-Stack.md b/doc/inst_specific/Engin-X-Sample-Stack.md
@@ -1,6 +1,6 @@
 # Engin-X Sample Stack
 
-The Engin X Sample Stack is controlled through IBEX but underneath IBEX link back into LabVIEW VIs from SECI hence why there are some special steps you need to use when looking at it. If you can't find the answer you are looking for in this page there is more information in the [developer wiki but beware this is quite low level](https://isiscomputinggroup.github.io/ibex_developers_manual/specific_iocs/motors/EnginX-Sample-Positioner.html).
+The Engin X Sample Stack is controlled through IBEX but underneath IBEX link back into LabVIEW VIs, hence why there are some special steps you need to use when looking at it. If you can't find the answer you are looking for in this page there is more information in the [developer wiki but beware this is quite low level](https://isiscomputinggroup.github.io/ibex_developers_manual/specific_iocs/motors/EnginX-Sample-Positioner.html).
 
 ## Define a Motor Position on the Engin-X Sample Stack
 - Using a file explorer, go to the following location on `ndxenginx`: `C:\Labview Modules\Drivers\Galil DMC2280`

diff --git a/doc/introduction/Starting-and-Stopping-IBEX.rst b/doc/introduction/Starting-and-Stopping-IBEX.rst
@@ -52,37 +52,3 @@ Stopping IBEX Server
 If you want to stop running the server, it is probably best to make sure you have stopped your client.
 
 Similar to the ``start_ibex_server.bat`` there is a ``stop_ibex_server.bat`` which you can usually access in the same ways. There will either be a shortcut in your start menu, which points to a file in the EPICS directory.
-
-
-Starting and Stopping IBEX Server After/Before Running SECI
------------------------------------------------------------
-
-There is a special case when you want to swap from IBEX to SECI when SECI is using IBEX as a *mini-inst* (this means IBEX is running an underlying ioc like the JASCO pump or a special DAE process). In this case there are multiple files that need to be changed to run in the two modes. To facilitate swapping there are scripts to allow you to do this easily. 
-
-Starting IBEX Server after running SECI
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To start IBEX Server after running SECI, proceed as follows:
-
-#. Use Windows Remote Desktop Connection to log in to your instrument control PC
-#. Open a command window
-#. At the command prompt type the following::
-
-    cd c:\Instrument\Apps\EPICS
-    start_ibex_server_close_seci.bat
-
-#. Allow the script a few minutes to complete.
-
-Stopping IBEX Server before running SECI
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To stop IBEX Server and then start SECI, proceed as follows:
-
-#. Use Windows Remote Desktop Connection to log in to your instrument control PC
-#. Open a command window
-#. At the command prompt type the following::
-
-    cd c:\Instrument\Apps\EPICS
-    stop_ibex_server_start_seci
-
-#. Allow the script a few minutes to complete.
diff --git a/doc/introduction/What-Is-IBEX.rst b/doc/introduction/What-Is-IBEX.rst
@@ -23,9 +23,3 @@ Introduction to genie_python
 ------------------------------------------------
 
 A full reference to genie_python is available `on GitHub <https://isiscomputinggroup.github.io/genie/genie_python>`_ or internally `on shadow <http://shadow.nd.rl.ac.uk/genie_python/sphinx/genie_python.html>`_.
-
-Previous Instrument Control at ISIS
-------------------------------------------------
-You can find out more about the previous control system, SECI, and how it relates to IBEX :doc:`here<../obsolete/Previous-Instrument-Control-at-ISIS-‐-SECI>`.
-
-
diff --git a/doc/obsolete/Converting-Open-GENIE-to-genie_python.rst b/doc/obsolete/Converting-Open-GENIE-to-genie_python.rst
diff --git a/doc/obsolete/Previous-Instrument-Control-at-ISIS-‐-SECI.rst b/doc/obsolete/Previous-Instrument-Control-at-ISIS-‐-SECI.rst