-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #82 from GreenBankObservatory/evan-devel
Baseline options, various documentation added
- Loading branch information
Showing
11 changed files
with
244 additions
and
69 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,11 @@ | ||
************* | ||
Git Workflows | ||
Git Workflows | ||
************* | ||
|
||
Branches | ||
======== | ||
|
||
The development team employs a GitFlow workflow with personal branching. This means that code in the `main` branch should always be in a releasable state. Developers should maintain their own development branches and commit changes to a `release-x.y.z` branch. When it's time to release, a dedicated team member will merge the `release-x.y.z` branch with the `main` branch and tag it accordingly. | ||
The development team employs a GitFlow workflow with personal branching. This means that code in the `main` branch should always be in a releasable state. Developers should maintain their own development branches and commit changes to a `release-x.y.z` branch. When it's time to release, a dedicated team member will merge the `release-x.y.z` branch with the `main` branch and tag it accordingly. | ||
|
||
.. mermaid:: | ||
|
||
|
@@ -40,4 +40,45 @@ The development team employs a GitFlow workflow with personal branching. This me | |
Releases | ||
======== | ||
|
||
Release branches will be locked once work on the next release begins. | ||
Release branches will be locked once work on the next release begins. | ||
|
||
Setting up your own development branch | ||
======== | ||
|
||
In the directory you want to work in, set up the repo: | ||
|
||
`$ git clone [email protected]:GreenBankObservatory/dysh.git` | ||
|
||
`$ cd dysh` | ||
|
||
`$ git checkout [branch-name]` | ||
|
||
with the [branch-name] replaced by the current release or other branch. Currently, this is "release-0.2.0". Then setup your own development branch with your first name followed by "-devel": | ||
|
||
`$ git checkout [name-devel]` | ||
|
||
Now make and activate a python virtual environment so your work doesn't impede or break other concurrent projects. Whenever you do some work, make sure you are in your own development branch. When you are ready to merge changes made by other developers into your own branch, | ||
|
||
`$ git checkout release-0.2.0` | ||
|
||
`$ git pull` | ||
|
||
`$ git checkout [name-devel]` | ||
|
||
`$ git merge release-0.2.0` | ||
|
||
When you are ready to commit changes, review what's been changed with | ||
|
||
`$ git status` | ||
|
||
and then add the intended files using | ||
|
||
`$ git add [path/to/changed/file]` | ||
|
||
check `dysh/.gitignore` to make sure you are not adding ignored files (virtual environment data, `_build/`, etc.). Then commit and push with | ||
|
||
`$ git commit -m "[this is my commit message]"` | ||
|
||
`$ git push` | ||
|
||
The first time you run this, it will give a command about setting the origin upstream. Simply copy and run that command. Users of GitHub Desktop can also achieve all of these above steps using the app interface. Next, go to the `dysh GitHub page <https://github.com/GreenBankObservatory/dysh/>`_ and submit a pull request. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
|
||
import matplotlib.pyplot as plt | ||
import numpy as np | ||
import astropy.units as u | ||
import copy | ||
|
||
|
||
from astropy.io import fits | ||
from astropy.utils.data import ( | ||
get_pkg_data_filename, | ||
get_pkg_data_filenames, | ||
) | ||
|
||
import dysh | ||
from dysh.fits import gbtfitsload | ||
|
||
|
||
dysh_root = pathlib.Path(dysh.__file__).parent.resolve() | ||
|
||
|
||
|
||
class test_specplot(): | ||
""" | ||
""" | ||
def test_default_plotter(): | ||
""" | ||
Just plot a default plot of a spectrum and visually inspect | ||
""" | ||
return 0 | ||
|
||
|
||
def test_complicated_plotter(): | ||
""" | ||
Plot a more complicated spectrum and visually inspect | ||
""" | ||
return 0 |
Oops, something went wrong.