Skip to content

Update GCAFS dev branch to match develop#4445

Merged
CoryMartin-NOAA merged 7 commits intoNOAA-EMC:dev/gcafs.v1from
CoryMartin-NOAA:feature/update-dev
Jan 15, 2026
Merged

Update GCAFS dev branch to match develop#4445
CoryMartin-NOAA merged 7 commits intoNOAA-EMC:dev/gcafs.v1from
CoryMartin-NOAA:feature/update-dev

Conversation

@CoryMartin-NOAA
Copy link
Contributor

Description

Bring in develop changes to GCAFSv1 dev branch. No results are changed but it should be done to include Ursa support for CI tests.

Type of change

  • Bug fix (fixes something broken)
  • New feature (adds functionality)
  • Maintenance (code refactor, clean-up, new CI test, etc.)

Change characteristics

Checklist

  • Any dependent changes have been merged and published
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have documented my code, including function, input, and output descriptions
  • My changes generate no new warnings
  • New and existing tests pass with my changes
  • This change is covered by an existing CI test or a new one has been added
  • Any new scripts have been added to the .github/CODEOWNERS file with owners
  • I have made corresponding changes to the system documentation if necessary

DavidHuber-NOAA and others added 7 commits January 13, 2026 14:54
This just updates the README to update the support levels for different
platforms. I dropped comments about METplus verification as it is not
supported anywhere at the moment except on WCOSS2.
# Description
This moves the `C96mx025_S2S` test case from the PR matrix to the
`sfsv1` directory so it can still be run but not for every PR.

Resolves NOAA-EMC#4429 

# Type of change
- [ ] Bug fix (fixes something broken)
- [ ] New feature (adds functionality)
- [x] Maintenance (code refactor, clean-up, new CI test, etc.)

# Change characteristics
- Is this change expected to change outputs NO
- Is this a breaking change (a change in existing functionality)? YES
the high res S2S case will no longer run in CI (by design)
- Does this change require a documentation update? NO
- Does this change require an update to any of the following submodules?
NO

# How has this been tested?
Successfully launched the `C96mx025_S2S` test case on C6 using
`generate_workflows.sh`:
```bash
./generate_workflows.sh -Y ../ci/cases/sfsv1 -y C96mx025_S2S /gpfs/f6/drsa-precip4/scratch/David.Huber/test_sfs
```

and verified the test still ran through the first forecast segment.

# Checklist
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have documented my code, including function, input, and output
descriptions
- [x] My changes generate no new warnings
- [x] New and existing tests pass with my changes
- [x] This change is covered by an existing CI test or a new one has
been added
# Description

This PR fixes a problem whereby the JEDI LETKF solver job,
`atmensanlsol`, attempts to process observation inputs that don't exist.
With these changes, the input YAML for the `atmensanlsol` JEDI
application is rendered after the LETKF observer job, `atmensanlobs`,
runs, and the rendering is performed using the `clean_empty_obsspaces`
option in the `initialize()` method of the `Jedi` class. This ensures
that the observation inputs that the solver needs, produced by the
observer, are present before initialization, so that missing observation
inputs can be removed using the `clean_empty_obsspaces` option.

  Resolves NOAA-EMC#4420

# Type of change
- [X] Bug fix (fixes something broken)
- [ ] New feature (adds functionality)
- [ ] Maintenance (code refactor, clean-up, new CI test, etc.)

# Change characteristics
<!-- Choose YES or NO from each of the following and delete the other
-->
- Is this change expected to change outputs (e.g. value changes to
existing outputs, new files stored in COM, files removed from COM,
filename changes, additions/subtractions to archives)? NO (If YES,
please indicate to which system(s))
  - [ ] GFS
  - [ ] GEFS
  - [ ] SFS
  - [ ] GCAFS
- Is this a breaking change (a change in existing functionality)? YES/NO
- Does this change require a documentation update? YES/NO
- Does this change require an update to any of the following submodules?
YES/NO (If YES, please add a link to any PRs that are pending.)
  - [ ] EMC verif-global <!-- NOAA-EMC/EMC_verif-global#1234 -->
  - [ ] GDAS <!-- NOAA-EMC/GDASApp#1234 -->
  - [ ] GFS-utils <!-- NOAA-EMC/gfs-utils#1234 -->
  - [ ] GSI <!-- NOAA-EMC/GSI#1234 -->
  - [ ] GSI-monitor <!-- NOAA-EMC/GSI-Monitor#1234 -->
  - [ ] GSI-utils <!-- NOAA-EMC/GSI-Utils#1234 -->
  - [ ] UFS-utils <!-- ufs-community/UFS_UTILS#1234 -->
  - [ ] UFS-weather-model <!-- ufs-community/ufs-weather-model#1234 -->
  - [ ] wxflow <!-- NOAA-EMC/wxflow#1234 -->

# How has this been tested?



# Checklist
- [X] Any dependent changes have been merged and published
- [X] My code follows the style guidelines of this project
- [X] I have performed a self-review of my own code
- [X] I have commented my code, particularly in hard-to-understand areas
- [ ] I have documented my code, including function, input, and output
descriptions
- [ ] My changes generate no new warnings
- [ ] New and existing tests pass with my changes
- [X] This change is covered by an existing CI test or a new one has
been added
- [ ] Any new scripts have been added to the .github/CODEOWNERS file
with owners
- [ ] I have made corresponding changes to the system documentation if
necessary
This adds support for the GCAFS tests on Ursa.
Resolves NOAA-EMC#3976
# Description
(This is a re-opening of NOAA-EMC#4382)

Fixes some issues from the recent expansion of bash code analysis and
switch to the reviewdog framework.

First and foremost, the permission issue that prevented errors from
being posted to the PR are fixed. This was only an issue for pull
requests from forks (which is all of them for us). The trigger is
changed to `pull_request_target`, which changes the context to the
target repo. This is safe as long as we are not attempting to build or
run the code. Because of the context change, an additional argument is
needed for checkout to checkout the head of the PR.

Second, some parameters are turned into conditionals to handle the fact
that the action is run on both pull requests and merges to develop. This
allows both the correct hash in the previous change, and also the
correct GH reporter to be used. This uses a new GH action that will need
to be added to the allowed list.

Third, the `shfmt` options are fixed so that it actually fails on error.
Reviewdog has deprecated `fail_on_error`, but the `reviewdog/shfmt`
action does not seem to support the replacement `fail_level`. So,
`fail_level` is passed to reviewdog directly as a flag.

Finally, the README status badges are updated for the new actions.
Additionally, clicking on the code analysis badges now brings up the GH
action logs.

Note: the `bash_code_analysis` actions may not run for this PR because
of the trigger change. It will run on develop after merge, and on PRs
from then on.

Resolves NOAA-EMC#4369
# Description
This PR is a hotfix for NOAA-EMC#4439
skip_ci_on_hosts:
- gaeac5
- awsepicglobalworkflow
- ursa
Copy link
Contributor

Choose a reason for hiding this comment

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

should we run this on Ursa now that its running well?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's what this does, removes Ursa from the 'skip' list

- gaeac5
- hercules
- awsepicglobalworkflow
- ursa
Copy link
Contributor

Choose a reason for hiding this comment

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

same

- X
- X
-
- x
Copy link
Contributor

Choose a reason for hiding this comment

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

should this be uppercase?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

no idea, it's whatever is in develop now

Copy link
Contributor

Choose a reason for hiding this comment

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

It should be. I'll fix this in develop on my next PR.

Copy link
Contributor

@bbakernoaa bbakernoaa left a comment

Choose a reason for hiding this comment

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

just a few comments. but take them or leave them

@CoryMartin-NOAA CoryMartin-NOAA merged commit 0c42431 into NOAA-EMC:dev/gcafs.v1 Jan 15, 2026
9 checks passed
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.

6 participants