Skip to content

Optimal I/O #2

Description

@jgomezdans

Currently, the I/O of the observations and subsequent results are just arrays. This is far form ideal, as they are created and take up memory lspace and thus reduce the size of problems that can be solved. A better approach is to have a dedicated method to process the observations on a per timestep/band basis, and use some specialist method to write out the data to an efficient format (HDF5, netCDF, whatever).

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions