tuneX issueshttps://gitlab.triumf.ca/hla/beam/tuneX/-/issues2022-01-09T14:51:04-08:00https://gitlab.triumf.ca/hla/beam/tuneX/-/issues/47Implementation of shared power supply devices is inconcistent with EPICS2022-01-09T14:51:04-08:00Rob ShanksImplementation of shared power supply devices is inconcistent with EPICSThere are devices that share power supplies and as a result, setpoints. Some of these devices in the ILE2 line,(there may be others but these are the ones I noticed) only respond to setpoints entered on one of the device sliders. TuneX o...There are devices that share power supplies and as a result, setpoints. Some of these devices in the ILE2 line,(there may be others but these are the ones I noticed) only respond to setpoints entered on one of the device sliders. TuneX only displays one of the devices that shares a power supply. The device that is displayed is not the one that is used to set the device(s) in EPICS.
The result is that when a tune is loaded through TuneX, the setpoint of the device that doesn't control the setpoint is changed but the voltage on the device(s) doesn't change. The listing in TuneX doesn't show a problem because the setpoint has changed to the desired value. This behavior is seen on ILE2:Q1/Q10 and ILE2:Q2/Q9. ![grab.nNMbCq](/uploads/8adc470fa4fef764b534953d11575047/grab.nNMbCq.png)![grab.yWMf1V](/uploads/ed0cc2a7ea5af09f0d92faff4e56b12c/grab.yWMf1V.png)https://gitlab.triumf.ca/hla/beam/tuneX/-/issues/33Show selected options on ISAC beam path selection page.2022-01-09T14:28:56-08:00Spencer KiyShow selected options on ISAC beam path selection page.https://gitlab.triumf.ca/hla/beam/tuneX/-/issues/46Calculated values for bend box plates don't match EPICS values2019-10-02T10:18:57-07:00Rob ShanksCalculated values for bend box plates don't match EPICS valuesBenders have 2 HV plates that are usually controlled by setting one plate and EPICS automatically setting the other based on the first one. The values for the same plates that are calculated by TuneX do not match both plates. The result ...Benders have 2 HV plates that are usually controlled by setting one plate and EPICS automatically setting the other based on the first one. The values for the same plates that are calculated by TuneX do not match both plates. The result is that one plate will always show up red TuneX. Not sure if this is a TuneX problem or the scale factor for EPICS needs to be changed.https://gitlab.triumf.ca/hla/beam/tuneX/-/issues/52ILE2T:B1 pos/neg values switched2019-10-02T10:18:08-07:00tiffILE2T:B1 pos/neg values switched![grab.El2SMr](/uploads/5461566ac4d94598ad4d8f6fa8a9e3a6/grab.El2SMr.png)![grab.tL0Pbc](/uploads/4e3a9d66218e64542e63a5a20d5740a4/grab.tL0Pbc.png)![grab.Kvom61](/uploads/f1f2d210f801cdb212f7faf95cb4e474/grab.Kvom61.png)noticed by Titan y...![grab.El2SMr](/uploads/5461566ac4d94598ad4d8f6fa8a9e3a6/grab.El2SMr.png)![grab.tL0Pbc](/uploads/4e3a9d66218e64542e63a5a20d5740a4/grab.tL0Pbc.png)![grab.Kvom61](/uploads/f1f2d210f801cdb212f7faf95cb4e474/grab.Kvom61.png)noticed by Titan yesterday.https://gitlab.triumf.ca/hla/beam/tuneX/-/issues/10tuneDisplay should split into a variable number of graphs based on the number...2019-10-02T10:09:14-07:00Spencer KiytuneDisplay should split into a variable number of graphs based on the number of elementshttps://gitlab.triumf.ca/hla/beam/tuneX/-/issues/59Possible missing step in, "Assignment - Intro to Flask Hello World Example", ...2019-10-02T10:08:39-07:00Rob ShanksPossible missing step in, "Assignment - Intro to Flask Hello World Example", instructionsHi all, I think I found a missing step on step 0 in the, "Assignment - Intro to Flask Hello World Example", tutorial.
Problem: Step 0 instructs the user to create their own git branch with the command, "git checkout mybranchname".
This ...Hi all, I think I found a missing step on step 0 in the, "Assignment - Intro to Flask Hello World Example", tutorial.
Problem: Step 0 instructs the user to create their own git branch with the command, "git checkout mybranchname".
This produces an error message,
"error: pathspec 'mybranchname' did not match any file(s) known to git."
I did some checking and it appears that the new branch needs to be created with the command:
git branch newbranchname
And then connected to with the command:
git checkout newbranchname
It is entirely possible that I misunderstood something. If so please let me know.
Rob S.https://gitlab.triumf.ca/hla/beam/tuneX/-/issues/4Automatic re-calculating of DTL quads and SC linac solenoids2019-08-21T14:09:36-07:00Spencer KiyAutomatic re-calculating of DTL quads and SC linac solenoidsCurrently SK has setup subroutines to read DTL or SC linac status and calculate quad or solenoid setpoints based on this, *only when* 'tuneDisplay' or 'Load Tune' is pressed from the beam properties form. So if a user is tuning the DTL a...Currently SK has setup subroutines to read DTL or SC linac status and calculate quad or solenoid setpoints based on this, *only when* 'tuneDisplay' or 'Load Tune' is pressed from the beam properties form. So if a user is tuning the DTL and the on/off status of tanks has changed, they currently have to return to the form so values are re-calculated. It would be worth considering having this automatically re-calculated when EPICS values are polled.https://gitlab.triumf.ca/hla/beam/tuneX/-/issues/53Add Griffin slit widths to TuneX2019-08-21T14:09:36-07:00Spencer KiyAdd Griffin slit widths to TuneXhttps://gitlab.triumf.ca/hla/beam/tuneX/-/issues/56Add Stephanie's Elinac calculator code to TuneX elinac page2019-08-21T14:08:59-07:00Spencer KiyAdd Stephanie's Elinac calculator code to TuneX elinac pagehttps://gitlab.triumf.ca/hla/beam/tuneX/-/issues/57Fix bug so that any floating point number can be entered for energy2019-06-20T10:16:38-07:00Spencer KiyFix bug so that any floating point number can be entered for energyhttps://gitlab.triumf.ca/hla/beam/tuneX/-/issues/55beam envelope: unable to load tune2019-04-10T13:23:47-07:00tiffbeam envelope: unable to load tunehttp://dev.envelope.triumf.ca/ariel/agtis-ebis-ayield/
save tune (as .json); attempt to (re)load seems to do nothing:
![envelope_unable_to_load](/uploads/bbc0d887d2d9a23eee3a92b83e2f21b1/envelope_unable_to_load.PNG)http://dev.envelope.triumf.ca/ariel/agtis-ebis-ayield/
save tune (as .json); attempt to (re)load seems to do nothing:
![envelope_unable_to_load](/uploads/bbc0d887d2d9a23eee3a92b83e2f21b1/envelope_unable_to_load.PNG)https://gitlab.triumf.ca/hla/beam/tuneX/-/issues/54Update formatting of isotope on tuneloader and tunedisplay pages2019-01-30T13:33:44-08:00Spencer KiyUpdate formatting of isotope on tuneloader and tunedisplay pagesKenneth LamKenneth Lamhttps://gitlab.triumf.ca/hla/beam/tuneX/-/issues/25Consider only displaying DTL energy if it is non-standard (1.50 MeV/u)2018-11-07T13:34:11-08:00Spencer KiyConsider only displaying DTL energy if it is non-standard (1.50 MeV/u)https://gitlab.triumf.ca/hla/beam/tuneX/-/issues/35Mobile display of beam path name2018-10-31T14:08:35-07:00Carla BarquestMobile display of beam path nameFinal beam path name is being cut off on mobile display when selecting beam path @sradel @cbarquest (╯°□°)╯︵ ┻━┻Final beam path name is being cut off on mobile display when selecting beam path @sradel @cbarquest (╯°□°)╯︵ ┻━┻Kenneth LamKenneth Lamhttps://gitlab.triumf.ca/hla/beam/tuneX/-/issues/5Molecule masses for FEBIAD targets2018-10-30T16:41:39-07:00Olivier ShelbayaMolecule masses for FEBIAD targetsIt was pointed out by an ISAC operator that currently there are no options for molecular masses when operating a FEBIAD with tuneX. We should add a functionality allowing for molecular masses, which presumably would simply add two (or mo...It was pointed out by an ISAC operator that currently there are no options for molecular masses when operating a FEBIAD with tuneX. We should add a functionality allowing for molecular masses, which presumably would simply add two (or more) isotope masses together as desired.Kenneth LamKenneth Lam2018-06-30https://gitlab.triumf.ca/hla/beam/tuneX/-/issues/13Implement beam parameter error checking2018-10-30T14:03:24-07:00Spencer KiyImplement beam parameter error checkingKenneth LamKenneth Lamhttps://gitlab.triumf.ca/hla/beam/tuneX/-/issues/36'0' is accepted in the charge and energy fields, this creates an 'internal se...2018-10-29T14:55:35-07:00Justin Lewis'0' is accepted in the charge and energy fields, this creates an 'internal server error'#### Summary
Entering a zero into any of the fields and trying to view loader/display will return a '500 internal server error'.
#### Steps to reproduce
1) Enter a '0' into any of the fields while attempting to load a tune
2) Click '...#### Summary
Entering a zero into any of the fields and trying to view loader/display will return a '500 internal server error'.
#### Steps to reproduce
1) Enter a '0' into any of the fields while attempting to load a tune
2) Click 'loader' or 'display' buttons
#### What is the current bug behavior?
(What actually happens)
#### What is the expected correct behavior?
Should probably only allow values greater than (not equal to) zero.
#### Any other reference material (i.e. relevant logs and/or screenshots)
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)Kenneth LamKenneth Lamhttps://gitlab.triumf.ca/hla/beam/tuneX/-/issues/6tuneX needs to be able to handle multiple tune files for a given path2018-10-29T14:49:55-07:00Spencer KiytuneX needs to be able to handle multiple tune files for a given pathAfter a beam path is selected, tuneX should search for all tune files beginning with this path, and display them all as possible selections (drop-down list?) on the same page where beam parameters are selected. By default tuneX should se...After a beam path is selected, tuneX should search for all tune files beginning with this path, and display them all as possible selections (drop-down list?) on the same page where beam parameters are selected. By default tuneX should search for and select 'beampath_ref.xml'Kenneth LamKenneth Lam2018-10-12https://gitlab.triumf.ca/hla/beam/tuneX/-/issues/43De-Select button on Tune Loader only available after selecting all2018-10-29T14:49:49-07:00Rob ShanksDe-Select button on Tune Loader only available after selecting all#### Summary
The "De-Select All PVs" button in Tune Loader only appears after hitting the "Select All PVs" button. This is only a minor inconvenience since the button can be reached by clicking the "Select All PVs" button. This might no...#### Summary
The "De-Select All PVs" button in Tune Loader only appears after hitting the "Select All PVs" button. This is only a minor inconvenience since the button can be reached by clicking the "Select All PVs" button. This might not be obvious to a user though and could cause inconvenience if a user has manually selected several PVs and wishes to de-select them all.
#### Steps to reproduce
Open Tune Loader and only the "Select All PVs" and "Load Selected PVs" buttons are shown.
#### What is the current bug behavior?
The "Deselect All PVs" button only appears when you have clicked the "Select All PVs" button.
#### What is the expected correct behavior?
I would suggest giving the option to de-select all whenever a user has PVs selected.
#### Any other reference material (i.e. relevant logs and/or screenshots)
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)Kenneth LamKenneth Lamhttps://gitlab.triumf.ca/hla/beam/tuneX/-/issues/41Add A/Q to displayed beam parameters2018-10-29T14:49:39-07:00Spencer KiyAdd A/Q to displayed beam parametersKenneth LamKenneth Lam