You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to: export data within Mantid Imaging from the Spectrum Viewer in a .dat and maybe .inp
For: a given dataset opened within the live viewer where the spectrum is of importance for Bragg edge imaging at IMAT.
So that: I can import my spectrum data created within the Mantid Imaging Spectrum Viewer into the RITS software, providing a smooth user experience, with more flexibility for IMAT to work with all cameras used at IMAT.
Unlike: the current solution which is to use ImageJ and Fortran scripts which is a big obstacle for users, and IMAT does not have the expertise to provide support and only works with a limited number of IMATs camera's.
Our solution is: to add a new file export method to Mantid Imaging core that can write spectrum data in a RITS format to .dat files which will be connected to a new front end widget accessible though the Spectrum Viewer within Mantid Imaging.
Acceptance criteria
A user can open a new widget within the spectrum viewer to export a spectrum to a RITS compatible format.
Provide simple control of a selected region and binning/averaging options.
Export a .dat file in a RITS compatible format
Import spectrum viewer exported .dat file into RITS software
Minimum Viable Project
Export .dat RITS file format
Exported data is full field
Exported data has fixed binning
ToF values from metadata used
Features in Scope
Exporting file format that can be read by RITS
Region selection
Binning / averaging options (running average, Gaussian kernel) in space and time
Handle metadata with image index to tof/wavelengths
Value in error column (Need more info)
Optionally note things out of scope (e.g. to clarify where there might be assumptions):
Compression or more efficient data format
Loading ToF data formats (will be separate epic)
Importing RITS Data
Enabling Conditions
What needs to be in place before this issue can be worked on?
Access to RITS software and Example RITS datasets.
Business Outcome Hypothesis
What is the expected outcome of this issue?
The current manual process is complex and time consuming. Users also lack the specialisms to provide support converting to the RITS format manually which could lead to errors in the converted data.
Users are therefore potentially unlikely to use IMAT as a preferred instrument if wishing to to perform Braggs edge imaging analysis with RITS software.
An incorporated solution within Mantid Imaging to easily export to the RITS format would save user time and require no technical specialist knowledge. Users will be less hesitant to to use IMAT for collecting data for Braggs edge analyse using RITS.
Improved user experience on IMAT that is more professional offering compatibility with RITS software.
Users more likely to come back.
Leading Indicators
What are the metrics that will indicate that we are on track to achieve the expected outcome?
Export something small (maybe a single pixel) into a format that can be successfully opened with RITS.
Progress on user controls and interface.
Non-functional Requirements (NFRs)
What are the NFRs for this issue?
Properly handle large data sizes (datasets close to RAM size). Don’t hit RAM limits, handle running out of disk space. If MI can currently load the dataset size on a given machine, it should be able to export it.
Simple and obvious to use. Can be used without requesting help. Well documented.
Unit and system tests.
Uses existing logging system.
Additional Information
Data format (.dat):
The three columns represent: "TOF [us]" , "transmission", "error_transmission"
Description
As a: IMAT user and external user
I want to: export data within Mantid Imaging from the Spectrum Viewer in a
.dat
and maybe.inp
For: a given dataset opened within the live viewer where the spectrum is of importance for Bragg edge imaging at IMAT.
So that: I can import my spectrum data created within the Mantid Imaging Spectrum Viewer into the RITS software, providing a smooth user experience, with more flexibility for IMAT to work with all cameras used at IMAT.
Unlike: the current solution which is to use ImageJ and Fortran scripts which is a big obstacle for users, and IMAT does not have the expertise to provide support and only works with a limited number of IMATs camera's.
Our solution is: to add a new file export method to Mantid Imaging core that can write spectrum data in a RITS format to .dat files which will be connected to a new front end widget accessible though the Spectrum Viewer within Mantid Imaging.
Acceptance criteria
.dat
file in a RITS compatible format.dat
file into RITS softwareMinimum Viable Project
.dat
RITS file formatFeatures in Scope
Optionally note things out of scope (e.g. to clarify where there might be assumptions):
Enabling Conditions
What needs to be in place before this issue can be worked on?
Business Outcome Hypothesis
What is the expected outcome of this issue?
The current manual process is complex and time consuming. Users also lack the specialisms to provide support converting to the RITS format manually which could lead to errors in the converted data.
Users are therefore potentially unlikely to use IMAT as a preferred instrument if wishing to to perform Braggs edge imaging analysis with RITS software.
An incorporated solution within Mantid Imaging to easily export to the RITS format would save user time and require no technical specialist knowledge. Users will be less hesitant to to use IMAT for collecting data for Braggs edge analyse using RITS.
Improved user experience on IMAT that is more professional offering compatibility with RITS software.
Users more likely to come back.
Leading Indicators
What are the metrics that will indicate that we are on track to achieve the expected outcome?
Non-functional Requirements (NFRs)
What are the NFRs for this issue?
Additional Information
Data format (
.dat
):The three columns represent: "TOF [us]" , "transmission", "error_transmission"
Broken Down Task to Accomplish this:
The text was updated successfully, but these errors were encountered: