fix inconsistent types related with noahmp and log functions#755
Conversation
climbfuji
left a comment
There was a problem hiding this comment.
Thanks for these bug fixes. I think that they won't impact the UFS at all, because the files you are changing are compiled with default double precision reals in the UFS.
|
@uturuncoglu I tested these changes, and I get compile errors (with Intel, haven't triedd GNU yet): |
climbfuji
left a comment
There was a problem hiding this comment.
Please fix the compile errors.
|
@climbfuji sure. it is probably due to the line continuation. I need to move it to the next line. |
|
@climbfuji btw, I am also using intel but compiling those sources did not reveal any issue. ccpp might use different flags than I am using. |
Good point. I think there are some hardcoded form flags for certain files. Generally, .f/.F files should be fixed form, .f90/.F90 files free form. |
|
@climbfuji I think I fixed it it was spacing issue. The |
|
Thanks, Ufuk! The code now compiles with both 32bit and 64bit fv3atm (physics is always 64bit in the UFS). I pulled your PR into #752. Please keep your PR open, it should be flagged as merged (and you of course get all the credit for it) when #752 gets merged (a week or longer from now). Thanks again for catching and fixing those problems. |
|
@climbfuji I confirmed that |
This PR aims to fix couple of minor issue related to the inconsistent data types in the CCPP/physics. If user wants to compile NoahMP and related files outside of the CCPP package, the compiler triggers errors since some of the subroutines uses
realdata type rather thanreal(kind=kind_phys), whichkind_physis set to R8 by default under CCPP.This is related with the following issue: #750