-
Notifications
You must be signed in to change notification settings - Fork 2
Deployment on an Instrument Control PC
Jack Harper edited this page Oct 21, 2022
·
206 revisions
This document describes the steps necessary to install/upgrade IBEX on an Instrument control PC. Be sure to login as spudulike
when deploying on instruments instead of gamekeeper
.
- Inform the instrument scientist that you are going to upgrade the instrument in 5 minutes so that they are not surprised when you remote desktop to the instrument, include a link to the release notes of the latest release in this email. Wait 5 minutes.
- Visit each instrument on which code will be released and check for changes which have been made which are not summarised on the IBEX wiki. Do this by running
git status
in the EPICs directory and looking at the diff and comparing with those changes. - Make sure that the public share has the most recent version of
ibex_utils
from Git (i.e. do git pull).
- Run
<public share>\ibex_utils\installation_and_upgrade\instrument_install.bat
(if you are on a test machine you may have to enter the full DNS path rather than the shorthand)- It will look for the highest version number in the release folder as a source.
- If you want to install a non-default release you need to set the
SUFFIX
variable in the batch file. For example withx.y.z
being the current release andhotfix
being the suffix, it will look for the folderReleases/x.y.z-hotfix
- Follow the instructions on the command line.
- If needed, shutdown IBEX and upgrade the ISISICP. Remember to run the journal parser installation (Step 8 of upgrading ICP) - this can take some time.
- After the script has successfully finished and the IBEX server has been started, run
instrument_test.bat
in the same folder and follow the instructions.
- Ensure the instrument is running and in a setup state (e.g. so you can take screenshots of blocks, motors, running VIs, etc.)
- Ensure all command lines to EPICS are closed
- Run
<public share>\ibex_utils\installation_and_upgrade\instrument_deploy.bat
- It will look for the highest version number in the release folder as a source.
- If you want to install a non-default release you need to set the
SUFFIX
variable in the batch file. For example withx.y.z
being the current release andhotfix
being the suffix, it will look for the folderReleases/x.y.z-hotfix
- Apart from the below points, just follow instructions
- 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