Skip to content

LETKF on the monarch grid#26

Open
andreapiacentini wants to merge 3 commits intodevelopfrom
feature/io_config_for_4d_letkf
Open

LETKF on the monarch grid#26
andreapiacentini wants to merge 3 commits intodevelopfrom
feature/io_config_for_4d_letkf

Conversation

@andreapiacentini
Copy link
Collaborator

Handling of the "member" key in the local I/O configuration (added by the LocalEnsemble solver).
Handling of date patterns in the I/O config.
A first test case

@andreapiacentini
Copy link
Collaborator Author

Tested with gnu compiler too.
Some issues can be foreseen for I/O efficacity with large ensembles and many variables in the States.
Other LETKF implementations have highly optimised this aspect. This investigation is related to Issue #22

andreapiacentini and others added 2 commits February 3, 2026 12:17
…of the observers. Pointing to its default value, but kept for memory in case one would to use a "linear" time interpolation
@benjaminmenetrier
Copy link
Owner

I just cleaned a bit the code with commit 9978e08, @andreapiacentini let me know if it is fine for you.

@andreapiacentini
Copy link
Collaborator Author

It looks cleaner indeed.
What I still cannot understand is whether there is anything parallel in the I/O of the 4D LETKF.

@andreapiacentini
Copy link
Collaborator Author

Nor why the PseudoModel threatens the memory limitations by loading the whole timeseries of the states even if the forecast method advances step by step. Even with linear time interpolation you never need more that two instances in memory. And there's a loop on members too...

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants