You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clarify wording to use when citing the models (both CICE and Icepack), and describe options for identifying the code used (DOI for series, DOI for particular release, hash for particular commit).
The text was updated successfully, but these errors were encountered:
but this sounds a little confusing to me, and it doesn’t mention how to cite codes not yet formally released. Is this better?
(Icepack)
Each individual release has its own DOI number, e.g. Icepack v1.2.2 has DOI 10.5281/zenodo.3888633. All versions of this lineage (e.g. Icepack v1) can be cited by using the DOI 10.5281/zenodo.1213462. This DOI represents all versions, and will always resolve to the latest one. More information can be found by following the DOI links to zenodo.
(CICE)
Each individual release has its own DOI number, e.g. CICE v6.1.2 has DOI 10.5281/zenodo.3888653. All versions of this lineage (e.g. CICE6) can be cited by using the DOI 10.5281/zenodo.1205674. This DOI represents all versions, and will always resolve to the latest one. More information can be found by following the DOI links to zenodo.
(add for both)
If using pre-release code from the repository master, the hash at time of download can be cited, determined by executing the command ‘git log’ in your clone. The last 7 digits are generally sufficient to identify the latest commit.
Note that the version index wikis say “The DOI links include citation instructions.” We should probably point to the docs instead.
Clarify wording to use when citing the models (both CICE and Icepack), and describe options for identifying the code used (DOI for series, DOI for particular release, hash for particular commit).
The text was updated successfully, but these errors were encountered: