... | @@ -20,23 +20,23 @@ Some examples of initial design of various tuneX webpages: |
... | @@ -20,23 +20,23 @@ Some examples of initial design of various tuneX webpages: |
|
|
|
|
|
![tuneX_landing](/uploads/8ef63687043068c5c610aba3636eef02/tuneX_landing.png)
|
|
![tuneX_landing](/uploads/8ef63687043068c5c610aba3636eef02/tuneX_landing.png)
|
|
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).
|
|
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).
|
|
<br><bR>
|
|
<br><bR><bR>
|
|
|
|
|
|
![tuneX_choosepath](/uploads/7bfa3ef7f125d9567334024e8e8ae905/tuneX_choosepath.png)
|
|
![tuneX_choosepath](/uploads/7bfa3ef7f125d9567334024e8e8ae905/tuneX_choosepath.png)
|
|
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 for the use.
|
|
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 for the use.
|
|
<br><bR>
|
|
<br><bR><bR>
|
|
|
|
|
|
![tuneX_beamparams](/uploads/df2b05818372503206abc5bcc2a6e964/tuneX_beamparams.png)
|
|
![tuneX_beamparams](/uploads/df2b05818372503206abc5bcc2a6e964/tuneX_beamparams.png)
|
|
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.
|
|
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.
|
|
<br><bR>
|
|
<br><bR><bR>
|
|
|
|
|
|
![tuneX_error](/uploads/8a3ba36d9ba56b1598765383b188b6c8/tuneX_error.png)
|
|
![tuneX_error](/uploads/8a3ba36d9ba56b1598765383b188b6c8/tuneX_error.png)
|
|
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 invalid values (text where a number is expected, or beam parameters outside of the machine's specifications), they are directed to an error page.
|
|
<br><bR>
|
|
<br><bR><bR>
|
|
|
|
|
|
![tuneX_readbacks](/uploads/def8e7077a640fe3fb7682934b3b338d/tuneX_readbacks.png)
|
|
![tuneX_readbacks](/uploads/def8e7077a640fe3fb7682934b3b338d/tuneX_readbacks.png)
|
|
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.
|
|
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.
|
|
<br><bR>
|
|
<br><bR><bR>
|
|
|
|
|
|
Some examples of the current TuneDisplay interface, written by Olivier Shelbaya:
|
|
Some examples of the current TuneDisplay interface, written by Olivier Shelbaya:
|
|
![tuneDisplay1](/uploads/e598403b7f7c40c09c77f8e7d9d1d78f/tuneDisplay1.png)
|
|
![tuneDisplay1](/uploads/e598403b7f7c40c09c77f8e7d9d1d78f/tuneDisplay1.png)
|
... | | ... | |