Display more information about the origin of a loaded instrument

[Martyn Gigg]

A few users have asked whether we can display source location for a loaded instrument, as it can be confusing when multiple files are involved along with embedded instrument definitions.

The work in #10489 will only extend the confusion when multiple locations are involved.

[Nick Draper]

re #10509 Add Instrument From to workspace details

Changeset: 791a73e5507748767424f40ff323ee0e7598b725

[Nick Draper]

re #10509 extend to support parameter files

Changeset: b846000a488939707060cd126fa5c2b5ff723591

[Nick Draper]

re #10509 solve failing test

Changeset: 6cbea49264901efb71945a3986d78a29c1c7d5d2

[Nick Draper]

To test

1. start mantidplot
2. Load MAR11010 from autotestdata/usagedata (any file with an instrument and parameter definition)
3. In the workspace list expand the workspace node (click the +)
4. You should see an instrument from, and parameter from entry defining the locations that the instrument and definition file was loaded from.
5. Run LoadParameterFile for this workspace and load another parameter file (it doesn't need to match).
6. You should get an additional Parameters from entry.

• You will not get parameter from entries for parameters loaded from a nexus data file.

[Federico M Pouzols]

Works well. I can see the new 'instrument from' and 'parameters from' lines. I also get additional lines when I run LoadParameterFile.

This will be extremely useful. I remember having had issues with a test not long ago because I was unadvertedly using 'instrument dir' and 'parameter dir' from different repos.

[Federico Montesino Pouzols]

Merge remote-tracking branch 'origin/feature/10509_Where_did_this_instrument_come_from'

Full changeset: ​1d93b6693e20e9165b6e80e702803c99dcbf5574

[Stuart Campbell]

This ticket has been transferred to github issue ​11351