Project

General

Profile

Feature #1025

end_paths and trigger_paths are now unnecessary and should be retired.

Added by Christopher Green over 8 years ago. Updated almost 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Navigation
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Scope:
Experiment:
-
SSI Package:
art
Duration:

Description

These items can be constructed internally now given our ability to identify modules as producer, filter, analyzer or output. We can also detect whether a module labeled as a trigger_path item actually an end_path item and vice versa. We should implement this and remove the need for users to compose these lines explicitly.


Related issues

Related to art - Feature #1463: Configuration blocks should enforce contentsClosed2011-07-17

History

#1 Updated by Walter E Brown over 7 years ago

Still desirable.

#2 Updated by Christopher Green almost 6 years ago

  • Status changed from Accepted to Rejected
  • Start date deleted (03/01/2011)
  • Experiment - added
  • SSI Package art added

end_paths and trigger_paths are no longer required due to commit 9a33fc91e2a9f0047cdb50d990cd4fe6fab6f529, but are honored if specified. However, experiments have stated that they wish to be able to easily disable "standard" paths included from other FHiCL files by simply omitting the path from the trigger_paths or end_paths parameters. It is therefore unlikely that the specification of these parameters will become an error in the future (although the proposed @erase FHiCL directive would also fulfill this requirement).



Also available in: Atom PDF