eWaterCycle / eWaterCycle/infra

ESMValTool memory issue in parallel computation

Open
#160 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Jinja
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

On the eWaterCycle teaching machines when generating forcing using LumpedMakkinkForcing the kernel freezes when the number of years > 4 (the juypter cell keeps running without producing a result) . It works fine up to 4 years of forcing.

After changing the ESMValTool configuration to use a sequential runner, the result is produced fast without issues.

stacktraces

![Screenshot 2024-04-02 at 12 49 53](https://github.com/eWaterCycle/infra/assets/12114825/8a69cea7-eade-417e-bdda-2eac4c30ab8b)
![Screenshot 2024-04-02 at 12 49 42](https://github.com/eWaterCycle/infra/assets/12114825/d102de5a-a05b-4a06-9a18-2785f26b94c0)


We should figure out if this is an ESMValTool problem, or if it's related to our [(dask) configuration](https://docs.esmvaltool.org/projects/ESMValCore/en/latest/quickstart/configure.html#dask-distributed-configuration).

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.