Spencer KiytuneX is a web application integrated into the beam framework. The tuneX application is divided into two main functions: tuneLoader and tuneDisplay. tuneLoader is designed to allow users to calculate and load a tune based on entered beam parameters, while tuneDisplay is intended to display graphically the differences between a calculated tune and the current device parameters.
This application was initially started with the ISAC/ARIEL RIB facility in mind, due to the large amount of possible beam paths, parameters, etc. It should however be flexible and able to be implemented in other control rooms if it is considered useful.
In ISAC, the tuneLoader portion of this application is intended to eventually obsolete the current sources for theoretical tune optics, which is the beam dynamics webpage for low energy (http://web.accel.triumf.ca/~baartman/Tunes/), and the OPTICS ISAC-I and OPTICS ISAC-II spreadsheets for high energy. These sources do not include any values for steerers, and are still typed in by hand for hundreds of devices.
Also in ISAC, tuneDisplay will replace the already existing tuneDisplay, written by Olivier Shelbaya, that can be seen at http://mcewan.triumf.ca/cgi-bin/autoTune2/Iterate.pl (possibly only accessible inside the controls firewall). A few examples of this can be seen in the pictures below.
The objectives of the tuneLoader app are:
- To simplify and expedite the loading of optics values when operators start tuning of a beamline.
- To reduce facility overhead (tuning time) by giving operators significantly improved optics values for use when starting tuning through any section of beamline.
- To give the Beam Delivery and Beam Physics groups a utility to continually monitor and improve upon tunes through beamlines while the procedures for operators remain unchanged.
The objectives of the tuneDisplay app are:
- To reduce facility overhead by clearly displaying the status of a given tune compared to the best known, calculated, tune (this will, among other things, expedite troubleshooting of a tune).
- To provide a full-picture tune diagnostic tool to users by including all possible devices that could affect the beam for a given tune.
- To give the Beam Delivery and Beam Physics groups a utility to continually monitor and improve upon tunes through beamlines while the procedures for operators remain unchanged.
Some examples of initial design of various tuneX webpages:
This is the initial webpage a user would land on when going to the tuneX appplicaiton. Here the user would choose their corresponding facility (ISAC, E-Linac, Cylotron, etc).
After selecting a facility, the user would then select a beampath. For facilities with few beampaths these could be listed as shown here. For ISAC/ARIEL however this page will prompt with questions (source, destination, options) to identify the correct path/tune to use.
After selecting a path/tune, the app searches through the tune, and prompts the user for any inputs that will be necessary to calculate this tune. At this point the user can either load the tune, or go to tuneDisplay to visualize the current device setpoints compared to the calculated tune.
If the user inputs invalid values (text where a number is expected, or beam parameters outside of the machine's specifications), they are directed to an error page.
If the user inputs are valid, the tune is loaded to the devices. The user is the re-directed to this page showing the entered beam parameters, calculated setpoints, and the current device setpoints. Devices that do not match are highlighted.
Some examples of the current TuneDisplay interface, written by Olivier Shelbaya:
Some examples of the current OPTICS spreadsheets used in ISAC:
