Feature/runlist configs #201
Open
+117
−43
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
…gh both fill_response and fillEvents.
Case where CONFIG not in runlist
…ory/V2DL3 into feature/runlist_configs
…ature/runlist_configs # Conflicts: # pyV2DL3/vegas/fillEVENTS_not_safe.py
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.
Add implementation of CONFIG file from runlist parser to use the unique configs per run group. Once loaded, these call the
VAEffectiveAreaManager::setOption()methods to set their values and use within the getSafeEnergyRange method. Somehow still need to check that these methods actually assign the numbers within the vegas library, but it is properly parsing through to that stage.