| ... | ... | @@ -4,12 +4,18 @@ This application was initially started with the ISAC/ARIEL RIB facility in mind, |
|
|
|
|
|
|
|
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 source do not include any values for steerers, and are still typed in by hand for hundreds of devices.
|
|
|
|
|
|
|
|
The objectives of the tuneLoader app are:
|
|
|
|
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:
|
|
|
|
|
|
|
|
|
| ... | ... | |
