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

Updates from v2 #626

Merged
merged 17 commits into from
Apr 26, 2021
Merged

Updates from v2 #626

merged 17 commits into from
Apr 26, 2021

Conversation

llpcarson
Copy link
Contributor

@llpcarson llpcarson commented Apr 14, 2021

Updates from the ufs-weather-model release v2.0.0 (CCPP release 5.0.0), including:

  • documentation, including in-line doxygen
  • fix some assumed-size array dimensions (gnu10.x complains)
  • rename gmtb-scm to scm (single column model routines)

Fixes #581

Related PRs
ufs-community/ufs-weather-model#521
NOAA-EMC/NEMS#96
NOAA-EMC/fv3atm#280
NOAA-GFDL/GFDL_atmos_cubed_sphere#94

@ligiabernardet
Copy link
Collaborator

Has the Scientific Documentation been parsed with Doxygen and shown to produce same/similar results as the CCPP v5.0.0 release (https://dtcenter.ucar.edu/GMTB/v5.0.0)?

@llpcarson
Copy link
Contributor Author

Has the Scientific Documentation been parsed with Doxygen and shown to produce same/similar results as the CCPP v5.0.0 release (https://dtcenter.ucar.edu/GMTB/v5.0.0)?

I have not, @mzhangw , did you do this with your branch? If not, could you do that? Thanks!

@grantfirl
Copy link
Collaborator

I don't see #573 represented, but it looks like that was fixed with #585 in the main branch already, so this looks OK with me. I'll test this with the SCM v5-> master branch to see if I run into any issues.

@grantfirl
Copy link
Collaborator

@llpcarson With the merge conflicts, it looks like this branch needs to be merged with the latest master, right?

@climbfuji
Copy link
Collaborator

Yes, and this will have to happen a few more times I guess. The commit queue is long ...

@llpcarson
Copy link
Contributor Author

Yes, I'll need to do another merge with master. I am thinking it makes sense to wait until the current round of PRs goes in, and do another merge (and fix conflicts) then.

@climbfuji
Copy link
Collaborator

Yes, I'll need to do another merge with master. I am thinking it makes sense to wait until the current round of PRs goes in, and do another merge (and fix conflicts) then.

I usually have my code up to date when I create the PRs to start the review process, but then don't update anymore until it is time to commit. Everything else is just a waste of time in my opinion.

@llpcarson
Copy link
Contributor Author

Agreed - it was up-to-date yesterday, and I'll wait until closer to commit-time to update again and re-test

@grantfirl
Copy link
Collaborator

Totally fine by me. I was just looking to test this branch with the SCM and noticed the conflicts, but it turns out that the SCM branch that I'm testing this ccpp-physics branch with is also not updated to the latest master, so there is actually no problem for me.

@mzhangw
Copy link
Collaborator

mzhangw commented Apr 20, 2021 via email

@climbfuji
Copy link
Collaborator

I am thinking that sfcsub is more part of GFS_phys_time_vary for surface cycling based on the calling structure.It is not associated with a specific scheme as you pointed out. how about we take a note and change it in the future?

How about changing it as part of this PR? Would be easy to do for Laurie.

@mzhangw
Copy link
Collaborator

mzhangw commented Apr 20, 2021 via email

@llpcarson
Copy link
Contributor Author

I updated the branch with Man's change, but will wait to update the submodule pointers until the next merge/update is in

@climbfuji climbfuji merged commit b578157 into NCAR:master Apr 26, 2021
@llpcarson llpcarson deleted the updates_from_v2 branch September 7, 2021 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

namelist option name fix in scientific documentation
6 participants