@@ -28,11 +28,12 @@ Overview
28
28
* Each tutorial should have 3–5 explicit `Learning Goals
29
29
<http://tll.mit.edu/help/intended-learning-outcomes> `_, demonstrate ~2–3
30
30
pieces of functionality relevant to astronomy, and 2–3 demonstrations of
31
- generic but commonly used functionality (e.g., numpy, matplotlib)
31
+ generic but commonly used functionality (e.g., `` numpy ``, `` matplotlib `` )
32
32
* Roughly follow this progression:
33
- * *Intput/Output *: read in some data (use `astroquery
34
- <https://astroquery.readthedocs.io/en/latest/> `_ where possible
35
- * *Analysis *: do something insightful/useful with the data
33
+ * *Input/Output *: read in some data (use `astroquery
34
+ <https://astroquery.readthedocs.io/en/latest/> `_ where possible to query
35
+ real astronomical datasets)
36
+ * *Analysis *: do something insightful / useful with the data
36
37
* *Visualization *: make a pretty figure (use `astropy.visualization
37
38
<http://docs.astropy.org/en/stable/visualization/> `_ where possible)
38
39
* The tutorials must be compatible with the versions supported by the last major
@@ -72,9 +73,9 @@ Narrative
72
73
formatting, links, latex, and code snippets.
73
74
* Title should be short yet descriptive and emphasize the learning goals of the
74
75
tutorial. Try to make the title appeal to a broad audience and avoid
75
- referencing a specefic instrument, catalog, or anything wavelength dependent.
76
- * List all author's full names (comma separated) and link to github profile
77
- and/or `ORCID iD <https://orcid.org/ >`_.
76
+ referencing a specific instrument, catalog, or anything wavelength dependent.
77
+ * List all author's full names (comma separated) and link to GitHub profile
78
+ and/or `ORCID iD <https://orcid.org/ >`_ when relevant .
78
79
* Include `Learning Goals <http://tll.mit.edu/help/intended-learning-outcomes >`_
79
80
at the top as a bulleted list.
80
81
* Include Keywords as a comma separated list of topics, packages, and functions
@@ -97,22 +98,23 @@ Template intro
97
98
98
99
.. code-block :: none
99
100
100
- # Doing a thing with things
101
+ # Title name
101
102
102
103
## Authors
103
104
Jane Smith, Jose Jones
104
105
105
- ## Leaning Goals
106
- - Query..
107
- - Calculate..
108
- - Display..
106
+ ## Learning Goals
107
+ * Query the ... dataset
108
+ * Calculate . ..
109
+ * Display . ..
109
110
110
111
## Keywords
111
112
Example, example, example
112
113
113
114
## Companion Content
114
115
Carroll & Ostlie 10.3, Binney & Tremaine 1.5
115
116
117
+ ## Summary
116
118
In this tutorial, we download a data file, do something to it, and then
117
119
visualize it.
118
120
@@ -126,7 +128,7 @@ concepts `branch, push, pull request <https://help.github.com/articles/proposing
126
128
127
129
To contribute a new tutorial, first fork the ``astropy-tutorials `` repository.
128
130
Then, clone your fork locally to your machine (replace <GITHUB USERNAME> with
129
- your github username)::
131
+ your GitHub username)::
130
132
131
133
git clone [email protected] :<GITHUB USERNAME>/astropy-tutorials.git
132
134
@@ -148,8 +150,8 @@ notebook file itself -- should go in this directory.
148
150
149
151
Specify the python packages the tutorial depends on by creating a text file
150
152
called ``requirements.txt `` in the same notebook directory. For example, if your
151
- tutorial requires scipy version 1.0 and numpy version 1.13 or greater, your
152
- ``requirements.txt `` file would look like:
153
+ tutorial requires `` scipy `` version 1.0 and `` numpy `` version 1.13 or greater,
154
+ your ``requirements.txt `` file would look like:
153
155
154
156
.. code-block :: none
155
157
@@ -158,15 +160,15 @@ tutorial requires scipy version 1.0 and numpy version 1.13 or greater, your
158
160
159
161
To see an example, have a look at the FITS-header `requirements.txt file <https:
160
162
//github.com/astropy/astropy-tutorials/blob/master/tutorials/notebooks/FITS-head
161
- er/requirements.json > `_.
163
+ er/requirements.txt > `_.
162
164
163
165
Push the notebook and other files from your local branch up to your fork of the
164
166
repository on GitHub (by default, named 'origin')::
165
167
166
168
git push origin Spectral-Line-Fitting
167
169
168
170
When the tutorial is ready for broader community feedback, `open a pull request
169
- <https://help.github.com/articles/creating-a-pull-request/> `_against the main
171
+ <https://help.github.com/articles/creating-a-pull-request/> `_ against the main
170
172
``astropy-tutorials `` repository in order for the community to review the new
171
173
tutorial.
172
174
0 commit comments