Refactors reprodata to make storage consistent #205
Merged
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
…ode] structure - rather than the implicit drop[reprodata][values] if singular and drop[reprodata][rmode] if all structure.
…ler and more changeable while testing the same conditions as before.
awicenec
approved these changes
Oct 14, 2022
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.
Originally, it was assumed that there would only be one rmode per graph, so the json was structured as {reprodata: {hash: x}} etc.
Allowing an 'ALL' mode added an extra layer to this - {reprodata: {RERUN: {hash: x}, REPEAT: {hash: x}}} etc.
This split the implementation into two branches - messy and difficult to follow.
This PR unifies the structure into {reprodata: {RMODE: {hash:x}}} even for a single rmode.