-
Notifications
You must be signed in to change notification settings - Fork 29
Improve contributing tutorial documentation #486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -47,6 +47,20 @@ SPRAS contributions: | |
| or `10 minutes to pandas | ||
| <https://pandas.pydata.org/pandas-docs/stable/user_guide/10min.html>`__ | ||
|
|
||
| Before getting started, verify your environment is ready with these | ||
| checks: | ||
|
|
||
| .. code:: bash | ||
|
|
||
| docker --version | ||
| docker run hello-world | ||
| docker login | ||
| conda --version | ||
| git --version | ||
| python -c "import spras; print('SPRAS import successful')" | ||
|
|
||
| If the commands above run without errors, your environment is ready. | ||
|
|
||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. should we also add a check to make sure SPRAS conda env is ready?
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. python -c "import spras; print('SPRAS import successful')" is what is in the spras tutorial. |
||
| ************************************************* | ||
| Step 0: Fork the repository and create a branch | ||
| ************************************************* | ||
|
|
@@ -202,8 +216,9 @@ and explore the nodes and interactome. | |
| .. code:: python | ||
|
|
||
| > from spras.dataset import Dataset | ||
| > dataset_dict = {'label': 'data0', 'node_files': ['node-prizes.txt', 'sources.txt', 'targets.txt'], 'edge_files': ['network.txt'], 'other_files': [], 'data_dir': 'input'} | ||
| > data = Dataset(dataset_dict) | ||
| > from spras.config.dataset import DatasetSchema | ||
| > dataset_schema = DatasetSchema(label='data0', node_files=['node-prizes.txt', 'sources.txt', 'targets.txt'], edge_files=['network.txt'], other_files=[], data_dir='input') | ||
| > data = Dataset(dataset_schema) | ||
| > data.node_table.head() | ||
| NODEID prize active sources targets | ||
| 0 C 5.7 True NaN True | ||
|
|
@@ -331,6 +346,13 @@ its contents before rerunning the Snakemake command. | |
| Step 5: Add Local Neighborhood to the tests | ||
| ********************************************* | ||
|
|
||
| .. note:: | ||
|
|
||
| These tests modify files in ``.github/workflows/``. If you push over | ||
| HTTPS using a Personal Access Token, make sure the token has | ||
| permission to modify GitHub Actions workflows. Otherwise, GitHub may | ||
| reject the push. SSH push works without this restriction. | ||
|
|
||
| Add test functions to the test file ``test/test_ln.py``. This file | ||
| already has existing tests to test the correctness of the Local | ||
| Neighborhood implementation that was added to the Docker image. The new | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we want to have these checks, should we also add the expected output? The specific output will be different depending on what each contributor has installed, but I think we should give some guidance about how someone can tell if everything is ready or not. Maybe the signal is that they don't get errors?