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
During the Gromet pipeline, the cwd is changed multiple times. Normally, the cwd is changed back once Gromet is generated. However, if the Gromet pipeline fails and the exception is caught, the cwd is never changed back. This causes unexpected behavior and depending on where the pipeline failed and where the script was originally run from, the cwd can be completely different.
This makes writing scripts like the model_coverage_report more complicated as you have to assume that the cwd has been changed and change it back before/after every step.
The text was updated successfully, but these errors were encountered:
During the Gromet pipeline, the cwd is changed multiple times. Normally, the cwd is changed back once Gromet is generated. However, if the Gromet pipeline fails and the exception is caught, the cwd is never changed back. This causes unexpected behavior and depending on where the pipeline failed and where the script was originally run from, the cwd can be completely different.
This makes writing scripts like the model_coverage_report more complicated as you have to assume that the cwd has been changed and change it back before/after every step.
The text was updated successfully, but these errors were encountered: