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

Update atmos upp job to use COMIN/COMOUT #2823

Closed
mingshichen-noaa opened this issue Aug 12, 2024 · 3 comments
Closed

Update atmos upp job to use COMIN/COMOUT #2823

mingshichen-noaa opened this issue Aug 12, 2024 · 3 comments
Assignees
Labels
Static Data Mgmt Update of static data (fix, ICs, etc.) triage Issues that are triage

Comments

@mingshichen-noaa
Copy link
Contributor

mingshichen-noaa commented Aug 12, 2024

Description

NCO has requested that each COM variable specify whether it is an input or an output. This completes that process for the global-workflow atmos upp job.

Refs#2451

Type of change

  • Maintenance (code refactor, clean-up, new CI test, etc.)

Change characteristics

  • Is this a breaking change (a change in existing functionality)? NO
  • Does this change require a documentation update? NO

How has this been tested?

  • C48_ATM experiment on RDHPCS Hecules/Hera
  • CI/CD will test the additional applications

Pickup location

/work2/noaa/global/mchen/global-workflow

Size

300

@mingshichen-noaa mingshichen-noaa added Static Data Mgmt Update of static data (fix, ICs, etc.) triage Issues that are triage labels Aug 12, 2024
@mingshichen-noaa
Copy link
Contributor Author

Walter, Kate,
Just now I created an issue #2823 refer to #2451. But I have some questions about selections:

  • pickup location: I picked up my local repo path, wasn't I?
  • size: I gave an estimate value: 300 MB, is it enough?

@WalterKolczynski-NOAA
Copy link
Contributor

Walter, Kate, Just now I created an issue #2823 refer to #2451. But I have some questions about selections:

  • pickup location: I picked up my local repo path, wasn't I?
  • size: I gave an estimate value: 300 MB, is it enough?

You opened the wrong kind of issue. Your work has nothing to do with fix files (files in the fix/ directory that we don't keep in the repo). Recommend closing this issue and reopening as the correct type (Feature Request).

@mingshichen-noaa
Copy link
Contributor Author

Walter,
Thank you for your response. I will close it and reopen the Feather Request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Static Data Mgmt Update of static data (fix, ICs, etc.) triage Issues that are triage
Projects
None yet
Development

No branches or pull requests

3 participants