Suggestion for output-datatier-branching in flow #665
Closed
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
|
There is a typo at len()!=0 to raise exception, while it should be == |
|
@srimanob this PR has not merged, therefore you cannot be using the feature it contains |
|
@anorkus |
|
Hi, what was so wrong with this suggestion that https://cms-pdmv.cern.ch/mcm/settings?prepid=datatier_input was introduced instead ? |
vlimant
referenced
this pull request
Sep 1, 2015
Added a test method to return datatiers for chole chain; Uses settings DB datatier_input as reference for inputs.
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
To be reviewed for possible typos.
TaskChain should be checked to not be broken.
Flows that have "use_datatier" mentioned in "request_parameters" will try to pick the corresponding output.
Came out easier than I thought.