Improved reading of fit pseudodata#1334
Merged
Merged
Conversation
f8675cb to
0529a31
Compare
Contributor
|
@siranipour I'll take a look at this when I can make a bit of time :) |
ba389c9 to
62c4521
Compare
0529a31 to
4cf6d57
Compare
Contributor
Author
|
I'm just going to merge this into #1328 so I can get the tests to pass for everything |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Just a quick PR that refines the way we read the pseudodata files from a fit. This builds on the production rules of #1328, which now allows for an easier way to handle the postfit pseudodata reshuffling.
Tests will fail for now. Blocked by #1333