This code is part of the Liquid Argon Software (LArSoft) project. It contains simulation and reconstruction algorithms for LAr TPC detectors. If you have a problem, please log a redmine issue: https://cdcvs.fnal.gov/redmine/projects/larsoft/issues/new
0
stars
18
forks
source link
WCT `IWireSchema` from LArSoft geometry service #38
We should provide a way to derive the needed WCT "wire geometry" information directly from a LS geometry service.
Background info
WCT geometry and wire-channel map is primarily determined by the exhaustive list of "wire" segments (including for strip+holes detectors).
So far, this information is in the form of a WCT "wires fill" in .json.bz form. This file is typically generated by a wire-cell-python program using a text file dump that comes from LArSoft geometry service.
A "wires file" is still required for WCT stand-alone use but when used as part of LS this baroque chain is not welcome. In rare, but possible situations the wire geometry in LS may be updated and we fail to update the "wires file". The "wires file" also poses yet another auxiliary file to track at the batch job level.
To be friendly to the LS+WC user we should develop a WC/LS component that can act as a WCT IWireSchema and populate the wire geometry information by directly calling the LS geometry service.
If the geometry service is not thread safe - or even it if is to be extra safe - the LS->WC conversion of the wire info should be performed eagerly inside configure().
Extra credit
Given this new WC/LS component, we should also include a way to directly dump out the WCT "wires file" in .json.bz2 format in order to negate the need for the baroque chain that would otherwise still be needed for stand-alone WCT usage.
A WC/LS Jsonnet/FHiCL config set should be provided for every popular LArTPC detector to simplify and standardize dumping their "wires file".
We should provide a way to derive the needed WCT "wire geometry" information directly from a LS geometry service.
Background info
WCT geometry and wire-channel map is primarily determined by the exhaustive list of "wire" segments (including for strip+holes detectors).
So far, this information is in the form of a WCT "wires fill" in
.json.bzform. This file is typically generated by awire-cell-pythonprogram using a text file dump that comes from LArSoft geometry service.A "wires file" is still required for WCT stand-alone use but when used as part of LS this baroque chain is not welcome. In rare, but possible situations the wire geometry in LS may be updated and we fail to update the "wires file". The "wires file" also poses yet another auxiliary file to track at the batch job level.
To be friendly to the LS+WC user we should develop a WC/LS component that can act as a WCT
IWireSchemaand populate the wire geometry information by directly calling the LS geometry service.If the geometry service is not thread safe - or even it if is to be extra safe - the LS->WC conversion of the wire info should be performed eagerly inside
configure().Extra credit
Given this new WC/LS component, we should also include a way to directly dump out the WCT "wires file" in
.json.bz2format in order to negate the need for the baroque chain that would otherwise still be needed for stand-alone WCT usage.A WC/LS Jsonnet/FHiCL config set should be provided for every popular LArTPC detector to simplify and standardize dumping their "wires file".