-
Notifications
You must be signed in to change notification settings - Fork 100
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 doxygen in AVIATION.f #395
Conversation
@fossell Would you please review the PR? Thanks! |
@edwardhartnett - Thanks for providing this an example of porting to doxygen syntax and standards. We will use this as guidance to translate other routines as well. @WenMeng-NOAA - This PR is just comment changes that Ed has provided as an example for doxygen. I have not tested this PR, just visually inspected. Only comments were changed in the routine, but if you want to run RTs to ensure no issues that's ok, either way is fine with me. |
@edwardhartnett Could you sync your branch with upstream/develop? Thanks! |
@WenMeng-NOAA I have synced branch... |
@edwardhartnett Do you have an UPP issue linking to this PR? |
@WenMeng-NOAA this relates to issue #392. |
…uld be the same as FV3_HRRR except for DT_ATMOS, dt_inner, and imfdeepcnv. (NOAA-EMC#395) This update also avoids some NA 13km FV3 crashes. Contributions from Tanya/Joe/Ming.
Part of #392
In this PR I fix the doxygen in the file AVIATION.f, to eliminate doxygen warnings for that file.
I cannot fix all your legacy documentation - this is just a sample to show how it should be done. ;-)
Some things to note for doxygen conversion:
In general, punctuation is missing from much of the documentation. Fortran programmers apparently are trying to save on keystrokes by refraining from putting a period on the end of the sentences. ;-) That's not good. Documentation should be punctuated properly to aid understanding.