single file to configure across the entire detector #51
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
|
Not sure which roc files are "stable" from the POV of CERN folks, so I'm striking the last to-do item. |
tomeichlersmith
deleted the
50-single-file-to-configure-across-the-entire-detector
branch
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.
Parsing of a parent yaml file for loading an entire configuration of the detector. This includes HGC ROC parameter settings as well as ad-hoc settings for other parts of the system (each of which must be added manually). Similar to the parameter settings YAML files, the keywords are case in-sensitive. There is additional special word
inheritsignalling that the child YAML nodes should be applied to all polarfires or hgcrocs on a polarfire (depending on the context).To Do