IMAT: Look at scripts

[John-Holt-Tessella]

IMAT scripts currently do g.load script in the instrument scrips. This is bad for performance and other things. Can we help them do this better? They still want to know if there are errors in these scripts (which are loaded from the script drive) because they are developing them. They are aware of the risks of not being able to run of the network goes down.

Acceptance Criteria

• Move g.load_scripts to imports in the inst folder

[FreddieAkeroyd]

Two issues to consider:

• load_script v import (performance)
• local v network drive (reliability, possible performance issue too)

we may or may not want to address both here

[ChrisM-S]

I'm also a little concerned (possibly completely unfounded if this is not what they are doing) that this might also act as a way of making it easier for them to load a script editable by the users sitting somewhere like C:\Scripts (from a more tested instrument script).

This would invert the ideal call order below in favour of a "hook" into a user script. user script -- calls --> tested instrument script function

(Much better to get the users to just type one line in the console to get any user side scripts started)