sPHENIX tracking discussion

[Hugo Pereira Da Costa <hugo.pereira-da-costa AT cea.fr>]

Hello Christof,

As far as I am concerned, no problem with breaking backward compatibility.

More importantly, the module was never used in any official macro that I 
know of, so we have no "official" DSTs that contain this container. 
(they would be rendered unreadible by a change in the container 
structure). You might want to double check with Chris though.

Hugo


On 7/6/22 07:26, Christof Roland via sPHENIX-tracking-l wrote:
> Hi Hugo,
>
> I will soon commit the switch to cluster version v4.
> For most reco modules it is rather easy to add a switch for the cluster 
> version number.
>
> For the TrackEvaluation this is not so easy. For the new cluster version we 
> need to change the content
> of the cluster struct to have access to the new cluster quality variables. So 
> in principle we would need to
> augment the TrackEvaluationContainer version number.
> This would make it very complicated or require a lot of code duplication to 
> keep this alive for cluster v3 and v4.
>
> Question do you care here about backward compatibility? Do you want to keep 
> acceess to clusterv3 alive?
>
> Coding wise it would be the easiest to add a few variables to 
> TrackEvaluationv1, i.e. break backward comaptibility,
> and move to clusterv4. Not good style, hence I am asking.
>
> Please let me know what you think/need.
>
> Cheers
>
>     Christof
> _______________________________________________
> sPHENIX-tracking-l mailing list
> sPHENIX-tracking-l AT lists.bnl.gov
> https://lists.bnl.gov/mailman/listinfo/sphenix-tracking-l