Modify existing output save formats to include Polarised SANS reduction outputs

[rbauststfc]

Existing output save formats need to be modified to include relevant metadata from the Polarised SANS reduction at ISIS. Proposed changes will need to be agreed by our scientists with the wider collaboration that determines the file format specifications. This is included in the MVP for the epic.

File Output Spec

(Currently in discussion with the working group, Stakeholders putting a demo together to present. All below is subject to change)

• (Up to) Four data blocks for the different spin states
  • Each of these need an identifying label.
  • A clear way to represent what the spin state identifiers mean (up/down | 0/1 | +/-)
• Metadata to indicate the files/run numbers used for the efficiency calculations for the:
  • Flipper
  • Analyser
  • Polariser

Data Workflow

• It was suggested that the saving only needs to work for 2D data, and so we only need to edit SaveNXCanSAS and LoadNXCanSAS
• The data blocks need to be readable in any analysis software, but as long as we stick to the standard agreed by the working group, we should be fine on that front.

[cailafinn]

From Steve K:

My tuppence would be to put the multiple periods in single output files unless there is a reason not to…

We know SasView will read multi-block files. However, I’m not sure that LoadCanSAS1D or LoadNXCanSAS do if you wanted to get them back into Mantid. So that loop would need closing.

My understanding is that they don't accept multiple blocks at present. So would need to modify the Savers and Loaders to save out the GroupWorkspaces properly into multiple blocks in the same file and vice versa.