Adding MCM parser script #1
Open
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
8 tasks
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.
After a discussion with @valsdav I took a look at the ways to query MCM for possible information about samples/campaigns.
In this PR a simple example is added (taken from mcm_scripts repo). An
mcm.mdfile is also added with some explanations.Regarding the names of the processes, I don't think we need/should reinvent a new naming convention. We should stick to the one used by GEN in the dataset creation.
It is described here for Run3 samples and here for Run2 samples. Yes, it is inconvenient to have different definitions, but we can not solve this by inventing a new convention.
The PR can be merged, if useful.