Skip to content

Commit 971a0bb

Browse files
committed
fix config file of linkchecker, fix some dead links in docs
1 parent d712a52 commit 971a0bb

4 files changed

Lines changed: 17 additions & 41 deletions

File tree

.linkspector.yml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
dirs:
2+
- ./docs
3+
excludedDirs:
4+
- ./docs/notebooks
5+
- ./docs/overrides
16
ignorePatterns:
27
- pattern: "^http://localhost"
38
- pattern: "^https://doi.org/<replace-with-created-DOI>"
@@ -6,5 +11,4 @@ ignorePatterns:
611
- pattern: "^https://test.pypi.org"
712
- pattern: "^https://bestpractices.coreinfrastructure.org/projects/<replace-with-created-project-identifier>"
813
- pattern: "^https://readthedocs.org/dashboard/import.*"
9-
1014
useGitIgnore: true

docs/bmi.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ Basic Model Interface. For the model, we generated Matlab Compiler Runtime
77
executable file (only available for x86 Linux). This requires installation of
88
MCR. The other option is to use the Dockerized version of the executable,
99
available on
10-
[ghcr.io/ecoextreml/stemmus_scope](ghcr.io/ecoextreml/stemmus_scope). For more
10+
[https://ghcr.io/ecoextreml/stemmus_scope](https://ghcr.io/ecoextreml/stemmus_scope). For more
1111
information on each method, see the sections below.
1212

1313
## Installation and setup

docs/downloading_global_data.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -46,8 +46,9 @@ A simple example for the parsing of the data is in
4646

4747
## DEM data from Copernicus
4848

49-
A word doc for instructions is available
50-
[here](https://spacedata.copernicus.eu/documents/20123/121286/Copernicus+DEM+Open+HTTPS+Access.pdf/36c9adad-8488-f463-af43-573e68b7f481?t=1669283200177). A simple example for the parsing of the data is in
49+
DEM data is provided by Copernicus, see
50+
[here](https://dataspace.copernicus.eu/explore-data/data-collections/copernicus-contributing-missions/collections-description/COP-DEM).
51+
A simple example for the parsing of the data is in
5152
`global_data/data_analysis_notebooks/parse_dem.ipynb`.
5253

5354
## LAI from Climate Data Store (CDS)
@@ -58,4 +59,4 @@ data is in `global_data/data_analysis_notebooks/parse_LAI.py`.
5859

5960
## Land cover from Climate Data Store (CDS)
6061

61-
Land cover data is available at [https://cds.climate.copernicus.eu/cdsapp#!/dataset/satellite-land-cover?tab=overview](https://cds.climate.copernicus.eu/cdsapp#!/dataset/satellite-land-cover?tab=overview).
62+
Land cover data is available at [https://cds.climate.copernicus.eu/datasets/satellite-land-cover](https://cds.climate.copernicus.eu/datasets/satellite-land-cover).

docs/project_setup.md

Lines changed: 7 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -7,28 +7,14 @@ text when the development of the software package takes off.
77
For a quick reference on software development, we refer to [the software guide
88
checklist](https://guide.esciencecenter.nl/#/best_practices/checklist).
99

10-
## Python versions
11-
12-
This repository is set up with Python versions:
13-
14-
- 3.9
15-
- 3.10
16-
- 3.11
17-
18-
Add or remove Python versions based on project requirements. See [the
19-
guide](https://guide.esciencecenter.nl/#/best_practices/language_guides/python) for more information about Python
20-
versions.
21-
2210
## Package management and dependencies
2311

24-
You can use either pip or conda for installing dependencies and package management. This repository does not force you
25-
to use one or the other, as project requirements differ. For advice on what to use, please check [the relevant section
26-
of the
12+
You can use either pip or conda for installing dependencies (see
13+
`pyproject.toml`) and package management. This repository does not force you to
14+
use one or the other, as project requirements differ. For advice on what to use,
15+
please check [the relevant section of the
2716
guide](https://guide.esciencecenter.nl/#/best_practices/language_guides/python?id=dependencies-and-package-management).
2817

29-
- Runtime dependencies should be added to `setup.cfg` in the `install_requires` list under `[options]`.
30-
- Development dependencies should be added to `setup.cfg` in one of the lists under `[options.extras_require]`.
31-
3218
## Packaging/One command install
3319

3420
You can distribute your code using PyPI.
@@ -43,33 +29,18 @@ help you decide which tool to use for packaging.
4329
- The testing framework used is [PyTest](https://pytest.org)
4430
- [PyTest introduction](https://pythontest.com/pytest-book/)
4531
- PyTest is listed as a development dependency
46-
- This is configured in `setup.cfg`
32+
- This is configured in `pyproject.toml`
4733
- The project uses GitHub action workflows to automatically run tests on GitHub infrastructure against multiple Python versions
4834
- Workflows can be found in [`.github/workflows`](../.github/workflows/)
4935
- [Relevant section in the guide](https://guide.esciencecenter.nl/#/best_practices/language_guides/python?id=testing)
5036

5137
## Documentation
5238

53-
- Documentation should be put in the [`docs/`](../docs) directory. The contents have been generated using `sphinx-quickstart` (Sphinx version 1.6.5).
54-
- We recommend writing the documentation using Restructured Text (reST) and Google style docstrings.
55-
- [Restructured Text (reST) and Sphinx CheatSheet](https://thomas-cokelaer.info/tutorials/sphinx/rest_syntax.html)
56-
- [Google style docstring examples](http://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html).
57-
- The documentation is set up with the ReadTheDocs Sphinx theme.
58-
- Check out its [configuration options](https://sphinx-rtd-theme.readthedocs.io/en/latest/).
59-
- [AutoAPI](https://sphinx-autoapi.readthedocs.io/) is used to generate documentation for the package Python objects.
60-
- `.readthedocs.yaml` is the ReadTheDocs configuration file. When ReadTheDocs is building the documentation this package and its development dependencies are installed so the API reference can be rendered.
61-
- [Relevant section in the guide](https://guide.esciencecenter.nl/#/best_practices/language_guides/python?id=writingdocumentation)
39+
- Documentation should be put in the `docs/` directory.
6240

6341
## Coding style conventions and code quality
6442

65-
- [Relevant section in the NLeSC guide](https://guide.esciencecenter.nl/#/best_practices/language_guides/python?id=coding-style-conventions) and [README.dev.md](README.dev.md).
66-
67-
## Continuous code quality
68-
69-
[Sonarcloud](https://sonarcloud.io/) is used to perform quality analysis and code coverage report
70-
71-
- `sonar-project.properties` is the SonarCloud [configuration](https://docs.sonarqube.org/latest/analysis/analysis-parameters/) file
72-
- `.github/workflows/sonarcloud.yml` is the GitHub action workflow which performs the SonarCloud analysis
43+
- [Relevant section in the NLeSC guide](https://guide.esciencecenter.nl/#/best_practices/language_guides/python?id=coding-style-conventions).
7344

7445
## Package version number
7546

0 commit comments

Comments
 (0)