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

Merge PM2.5 data assimilation for RRFS-SMOKE #480

Closed
hongli-wang opened this issue Oct 3, 2022 · 5 comments
Closed

Merge PM2.5 data assimilation for RRFS-SMOKE #480

hongli-wang opened this issue Oct 3, 2022 · 5 comments

Comments

@hongli-wang
Copy link
Collaborator

Merge GSI PM2.5 data assimilation development for RRFS-SMOKE at GSL.

@RussTreadon-NOAA
Copy link
Contributor

@hongli-wang , is this the issue associated with PR #482?

@CoryMartin-NOAA
Copy link
Contributor

@RussTreadon-NOAA I believe it is, but before closing we should wait for confirmation from @hongli-wang

@hongli-wang
Copy link
Collaborator Author

hongli-wang commented Jan 25, 2023

@RussTreadon-NOAA Yes, it is associated with PR #482. Thanks.

@RussTreadon-NOAA
Copy link
Contributor

@hongli-wang , thank you for the confirmation.

Future development requires a more detailed issue. The issue should be opened at the start of development and document all your commits. Once development is ready to be considered for merger into develop, a PR can be opened. The PR should reference the issue. Merging and closing the PR will then automatically close the issue.

I will manually close this issue.

@hongli-wang
Copy link
Collaborator Author

@hongli-wang , thank you for the confirmation.

Future development requires a more detailed issue. The issue should be opened at the start of development and document all your commits. Once development is ready to be considered for merger into develop, a PR can be opened. The PR should reference the issue. Merging and closing the PR will then automatically close the issue.

I will manually close this issue.

@RussTreadon-NOAA Sure. I will fellow your guidance on the issues documenting. Thanks.

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

No branches or pull requests

3 participants