Skip to content

Commit c66ba58

Browse files
authored
Merge pull request #1049 from aphearin/docs_v08
Docs v08
2 parents 1b95a85 + 958bdbf commit c66ba58

File tree

5 files changed

+51
-54
lines changed

5 files changed

+51
-54
lines changed

.github/workflows/wheels.yml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,10 @@
11
name: Build wheels
22

3-
on: [push, pull_request]
3+
on:
4+
workflow_dispatch:
5+
release:
6+
types:
7+
- published
48

59
jobs:
610
build_wheels:

CHANGES.rst

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,9 @@
1-
0.9 (2022-9-14)
1+
0.8 (unreleased)
22
----------------
33

4-
- No changes yet
4+
- Change packaging tools to pyproject.toml
55

6-
7-
0.8 (2022-9-14)
8-
----------------
6+
- Drop dependency on astropy-helpers
97

108
- Add new calculator for uber_hostid quantity
119

README.rst

Lines changed: 31 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -12,18 +12,24 @@ The core feature of Halotools is a modular platform for creating mock universes
1212

1313
The code is publicly available at https://github.com/astropy/halotools.
1414

15-
Documentation
15+
Installation
1616
-------------
17-
The latest build of the documentation can be found at http://halotools.readthedocs.io. The documentation includes installation instructions, quickstart guides and step-by-step tutorials. The *Basic features* section below gives an overview of the primary functionality of the package.
17+
The simplest way to install the latest release of the code is with conda-forge::
1818

19+
conda install -c conda-forge halotools
1920

20-
Installation
21-
-------------
21+
Or alternatively, you can install using pip::
22+
23+
pip install halotools
2224

2325
You can find detailed installation instructions
2426
in the **Package Installation** section of http://halotools.readthedocs.io. After installing the package, you should navigate to the *Quickstart Guides and Tutorials* section and follow the *Getting started with Halotools* 10-minute tutorial. This will get you set up with the default halo catalog so that you can quickly get started with creating mock galaxy populations.
2527

2628

29+
Documentation
30+
-------------
31+
The latest build of the documentation can be found at http://halotools.readthedocs.io. The documentation includes installation instructions, quickstart guides and step-by-step tutorials. The *Basic features* section below gives an overview of the primary functionality of the package.
32+
2733

2834
Basic features
2935
--------------
@@ -107,7 +113,7 @@ Although the **sim_manager** provides an object-oriented framework for creating
107113
Project status
108114
--------------
109115

110-
Halotools is a fully open-source package with contributing scientists spread across many universities. The latest stable release of the package, v0.7, is now available on pip and conda-forge. You can also install the development version of the package by cloning the master branch on GitHub and locally building the source code, as described in the installation instructions.
116+
Halotools is a fully open-source package with contributing scientists spread across many universities. The latest stable release of the package, v0.8, is now available on pip and conda-forge. You can also install the development version of the package by cloning the master branch on GitHub and locally building the source code, as described in the installation instructions.
111117

112118

113119
## Asking questions and staying up-to-date
@@ -117,8 +123,26 @@ You can contact Andrew Hearin directly by email at ahearin-at-anl-dot-gov, or by
117123

