NCAR / NCAR/DART

Can coupler history (forcing) files from the CAM6 Reanalysis be used in CESM3?

Open
#878 34 comments 0 reactions 1 assignee View on GitHub

@kdraeder is already working on this.

Since May 27, 2025.

CAM cice CLM Documentation mom6 Question
Dominant language
Fortran
Stars
263
Forks
182
Avg merge
11d 12h
Merged PRs (30d)
7

Description

The implementation of the NUOPC mediator in CESM3 (replacing CESM2's coupler)
has resulted in the forcing files and the variables in them getting new names.
This raises questions about whether the Reanalysis files (CESM2.1)
can be fed to CESM for assimilations using the CESM3 surface models; CTSM, MOM6, CICE, ...
It appears that they can

I've attached a list of the stream files from the case referenced there,
but I don't have much experience looking at the contents of stream files,
so it would be helpful for an expert or 2 to do that.
keerzhang_user_nl_datm_streams.txt

In the user_nl_datm_streamfile file I see:
CPLHISTForcing.State1hr:datavars=a2x1h_Sa_u Sa_u, a2x1h_Sa_v Sa_v
but in a similar file it was
CPLHISTForcing.State1hr:datavars=a2x1h_Sa_u u, a2x1h_Sa_v v
I don't know whether those are equivalent.

I also haven't tested them. I'm hoping that it will be simple for someone
who runs a surface model to try this in CESM3. It wouldn't require any assimilation.

We will probably want to add files and documentation to describe how to use the old forcing files.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.