Check DSID ranges and automatic booking of DSIDs

500000 MadGraph/aMC@NLO
600000 Powheg
700000 Sherpa
800000-829999 Pythia/PythiaB
830000-859999 Herwig
860000-899999 HI generators
900000-949999 Miscellaneous
950000-999999 Validation/not for physics

Tagging @ewelina @fsiegert @cgutscho

We also need to think of a way to automatically book DSIDs
=> Suggestion: use a "deploy" job that only runs on master at the very end of the pipeline that will rename the DSIDs according to the above convention. If the job runs only on master it means that independent branches (where new DSIDs will be registered) don't need to agree beforehand on a convention (same dummy DSIDs can be used in several branches) and the assignment of DSIDs will be done automatically at the very end only when the branch is merged in master.

Alternative
The above most likely won't work since master is protected so the CI job won't be able to push directly. Alternatively the assignment of DSIDs can be incorporated in the commit_new_dsid.sh, which at the time of the commit can check all branches and rename the DSIDs locally just before committing.

The DSIDs in all branches can be extracted with:

for branch in $(git for-each-ref --format='%(refname)' refs/heads/); do git ls-tree -r --name-only $branch ; done | awk -F'/' '/[0-9]{3}xxx/{print $2}' | sort -u

• Develop deploy CI job
• enforce above convention for DSIDs in that job
• print in pipeline how each dummy DSID is named -> if needed (useful for JIRA/spreadsheet) this can be exported in a file which can be saved as an artifact and later downloaded from the pipeline