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

bug: Sampling Error Correction doesn't affect adaptive inflation updates #778

Open
jlaucar opened this issue Nov 28, 2024 · 2 comments
Open
Assignees

Comments

@jlaucar
Copy link
Contributor

jlaucar commented Nov 28, 2024

Sampling error correction does not appear to impact the adaptive inflation updates.

The value of the sampling error correction is read from the table in subroutine update_from_obs_inc in assim_tools_mod.f90. It is then used to modify the value of the reg_coef which is subsequently multiplied by the obs_inc to get the state_inc which is returned. The updated value of the reg_coef is also returned to the calling location in subroutine obs_updates_ens. However, the reg_coef is a local variable array in obs_update_ens and is not returned from this subroutine. Subroutine update_varying_state_space_inflation does not make any use of the sampling error correction table. It seems like it would be appropriate to apply sampling error correction to reduce the strength of the relation between the observation and state variable when updating the inflation, too.

The current behavior has been unchanged since the original implementation of the adaptive inflation algorithms. Should we update the behavior to include the use of sampling error correction, or should we document that it is not being done?

@mgharamti
Copy link
Contributor

I can confirm that the regression coefficient used to update the inflation does not apply SEC. I've always thought that SEC is used to update the inflation but I was mistaken. Question: Do we actually need SEC in the inflation update?
To answer this question, we'll need some testing. I'll conduct some experiments with low-order models to gain some insights. More to follow ..

@jlaucar
Copy link
Contributor Author

jlaucar commented Dec 9, 2024 via email

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

3 participants