Giter Club home page Giter Club logo

noresm-docs's Introduction

Norwegian Earth System Model Documentation

License: GNU LGPL 3.0 NordicESMhub chat

The NorESM documentation on Read the Docs is built from the branches in this repository. The branches correspond to different versions of the NorESM source code.

version build status note
NorESM1 NorESM1 Documentation Status Model version used for CMIP5 and IPCC AR5
NorESM2 NorESM2 Documentation Status Model version used for CMIP6 and IPCC AR6
NorESM2.1 NorESM2.1 Documentation Status bugfix and technical release version
NorESM2.2 NorESM2.2 Documentation Status unvalidated development version

How to contribute to the NorESM documentation

  • step 1: Fork this repository as shown in the figure below.

Fork NorESM documentation repository

  • step 2: Go online to NorESM documentation and whenever you would like to update the documentation, click on "Edit on GitHub".

Edit documentation online

  • step 3: Then click on the "pen" (see image below) and write your text (reStructuredText)

Edit the file in your fork

  • step 4: Save your changes in your forked repository and create a pull request.

Propose your changes

If you do not like to update the documentation online and prefer to use your favorite editor locally on your machine/laptop, you can skip step-3 and 4 and then clone your forked repository to edit the files locally. Once pushed to your forked github repository, you can create a pull request and propose your changes.

Example on how to see your changes locally with sphinx:

Prepare your PC/MAC

$ conda install sphinx
$ conda install -c conda-forge sphinxcontrib-bibtex
$ conda install -c conda-forge sphinx_rtd_theme

Copy NorESMdoc repository to local

$ git clone [email protected]:NorESMhub/NorESM-docs.git

go to NorESM-docs dir

$ sphinx-build . _build

open _build/index.html in browser

More info See https://coderefinery.github.io/documentation/sphinx/

noresm-docs's People

Contributors

evalieungh avatar tomastorsvik avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

noresm-docs's Issues

Create new version for NorESM 2.dev

As progress is made towards the next version of NorESM based on the NUOPC architecture, a new version of the documentation is needed to correctly document the places where the structure of the code or use of the model is different.

version overview in all versions?

Would it be possible to have upfront an overview of all versions - in all versions? When you get to noresm2, there is no note on that there is also a technically supported version 2.1 . I think a note deserves its place there.

Create NorESM2.5 documentation for developers

I believe it is time to start a new documentation for NorESM2.5. Initially, this should be targeted towards developers only. We can include information on how to use profiling and timing (Johannes has already started documenting this), where to find simulations and test cases, technical details on branches, where to find initial conditions and restart files. And xmlchange, git ++++. Do we start from scratch? I'm thinking that is a good plan, and then we can add useful parts from the noresm2 documentation at a later stage when we want to make it more user friendly. What are your thoughts?

Version links from the bottom collapsible menu are broken

Pages apart from main https://noresm-docs.readthedocs.io/en/tag/. Will give 404 when switching to another version through the bottom menu (since most of them do not exist for another version). F.e. from https://noresm-docs.readthedocs.io/en/noresm2.1/noresm2.1/noresm2.1.html at noresm2.1 will give you 404 when switching to any other tag. Not sure how to configure the flyout menu to go to the base URL when clicking on version.

NIRD mount points out of date?

In section 2.4, the documentation says that the NIRD mount points on Betzy are /trd-project*/xx, however, I could not find those. Instead, I see /nird/projects/NS* (along with a few other directories under /nird/).
Should the documentation (2.0 and 2.1) be updated/

Document the NorESM2.1 release

I have created a noresm2.1 branch as a clone of the noresm2 branch.

Things to do before documentation release:

  • Remove specific topics related to CMIP6 (noresm2.0 version)
  • Add release notes
  • Notify that noresm2.1 is a technical release, and what this implies for use of the model
  • Add information about test runs for noresm2.1
  • Add information on longer test runs
  • Add information on build changes (AEROCOM)
  • Update main branch with info about the noresm2.1 branch
  • Write news item for noresm.org
  • Update README.md file in NorESM repo for noresm2.1?

NorESM2.3 documentation

  • Update general description of NorESM2.3
    • what is the purpose of NorESM2.3?
    • updates form NorESM2.1
    • major changes from NorESM2.0/CMIP6 version
  • Include release notes
  • Include description of test runs

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.