Project

General

Profile

Bug #2903

FHICL processing reject hex values

Added by Robert Hatcher almost 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
-
Start date:
08/23/2012
Due date:
% Done:

0%

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

Description

According to the language specifications (which I checked) FHICL supports the use of hex values (in the standard 0x format). The FHICL quick guide makes no mention either way. Empirically the use doesn't seem to be supported.

in the .fcl file:

  physics.producers.geantgen.G4AlgPSet.DebugAction.DebugFlags: 0x7FFF

in the code:

DebugAction.h:

  unsigned int fStepStateVetoFlags; ///< bits suppress field 

DebugAction.cxx:

  fStepStateVetoFlags = pset.get< unsigned int >("DebugFlags",0);

yields:

---- EventProcessorFailure BEGIN
 An exception occurred during current event processing
 ---- ScheduleExecutionFailure BEGIN
   ProcessingStopped.
   ---- Type mismatch BEGIN
     DebugFlags
     ---- Type mismatch BEGIN
       error in unsigned string:
       0x7FFF
       at or before:
     ---- Type mismatch END
     cet::exception going through module G4Gen/geantgen run: 1
   ---- Type mismatch END
   Exception going through path simulate
 ---- ScheduleExecutionFailure END
 cet::exception caught in EventProcessor and rethrown
---- EventProcessorFailure END

History

#1 Updated by Marc Paterno almost 8 years ago

  • Category set to Infrastructure
  • Status changed from New to Assigned
  • Assignee set to Qiming Lu

There is now a failing test in the fhiclcpp test suite that identifies the failure.

#2 Updated by Marc Paterno almost 8 years ago

  • Status changed from Assigned to Resolved

#3 Updated by Marc Paterno almost 8 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF