Add marine LEKTF workflow support

[AndrewEichmann-NOAA]

Description

Companion PR to NOAA-EMC/global-workflow#4789 to add marine LETKF to workflow and recenter increments around deterministic background to initialize ensemble.

Companion PRs

NOAA-EMC/global-workflow#4789

Issues

NOAA-EMC/global-workflow#5025
Also resolves #2155

Automated CI tests to run in Global Workflow

• atm_jjob
• C96C48_ufs_hybatmDA
• C96C48_hybatmsnowDA
• C96_gcafs_cycled
• C48mx500_3DVarAOWCDA
• C48mx500_hybAOWCDA
• C96C48_ufsgsi_hybatmDA
• C48_ufsenkf_atmDA
• C96C48_hybatmDA

[AndrewEichmann-NOAA]

@shlyaeva Is @lslivins Laura?

[Copilot]

Pull request overview

This PR is a draft companion to global-workflow changes, intended to add/enable marine LETKF workflow support and related recentering/ensemble-increment handling in GDASApp’s marine configuration templates.

Changes:

• Updates marine workflow YAML templates to stage/route LETKF increment outputs into analysis COM locations and to stage recentering inputs (increments/analysis).
• Extends marine LETKF configuration to include additional sea-ice increment variables and enables saving posterior ensemble increments.
• Adds a JCB marine output template for ensemble increments and introduces marine_letkf_app-conditioned behavior in marine JCB templates.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
parm/marine/marine_ens_config.yaml.j2	Updates LETKF staging/output paths and switches per-resolution fix template inclusion to zero-padded OCNRES.
parm/marine/marine_ecen_config.yaml.j2	Adds staging for LETKF increments/analysis for ensemble recentering and updates fix-template inclusion formatting.
parm/marine/marine_det_config.yaml.j2	Zero-pads OCNRES when including the marine fix staging template.
parm/marine/marine_bmat_config.yaml.j2	Zero-pads OCNRES when including the marine fix staging template.
parm/marine/jcb-base.yaml.j2	Adds ice thickness variables and enables saving posterior ensemble increments for marine LETKF driver settings.
parm/jcb-gdas/model/marine/marine_output_ensemble_increments.yaml.j2	Introduces a marine model output template intended for ensemble increment output.
parm/jcb-gdas/model/marine/marine_background_ensemble.yaml.j2	Conditions ensemble state variable lists on LETKF-app mode (and adds additional ice variables for that path).
parm/jcb-gdas/algorithm/marine/soca_ens_handler.yaml.j2	Adds LETKF-app-conditioned behavior for increment variables, optional analysis-increment inputs, and recentering background selection.

[guillaumevernieres]

@AndrewEichmann-NOAA , is it ready to be ci tested? If so, trigger the tests.

[lslivins]

@AndrewEichmann-NOAA I'm running the workflow now, and so far it's working as expected, though I haven't read through the code. It's made it through 3 cycles.

I do have to make some changes to dev/jobs/JGLOBAL_MARINE_ANALYSIS_ECEN and dev/jobs/JGLOBAL_MARINE_ANALYSIS_LETKF, because my project name is 'gsienkf'. I need to change the following for myself, though this isn't relevant for NCEPDEV projects unless they have 'enkf' in the name. Leaving the code as-is results in changing my directory names from /scratch4/BMC/gsienkf/to /scratch4/BMC/gsi/.

Replace: export DATAjob="${DATAROOT/enkf/}/marineanalysis.${PDY:-}${cyc}" with export DATAjob="${DATAROOT%enkf*}${DATAROOT##*enkf}/marineanalysis.${PDY:-}${cyc}"
Replace: cd "${DATAROOT/enkf/}" && true with cd "${DATAROOT%enkf*}${DATAROOT##*enkf}" && true
Replace: ${RUN/enkf/} with "${RUN%enkf*}${RUN##*enkf}

I'm not sure if this is something worth modifying for this PR or not though.

[emcbot]

Automated GW-GDASApp Testing Results:
Machine: ursa

Start: Wed Jun 17 21:46:38 UTC 2026 on ufe02
---------------------------------------------------
Build:                                  *FAILED*
Build: Failed at Wed Jun 17 21:48:00 UTC 2026
Build: see output at /scratch4/NCEPDEV/stmp/role.jedipara/CI/ursa/GDASApp/workflow/PR/2175/global-workflow/sorc/log.build

[RussTreadon-NOAA]

@AndrewEichmann-NOAA : The CI failure was due to soca compilation issues. Not sure why this happened. I will log into Ursa role.jedipara and manually rerun CI to troubleshoot.

[emcbot]

Automated GW-GDASApp Testing Results:
Machine: ursa

Start: Thu Jun 18 11:19:17 UTC 2026 on ufe04
---------------------------------------------------
Build:                                  *FAILED*
Build: Failed at Thu Jun 18 11:20:36 UTC 2026
Build: see output at /scratch4/NCEPDEV/stmp/role.jedipara/CI/ursa/GDASApp/workflow/PR/2175/global-workflow/sorc/log.build

[emcbot]

Automated GW-GDASApp Testing Results:
Machine: ursa

Start: Thu Jun 18 11:48:48 UTC 2026 on ufe04
---------------------------------------------------
Build:                                  *FAILED*
Build: Failed at Thu Jun 18 11:50:07 UTC 2026
Build: see output at /scratch4/NCEPDEV/stmp/role.jedipara/CI/ursa/GDASApp/workflow/PR/2175/global-workflow/sorc/log.build

[RussTreadon-NOAA]

@AndrewEichmann-NOAA :

Not sure if the following is the problem, but it's something I noticed:

• Your g-w branch AndrewEichmann-NOAA:feature/revive_marine_letkf_workflow points at gdas.cd @ 5227899. This hash of GDASApp branch feature/revive_marine_letkf_workflow is from May 12, 2026.
• In contrast, the head of GDASApp branch feature/revive_marine_letkf_workflow is at ad9c3ea. This hash is from June 17, 2026.

I would update sorc/gdas.cd in your g-w branch AndrewEichmann-NOAA:feature/revive_marine_letkf_workflow to point at hash ad9c3ea, Apply the ursa-GW-RT label in this PR after updating your g-w branch and see what happens.

[shlyaeva]

I have one major question below (on whether DOLETKF_OCN_INC means the same as marine_letkf_app). Also, I think it would be good to add @lslivins's changes.

[shlyaeva]

I think we only need this when we have DOLETKF_OCN_INC, is the check consistent here?

[shlyaeva]

suggest removing commented out lines

[shlyaeva]

I think we can just remove the velocities altogether, for both with and without LETKF cases.
I would however ignore this comment (because it requires more testing, and it's probably easier to not do it at this point), not very important.

[shlyaeva]

did you mean to remove this file?