Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Update MODEL_DOI_URL for cesm to a CESM3 page

Open
#712 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
xml
Domain
backend

Research direction

Start by reading config_component_cesm.xml and checking how MODEL_DOI_URL is configured for different cime_model values. The issue asks whether CESM3 has a starting page and DOI, and whether NorESM needs a separate value; confirm those decisions before changing the entry. Done means the appropriate CESM3 and NorESM DOI values are defined, with a CESM3 page available.

Written by the indexing model from the issue text.

Description

CESM only enhancement

Currently config_component_cesm.xml has MODEL_DOI_URL as

https://doi.org/10.5065/D67H1H0V

which is for CESM2. We'll need a new DOI for CESM3. Do we have a starting page for CESM3 at this point? That will need to be created soon as well as the DOI for it. Who can do this?

Also @mvertens @mvdebolskiy is this something where NorESM will point to something different using cime_model? It coudl be easily done with something like this:

  <entry id="MODEL_DOI_URL">
    <type>char</type>
    <default_value cime_model="cesm">https://doi.org/10.5065/CESM3_DOI</default_value>
    <default_value cime_model="noresm">https://doi.org/NorESM_DOI</default_value>
    <group>run_metadata</group>
    <file>env_case.xml</file>
    <desc>run DOI</desc>
  </entry>
Dominant language
Fortran
Stars
36
Forks
107
Avg merge
1d 5h
Merged PRs (30d)
2

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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.

More from ESCOMP/CMEPS

All issues in ESCOMP/CMEPS

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.