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
This is the release commit of GCPy 1.6.0. Please see the CHANGELOG.md
for a list of updaes. Documentation for GCPy 1.6.0 is now available
at gcpy.readthedocs.io.
Signed-off-by: Bob Yantosca <yantosca@seas.harvard.edu>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+36-2Lines changed: 36 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,42 @@ All notable changes to GCPy will be documented in this file.
4
4
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
6
6
7
-
## [Unreleased] - TBD
7
+
## [1.6.0] - 2025-01-29
8
+
### Added
9
+
- Added example script `gcpy/examples/hemco/make_hemco_sa_spec.py` (creates the HEMCO standalone configuration file `HEMCO_sa_Spec.rc`)
10
+
- Added module `benchmark_gcclassic_stats.py` for scraping statistics from GEOS-Chem Classic cloud benchmarks
Thank you for looking into contributing to GCPy! GEOS-Chem is a grass-roots model that relies on contributions from community members like you. Whether you're new to GEOS-Chem or a longtime user, you're a valued member of the community, and we want you to feel empowered to contribute.
3
+
Thank you for looking into contributing to GCPy! GCPy is a grass-roots package that relies on contributions from community members like you. Whether you're new to GCPy or a longtime user, you're a valued member of the community, and we want you to feel empowered to contribute.
4
4
5
5
## We use GitHub and ReadTheDocs
6
+
6
7
We use GitHub to host the GCPy source code, to track issues, user questions, and feature requests, and to accept pull requests: [https://github.com/geoschem/gcpy](https://github.com/geoschem/gcpy). Please help out as you can in response to issues and user questions.
7
8
8
9
GCPy documentation can be found at [gcpy.readthedocs.io](https://gcpy.readthedocs.io).
9
10
10
11
## When should I submit updates?
11
12
12
-
Submit bug fixes right away, as these will be given the highest priority. Please see "Support Guidelines" for more information.
13
+
Submit bug fixes right away, as these will be given the highest priority. Please see **[Support Guidelines](https://gcpy.readthedocs.io/en/stable/reference/SUPPORT.html)** for more information.
13
14
14
15
The practical aspects of submitting code updates are listed below.
15
16
16
17
## How can I submit updates?
17
-
We use [GitHub Flow](https://guides.github.com/introduction/flow/index.html), so all changes happen through pull requests. This workflow is [described here](https://guides.github.com/introduction/flow/index.html).
18
+
19
+
We use **GitHub Flow**, so all changes happen through [pull requests](https://help.github.com/articles/creating-a-pull-request/). This workflow is [described here](https://docs.github.com/en/get-started/using-github/github-flow).
18
20
19
21
As the author you are responsible for:
20
22
- Testing your changes
@@ -25,28 +27,35 @@ As the author you are responsible for:
25
27
26
28
1. Create or log into your [GitHub](https://github.com/) account.
27
29
2.[Fork the GCPy repository](https://help.github.com/articles/fork-a-repo/) into your Github account.
28
-
5. Clone your fork of the GCPy repositories to your computer system.
29
-
6. Add your modifications into a [new branch](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell) off the **main** branch.
30
-
7. Test your update thoroughly and make sure that it works.
31
-
8. Review the coding conventions and checklists for code and data updates listed below.
32
-
9. Create a [pull request in GitHub](https://help.github.com/articles/creating-a-pull-request/).
33
-
10. The [GEOS-Chem Support Team](https://wiki.geos-chem.org/GEOS-Chem_Support_Team) will add your updates into the development branch for an upcoming GCPy version.
34
-
11. If the benchmark simulations reveal a problem with your update, the GCST will request that you take further corrective action.
30
+
3. Clone your fork of the GCPy repositories to your computer system.
31
+
4. Add your modifications into a [new branch](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell) off the **main** branch.
32
+
5. Add a sentence to the `CHANGELOG.md` file describing your update.
33
+
6. Test your update thoroughly and make sure that it works.
34
+
7. Review the coding conventions and checklists for code and data updates listed below.
35
+
8. Create a [pull request in GitHub](https://help.github.com/articles/creating-a-pull-request/).
36
+
9. The [GEOS-Chem Support Team](https://wiki.geos-chem.org/GEOS-Chem_Support_Team) will add your updates into the development branch for an upcoming GCPy version.
37
+
10. If the benchmark simulations reveal a problem with your update, the GCST will request that you take further corrective action.
35
38
36
39
### Coding conventions
37
-
GCPy includes contributions from many people and multiple organizations. Therefore, some inconsistent conventions are inevitable, but we ask that you do your best to be consistent with nearby code.
40
+
41
+
We recommend that GCPy developers adhere to the [PEP-8 Python style guide](https://peps.python.org/pep-0008/). You can run `pylint` on all source code files that you modify to ensure adherence to PEP-8 style conventions.
38
42
39
43
### Checklist for submitting code updates
40
44
41
45
1. Include thorough comments in all submitted code.
42
46
2. Include full citations for references at the top of relevant source code modules.
43
47
3. Remove extraneous code updates (e.g. testing options, other science).
48
+
4. Check that you have updated the `CHANGELOG.md` file.
49
+
5. Run `pylint` on each source code file that you have modified to check for bugs and conformance to the PEP-8 style conventions.
44
50
45
51
## How can I request a new feature?
52
+
46
53
We accept feature requests through issues on GitHub. To request a new feature, **[open a new issue](https://github.com/geoschem/gcpy/issues/new/choose)** and select the feature request template. Please include all the information that migth be relevant, including the motivation for the feature.
47
54
48
55
## How can I report a bug?
56
+
49
57
Please see **[Support Guidelines](https://gcpy.readthedocs.io/en/stable/reference/SUPPORT.html)**.
50
58
51
59
## Where can I ask for help?
60
+
52
61
Please see **[Support Guidelines](https://gcpy.readthedocs.io/en/stable/reference/SUPPORT.html)**
0 commit comments