Repository navigation
DETECT: Update and document etc NDXDETECT and NDXDETECT2 and NDXDETECT3 #8842
Description
Issue Description
As a member of the Experiment Controls group I would like to have the NDX and NDHs for the detector group treated, and documented, the same as the rest of the machines we support.
How & Where?
In conversation with JS (Detectors group leader), he mentioned something he would like on IBEX on NDXDETECT to @GRyall . @GRyall was puzzled as he has never heard of these or seen them mentioned in deploy tickets and the like.
Initial investigation suggests NDXDETECT2 is running These are running an old version (?9?) of IBEX.
Additional Information
Host include, but may not be limited to:
- NDXDETECT
- NDXDETECT2
- NDHDETECT
- NDHDETEC2
The scope of work includes:
- Finding out if there are any more DETECT hosts
- upgrading IBEX on them to the current version
- Ensuring our templates for deploys and all instruments (etc.) include the hosts
- Ensuring we are running the same Nagios checks on them as other support machines
- ensuring they appear in inst list so they e.g. appear in the wall display
See our Git Workflow.
Acceptance Criteria
- hosts identified
- IBEX upgraded
- hosts appear in nagios
- hosts appear in inst list and so on wall display
- templates that list hosts (e.g. deploy tickets and all instrument issues) updated
- documentation reflects the existence of these hots
- ...
How to Review
Before making a PR...
- Provide verbose instructions for the reviewer to test that your changes work and fix the issue
- Describe if/how you have implemented testing for this issue
- Provide screenshots of the feature to help the reviewer if relevant
If not applicable, write "Not applicable"
...
To the reviewer: Make sure to update submodules!
Discussed 01:07:00 - in planning 02/10/25
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[-]DETECT: Update and document etc NDXDETECT and NDXDETECT2[/-][+]DETECT: Update and document etc NDXDETECT and NDXDETECT2 and NDXDETECT3[/+]KathrynBaker commentedon Jul 22, 2026
Two of these systems are in the progress of being put back together, the third is in use, but will be updated to be the same as the other two. I have asked about updating the version of IBEX on that existing system from version 9.x.x to something more current.
KathrynBaker commentedon Aug 21, 2026
I have not heard anything, and am considering that the system is not being used at all (the computer was restarted but IBEX is not yet running again), so have asked opinions on whether to warn the detector group and go for the massive jump, wait until at least one of the other two is available, or just give the detector group a week or so to use the system and then just go for the upgrade anyway.
KathrynBaker commentedon Oct 1, 2026
Per the Hardware list (there is an appropriate sharepoint link on https://shadow.nd.rl.ac.uk/ibex_sysadmin_manual/systems/NDH.html) there are 3 nominal DETECT instruments. 1 and 3 are not available at present, 2 is.
1 and 3 should follow eventually, but there is no timeline at present, so this has focussed on bringing DETECT2 into a maintainable state.
IBEX has been upgraded on DETECT2.
DETECT2 has been added to the release groups list (https://github.com/ISISComputingGroup/IBEX/wiki/Release-Group and https://github.com/ISISComputingGroup/IBEX/wiki) with the support systems in the Winter Deploy/Group B, which is where it was in the Ansible playbooks.
Similarly it was added into the PI Template (https://github.com/orgs/ISISComputingGroup/projects/9) in the Deploy Ticket
#9036 is the PR for adding it to the Issues Template
#9037 was created to add DETECT2 to the instrument list, PR For the flash review: ISISComputingGroup/EPICS-inst_servers#461, the associated script has been run and all should be in place and hopefully reviewed as part of 9037
As per the requirements the changes have been made to Nagios already. https://github.com/ISISComputingGroup/ControlsWork/pull/883 has been created to cover which files were changed, note that the NDH and NDX were just created, but as well as the DETECT2 host group, R52 was also created to allow for that as a lookup on the hosts page in Nagios. Some of the inapplicable at present services have been hidden, and only the empty journal warning remains as that is likely valid until a run is undertaken which writes something to it.