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

possible bug: MITgcm_ocean potential temperature #774

Open
hkershaw-brown opened this issue Nov 13, 2024 · 0 comments
Open

possible bug: MITgcm_ocean potential temperature #774

hkershaw-brown opened this issue Nov 13, 2024 · 0 comments
Labels
pot temp potential vs sensible temperature in model_interpolate

Comments

@hkershaw-brown
Copy link
Member

The mitgcm_ocean model_mod interpolates qty_temperature directly (no conversion from potential temp)

subroutine model_interpolate(state_handle, ens_size, location, quantity, interp_val, istatus)

The model appears to use potential temperature in the state:

mitgcm_variables = 'PSAL', 'QTY_SALINITY', 'NA', 'NA', 'update',
'PTMP', 'QTY_TEMPERATURE', 'NA', 'NA', 'update',

TVarID = define_variable(ncid,"PTMP", nf90_real, all_dimids, MITgcm_3D_FIELD)
call add_attributes_to_variable(ncid, TVarID, "Potential Temperature", "C", "degrees celsius")

note also potential salinity vs salinity.

Possibly this is just a naming issue with the model state, but I figured I would note this rather than the comment getting buried in
#773

@hkershaw-brown hkershaw-brown added the pot temp potential vs sensible temperature in model_interpolate label Nov 13, 2024
@hkershaw-brown hkershaw-brown changed the title possible bug: MITgcm_ocean possible bug: MITgcm_ocean potential temperature Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pot temp potential vs sensible temperature in model_interpolate
Projects
None yet
Development

No branches or pull requests

1 participant