Skip to content

Recognize CMA as a valid center in rd_grib2.F#285

Open
Geek-007 wants to merge 1 commit into
wrf-model:developfrom
Geek-007:master
Open

Recognize CMA as a valid center in rd_grib2.F#285
Geek-007 wants to merge 1 commit into
wrf-model:developfrom
Geek-007:master

Conversation

@Geek-007

@Geek-007 Geek-007 commented Apr 14, 2026

Copy link
Copy Markdown

Include support for CMA dataset.

@jimbresch jimbresch changed the title Add support for CMA source in rd_grib2.F Recognize CMA as a valid center in rd_grib2.F Apr 14, 2026
@jimbresch

Copy link
Copy Markdown
Collaborator

This small change recognizes CMA as a valid center for labeling purposes. It was already added to g2print, but for some reason was omitted from rd_grib2.F. It can be merged once the unnecessary comment is removed.
If it can be confirmed that iprocess 15 is the CMA GFS Model (rather than another model or analysis) the new code can be changed to

else if (icenter .eq. 38) then
map%source = 'CMA'
if (iprocess.eq.15) then
map%source = 'CMA GFS Model'
endif

@Geek-007

Copy link
Copy Markdown
Author

Thanks for adding that.

@islas

islas commented Jun 27, 2026

Copy link
Copy Markdown
Contributor

@jimbresch

It can be merged once the unnecessary comment is removed

Do you mean the ! Edited by ... comment?

@jimbresch

Copy link
Copy Markdown
Collaborator

Yes, we don't normally include 'edited by' or 'modified by' comments in the code. The pull request serves as the attribution.

Comment thread ungrib/src/rd_grib2.F
map%source = 'UKMO'
else if (icenter .eq. 78 .or. icenter .eq. 79 ) then
map%source = 'DWD'
else if (icenter .eq. 38) then ! Edited by Geek-007

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Geek-007 Could you please remove the comment ! Edited by Geek-007? As @jimbresch notes, the git commit will record your changes:

Author: Geek <1069xxxxxx@qq.com>
Date:   Tue Apr 14 12:26:02 2026 +0800

    Add support for CMA source in rd_grib2.F

and anyone running, e.g., git show 4ec99405 will be able to see exactly what changes you have contributed in the commit. (Note, I anonymized your email address above, though it will appear correctly in the commit info.)

It would also be preferable for your changes to come in from a branch other than master. We typically only merge the master branch to the develop branch after a release, and so merging your master branch to our develop branch does create a less than ideal commit history. If you'd like some pointers on committing your changes to a new branch, just let me know and I will be glad to help.

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.

4 participants