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

Create sanity checks #41

Open
patnr opened this issue Jun 28, 2023 · 0 comments
Open

Create sanity checks #41

patnr opened this issue Jun 28, 2023 · 0 comments

Comments

@patnr
Copy link
Collaborator

patnr commented Jun 28, 2023

There should be tests that make sure that the results of the algorithms are sensible.
These don't necessarily need to be part of automated CI tests,
as mentioned in #40, but rather the examples.

I suggest to use a trivial case, for example, for DA:
5d, no dynamics, observe (directly) 1 component.

  • posterior mean/cov should nearly match theoretical.
  • test all of the methods
  • test for different configs (ensemble size, iteration numbers, with and without localisation)

For optimisation, for example: a 5d quadratic objective

  • Check optimum is found
  • Check number of iterations not excessive.
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

No branches or pull requests

1 participant