Skip to content

Enable Postprocessing for RatesAnalyses with custom triggers

So far, RatesAnalysisPostprocessing.py failed for the results of RatesAnalysis if emulated triggers or RatesGroups were used, since certain information was not included in the metadata of the sample.

By getting the information from metadata with the dict.get method, a KeyError can be avoided and the script can run with added triggers in the RatesHistogram.

Mentioning @aporeba

Merge request reports