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
Refactor Inelastic QENS FitTab #37193
Merged
SilkeSchomann
merged 16 commits into
mantidproject:main
from
robertapplin:36390-refactor-fit-tab
Apr 30, 2024
Merged
Refactor Inelastic QENS FitTab #37193
SilkeSchomann
merged 16 commits into
mantidproject:main
from
robertapplin:36390-refactor-fit-tab
Apr 30, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
robertapplin
added
Indirect/Inelastic
Issues and pull requests related to indirect or inelastic
Maintenance
Unassigned issues to be addressed in the next maintenance period.
ISIS Team: Spectroscopy
Issue and pull requests managed by the Spectroscopy subteam at ISIS
labels
Apr 22, 2024
👋 Hi, @robertapplin, Conflicts have been detected against the base branch. Please rebase your branch against the base branch. |
github-actions
bot
added
the
Has Conflicts
Used by the bot to label pull requests that have conflicts
label
Apr 24, 2024
robertapplin
force-pushed
the
36390-refactor-fit-tab
branch
from
April 24, 2024 08:28
4fd31d7
to
7c207e3
Compare
robertapplin
removed
the
Has Conflicts
Used by the bot to label pull requests that have conflicts
label
Apr 24, 2024
pre-commit.ci run |
adriazalvarez
requested changes
Apr 29, 2024
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.
Thanks for spotting that weird warning, not sure how I missed it! |
robertapplin
force-pushed
the
36390-refactor-fit-tab
branch
from
April 29, 2024 13:03
69b0ca0
to
b3a25bc
Compare
robertapplin
force-pushed
the
36390-refactor-fit-tab
branch
from
April 29, 2024 13:32
b3a25bc
to
1d257a8
Compare
Thanks for the changes. It looks good to me. |
adriazalvarez
approved these changes
Apr 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Indirect/Inelastic
Issues and pull requests related to indirect or inelastic
ISIS Team: Spectroscopy
Issue and pull requests managed by the Spectroscopy subteam at ISIS
Maintenance
Unassigned issues to be addressed in the next maintenance period.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of work
This PR does some refactoring of the FitTab of Inelastic QENS Fitting interface. It reduces the amount of code in this FitTab by removing unused code, and moving some of the code to more testable locations, such as the FittingModel of some of the Presenters.
Part of #36390
To test:
Follow the testing instructions here
https://developer.mantidproject.org/Testing/Inelastic/QENSFittingTests.html
This does not require release notes because it is an internal change
Reviewer
Please comment on the points listed below (full description).
Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.
Code Review
Functional Tests
Does everything look good? Mark the review as Approve. A member of
@mantidproject/gatekeepers
will take care of it.Gatekeeper
If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.