Project

General

Profile

Feature #25551

art_root_io/RootDB actually belongs to canvas_root_io

Added by Gianluca Petrillo about 2 months ago. Updated about 2 months ago.

Status:
Under Discussion
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/23/2021
Due date:
% Done:

0%

Estimated time:
Scope:
Internal
Experiment:
-
SSI Package:
Duration:

Description

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.

History

#1 Updated by Kyle Knoepfel about 2 months ago

  • Scope set to Internal
  • Status changed from New to Under Discussion
  • Tracker changed from Idea to Feature

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?

#2 Updated by Gianluca Petrillo about 2 months ago

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.
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).

Also available in: Atom PDF