-
Notifications
You must be signed in to change notification settings - Fork 41
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
[Release 5.0.6] Master 5.0.6 release PR #2407
Conversation
Thanks @krzywon for the suggestion!
fitting widget shows properly. #2272
…data from results panel when data deleted
Co-Authored-By: caitwolf <caitmwolf@gmail.com>
…x data in correlation space to the calculator which requires x data in q space
I added cherry-picks for the following PRs as part of the 5.0.6 release, many of these are SESANS related: |
the slicers defaulted to 20 or 36 points (depending on the slicer). This is almost never a reasonable number and there have been several request for that to be made larger. Upped it to 100 here. Noted in testing that the box slicer validators were not properly checking for 0 points (the other slicers did) . In fact they were do nothing functions so fixed that by adding the appropriate code snipet. Also all the slicers seemed to have the default set in a couple of different places which caused some odd behavior in at least on case. that was cleaned up as well.
Modified initial state to be log scale
from 50 to 150 points and default to log spacing of data
…als creation and delete from residuals plotting
…View/sasview into release_5.0.6_plotting_fixes
I haven't tested this version extensively but copying parameters to LATEX and Excel doesn't seem to work: |
@wpotrzebowski - #2369, opened by @smk, seems to be a similar, if not the same, issue. |
Thanks @krzywon for pointing this out. In my case it didn't work with core shell model. I need to check if it is model dependent and more importantly in the context of 5.0.6 is it also a bug in 5.0.5. |
The second comment in the ticket mentions it applies to all multiplicity models, not just Edited to correct: the second comment suggests it applies to them, but I've tested and the error is thrown on the |
Embedded latex ends up with lots of backslashes that need to be protected as raw strings rather than (mis)interpreted as standard C-style escape sequences.
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.
This PR just cherry picks a number of agreed upon commits to main which were already tested and code reviewed. Thus I think we should approve the merge and test the release branch as a whole to make sure none of these are relying on changes not picked.
This PR cherry-picks most/all of the plotting fixes we plan to include in v5.0.6.