You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I know this is a controversial feature, but I would like to start thinking of an option to disable the nopp section in scripts and the associated automatic export of ecflow variables. This would really simplify the porting of legacy suites to pyflow and could provide more flexibility for some operational workflows (use of common very generic headers for instance).
Maybe something to discuss with RD at ECMWF. What do you think @oiffrig, @floriankrb, @tlmquintino?
Describe the solution you'd like
An option could be added at the node level, such as nopp=True, False would disable the nopp section in all the scripts contained in the node.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I know this is a controversial feature, but I would like to start thinking of an option to disable the nopp section in scripts and the associated automatic export of ecflow variables. This would really simplify the porting of legacy suites to pyflow and could provide more flexibility for some operational workflows (use of common very generic headers for instance).
Maybe something to discuss with RD at ECMWF. What do you think @oiffrig, @floriankrb, @tlmquintino?
Describe the solution you'd like
An option could be added at the node level, such as
nopp=True
, False would disable the nopp section in all the scripts contained in the node.The text was updated successfully, but these errors were encountered: