For the hybrid ecal reconstruction, MergeCollections is used to merge si-ecal collections in even and odd layers; this merged collection is then passed to the digitisation step.
The RealisticCaloDigi.cc processor uses the CellIDEncoding: col->getParameters().getStringVal(LCIO::CellIDEncoding);
However, the merged collection keeps the encodings of the original input collections in a way not known about to the digitisation processor:
I had addressed this in https://github.com/iLCSoft/LCTuple/pull/2 - but just after making the v01-19-04 iLCSoft release. So you can update the LCTuple version to v01-09 for now...
For the hybrid ecal reconstruction, MergeCollections is used to merge si-ecal collections in even and odd layers; this merged collection is then passed to the digitisation step. The RealisticCaloDigi.cc processor uses the CellIDEncoding:
col->getParameters().getStringVal(LCIO::CellIDEncoding);
However, the merged collection keeps the encodings of the original input collections in a way not known about to the digitisation processor:
Am I missing something, or do we need a work-around?