2018 12 04 LARMOR ZOOM demo

LARMOR and ZOOM seem generally very happy with IBEX's performance. Below is the feedback from the sprint demo meeting with them, loosely categorised:

Reflectometry

As the scaling on live view changes between (for example) 4.9 and 4.91 it changes the width of the plot which gives the impression of a "judder".
Rob would like some instructions on how to set up a 1D live view.
Time-of-flight cut-off is not working properly - the data does not look like Rob expects. Apparently mantid has the same bug.
LARMOR would like to display two live views simultaneously, each of which is pinned to a specific period number
XY profile is "ridiculously useful" for aligning a beam-stop

Wiring table readback in the GUI is not updating when the tables are changed via genie_python
Alarms and ioc log perspectives "never contain anything of use" so they don't look at them
Python console can pop up in the wrong view
Would like script, graph and synoptic all on one screen
How do we define the order of blocks when those blocks are defined in components

LARMOR are still using globals.txt for most things. Asks what the "recommended" approach is.
If we set things up in the GUI configuration screens, can we see a list of ALL the macros that have been set (simultaneously)
Would like some form of warning/protection against loading a configuration with inconsistent macros (e.g. clashing COM port settings). Can we run configchecker locally on a config change and warn if tests fail?
LARMOR would like to refactor configurations and would like some advice about how best to set these up.
LARMOR would like a way to "dismiss" a block even though it is defined in the current config, to save space. This might not be needed after the refactoring mentioned above.
Long block names are being truncated in blocks view in the GUI

The server is too slow to start ("multiple minutes")
Lack of microsoft patches on NDH machine for processes not dying contributed to a DAE problem on surf/made it harder to diagnose.
SURF still runs SECI but has some IBEX processes installed. As a user it is not clear exactly what I need to start/restart after an NDX power cycle
Julabo - would like a way to send fixed values on IOC startup
Would like a (better) way to set motor limits as part of a configuration
KEPCO driver did not work. Failed to communicate. When the physical unit was swapped, the IOC talked but couldn't set a negative value