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/RAM solutions #5

Open
CeresBarros opened this issue Apr 22, 2024 · 1 comment
Open

Memory/RAM solutions #5

CeresBarros opened this issue Apr 22, 2024 · 1 comment
Assignees

Comments

@CeresBarros
Copy link
Member

CeresBarros commented Apr 22, 2024

We'll need to think about how and "where" to deal with RAM limitations, when dealing with e.g. many climate projections.
At the moment, in a 32GB machine, climr runs out of memory if all GCMs/periods/scenarios are requested (process_one_raster runs out of memore when extracting the climate values)

Options are to (not mututally exclusive):

  1. (partially) deal with these in climr
  2. deal with these externally to climr (e.g. in the modules that will need to extract cliamte projections)
  3. have climr warn the user about memory limitations (implemented in climr@out-of-memory-extract)
@CeresBarros CeresBarros transferred this issue from bcgov/CCISS Apr 23, 2024
@CeresBarros
Copy link
Member Author

currently implementing options 2 and 3

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

No branches or pull requests

2 participants