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

Memory issue when running for longer timeframe and finer resolution sub-basin (for forcing file) #18

Open
sujata91 opened this issue Apr 5, 2024 · 1 comment
Labels
wontfix This will not be worked on

Comments

@sujata91
Copy link

sujata91 commented Apr 5, 2024

I encountered a memory issue in generating the forcing file required for MESH using the meshflow workflow. The workflow runs well for smaller timeframe and smaller number of subbasin. But there is issue with the memory with larger forcing dataset. Previously I had ~1600 subbasin and ran from 1980-2018 forcing files and had to provide like 128GB memory specs. With another geofabric (waterloo Merithydro geofabric) there are ~4000 subbasin and same time frame. Providing larger memory makes the job pending in cluster and even if it runs there is a memory issue. May be there could be some alternative solution to this in the workflow?

@kasra-keshavarz kasra-keshavarz added the wontfix This will not be worked on label Apr 5, 2024
@kasra-keshavarz
Copy link
Collaborator

Unfortunately, I cannot think of a way, but to have MESH read multiple NetCDF files at once. The functionality exists in common hydrological modelling programs such as SUMMA and mizuRoute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants