|
1 | 1 | # Simulation Systems |
2 | 2 |
|
3 | | -This repository contains documentation that is common across the many simulation and modelling codes owned by the Met Office. |
| 3 | +This repository contains documentation that is common across the many |
| 4 | +[simulation and modelling repositories](https://github.com/MetOffice/simulation-systems/wiki) |
| 5 | +owned by the Met Office. |
4 | 6 |
|
5 | | -To build this documentation from the top level of the project run: |
| 7 | +## Build the documentation |
| 8 | + |
| 9 | +A quick and clean way to get the package dependencies is via |
| 10 | +[uv](https://docs.astral.sh/uv/) package manager. |
| 11 | + |
| 12 | +Ps: Optional system dependencies for PDF generation may require LaTeX |
| 13 | +distributions and other third-party libraries. |
| 14 | + |
| 15 | +### using uv |
| 16 | + |
| 17 | +```shell |
| 18 | +git clone https://github.com/MetOffice/simulation-systems |
| 19 | +cd simulation-systems |
| 20 | + |
| 21 | +# Install dependencies (see pyproject.toml) in project .venv |
| 22 | +uv sync |
| 23 | +uv run make clean html |
| 24 | + |
| 25 | +# Verify documentation |
| 26 | +firefox build/html/index.html |
| 27 | +``` |
| 28 | + |
| 29 | +### using pip |
| 30 | + |
| 31 | +Alternatively, if your have Python-3.11 or higher installed (sphinx==8.2.3 |
| 32 | +requirement), you can install the dependencies in a virtual environment via pip, |
| 33 | +and build the documentation like: |
| 34 | + |
| 35 | +```shell |
| 36 | +cd simulation-systems |
| 37 | + |
| 38 | +</path/to/python3.11+> -m venv .venv |
| 39 | +source .venv/bin/activate |
| 40 | +pip install . |
| 41 | +make clean html |
6 | 42 | ``` |
| 43 | + |
| 44 | +### using conda |
| 45 | + |
| 46 | +```shell |
7 | 47 | conda env create -f env.yml |
8 | 48 | conda activate sphinx_doc_env |
9 | 49 | make clean html |
10 | 50 | firefox build/html/index.html |
11 | 51 | ``` |
12 | 52 |
|
13 | | -The documentation is written in sphinx markup. To develop changes to this |
| 53 | +## Contributing |
| 54 | + |
| 55 | +The documentation is written in sphinx markup. To develop changes to this |
14 | 56 | documentation first create an issue detailing the changes that are required. |
15 | 57 | Then create a branch in a clone of this repository, linking it to your issue and |
16 | | -regularly building your changes as described above. |
| 58 | +regularly building your changes as described above. |
17 | 59 |
|
18 | | -Once happy with your development create a pull request and request a review |
19 | | -from MetOffice/ssdteam. |
| 60 | +Once happy with your development create a pull request and request a review from |
| 61 | +[MetOffice/ssdteam](https://github.com/orgs/MetOffice/teams/ssdteam). |
0 commit comments