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
Copy file name to clipboardExpand all lines: README.md
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,8 @@ This is the development branch for version 2 of ESMValTool. To get started devel
15
15
16
16
### Getting started
17
17
To install in development mode, follow these instructions.
18
+
- Install gcc, g++ and gfortran if these are not available on your system. On Debian based systems, this can be done by
19
+
running `apt install build-essential gfortran`.
18
20
-[Download and install conda](https://conda.io/docs/user-guide/install/linux.html) (this should be done even if the system in use already has a preinstalled version of conda, as problems have been reported with NCL when using such a version)
19
21
- If using (t)csh shell, do not prepend the installation path (`<prefix>`) to the environment variable PATH (as recommended by the installation procedure), but add `source <prefix>/etc/profile.d/conda.csh` to the `.cshrc`/`.tcshrc` file instead
20
22
- Update conda: `conda update -y conda`
@@ -31,6 +33,10 @@ To install in development mode, follow these instructions.
31
33
32
34
### Anaconda Package
33
35
The Anaconda packages can be found on [ESMValGroup Anaconda Channel.](https://anaconda.org/ESMValGroup)
36
+
37
+
First install gcc, g++ and gfortran if these are not available on your system. On Debian based systems, this can be done by
38
+
running `apt install build-essential gfortran`.
39
+
34
40
If you already installed Anaconda, you can install ESMValTool by running:
Copy file name to clipboardExpand all lines: doc/sphinx/source/developer_guide2/git_repository.inc
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
.. _git_repository:
2
2
3
+
**************
3
4
Git repository
4
5
**************
5
6
@@ -161,7 +162,7 @@ Do-s
161
162
* Comment your code as much as possible and in English.
162
163
* Use short but self-explanatory variable names (e.g., model_input and reference_input instead of xm and xr).
163
164
* Consider a modular/functional programming style. This often makes code easier to read and deletes intermediate variables immediately. If possible, separate diagnostic calculations from plotting routines.
164
-
* Consider reusing or extending existing code. General-purpose code can be found in diag_scripts/lib/ and in plot_scripts/.
165
+
* Consider reusing or extending existing code. General-purpose code can be found in esmvaltool/diag_scripts/shared/.
165
166
* Comment all switches and parameters including a list of all possible settings/options in the header section of your code (see also Section :ref:`std_diag`).
166
167
* Use templates for recipes (Section :ref:`std_recipe`) and diagnostics (Section :ref:`std_diag`) to help with proper documentation.
167
168
* Keep your *FEATURE BRANCH* regularly synchronized with the *DEVELOPMENT BRANCH* (git merge).
@@ -174,5 +175,5 @@ Don't-s
174
175
* Do not develop without proper version control (see do-s above).
175
176
* Avoid large (memory, disk space) intermediate results. Delete intermediate files/variables or see modular/functional programming style.
176
177
* Do not use hard-coded pathnames or filenames.
177
-
* Do not mix developments / modifications of the ESMValTool framework and developments / modifications of diagnotics in the same *FEATURE BRANCH*.
178
+
* Do not mix developments / modifications of the ESMValTool framework and developments / modifications of diagnostics in the same *FEATURE BRANCH*.
0 commit comments