-
Notifications
You must be signed in to change notification settings - Fork 157
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 the real(8) lat/lon in netcdf file #37
Comments
junwang-noaa
added a commit
to junwang-noaa/fv3atm
that referenced
this issue
Jan 7, 2020
DusanJovic-NOAA
added a commit
that referenced
this issue
Jan 24, 2020
* fv3atm issue #37: fix the real(8) lat/lon in netcdf file * fv3atm #35: Reducing background vertical diffusivities in the inversion layers * fv3atm #24: bug in gfsphysics/physics/moninedmf_hafs.f * fv3atm #18: Optimize netcdf write component and bugfix for post and samfdeepcnv.f * set (0-1) bounds for ficein_cpl * remove cache_size due to lower netcdf verion 4.5.1 on mars * Change ice falling to 0.9 in gfsphysics/physics/gfdl_cloud_microphys.F90
The code is committed, close issue. |
climbfuji
added a commit
to climbfuji/fv3atm
that referenced
this issue
Apr 8, 2020
…ninedmf dtc/hwrf-physics: combined version of HAFS/GFS moninedmf scheme (hybrid EDMF PBL)
climbfuji
pushed a commit
to climbfuji/fv3atm
that referenced
this issue
Jun 25, 2020
…_develop_20200616 Update gsd/develop from develop 2020/06/16
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is reported that the values of lat/lon in the netcdf history file are not exactly real(8) as they are defined in some of FV3 runs. The issue is identified in fv3 32bit runs when the lat/lon coordinate in the write component grid is changed from degrees to radians when computing the vector interpolation. The computation is done with real(4) numbers when compiled with 32BIT=Y so the values lat/lon is not purely real(8). The problem is fixed by using two local arrays to hold the lat/lon in radians.
The text was updated successfully, but these errors were encountered: