Project

General

Profile

Bug #2972

Issue with starting at a certain event number

Added by Ben Carls over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Christopher Green
Category:
Application
Target version:
1.02.04
Start date:
09/27/2012
Due date:
% Done:

100%

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

Description

I am having an issue with the current development version of LArSoft (built with ART version 1_02_03). The flag to indicate which event to start at (-e or --estart) has been giving me back an error message. For example, attempting to start processing at event 8, I receive the error:

<> lar -e 8 -c job/standard_reco_uboone_engrecov.fcl -s standard_reco_uboone_engsave.root
OptionsHandler caught an std::exception calling art::BasicSourceOptionsHandler::doProcessOptions()
boost::bad_any_cast: failed conversion using boost::any_cast
Art has completed and will exit with status 7002.

I also should mention that using the --nskip flag gives back an identical error.

Using a stable version of LArSoft (built with ART version 1_00_11), I do not see the error and processing begins at the specified event.

Thanks for having a look at it.

Associated revisions

Revision 9025bc9b (diff)
Added by Christopher Green over 8 years ago

Test and fix for issue #2972.

Also, sam-empty.fcl -> opt-empty.fcl for generality.

History

#1 Updated by Christopher Green over 8 years ago

  • Category set to Application
  • Status changed from New to Assigned
  • Assignee set to Christopher Green
  • Target version set to 1.02.04

This issue has been confirmed. A fix is on the way.

#2 Updated by Christopher Green over 8 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

Resolved with 9025bc9. Regression tests should prevent recurrence.

#3 Updated by Christopher Green over 8 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF