tavg_helper file should possibly be added to config_archive.xml
还没有人认领这个 Issue。
评估
调研方向
首先，将 cime_config/config_archive.xml 与 CISM 现有的 config_archive.xml 进行比较，并追踪 tavg_helper 在重启或分支运行期间如何归档和重新暂存。检查 hist_file_extensions 和 rest_file_extensions 如何影响 system-test 比较，包括 initial_hist 的处理。完成的标准是确定适当的分类并更新归档配置，或确定所需的 CIME 测试行为。
由索引模型根据 Issue 内容生成。
描述
As I'm moving CISM's config_archive.xml entries into this repository (under cime_config/config_archive.xml) and reworking it to support multiple ice sheets, it occurred to me that the tavg_helper file should possibly be listed here. This could be important if the tavg_helper file should be saved to the archive and if it's important for this file to be retrieved from the archive and restaged in the run directory in order for restarts / branch runs to be bit-for-bit in the diagnostic fields that this file is tracking when a run stops part-way through an averaging period.
Since I don't fully understand the tavg_helper file, I'm not positive that this is necessary (though I suspect that it is under some conditions). If this is added to config_archive.xml, however, we may run into the same issue we ran into for the initial_hist file: the hist_file_extensions in config_archive are also used to tell the test system which files to compare in system tests, which can possibly cause problems in restart test comparisons. If this is an issue, we may be able to deal with it by either:
- Listing this as a rest_file_extension instead of hist_file_extension. This would need some thought / investigation about which is appropriate here... it may actually be that rest_file_extension is most appropriate. (I think the differences are in whether files are moved or copied to the archive, retrieved from the archive, and whether only the last time's file is dealt with or all times; there may be other differences, too.)
- Putting some special purpose code in cime to ignore these helper files in tests (that's how we ignore initial_hist files, though that isn't ideal)
- (I thought another solution may be to use the
rest_history_varnameoption in config_archive, but I think that's probably not the right thing to do here.)
@Katetc @whlipscomb @gunterl - fyi.
- 主要语言
- Fortran
- 星标
- 4
- 派生
- 18
- 平均合并
- 3 天 17 小时
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ESCOMP/CISM-wrapper 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 35/100
ESCOMP/CISM-wrapper#154 ·
-
Consider aborting with an error if the user tries to set cisminputfile in a branch run可能已有人在做 @billsacks 于 15 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 45/100
ESCOMP/CISM-wrapper#152 · 1 条评论 ·
-
Coupler Updates for Missing Ablation可能已有人在做 @Katetc 于 22 天前认领。 未关闭
ESCOMP/CISM-wrapper#151 · 1 条评论 · 已指派 1 人 ·
-
ERI_Ly10.f10_f10_mg37.I1850Clm50SpG.derecho_intel.cism-isostasy_period4 Fail in cism_wrap_3.0.0可能重新可做 @Katetc 于 42 天前认领，目前没有进行中的 PR。 未关闭
ESCOMP/CISM-wrapper#148 · 已指派 1 人 ·
-
Update Externals and Tests for CESM3可能重新可做 @Katetc 于 86 天前认领，目前没有进行中的 PR。 未关闭
ESCOMP/CISM-wrapper#145 · 2 条评论 · 已指派 1 人 ·
查看 ESCOMP/CISM-wrapper 的全部 Issue
相似的 Issue
-
test_rescues_connection_reset_on_issue_comments_lookup fails on master and blocks every pull request未关闭
难度 1/5 1 小时以内 新手友好度 91/100
zerocracy/judges-action#3142 ·
维护者通常 2 天内回复
-
agent-butler-finding chore
难度 1/5 1 小时以内 新手友好度 94/100
jordansmall/spindrift#6552 ·
维护者通常 1 天内回复
-
Malformed encoded_filters causes a 500, and keeps failing with session persistence可能已有人在做 @officialasishkumar 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 80/100
维护者通常 1 天内回复
-
Synth suite fails unless run from the repo root: signal_flow's default machine path is cwd-relative未关闭bug
难度 2/5 1-3 小时 新手友好度 80/100
Nimblesite/osprey#370 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 70/100