Script Generator

The purpose of this page is to collect requirements, ideas, suggestions, etc. for a Script Generator for IBEX. The requirements are listed in no particular order. When the time comes to create the Script Generator a selection of these ideas (i.e. those judged to be of the highest priority) can be turned into user stories for implementation.

Script Generator Requirements

1. Script Generator should be capable of working offline (i.e. stand-alone, remotely from IBEX). This has several advantages:
   1. the Script Generator can be given to visiting scientists to prepare their own scripts ahead of their visit to ISIS. This helps maximise the use of beam time (i.e. there are no delays while users write scripts).
   2. a separate Script Generator does not need to run on the IBEX control PC. This means that the task of writing scripts does not interfere with the task of controlling the instrument.
2. Script Generator could be integrated with IBEX. This has the advantage of being able to use IBEX configs (to get information about blocks) and local genie_python libraries (to use instrument specific methods).
3. Implementing the Script Generator as a web application might be one approach to creating a solution that satisfies the two previous requirements.
4. The Script Generator should be capable of submitting scripts to the IBEX ScriptServer.
   1. this capability should only be available to users in the instrument control cabin (i.e. it should not be possible to submit scripts from remote locations).
   2. once a script has been sent from the Script Generator to the IBEX ScriptServer any modification (e.g. on-the-fly editing of the script, adjusting its position in the queue) should be done via IBEX ScriptServer.
5. The Script Generator should allow the user to set a run title
6. The Script Generator should allow the user to switch between detector & monitor type measurements (is this the same as switching between transmission & reflection measurements?).