Skip to content
New issue

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

Fix ObjectID data type conversions in FarDetectorTrackerCluster #1477

Open
wants to merge 11 commits into
base: main
Choose a base branch
from
2 changes: 1 addition & 1 deletion src/algorithms/fardetectors/FarDetectorTrackerCluster.cc
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,7 @@ namespace eicrecon {

ROOT::VecOps::RVec<unsigned long> clusterList = {maxIndex};
ROOT::VecOps::RVec<float> clusterT;
std::vector<podio::ObjectID> clusterHits;
std::vector<edm4hep::ObjectID> clusterHits;

// Loop over hits, adding neighbouring hits as relevant
while(clusterList.size()){
Expand Down
2 changes: 1 addition & 1 deletion src/algorithms/fardetectors/FarDetectorTrackerCluster.h
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ struct FDTrackerCluster {
double energy{0.0};
double time{0.0};
double timeError{0.0};
std::vector<podio::ObjectID> rawHits;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a comment as to why we use edm4hep, not podio (which we use everywhere else) with a link to relevant definition? I would hate for someone to change it back to podio in a year from now.

Also, can this be considered a bug in podio or edm4hep or edm4eic? One would expect these all to have consistent ObjectID types.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I couldn't quite work out how this was wrong here but the edm4hep::ObjectID type has already been removed from the recent edm4hep releases. This means if we update, the old edm4hep::TrackerHit I'm using will break it anyway as it contains a vector of objectIDs rather than using podio relations. I believe our data model has progressed to a state the work around isn't necessary anymore.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's still missing from edm4eic is a Measurement3D, effectively Measurement2D swapping surface for the extra dimension, through the transformation to global coordinates (or not transforming back to 2D).

std::vector<edm4hep::ObjectID> rawHits;
};
namespace eicrecon {

Expand Down
Loading