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
As an Instrument Scientist, I want to have the EQSANS reduction script to be able to reduce data from a local file saved outside of the data folder (the default folder where the measured data get saved directly).
When the runNumber is specified as an int number OR a string of number (for example, runNumber = 12345 or runNumber = "12345"), then the reduction code will automatically find the associated data on the default place.
When the runNumber is specified as a nexus file path as a string then the reduction code will load that specific nexus file and reduce it. For example, runNumber = '/SNS/EQSANS/shared/IPTS-1111/shared/mydata/EQSANS_12345.nxs.h5'
This interpretation of runNumber should be applied to all places where the runNumbers are used as an input.
Description, Additional Detail, Context:
The text was updated successfully, but these errors were encountered:
As an Instrument Scientist, I want to have the EQSANS reduction script to be able to reduce data from a local file saved outside of the data folder (the default folder where the measured data get saved directly).
=======================================================================
Acceptance Criteria:
When the runNumber is specified as an int number OR a string of number (for example, runNumber = 12345 or runNumber = "12345"), then the reduction code will automatically find the associated data on the default place.
When the runNumber is specified as a nexus file path as a string then the reduction code will load that specific nexus file and reduce it. For example, runNumber = '/SNS/EQSANS/shared/IPTS-1111/shared/mydata/EQSANS_12345.nxs.h5'
This interpretation of runNumber should be applied to all places where the runNumbers are used as an input.
Description, Additional Detail, Context:
The text was updated successfully, but these errors were encountered: