Chris Gavanas 31/08/2016 Summer Student Report

Outline Script to automate tasks Iso-target heating Iso-proton integrator ASAP application Minor improvements in existing applications

Script to record devices used inside code The devices in ISOLDE are numerous. Each one of them has a name and a few: Parameters Fields Some times in the past the parameters change without communicating it to OP and we find out the hard way. This application would proactively inform us of any changes to any ISOLDE related classes. However after implementing a part of it, I’ve realised that it’s not viable without tools that I am not aware of.

Iso-Target App HRS/GPS target and line need heating or cooling quite frequently. However this procedure sometimes lasts several hours. A progress bar and an estimated timer have been added to the existing application so the user can know in advance the exact time that the procedure would take, but also watch in real time the progress in a more friendly interface. You can see the screenshots below:

Cooling Heating At last if multiple different users try to heat or cool the target/line from a different terminal then both applications will stop to prevent damaging the target.

(After set-up auto-save App) ASAP (After set-up auto-save App) Before each experiment, there is a lot of beam set up that needs to be done. This set up is always saved in the logbook manually with some calculations and screenshots. This process can take up to 30’. Some times important data are missing. There is no standard template. This new application comes to (almost) automate this job and decrease its time from ½ hour to less than a minute and also ensure that the procedure is completed successfully.

Application configuration The user must set the below configuration: Starting from HRS or GPS Follow path of CAO, GHM or GLM Oven1 and Oven2 (optional) material used The user can also exclude devices from a list whose values will not be saved. You can take a look a beta version of it in the screenshot below:

Application’s task and output The value of several critical devices is stored The value of beam in every faraday cup device is stored Screenshots of grids are taken (IN/OUT operation needed to be done manually) Screenshots of wire scanners are taken (IN/OUT operation needed to be done manually) User can add his own comments All the above are stored to logbook User can exclude easily any of the above tasks Storing functionality of electrostatic elements will be added next week

Procedural decisions Sometimes there may be some impediments to the automation of this procedure. Active lasers Switchyard set for GHM or GLM Closed valves In case the lasers are on, the devices affected by them are ignored in the procedure. When the Switchyard is set to GHM or GLM path, the faraday cup value from that position is asked from the user as an input since faraday cup can’t be inserted. In case the valves are closed, the user should be notified and the process would be stopped. However there is not any library in JAVA at the moment to allow the check of the valves, so this could be added in the future.

Iso-Proton Integrator Until now every user needed to copy manually to the logbook the number of protons. This could result to accidental errors while copying those big numbers. This procedure has been now automated by a button as you can see on the screenshot below:

More applications… I have also made slight changes to Iso-HtControl application to improve the graphical user interface in panel Found and reported a bug in a very commonly used library at CERN (WheelSwitch)

Any Questions???

Thanks for your time. Many thanks to my supervisor Eleftherios Fadakis and everyone else in ISOLDE I collaborated with. It was a very pleasant 3 months stay and a great experience. Thank you all!