Discussion Notes from Release 10.0.0 Demo with Reflectometry

[JackEAllen]

Discussion took place between 16:00-17:00 07/03/2022
Members from IBEX present:

• @ThomasLohnert
• @JackEAllen

Instrument scientists present:

• POLREF

The purpose of the discussion was to summarise and explain changes made to IBEX as part of the 10.0.0 release relevant to Reflectometry since last used just over a year ago.

Below is a summary of actionable points discussed.

Summary:

• Main priority is performance issues with CPU usage and memory issues (memory is better, but still filling up quite fast)
• Characteristic values - Would like a header for this column called “Dial Position” and easy way to find documentation on how to add value to column.
• Similarly to INTER, POLREF would like to be able to lock certain axis, for example the Polariser #7073
  • POLREF don’t want to move the polariser sometimes and would like a button that says “Lock” to disable in redefine motors tab.
• POLREF would like there to be a confirmation step when redefining a position from the reflectometry OPI (instead of setting it as soon as you press "enter" on the text entry field) #7070
• Documentation for who to contact to link drive to NDXPOLREF to allow for using various tools such as pycharm to work on NDXPOLREF
• Using scan(block, .. ..., fit=SlitScan) useful compared to just taking the points - Would like documentation on how to do this.
• MercuryITC boxes front panel disconnected - fixed - Still struggling with when setting up VI, A discussion will take place to make this easier Thursday 10th or Friday 11th March 2022. Users would like master tab to view them all in VI.
• Easy way of picking up syntactical errors for dry runs was discussed. Users find it frustrating when error only occurs during runtime as this causes retries of real runs because not picked up in dry runs - can only really be done through manual checks.