We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The ntupliser curently assumes that sharing is not enabled and therefore a 1-to-1 association between rechits and layer clusters exists: https://github.com/CMS-HGCAL/reco-ntuples/blob/master/HGCalAnalysis/plugins/HGCalAnalysis.cc#L1831-L1851
With sharing enabled, a rechit can be associated to more than one cluster. If we want to preserve this information in the ntuple, we would need to change rechit_cluster2d_ (the variable that stores the index of the associated layer cluster, https://github.com/CMS-HGCAL/reco-ntuples/blob/master/HGCalAnalysis/plugins/HGCalAnalysis.cc#L1917) to a vector of integers.
rechit_cluster2d_
Any comments or alternative suggestions?
The text was updated successfully, but these errors were encountered:
I guess, in that case one would also need to add a vector like rechit_cluster2d_fraction_ for the corresponding fractions?
rechit_cluster2d_fraction_
Sorry, something went wrong.
No branches or pull requests
The ntupliser curently assumes that sharing is not enabled and therefore a 1-to-1 association between rechits and layer clusters exists: https://github.com/CMS-HGCAL/reco-ntuples/blob/master/HGCalAnalysis/plugins/HGCalAnalysis.cc#L1831-L1851
With sharing enabled, a rechit can be associated to more than one cluster. If we want to preserve this information in the ntuple, we would need to change
rechit_cluster2d_
(the variable that stores the index of the associated layer cluster, https://github.com/CMS-HGCAL/reco-ntuples/blob/master/HGCalAnalysis/plugins/HGCalAnalysis.cc#L1917) to a vector of integers.Any comments or alternative suggestions?
The text was updated successfully, but these errors were encountered: