This package provides a Jupyter notebook for reducing CCD data.
Documentation is at: https://reducer.readthedocs.org
Please provide feedback
Comments are very, very much welcome. Please comment by making a new issue on Github (if, by chance, a reasonably senior academic is using this, you can send feedback by email; anyone else should really create a github account so you can make an issue :)).
Installation
Note about IPython/Jupyter version support: Version 0.3 and higher of reducer works with IPython 4/Jupyter. Version 0.1 works with IPython 2, and Version 0.2.x work with IPython 3 or IPython 4/Jupyter. No improvements to reducer will be backported to version 0.1.x/IPython 2 or to 0.2.x/IPYthon 3. Feel free to fork if you need that!
You need python (2.7, or 3.4 or higher) and the SciPy stack. The easiest way to the get the full stack is from a distribution like anaconda.
On Windows it will be easiest to install using the Anaconda Python distribution and conda (because everything has been compiled for you).
To install using conda:
conda install -c conda-forge -c astropy reducer
If you prefer, you can install with pip in any python distribution (but may end up compiling some of the dependencies):
pip install reducer
You can, if you want, grab the source on github (there is a “Download as ZIP” link on the right you can use if you don’t want to mess git), change into the source directory, and run python setup.py install.
Usage
This package doesn’t magically do your reduction for you. Instead, it creates a template jupyter notebook that leads you through data reduction. When you are done you have reduced your data and you have a notebook that allows you or someone else to reproduce your work.
In a terminal, navigate to the directory where you want to keep the notebook for doing your reduction (which does not have to be the same directory where the data is, though it can be), then type:
reducer
This will create a new template notebook. To open the notebook, type in a terminal:
jupyter notebook
A browser window will open; the notebook you want is named “reduction.ipynb”. Click on it, then just do what it says in the notebook and reduced data (and someday photometry!) will be yours.
Under the hood
If you look at the source code you’ll notice pretty quickly that there is no actual science code. Think of this as the glue that brings together a couple related packages:
Metadata
Release files for reducer 0.9.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| reducer-0.9.4.tar.gz | 11.7 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| reducer-0.9.4-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 23.4 MB
Release files / reducer-0.9.4.tar.gz
| Download URL | reducer-0.9.4.tar.gz |
|---|---|
| Size | 11.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bd8453eb553e5189a738dcf927e2f6c1f8fbcfdb4dfce51c16bb80794ae5fbf9
|
|
BLAKE2b-256 checksum How to use checksums |
f3db75f15e3e32331d20c14ba6feaf67c6eb316664d5eab6b59acf091a483220
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.
Transparency logRelease files / reducer-0.9.4-py2.py3-none-any.whl
| Download URL | reducer-0.9.4-py2.py3-none-any.whl |
|---|---|
| Size | 11.7 MB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
555bcd3cd84700efb73048ccd202e4e81e3f532b961423f362f436cea0397c6d
|
|
BLAKE2b-256 checksum How to use checksums |
aa8070d021e4839a2f1aa1efde2342eeca7966da714e45611dfa33ec25b29ce6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.
Transparency log