@@ -36,8 +36,10 @@ so it is important to define the scope of the website.
36
36
In general, ** the PyAOS website provides information on Python packages and training resources that are unique
37
37
to the atmosphere and ocean sciences and of interest to physical data scientists.**
38
38
The focus is on packages and resources that are under active development and/or maintenance,
39
- have a non-trivial user-base (i.e. more users than just the author/s) and
40
- are for a general audience.
39
+ have a non-trivial user-base (i.e. more users than just the author/s),
40
+ offer somewhat unique functionality
41
+ (i.e. rather than simply coordinating the execution of functionality from other packages)
42
+ and are for a general audience.
41
43
42
44
Following that definition, here are some examples of things that would be out of scope:
43
45
* Unidata's [ cftime] ( https://unidata.github.io/cftime/ ) package:
@@ -58,6 +60,10 @@ In other words, this package isn't for a general audience.
58
60
* The [ GeoPandas] ( https://geopandas.org/ ) package: While this is a great package for working with geospatial vector data,
59
61
it is of interest to the much broader field of geospatial data science.
60
62
In other words, it isn't unique (or even predominantly used by or supported by) the PyAOS community.
63
+ * The [ PCMDI Metrics Package] ( http://pcmdi.github.io/pcmdi_metrics/index.html ) or [ ESMValTool] ( https://docs.esmvaltool.org/en/latest/ ) .
64
+ Model evaluation/diagnostics packages like these tend to coordinate the execution of many existing packages
65
+ (e.g. that calculate climate indices) rather than offering unique funcionality.
66
+
61
67
62
68
If you're unsure whether a particular Python package or training resource is within scope,
63
69
feel free to [ open an issue] ( https://github.com/PyAOS/pyaos.github.io/issues )
0 commit comments