-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve user experience #151
Conversation
Previously the range in tof to be masked was being specified by ','. It makes more sense to use '-' to describe the range.
Previously the workspaces for the y-space fit were being overwritten when the fitting model changed. This change changes the name of the workspace which makes sure the workspaces do not get overwritten.
Save some plots by default that were not being saved
Added function to save workspaces containing the result in y space fit in Ascii format, and made minor esthetic improvements to plots that are also saved.
a97f056
to
6e733e9
Compare
Re-running y-space fit with subtraction of fse turned on was picking up the wrong workspace that also ended in 'fse'. This correction guarantees the right workspace is chosen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When running the analysis script with different fitting models, previous workspaces are not overwritten anymore. Also, the naming makes it easy to match output files to the corresponding fitting model. The variable names are now easier to understand and there are some new useful comments, especially in the input sections of the different analysis algorithms.
Description of work:
To test:
Code review
+
Manual testing:
Activate an environment with mantidworkbench installed:
pip install -e .
~/.mvesuvio
mvesuvio config
, this should create a new~/.mvesuvio
~/.mvesuvio/analysis_inputs.py
ForwardAnalysisInputs
change the fieldmask_time_of_flight_range = '112-120'
analysis_inputs_fwd_0
and check that dataY has zeros in columns between 112 and 120YSpaceFitInputs
changefitting_model = "gcc4c6"
gauss
andgcc4c6
fits and the data and the fits should look sensible.~/.mvesuvio/analysis_inputs/figures/
and check that figures ending in_fitglobal.png
and_gauss_autominos.png
were saved._gauss_Workspace.pdf
and check that residuals (blue dots) appear in the figure~/.mvesuvio/analysis_inputs/output_files/
and check that several ASCII files ending in_Workspace
and_Parameters
were saved.Fixes #145 .