-
Notifications
You must be signed in to change notification settings - Fork 109
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
doxygen documentation for sorc/grid_tools.fd #343
Comments
In review of this issue, it included 4 directories and 12 f90 source codes. I think it will be helpful if @GeorgeGayno-NOAA can take a view and input high level description document before we can finish this issue with detail doxygen update. |
We need these files doxygenated. Please add doxygen formatting as best you can. Do one or two files and put up a PR, and we will start filling in the missing information. |
doxygen documentation for sorc/grid_tools.fd ufs-community#343 The grid_tools.fd included 4 directories and 12 f90 source codes. Changes to be committed: modified: regional_esg_grid.fd/psym2.f90 modified: regional_esg_grid.fd/regional_esg_grid.f90 modified: shave.fd/shave_nc.F90
I am working with Jim Purser to get the rest of these question marks filled in... |
OK, in sorc/grid_tools.fd/regional_esg_grid.fd there is one file with three remaining undocumented fields, I have sent that to Jim Purser to get the answers. The other undocumented file is filter_topo.f90. This was written by two GFDL programmers. I have sent the file to Rusty Benson and asked them to fill in the missing fields. |
@bensonr any progress getting the programmers to document their work in filter_topo.f90? |
@edwardhartnett - there is a section dedicated to the topography filtering algorithm in the soon to be released comprehensive, scientific description of FV3 "the dycore" documentation. As this offline filtering algorithm comes directly from FV3 "the dycore", that will be the authoritative source. Once it is released, proper referencing will be available. |
@bensonr scientific documentation of the algorithm is pretty different from code documentation. Can we have the programmers document the code as well? |
Part of #191
The text was updated successfully, but these errors were encountered: