[IDA] Elwin - Allow User to Specify Range of Files

[Peter Parker]

In the Energy Transfer tab of C2E, a user can specify a range of files to load by simply typing in the range, e.g. "2012-2020". The interface takes the currently selected instrument, analyser and reflection options, finds the appropriate file(s), and outputs the result with appropriate file names.

No such mechanism exists in IDA.

A possible way to implement this so that a range of files of the form [INST][RUN]_[ANALYSER][REFLECTION]_red.nxs could be loaded, would be the following:

• Insist that the user inputs the range, as well as the instrument suffix (i.e. "IRS2012-2020" for the range of reduced Iris runs from 2012 to 2020).
• Add functionality to FileFinder to accept a wild card^[+] as well as the instrument / run number hint and file extensions.
• Change the tabs so that they feed a wild card to FileFinder, placed between the range string and "_red.nxs".

[+] - The ability to accept any arbitrary string here, and not just a wildcard, would be useful elsewhere.

[Nick Draper]

Moved at end of release 2.1

[Nick Draper]

Moved at the end of release 2.2

[Nick Draper]

Moved to milestone 2.4

[Nick Draper]

Moved at the code freeze for release 2.4

[Nick Draper]

Moved to r2.6 at the end of r2.5

[Nick Draper]

Moved to backlog at the code freeze for R2.6

[Nick Draper]

Bulk move to assigned at the introduction of the triage step

[Samuel Jackson]

Refs #5012 Add support for range searching in FileFinder.

This includes a new public method called getFullPaths that takes a comma separated string for potential file paths attempts to find a match. If the file path contains something that looks like a range it will expand the range and look for each file in the range individually.

Changeset: cde229e43c78acfd9357e6036db55df3cd113fe2

[Samuel Jackson]

Refs #5012 Move file finding logic to be contained in FindFiles.

This includes modifying the widget to use the getFullPaths function to find multiple file paths.

Changeset: 04fbaa38221dc9c73d00b82a7255557a1b65ec80

[Samuel Jackson]

Refs #5012 Correct a seg fault with single file searching.

Changeset: 256658ca5062b8c2b2f45aae9c0f94b68a98f1e0

[Samuel Jackson]

Refs #5012 Swap IDA interface to run LoadNexus C++ side.

This algorithm was being executed on a separate thread which was causing the automatic file searching to play up in certain cases where it would still be searching for files while the user had clicked the run button.

This change stops that from happening, but this should really be changed to use AlgorithmRunner. But that's outside the scope of this ticket.

Changeset: 5079b9b1bfd689d04b5a8cd2f1e8736b92ba7faf

[Samuel Jackson]

Refs #5012 Export method to python api.

Changeset: 718cab70969cb6b95c25871e2259776e05d6063a

[Samuel Jackson]

Refs #5012 Throw NotFoundError instead of invalid argument.

Changeset: 014638549299d0a0406b6552f671aa862d78f35c

[Samuel Jackson]

Refs #5012 Add unit tests for new method.

Changeset: 89521499b5aea0100ba97e7c6e7d20fb23fbcd1e

[Samuel Jackson]

To Tester

There is a new function on FileFinder (that is also exposed to python) called getFullPaths. This takes a comma separated list of string as hints that get passed to FileFinder.getFullPath.

e.g. FileFinder.getFullPaths("irs55127*, irs55128*, irs55129*")

This also accepts range hints. For example typing:

e.g. FileFinder.getFullPaths("irs55127:irs55129*")

Should produce the exact same output as the first example. Test that this works as you would expect.

Once you're sure this works, check that the file input widget on Elwin still works as before, but that you can now specify a range of runs using the same syntax as the examples above. For general instructions on running ElWin see:

http://www.mantidproject.org/Indirect:Indirect_Data_Analysis#Running_Elwin

[Samuel Jackson]

This ticket should hold off until we decide what is happening with #7515

[Stuart Campbell]

This ticket has been transferred to github issue ​5858