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

Deprecate: PodioInput, k4DataSvc, PodioDataSvc, (FCCDataSvc) #292

Open
1 of 3 tasks
andresailer opened this issue Feb 25, 2025 · 3 comments
Open
1 of 3 tasks

Deprecate: PodioInput, k4DataSvc, PodioDataSvc, (FCCDataSvc) #292

andresailer opened this issue Feb 25, 2025 · 3 comments
Labels
enhancement New feature or request

Comments

@andresailer
Copy link
Contributor

andresailer commented Feb 25, 2025

Only the IOSvc must be used for new code from now on

@andresailer andresailer added the enhancement New feature or request label Feb 25, 2025
@andresailer andresailer changed the title Deprecate: PodioInput and k4DataSvc Deprecate: PodioInput, k4DataSvc, PodioDataSvc (FCCDataSvc) Feb 25, 2025
@andresailer andresailer changed the title Deprecate: PodioInput, k4DataSvc, PodioDataSvc (FCCDataSvc) Deprecate: PodioInput, k4DataSvc, PodioDataSvc, (FCCDataSvc) Feb 25, 2025
@m-fila
Copy link
Member

m-fila commented Feb 25, 2025

The services to be deprecated are still advertised in the documentation:

@tmadlener
Copy link
Contributor

We need to make sure that Gaudi::Algorithms are still supported, I think. They still use DataHandle and there might be some subtleties in the fact that a DataHandle doesn't store things as an AnyDataWrapper into the TES. This is currently causing an issue in key4hep/k4MarlinWrapper#219

@tmadlener
Copy link
Contributor

These are also injected by default in k4MarlinWrapper: key4hep/k4MarlinWrapper#231

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants