Memory/RAM solutions
Open
Type: Workflow
- Dominant language
- R
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
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 `extract`ing 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`)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.