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

art_root_io/RootDB actually belongs to canvas_root_io #106

Open
knoepfel opened this issue Oct 28, 2021 · 2 comments
Open

art_root_io/RootDB actually belongs to canvas_root_io #106

knoepfel opened this issue Oct 28, 2021 · 2 comments
Labels
feature An enhancement to the project

Comments

@knoepfel
Copy link
Contributor

This issue has been migrated from https://cdcvs.fnal.gov/redmine/issues/25551 (FNAL account required)
Originally created by @PetrilloAtWork on 2021-02-23 22:23:24


That is my bold statement, and if you end up agreeing I would request that that code be moved into canvas_root_io.

The gain is an easier access to the FHiCL configuration stored in art/ROOT files from gallery.

@knoepfel knoepfel added the feature An enhancement to the project label Oct 28, 2021
@knoepfel
Copy link
Contributor Author

Comment by @knoepfel on 2021-02-24 03:12:04


You may be right, Gianluca. Let me talk with some folks on this end. Could you give some examples, though, in how you would use it with gallery?

@knoepfel
Copy link
Contributor Author

Comment by @PetrilloAtWork on 2021-02-24 15:31:08


It might be something similar to how config_dumper does:

art::SQLite3Wrapper sqliteDB(&file, "RootFileDB");
fhicl::ParameterSetRegistry::importFrom(sqliteDB);
fhicl::ParameterSetRegistry::stageIn();
auto const& collection = fhicl::ParameterSetRegistry::get();
for (auto const& pr : collection) { /* ... */ }

Right now, in ICARUS data there is some DAQ configuration in there that can be found.
Or something like what happend in "DetectorClocksServiceStandard":https://github.com/LArSoft/lardata/blob/1d1ff479bd64ab6db99082570173de10ccb30fe0/lardata/DetectorInfoServices/DetectorClocksServiceStandard_service.cc#L103-L112.
If there were some public tool to make this process even easier, it would be welcome (e.g. a sequence like the one in config_dumper, but not using a global instance but rather a local registry, not to mess with the rest of the configuration).

@knoepfel knoepfel added this to Issues Oct 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature An enhancement to the project
Projects
Status: No status
Development

No branches or pull requests

1 participant