Add support for changing the year when starting a branch run

未关闭
#243 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
领域
backend

调研方向

首先跟踪 CESM branch-run 的设置以及 restart files 如何保留日历,并将其与 issue 中描述的 hybrid-run 路径进行比较。当一个 branch 能够将年份重置为 0001 或选择任意年份,同时保留 restart 的月份和日期,且不会出现从 9999 到 10000 的失败时,即可视为完成;首先解决日历与五位或六位数年份之间的权衡。

由索引模型根据 Issue 内容生成。

描述

A user ran 9982 years of a 3 degree ocean-ice run (the CORE forcing dataset covers 62 years, so this represents 161 cycles). They then tried to branch off the run for a couple of experiments, and ran into an illegal linear times issue when 9999-12-31 tried to roll over to 10000-01-01. (I believe he's using CESM 2.1, which is MCT-based rather than NUOPC-based, so the error message out of a recent beta tag might be different.)

Anyway, setting up a branch run instead of a hybrid is preferable because a hybrid run doesn't start the ocean component until the second coupling interval... so a branch would be a bit-for-bit continuation while a hybrid would change answers. However, he currently has to use a hybrid because the branch forces the user to keep the calendar from the run being continued.

While I could see an issue with creating a branch run B from the January 1st restart files from run A and trying to claim B starts in the middle of the year, a way to either reset the year to 0001 or set it to an arbitrary YYYY value while keeping the month and day constant would be helpful.

At a recent CSEG meeting, we discussed another option for supporting this use case: using 5 or 6 digits for the year instead of the current 4 digits. That seems more complicated than letting users branch from 9999 and reset the calendar back to 0001, and also has the potential for creating other issues (such as https://github.com/ESMCI/cime/issues/2903).

主要语言
Python
星标
495
派生
253
平均合并
34 分钟
30 天内合并 PR
4

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ESCOMP/CESM 的其他 Issue

查看 ESCOMP/CESM 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。