Skip to content

Commit 8a9c901

Browse files
authored
Merge pull request #4 from ISISComputingGroup/seci_dead
Remove obsolete
2 parents 0710de0 + 42c4cb8 commit 8a9c901

12 files changed

+4
-252
lines changed

doc/FAQ.rst

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -29,15 +29,10 @@ How do I install IBEX Client?
2929

3030
To install IBEX Client - see :ref:`installing_ibex_client`.
3131

32-
Can I run IBEX and SECI at the same time?
33-
-----------------------------------------
34-
35-
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.
36-
3732
Which version of Python does IBEX use?
3833
--------------------------------------
3934

40-
IBEX currently uses Python 3.11.2.
35+
IBEX currently uses Python 3.12
4136

4237
Where can I learn about Python?
4338
-------------------------------
@@ -67,11 +62,6 @@ How do I stop IBEX Server?
6762

6863
To stop IBEX Server - see :ref:`stopping_ibex_server`.
6964

70-
Can I switch from running IBEX to SECI and vice-versa?
71-
------------------------------------------------------
72-
73-
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.
74-
7565
Can I write scripts to control my experiment?
7666
---------------------------------------------
7767

doc/Key-Concepts-in-IBEX.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,7 @@ A veto is a hardware signal that can, on a frame by frame basis, tell the DAE no
166166

167167
* ISIS 50Hz veto: vetoes frames when accelerator not running at 50Hz (e.g. during beam run up or diagnostics)
168168

169-
* Used on IRIS/OSIRIS, but they also use ISISFREQ SECI block
169+
* Used on IRIS/OSIRIS, but they also use ISISFREQ block
170170

171171
.. _concept_timing:
172172

doc/Obsolete.md

Lines changed: 0 additions & 16 deletions
This file was deleted.

doc/concepts/Blocks.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
Blocks
22
######
33

4-
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.
4+
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.
55

66
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.
77

doc/index.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,6 @@ How-To
4444
IBEX-File-Paths-page
4545
Instrument-Specific-Guidance
4646
Device-Specific-Guidance
47-
Obsolete
4847
```
4948

5049
## Further information & Links

doc/inst_specific/Engin-X-Sample-Stack.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Engin-X Sample Stack
22

3-
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).
3+
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).
44

55
## Define a Motor Position on the Engin-X Sample Stack
66
- Using a file explorer, go to the following location on `ndxenginx`: `C:\Labview Modules\Drivers\Galil DMC2280`

doc/introduction/Starting-and-Stopping-IBEX.rst

Lines changed: 0 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -52,37 +52,3 @@ Stopping IBEX Server
5252
If you want to stop running the server, it is probably best to make sure you have stopped your client.
5353

5454
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.
55-
56-
57-
Starting and Stopping IBEX Server After/Before Running SECI
58-
-----------------------------------------------------------
59-
60-
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.
61-
62-
Starting IBEX Server after running SECI
63-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
64-
65-
To start IBEX Server after running SECI, proceed as follows:
66-
67-
#. Use Windows Remote Desktop Connection to log in to your instrument control PC
68-
#. Open a command window
69-
#. At the command prompt type the following::
70-
71-
cd c:\Instrument\Apps\EPICS
72-
start_ibex_server_close_seci.bat
73-
74-
#. Allow the script a few minutes to complete.
75-
76-
Stopping IBEX Server before running SECI
77-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
78-
79-
To stop IBEX Server and then start SECI, proceed as follows:
80-
81-
#. Use Windows Remote Desktop Connection to log in to your instrument control PC
82-
#. Open a command window
83-
#. At the command prompt type the following::
84-
85-
cd c:\Instrument\Apps\EPICS
86-
stop_ibex_server_start_seci
87-
88-
#. Allow the script a few minutes to complete.

doc/introduction/What-Is-IBEX.rst

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,3 @@ Introduction to genie_python
2323
------------------------------------------------
2424

2525
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>`_.
26-
27-
Previous Instrument Control at ISIS
28-
------------------------------------------------
29-
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>`.
30-
31-

doc/obsolete/Converting-Open-GENIE-to-genie_python.rst

Lines changed: 0 additions & 66 deletions
This file was deleted.

doc/obsolete/Previous-Instrument-Control-at-ISIS-‐-SECI.rst

Lines changed: 0 additions & 37 deletions
This file was deleted.

0 commit comments

Comments
 (0)