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: mpas 2m temp, 10m wind interpolations #768

Open
hkershaw-brown opened this issue Nov 6, 2024 · 9 comments
Open

bug: mpas 2m temp, 10m wind interpolations #768

hkershaw-brown opened this issue Nov 6, 2024 · 9 comments
Labels
Bug Something isn't working mpas Model for Prediction Across Scales (MPAS)

Comments

@hkershaw-brown
Copy link
Member

💀 skeleton issue will fill in.

User reported 2M temperature observation, model_interpolate is using the 3D theta temp field

@hkershaw-brown hkershaw-brown added Bug Something isn't working mpas Model for Prediction Across Scales (MPAS) labels Nov 6, 2024
@hkershaw-brown
Copy link
Member Author

similarly, for 2m (or 10m or whatever surface qtys) convert_vertical_state is using the 1st level of zgrid as the vertical location, should this be using 2m, 10m?

! surface obs should use the lower face of the first level. the rest
! of the quantities should use the level centers.
if ( ndim == 1 ) then
zout(:) = zGridFace(1, cellid)

@nancycollins
Copy link
Collaborator

the first level of the 3d field is the model surface, and 2m and the surface are probably close enough. but the code does need to convert from theta (potential temperature) to sensible temperature - by computing with theta, rho, and qv. if it's not doing that with surface obs, then that's a bug.

if someone wants to interpolate 2m temps using the diagnostic 2m temperature field, i believe that is already sensible temperature and it shouldn't be corrected like the theta field is - just return the interpolated value.

@hkershaw-brown
Copy link
Member Author

hkershaw-brown commented Nov 11, 2024

for completeness (coping from the email support - amazingly my skeleton issue is not enough information for this problem) user report that the 2m increments looks incorrect.
So maybe close enough but doing an (incorrect) conversion.
Or not close enough (with conversion correct).
Or maybe both not close and not correct.

to confirm:

  1. conversion 'correct' theta (pot temp) -> 2m (temp) using level 1 of theta
  2. surface obs (temp) -> using t2m (temp)
  3. 1 is worse than 2.
  4. t2m temperatures are quite different (cold bias?) output from MPAS

@criedel40
Copy link
Collaborator

criedel40 commented Nov 11, 2024 via email

@hkershaw-brown
Copy link
Member Author

Thanks Chris, here is the clarification (apologies for doing a terrible job of reporting this issue!)

The 2m temperature is just much colder than the 3d temperature field (the plots I sent along earlier converted the 3d field from theta to temperature before plotting). Is there a known cold bias in the 2m temperature field for MPAS? It seems to have a really large cold bias for my fog cases.

@criedel40
Copy link
Collaborator

criedel40 commented Nov 11, 2024 via email

@syha
Copy link
Collaborator

syha commented Nov 11, 2024 via email

@nancycollins
Copy link
Collaborator

someone pointed out to me that the bottom face of the first row of cells is the model surface, but theta is computed on cell centers, which are halfway up the thickness of the first level. sorry for adding to the confusion about surface obs.

hkershaw-brown added a commit that referenced this issue Nov 12, 2024
@hkershaw-brown
Copy link
Member Author

!MARINE_SFC_TEMPERATURE, QTY_2M_TEMPERATURE, COMMON_CODE
vs
!MARINE_SFC_TEMPERATURE, QTY_TEMPERATURE, COMMON_CODE
how general is this, e.g. cam-se, fv, ocean models, etc.
see Brett discussion pull request: #708 model_mod taking care of this. Switch out fwd operator depending on model? Obs def queries for QTY_2M first?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working mpas Model for Prediction Across Scales (MPAS)
Projects
None yet
Development

No branches or pull requests

4 participants