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: CONTRIBUTING.md
+21-29
Original file line number
Diff line number
Diff line change
@@ -2,35 +2,29 @@
2
2
3
3
Welcome to the ``gReLU`` contributor's guide.
4
4
5
-
This document focuses on getting any potential contributor familiarized with the development processes,
6
-
but [other kinds of contributions](https://opensource.guide/how-to-contribute) are also appreciated.
5
+
This document focuses on getting any potential contributor familiarized with the development processes, but [other kinds of contributions](https://opensource.guide/how-to-contribute) are also appreciated.
7
6
8
7
If you are new to using git or have never collaborated in a project previously, please have a look at
9
8
[contribution-guide.org](https://www.contribution-guide.org/). Other resources are also listed in the
10
9
excellent [guide created by FreeCodeCamp](https://github.com/FreeCodeCamp/how-to-contribute).
11
10
12
11
Please notice, all users and contributors are expected to be **open, considerate, reasonable, and
13
-
respectful**. When in doubt, [Python Software Foundation's Code of Conduct](https://www.python.org/psf/conduct/)
14
-
is a good reference in terms of behavior guidelines.
12
+
respectful**. When in doubt, [Python Software Foundation's Code of Conduct](https://www.python.org/psf/conduct/) is a good reference in terms of behavior guidelines.
15
13
16
14
## Issue Reports
17
15
18
16
If you experience bugs or general issues with ``gReLU``, please have a look at the
19
-
[issue tracker](https://github.com/Genentech/gReLU/issues). If you don't see anything useful there, please
20
-
file a new issue report.
17
+
[issue tracker](https://github.com/Genentech/gReLU/issues). If you don't see anything useful there, please file a new issue report.
21
18
22
-
(Don't forget to include the closed issues in your search. Sometimes a solution was already reported, and
23
-
the problem is considered solved.)
19
+
(Don't forget to include the closed issues in your search. Sometimes a solution was already reported, and the problem is considered solved.)
24
20
25
21
You can file a new issue by clicking the "New issue" button at the top right of the issue tracker.
26
22

27
23
28
24
Your new issue report should include the following information:
29
25
30
26
1. Information about your programming environment (e.g., operating system, Python version)
31
-
2. Steps to reproduce the problem. Please try to simplify the reproduction steps to a very minimal example
32
-
that still illustrates the problem you are facing. By removing other factors, you help us to identify the
33
-
root cause of the issue.
27
+
2. Steps to reproduce the problem. Please try to simplify the reproduction steps to a very minimal example that still illustrates the problem you are facing. By removing other factors, you help us to identify the root cause of the issue.
34
28
4. The full error message that you encountered, if any.
35
29
5. Any steps that you took to diagnose or fix the issue, and their outcomes.
36
30
6. Any suggestions for resolving the issue.
@@ -40,33 +34,25 @@ root cause of the issue.
40
34
41
35
### Coding resources
42
36
43
-
``gReLU`` uses pytorch and pytorch-lightning. The below tutorials are good starting points to become familiar
44
-
with these frameworks:
37
+
``gReLU`` uses pytorch and pytorch-lightning. The below tutorials are good starting points to become familiar with these frameworks:
We welcome external contributions to ``gReLU``. Before planning changes to the code, we suggest carefully
53
-
examining the current structure and organization of the package.
45
+
We welcome external contributions to ``gReLU``. Before planning changes to the code, we suggest carefully examining the current structure and organization of the package.
54
46
55
-
The [API reference](https://genentech.github.io/gReLU/autoapi/index.html) lists all the modules and submodules
56
-
available in gReLU. Clicking on individual modules on this list will reveal a description of the module and
57
-
what kinds of functions it is meant to contain. The descriptions also contain more detailed explanations of the
58
-
expected structure of each module and how to contribute to it. This will help you find the appropriate location
59
-
to make changes.
47
+
The [API reference](https://genentech.github.io/gReLU/autoapi/index.html) lists all the modules and submodules available in gReLU. Clicking on individual modules on this list will reveal a description of the module and what kinds of functions it is meant to contain. The descriptions also contain more detailed explanations of the expected structure of each module. This will help you find the appropriate location to make changes.
60
48
61
-
For instance, the table below lists some different types of functionality that contributors may want to add
62
-
or change, and the corresponding module / submodule of ``gReLU``. Click on the name of a module for more details
63
-
on its structure.
49
+
For instance, the table below lists some different types of functionality that contributors may want to add or change, and the corresponding module / submodule of ``gReLU``. Click on the name of a module for more details on its structure.
64
50
65
51
| Functionality | Module |
66
52
| ---------------- | ------- |
67
53
| Functions to read / write genomic data |[`grelu.io`](https://genentech.github.io/gReLU/autoapi/grelu/io/index.html)|
68
54
| Functions to preprocess genomic data after it is loaded |[`grelu.data.preprocess`](https://genentech.github.io/gReLU/autoapi/grelu/data/preprocess/index.html)|
69
-
| New augmentation functions for training models|[`grelu.data.augment`](https://genentech.github.io/gReLU/autoapi/grelu/data/augment/index.html)|
55
+
| New data augmentation methods|[`grelu.data.augment`](https://genentech.github.io/gReLU/autoapi/grelu/data/augment/index.html)|
70
56
| Functions to introduce various types of in silico mutations into DNA sequences |[`grelu.sequence.mutate`](https://genentech.github.io/gReLU/autoapi/grelu/sequence/mutate/index.html)|
71
57
| Other functions to manipulate DNA sequences |[`grelu.sequence.utils`](https://genentech.github.io/gReLU/autoapi/grelu/sequence/utils/index.html)|
72
58
| Functions to score DNA sequences based on their content |[`grelu.transforms.seq_transforms`](https://genentech.github.io/gReLU/autoapi/grelu/transforms/seq_transforms/index.html)|
@@ -76,9 +62,12 @@ on its structure.
76
62
| New loss functions |[`grelu.lightning.losses`](https://genentech.github.io/gReLU/autoapi/grelu/lightning/losses/index.html)|
77
63
| New metrics to calculate model performance |[`grelu.lightning.metrics`](https://genentech.github.io/gReLU/autoapi/grelu/lightning/metrics/index.html)|
78
64
| New plots and visualizations |[`grelu.visualize`](https://genentech.github.io/gReLU/autoapi/grelu/visualize/index.html)|
65
+
| Unit tests for new functions |[`tests`](https://github.com/Genentech/gReLU/tree/main/tests)|
79
66
80
-
For complex changes that may not fit clearly within the established package structure, it is important to first
81
-
raise an issue (see instructions below).
67
+
Two ex
68
+
69
+
70
+
For complex changes that may not fit clearly within the established package structure, it is important to first raise an issue (see instructions below).
82
71
83
72
84
73
## Step-by-step instructions to contribute new code
@@ -92,8 +81,7 @@ This often provides additional considerations and avoids unnecessary work.
92
81
### Create an environment
93
82
94
83
Before you start coding, we recommend creating an isolated [virtual
95
-
environment](https://realpython.com/python-virtual-environments-a-primer/) to avoid any problems with your
96
-
installed Python packages. This can easily be done via either [virtualenv](https://virtualenv.pypa.io/en/stable/):
84
+
environment](https://realpython.com/python-virtual-environments-a-primer/) to avoid any problems with your installed Python packages. This can easily be done via either [virtualenv](https://virtualenv.pypa.io/en/stable/):
97
85
```
98
86
virtualenv <PATH TO VENV>
99
87
source <PATH TO VENV>/bin/activate
@@ -142,7 +130,7 @@ or [Miniconda](https://docs.conda.io/en/latest/miniconda.html):
142
130
143
131
3. If you change or add any functions, modules and classes, don't forget to update or add docstrings to describe these changes.
144
132
145
-
4. If your contribution adds an additional feature and is not just a bugfix, we suggest also adding unit tests.
133
+
4. If your contribution adds an additional feature and is not just a bugfix, we suggest also adding unit tests in https://github.com/Genentech/gReLU/tree/main/tests.
146
134
147
135
5. Add yourself to the list of contributors in ``AUTHORS.rst``.
148
136
@@ -246,3 +234,7 @@ the following steps can be used to release a new version for ``grelu``:
246
234
500KB), unwanted clutter may have been accidentally included.
247
235
6. Run ``tox -e publish -- --repository pypi`` and check that everything was
248
236
uploaded to PyPI_ correctly.
237
+
238
+
## Contributing to the model zoo
239
+
240
+
gReLU's [model zoo](https://wandb.ai/grelu) is intended to host a curated set of models which are likely to be broadly useful to many users of the package. If you would like to contribute such a model, please let us know via a GitHub issue (see instructions above). Note that it is not necessary to contribute a model to the zoo in order to share it with the community, as gReLU saves checkpoint files that contain exhaustive metadata and can be easily shared and reused.
0 commit comments