Skip to content

2018 11 23 GEM SANDALS POLARIS INES demo

Jump to bottom
Freddie Akeroyd edited this page Nov 28, 2021 · 2 revisions

  • Genie python consoles: It is difficult to know what consoles are running. SANDALS has two scripts running at the same time last cycle. We showed them how to view the list of consoles and start multiple consoles. They would like a new tab for each console that is running, I said we would create a ticket (see #3769 which was already created)

  • They love the idea of the script server but the only person to try could not make it work (we think they didn't have the import line). They would like some training in this. If others ask for it lets do this.

  • Would like a way of checking scripts (including if blocks are not defined in a configuration). This is on our roadmap but is hard.

  • Instrument scientists would like a way of setting up conditions under which they are automatically contacted. E.g. If there is an alarm, if no data is collected for a time, if a pv becomes/doesn't become. (see #3811)

  • Is a script generator useful? Yes especially for express runs

  • Log plotter is now horrible. It needs to autoscale once on open then not again (report it is already in ticket #3585 have reproposed it)

  • Set points should be set to setpoint readback or readback on ioc startup. Said this was hard they said this was desired but not essential.

  • Alarms perspective is fairly underused but is being looked at. Would be better if alarm entries were more informative of what was going on. What is PV for? Can we make the description better. Created ticket 3812

  • Can the title in the dash board wrap onto multiple lines if needed ticket 3813

  • Talked about scripting technique, including a wait for time or block reaching a value; Said we could do this. Thinks we should create a wiki which has good examples of scripts in.

  • Indicate on the scripting view that the script server is running a script [ticket 3905]

Clone this wiki locally