Project

General

Profile

Feature #1463

Configuration blocks should enforce contents

Added by Rob Kutschke about 8 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Navigation
Target version:
Start date:
07/17/2011
Due date:
% Done:

100%

Estimated time:
Scope:
Internal
Experiment:
Mu2e
SSI Package:
art
Duration:

Description

I have a module which is an EDFilter. I wrote an fcl file in which I put, incorrectly, the pset for that module in the analyzer block. I correctly put the name of the filter module into a trigger path. All worked fine. Is that the intended behaviour? If I put the module into an endpath, then I do get a diagnostic at startup-time, saying that filters belong in triggerpaths, not endpaths.


Related issues

Related to art - Feature #1025: end_paths and trigger_paths are now unnecessary and should be retired.Rejected

History

#1 Updated by Christopher Green about 8 years ago

  • Category set to Navigation
  • Status changed from New to Feedback
  • Assignee set to Christopher Green

We don't currently have the information at the time we read the parameter sets for modules to verify that the module type matches the placement of its parameter set. However, at the time the trigger_paths and end_paths are checked we can verify that filters and producers are correctly not in end paths and the placement of the parameter set is not used in this determination. If you think it would be useful to you we can investigate methods of doing the check you specify but it's not something we have in our plans at the moment.

Let us know.

#2 Updated by Rob Kutschke about 8 years ago

This is not a high priority. But it's the sort of thing that can confuse people if bad examples get into common circulation. Put it on the low priority list. If it makes your life easier, it's OK by me if the check comes a little later rather than a little earlier, just so long as it is done in the startup phase.

#3 Updated by Christopher Green about 8 years ago

  • Status changed from Feedback to Assigned
  • Priority changed from Normal to Low

#4 Updated by Walter E Brown over 7 years ago

  • Status changed from Assigned to Accepted
  • Assignee deleted (Christopher Green)
  • Priority changed from Low to Normal

#5 Updated by Walter E Brown over 7 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from Is this a bug? to Configuration blocks should enforce contents

#6 Updated by Christopher Green about 6 years ago

  • Status changed from Accepted to Resolved
  • Assignee set to Christopher Green
  • Target version set to 1.08.00
  • % Done changed from 0 to 100
  • Scope set to Internal
  • Experiment Mu2e added
  • SSI Package art added

#7 Updated by Christopher Green about 6 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF