Welcome to NorESM documentation!¶
The purpose of the norESM documentation is to provide a common place for NorESM users and developers to share information. How is the code organised? What tools are you using? Which version should I run for what purpose? etc.
This documentation is being re-organized and a Github project has been created to follow the progress at https://github.com/NorESMhub/NorESM-docs/projects.
If you have any questions or interested in actively participate in the reorganization, create a new issue on github at https://github.com/NorESMhub/norESM-docs/issues
How to contribute¶
Information on how to contribute to this documentation can be found at https://github.com/NorESMhub/NorESM/blob/master/doc/README.md.
Content:
- Introduction
- Newbies guide to running NorESM
- Advanced configuration of NorESM1
- Advanced configuration of NorESM2
- Fluxes crossing boundaries
- CMIP6 volcanic forcing
- CMIP6 emissions of short-lived components
- Atmospheric output for some commonly used configurations of NorESM2
- Update of NorESM2 with CESM2.1.0
- Setting up CAM on your own linux PC
- Model Diagnostic Tools
- NorESM Diagnostic Packages
- Recent updates
- Using diag_run with cron
- Other tips
- NorESM diagnostics on GitHub
- Configuring a run with more aerosol diagnostics in (NorESM2)
- Fields produced in monthly average files when running with budgets activated
- Looking at the aerosol budgets (CAM-Oslo only)
- Making ncl plots of often used aerosol and cloud fields, including ERFs, for two model versions (CAM-Oslo only)
- Configuring a run with more cloud diagnostics in NorESM2
- Using the issue tracker
- Test list for NorESM
- Coding guidelines for HAMOCC
- Obtain a copy of the model (using git)
- Verify that you have the correct checkout
- Modify files
- Get modifications from github
- Send modifications to github
- If you don’t understand and want to get back to svn
- SVN - Best Practice/FAQ
- Branches
- What is a branch?
- When should I work on a branch?
- How should I name the branch?
- A note on branch / tag naming
- How and when should I merge from trunk to my branch?
- How can I merge my branch back into the trunk?
- What is a tag?
- When should I create a tag?
- What tags exist?
- How should I name the tag?
- Tagging noresm0 and noresm1 branches?
- Case 1
- Case 2
- Case 3
- What should be stated in the commit message?
- What should be stated in the copy message of a branch?
- What should be stated in the copy message of a tag?
- Subversion how-to for NorStore
- Uncertain parameters (which can be discussed) in the aerosol model
- NorStore Tape Storage
- NorStore Research Data Archive: Guidelines for ingestion of NorESM output
- Existing projects
- References