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 develop up to 2024-01-11 to dev/ufs-weather-model #1342

Conversation

JessicaMeixner-NOAA
Copy link
Collaborator

@JessicaMeixner-NOAA JessicaMeixner-NOAA commented Jan 6, 2025

Pull Request Summary

Merge develop branch up to commit date on 2024-01-11 to dev/ufs-weather-model

Description

Merge develop branch up to commit date on 2024-01-11 to dev/ufs-weather-model . This is the first in a sequence of PRs updating dev/ufs-weather-model with updates from develop.

Issue(s) addressed

None

Commit Message

Merge develop up to 2024-01-11 to dev/ufs-weather-model

Check list

Testing

  • How were these changes tested? in ufs-weather-model, see ufs-weather-model PR Merge develop of WW3 up to 2024-01-11 to dev/ufs-weather-model #1342 ufs-community/ufs-weather-model#2549
  • Are the changes covered by regression tests? (If not, why? Do new tests need to be added?)
  • Have the matrix regression tests been run (if yes, please note HPC and compiler)?
  • Please indicate the expected changes in the regression test output, (Note the list of known non-identical tests.)
  • Please provide the summary output of matrix.comp (matrix.Diff.txt, matrixCompFull.txt and matrixCompSummary.txt):

mickaelaccensi and others added 27 commits July 31, 2023 11:38
…efined in w3odatmd (size=15). Also, defined unit numbers for NDS(14) and NDS(15). (NOAA-EMC#1098)
 Conflicts:
	.github/workflows/intel.yml
	model/src/w3initmd.F90
	model/src/w3iogomd.F90
	model/src/w3ounfmetamd.F90
Copy link
Collaborator

@sbanihash sbanihash left a comment

Choose a reason for hiding this comment

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

Changes have been reviewed. Build test in standalone and within the ufs-wm structure have been passed successfully. I approve this PR

@sbanihash sbanihash merged commit d61564b into NOAA-EMC:dev/ufs-weather-model Jan 14, 2025
2 of 4 checks passed
@BrianCurtis-NOAA
Copy link

I think UFSWM would prefer we finish our testing before this merging takes place, in case something happens over there and we need to revert something with WW3.

sbanihash added a commit that referenced this pull request Jan 14, 2025
@sbanihash
Copy link
Collaborator

@BrianCurtis-NOAA will revert this then.

@BrianCurtis-NOAA
Copy link

@JessicaMeixner-NOAA The previous WW3_input_data was 20240214, so I just wanted to verify that we are going back in time with 20240111 ?

@BrianCurtis-NOAA
Copy link

@BrianCurtis-NOAA will revert this then.

No need to right now, let's see how testing goes first.

@JessicaMeixner-NOAA
Copy link
Collaborator Author

@JessicaMeixner-NOAA The previous WW3_input_data was 20240214, so I just wanted to verify that we are going back in time with 20240111 ?

Feel free to move it to a different date. It was my nomenclature and is not consistent with the way the other inputs are numbered.

@BrianCurtis-NOAA
Copy link

@JessicaMeixner-NOAA The previous WW3_input_data was 20240214, so I just wanted to verify that we are going back in time with 20240111 ?

Feel free to move it to a different date. It was my nomenclature and is not consistent with the way the other inputs are numbered.

How should we number it? 20250114 ? Will that hurt/break anything? The number would be set based on when the new data will be "viable" for UFSWM and that date forward.

@JessicaMeixner-NOAA
Copy link
Collaborator Author

@BrianCurtis-NOAA that works! Sorry for this oversight on my part, I saw it but then forgot about it. This will not hurt anything - we just need to make sure we point to the correct date in rt.sh.

@DeniseWorthen
Copy link
Contributor

DeniseWorthen commented Jan 17, 2025

@JessicaMeixner-NOAA Did you mean to merge dev/ufs-weather-model prior to the UWM PR being committed?

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.