Bug #15127
SpaceChargeService service is configured with the wrong name
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
01/12/2017
Due date:
% Done:
0%
Estimated time:
Description
It is customary to specify the configuration of a service under the name of the service itself. For example:
services: { SpaceChargeService: { service_provider: SpaceChargeServiceMicroBooNE # ... } }
This is mandatory for concrete services (e.g.
Geometry
), but art surprisingly does the right thing with service interfaces.Anyway, the name of the space charge art service is
SpaceChargeService
, not SpaceCharge
.The configuration in
services_microboone_basic.fcl
and other files are using the latter, and that should be fixed.