Skip to content

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

@richardarsenault

Description

@richardarsenault

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions