Warn user of non-existing dataset key
Created by: mmarchegiani
A desirable behavior of the Configurator would be to warn the user in case some samples that don't exist in the json dataset are requested in the filter
dictionary.
For example in the snippet from the config reported below if the key QCD_Pt-470to600
is not present in the json dictionary, at the moment no dataset is filtered and no warning is raised.
I think it would be better if the Configurator would raise an exception when a non-existing dataset key is requested, such that if a key is improperly spelled in either the json dictionary or in the list of samples to filter, or the corresponding dataset doesn't exist the processor is not launched and the user has the possibility to add the missing dataset in the json file and/or fix the requested keys in the config.
"dataset" : {
"jsons": ["datasets/skim/datasets_definition_skim.json"],
"filter" : {
"samples": ["QCD_Pt-170to300",
"QCD_Pt-300to470",
"QCD_Pt-470to600",
"QCD_Pt-600to800",
"QCD_Pt-800to1000",
"QCD_Pt-1000toInf",
"DATA"],
"samples_exclude" : [],
"year": ['2017']
},
"subsamples": {}
},