Project

General

Profile

Feature #7662

Allow absolute include paths in fcls

Added by Christopher Backhouse over 4 years ago. Updated over 1 year ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
Application
Target version:
-
Start date:
01/20/2015
Due date:
% Done:

0%

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

Description

Currently you can't #include a fcl using a full absolute path. I think it is possible with a relative path from your pwd.

Obviously it's a bad idea to have any official/standard fcls configured this way, but it would be very useful during development/debugging.

History

#1 Updated by Christopher Green over 4 years ago

  • Category set to Application
  • Status changed from New to Feedback
  • SSI Package art added
  • SSI Package deleted ()

As you state, this would be a bad idea in a production context: this is why the feature is as it currently is. It is not technically hard to implement, and can even be done specifically for the NOvA exec (nova) and no other, but we would like to be sure that the NOvA collaboration is happy with the implications of implementing this, including the likelihood of bleedover into production FHiCL files or of the command line option making its way into production scripts, causing problems with the release.

We will discuss this at an upcoming stakeholders meeting.

#2 Updated by Kanika Sachdev over 4 years ago

The NOvA production job fcls are separately maintained from the job fcls for common packages under development, and they are frequently audited. I don't expect this to be a problem for us in the production context.

Thanks!

#3 Updated by Kyle Knoepfel over 4 years ago

  • Target version set to 521

#4 Updated by Kyle Knoepfel over 1 year ago

  • Target version deleted (521)


Also available in: Atom PDF