118124
Citing Halotools
119125
----------------
120-
If you use Halotools modules to support your science publication, we ask that you cite the code-release paper, http://arxiv.org/abs/1606.04106 paper, ideally taking note of the version of the code you used, e.g., v0.7. Depending on what modules you use, other citations may also be appropriate; see the **License and Citation Information** section of http://halotools.readthedocs.io for further information about how to properly cite Halotools and its supporting science and software.
121-
126+
If you use Halotools modules to support your science publication, please cite `Hearin et al. (2017) <https://arxiv.org/abs/1606.04106>`_, ideally taking note of the version of the code you used, e.g., v0.8::
127+
128+
@ARTICLE{halotools,
129+
author = {{Hearin}, Andrew P. and {Campbell}, Duncan and {Tollerud}, Erik and {Behroozi}, Peter and {Diemer}, Benedikt and {Goldbaum}, Nathan J. and {Jennings}, Elise and {Leauthaud}, Alexie and {Mao}, Yao-Yuan and {More}, Surhud and {Parejko}, John and {Sinha}, Manodeep and {Sip{\"o}cz}, Brigitta and {Zentner}, Andrew},
130+
title = "{Forward Modeling of Large-scale Structure: An Open-source Approach with Halotools}",
131+
journal = {The Astronomical Journal},
132+
keywords = {cosmology: theory, galaxies: halos, galaxies: statistics, large-scale structure of universe, Astrophysics - Instrumentation and Methods for Astrophysics, Astrophysics - Cosmology and Nongalactic Astrophysics, Astrophysics - Astrophysics of Galaxies},
133+
year = 2017,
134+
month = nov,
135+
volume = {154},
136+
number = {5},
137+
eid = {190},
138+
pages = {190},
139+
doi = {10.3847/1538-3881/aa859f},
140+
archivePrefix = {arXiv},
141+
eprint = {1606.04106},
142+
primaryClass = {astro-ph.IM},
143+
adsurl = {https://ui.adsabs.harvard.edu/abs/2017AJ....154..190H},
144+
adsnote = {Provided by the SAO/NASA Astrophysics Data System}
145+
}
122146

123147
License
124148
-------

docs/install.rst

Lines changed: 8 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,12 @@ Package Installation
77
To install Halotools, you can use conda-forge, pip, or clone the repo from GitHub and build the source code.
88
Either way, be sure to read the :ref:`halotools_dependencies` section prior to installation.
99

10-
Using pip
11-
====================
10+
Using conda-forge and pip
11+
=========================
1212

1313
The simplest way to install the latest release of the code is with conda-forge.
1414
If you will be :ref:`installing_halotools_with_virtualenv`, activate the environment before installing::
1515

16-
1716
conda install -c conda-forge halotools
1817

1918
Alternatively, you can install using pip::
@@ -65,7 +64,7 @@ All official releases of the code are tagged with their version name, e.g., v0.7
6564
To install a particular release::
6665

6766
git checkout v0.7
68-
python setup.py install
67+
pip install .
6968

7069
This will install the v0.7 release of the code. Other official release versions (e.g., v0.5) can be installed similarly.
7170

@@ -75,7 +74,7 @@ Installing the most recent master branch
7574
If you prefer to use the most recent version of the code::
7675

7776
git checkout master
78-
python setup.py install
77+
pip install .
7978

8079
This will install the master branch of the code that is currently under development. While the features in the official releases have a stable API, new features being developed in the master branch may not. However, the master branch may have new features and/or performance enhancements that you may wish to use for your science application. A concerted effort is made to ensure that only thoroughly tested and documented code appears in the public master branch, though Halotools users should be aware of the distinction between the bleeding edge version in master and the official release version available through pip.
8180

@@ -110,28 +109,26 @@ Dependencies
110109

111110
If you install halotools using conda or pip, then most of your dependencies will be handled for you automatically. The only additional dependency you may need is:
112111

113-
- `h5py <http://h5py.org/>`_: 2.5 or later
112+
- `h5py <http://h5py.org/>`_: 3.7 or later
114113

115114
The h5py package is used for fast I/O of large simulated datasets.
116115

117116
If you did not use conda or pip, then you should be aware of the following strict requirements:
118117

119-
- `Python <http://www.python.org/>`_: 3.7.x
118+
- `Python <http://www.python.org/>`_: 3.9.x
120119

121120
- `Numpy <http://www.numpy.org/>`_: 1.9 or later
122121

123122
- `Scipy <http://www.scipy.org/>`_: 0.15 or later
124123

125-
- `Cython <http://www.cython.org/>`_: 0.23 or later
124+
- `Cython <http://www.cython.org/>`_: 0.29.32 or later
126125

127-
- `Astropy`_: 4.0 or later
126+
- `Astropy`_: 5.0 or later
128127

129128
- `BeautifulSoup <http://www.crummy.com/software/BeautifulSoup/>`_: For crawling the web for halo catalogs.
130129

131130
- `Requests <http://docs.python-requests.org/en/latest/>`_: Also for crawling the web for halo catalogs.
132131

133-
- `h5py <http://h5py.org/>`_: 2.5 or later
134-
135132
Any of the above can be installed with either pip or conda.
136133

137134
.. _verifying_your_installation:

docs/quickstart_and_tutorials/development/getting_started.rst

Lines changed: 4 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -11,39 +11,13 @@ Then install the dependencies listed on the :ref:`step_by_step_install` page.
1111
Code
1212
====
1313

14-
Halotools contains a compiled component. To compile all cython (``.pyx``) files inplace run, ::
15-
16-
python3 setup.py build_ext --inplace
17-
18-
If you modify a ``.pyx`` file use the same command to recompile it. Subsequent runs will only compile files whose source has changed and so will be much quicker.
19-
20-
Halotools also has comprehensive unit tests and uses pytest. To run all tests, assuming you are in the base of the repository, first change directory into ``halotools`` and then run ``pytest``. ::
21-
22-
cd halotools
23-
pytest
24-
25-
If you have made a change and only want to run a subset of tests run, ::
26-
27-
pytest -k tests_matching_this_string_will_run
28-
29-
Run ``pytest --help`` for a full list of options.
14+
Halotools testing is handled with tox::
3015

16+
tox -e test
3117

3218
Docs
3319
====
3420

35-
First ensure that the halotools package and sphinx are installed. From the base of the repository run, ::
36-
37-
pip3 install -e .
38-
pip3 install sphinx==1.3.1 # see docs/conf.py for the sphinx version
39-
40-
Then build documentation with, ::
41-
42-
cd docs
43-
make html
44-
45-
You can see the built documentation in ``docs/_build/html/``. The easiest way to view it in your browser is to spin up a local server. One way to do this is to run, from the built directory, ::
46-
47-
python3 -m http.server
21+
Then build documentation with tox, ::
4822

49-
The docs should then be viewable at ``localhost:8000`` (the port will be logged when you start the server).
23+
tox -e build_docs

0 commit comments

Comments
 (0)