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

fix: passing istatus set for vertislevel and vertisheight mpas_atm #761

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

hkershaw-brown
Copy link
Member

Description:

MPAS_ATM user reported that 2m and 10m fields in the state were not being updated by filter when they had vertical localization switched on.

In get_close_state, state with VERTISSURFACE was being converted to VERTISHEIGHT but given a failing istatus so the distance was "far away" (1e9), and thus not updated in the assimilation.

This pull request adds a passing istatus to convert_vert_distrib_state to the cases that did not set an istatus:

  • case (VERTISLEVEL)
  • case (VERTISHEIGHT)

This istatus was a problem for get_close_state where the convert_vert_distrib_state is used, but not for convert_vertical_state (since that istatus is ignored).

The mpas state is in height (m) so the 3D state variables (non-surface) don't enter the case statement localizing in height (ztypein == ztypeout).

Note I added a note in case (VERTISSCALEHEIGHT) line 5050 because ztypein == VERTISSURFACE can never be .true. at that point in the code. I can pull this out and make a separate issue to keep track of that.

Fixes issue

fixes #756

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Documentation changes needed?

  • My change requires a change to the documentation.
    • I have updated the documentation accordingly.

Tests

I compared the state (no inflation) t2m variables before and after assimilation.
no difference = not updated
difference = updated.

Checklist for merging

  • Updated changelog entry
  • Documentation updated
  • Update conf.py

Checklist for release

  • Merge into main
  • Create release from the main branch with appropriate tag
  • Delete feature-branch

Testing Datasets

  • Dataset needed for testing available upon request
  • Dataset download instructions included
  • No dataset needed

/glade/derecho/scratch/hkershaw/DART/Bugs/mpas_2m_10m/small_run (low res)
/glade/derecho/scratch/hkershaw/DART/Bugs/mpas_2m_10m/rundir this is the user case (high res)

fixes ##756
state with VERTISSURFACE was being converted to VERTISHEIGHT but given
a failing istatus so get_close_state was "far away"
@hkershaw-brown hkershaw-brown added mpas Model for Prediction Across Scales (MPAS) release+1 labels Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mpas Model for Prediction Across Scales (MPAS) release+1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug: MPAS_ATM get_close_state puts all VERTISSURFACE state "far away" (dist=1.0e9_r8)
1 participant