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

Add version/DOI to output history files

Open
#711 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
fortran
Domain
data

Research direction

Start by finding where CMEPS writes the global attributes into history files, the place that currently emits file_version and model_doi_url. Then trace how the case's MODEL_VERSION and DOI values could reach that code, and check how CTSM already passes its version through, since the issue cites that as a working example. Done when history files include a version attribute and a populated model_doi_url taken from the case.

Written by the indexing model from the issue text.

Description

enhancement

CMEPS output history files don't contain version information for the overall model, nor CMEPS version. There's probably a way to output the CMEPS version as well, but as MODEL_VERSION is set in the case it can certainly at least output that.

What it currently outputs is this:

// global attributes:
                :file_version = "cmeps0" ;
                :model_doi_url = "unset" ;
}

CTSM is able to use MODEL_VERSION, either from the case, or sent from CMEPS to get something like this:

                :version = "ctsm5.4.062-8-g263a179d1" ;

which is very useful. And model_doi_url should also be able to be set, since it's also set in the case. It's currently set to CESM2 with this:

https://doi.org/10.5065/D67H1H0V

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 Data Engineering issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.