Project

General

Profile

Bug #6346

registerSecondaryFileNameProvider and fileNames parameter

Added by Christopher Backhouse over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Category:
I/O
Target version:
Start date:
05/24/2014
Due date:
% Done:

100%

Estimated time:
1.00 h
Spent time:
Occurs In:
Scope:
Internal
Experiment:
NOvA
SSI Package:
art
Duration:

Description

I reworked my MixFilter to use the new interface introduced in issue 5410 (registerSecondaryFileNameProvider).

On first attempt to run I get this:

%MSG-s ArtException: LEMMixer:lemmix@Construction 24-May-2014 14:28:08 CDT ModuleConstruction
cet::exception caught in art
---- Configuration BEGIN
Provision of a secondary file name provider is incompatiblewith a
non-empty fileNames parameter to the mix filter.
---- Configuration END
%MSG

Fair enough, though I'd probably prefer not to have this check, for simplicity of toggling between the two modes (explicitly provided filename, or computed at runtime).

So I remove fileNames from my LEMMixer.fcl. Now I get this:

%MSG-s ArtException: LEMMixer:lemmix@Construction 24-May-2014 14:23:55 CDT ModuleConstruction
cet::exception caught in art
---- Can't find key BEGIN
fileNames
---- Can't find key END
%MSG

This is coming from somewhere inside MixFilter, I don't request this key.

Seems like the left hand and right hand aren't talking.

If we need to run mixing in a different (older) release than everything else until this is sorted out, that's going to be inconvenient.


Related issues

Related to art - Feature #5410: Allow MixFilter to set secondary filenames at runtimeClosed02/10/2014

Associated revisions

History

#1 Updated by Christopher Green over 6 years ago

  • Category set to I/O
  • Target version set to 1.10.00
  • Estimated time set to 1.00 h
  • Experiment NOvA added
  • Experiment deleted (-)
  • SSI Package art added
  • SSI Package deleted ()

You should be able to work around this problem by providing an empty parameter:

fileNames: []
We agree that this should be fixed, and we hope to be able to get this into 1.10.00 by the end of this week.

#2 Updated by Christopher Backhouse over 6 years ago

This works around the problem. But see my update to issue 5410.

#3 Updated by Christopher Green over 6 years ago

  • Status changed from New to Resolved
  • Assignee set to Christopher Green
  • % Done changed from 0 to 100

This was a typo: fixed with b8c6798.

#4 Updated by Christopher Green over 6 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF