Skip to content
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

Notebook errors due to netcdf permission denied after failed RAVEN run #425

Open
richardarsenault opened this issue Feb 28, 2022 · 0 comments

Comments

@richardarsenault
Copy link
Contributor

Description

While using Notebooks on the pavics.ouranos.ca JupyterLab instance, and having 2 notebooks open:

  • One to generate forcing data and write the file to disk
  • One to run RAVEN using that forcing data from disk

These steps cause an error that might be hard for users to fix unless they know what they are doing:

  1. Running the first notebook to generate forcing data runs fine, produces a netcdf file.
  2. Running the second notebook causes an error due to errors in the forcing data (precipitation above 10000mm/day, or temperatures above 60°C), usually due to units not being the required ones. The error is well identified and explicit.
  3. Then, immediately after, running notebook 1 again to regenerate fixed data and overwriting the existing (erroneous) forcing data netcdf file fails with [Permission Denied] error, since it is still open in the 2nd notebook after the Raven error.
  4. To resolve, we must restart the kernel of the 2nd notebook, which releases the netcdf file and the 1st notebook can proceed with the write operation.

Ideally, if we could force netcdf files to be released after a raven error, that would solve this issue from happening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant