-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
re-run diagnostic script stuck #136
Comments
Note that those options are specific for Python diagnostics, they are not implemented in NCL, R, or Julia. |
@bouweandela I recognize it is rather trivial, although not immediate, so I'll close this issue if you agree... |
It's up to you, I think it's a good suggestion for improving the user friendliness of the tool. Unfortunately we have limited time available to implement all of those suggestions... |
@bouweandela I report here below a tiny change to the above referred code to incldue the @@ -411,6 +411,8 @@ class DiagnosticTask(BaseTask):
rerun_msg += ' '.join('{}="{}"'.format(k, env[k]) for k in env
if k not in os.environ)
rerun_msg += ' ' + ' '.join(cmd)
+ if cmd[1].endswith('.py'):
+ rerun_msg = rerun_msg.replace('.py', '.py -i', 1)
logger.info("To re-run this diagnostic script, run:\n%s", rerun_msg)
try: If it looks ok, should I open a PR or you want to add it in the code .... |
This was solved via #326 |
After the successful execution of a recipe, re-running the diagnostic script stop with the following message:
This can be easily solved by adding the suggested options
-f
or-i
, but I fell like that the re-run message produced by code at the end of diagnostic function should more clear, e.g. by including at least-i
.In particular,
-i
can be added inrerun_msg
variable within the following piece of code:ESMValCore/esmvalcore/_task.py
Lines 409 to 414 in 82178a9
It could be also an idea to add in the log informations the need to specify
-f
or-i
options.The text was updated successfully, but these errors were encountered: