├── .nojekyll ├── .gitignore ├── CNAME ├── css ├── .DS_Store ├── github_issues.css ├── jquery.sidr.light.css └── style.css ├── favicon.ico ├── images ├── menu.png ├── .DS_Store ├── aplpy.png ├── ginga.png ├── montage.png ├── background.jpg ├── python-mark.png ├── astropy_banner_96.png ├── astropy_powered.png ├── astropy_word_32.png ├── astropy_powered_white.png ├── menu.svg ├── astropy_word.svg └── astropy_banner.svg ├── .travis.yml ├── README.md ├── js ├── analytics.js ├── jquery.sidr.min.js └── functions.js ├── team.html ├── editing_tips.txt ├── getteam.py ├── help.html ├── announcements ├── release-0.4.html └── release-1.0.html ├── affiliated ├── registry.json └── index.html ├── contribute.html ├── index.html └── about.html /.nojekyll: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | *.py[co] 2 | -------------------------------------------------------------------------------- /CNAME: -------------------------------------------------------------------------------- 1 | www.astropy.org 2 | 3 | -------------------------------------------------------------------------------- /css/.DS_Store: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mwcraig/astropy.github.com/HEAD/css/.DS_Store -------------------------------------------------------------------------------- /favicon.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mwcraig/astropy.github.com/HEAD/favicon.ico -------------------------------------------------------------------------------- /images/menu.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mwcraig/astropy.github.com/HEAD/images/menu.png -------------------------------------------------------------------------------- /images/.DS_Store: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mwcraig/astropy.github.com/HEAD/images/.DS_Store -------------------------------------------------------------------------------- /images/aplpy.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mwcraig/astropy.github.com/HEAD/images/aplpy.png -------------------------------------------------------------------------------- /images/ginga.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mwcraig/astropy.github.com/HEAD/images/ginga.png -------------------------------------------------------------------------------- /images/montage.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mwcraig/astropy.github.com/HEAD/images/montage.png -------------------------------------------------------------------------------- /images/background.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mwcraig/astropy.github.com/HEAD/images/background.jpg -------------------------------------------------------------------------------- /images/python-mark.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mwcraig/astropy.github.com/HEAD/images/python-mark.png -------------------------------------------------------------------------------- /images/astropy_banner_96.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mwcraig/astropy.github.com/HEAD/images/astropy_banner_96.png -------------------------------------------------------------------------------- /images/astropy_powered.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mwcraig/astropy.github.com/HEAD/images/astropy_powered.png -------------------------------------------------------------------------------- /images/astropy_word_32.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mwcraig/astropy.github.com/HEAD/images/astropy_word_32.png -------------------------------------------------------------------------------- /images/astropy_powered_white.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mwcraig/astropy.github.com/HEAD/images/astropy_powered_white.png -------------------------------------------------------------------------------- /.travis.yml: -------------------------------------------------------------------------------- 1 | language: python 2 | 3 | python: 4 | - 3.4 5 | 6 | script: 7 | # Validate JSON for affilaited package registry 8 | - python -c 'import json; json.load(open("affiliated/registry.json"))' -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | This repository contains the Astropy web site (primary URL http://www.astropy.org). 2 | 3 | In a previous version of this web site (on the [old_site branch](https://github.com/astropy/astropy.github.com/tree/old_site)), this repository held the build for the site, but the content was generated from the [astropy-website repository](https://github.com/astropy/astropy-website). That repo is no longer active, and issues with the astropy web site should now be reported in *this* repository. 4 | -------------------------------------------------------------------------------- /js/analytics.js: -------------------------------------------------------------------------------- 1 | (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ 2 | (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), 3 | m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) 4 | })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); 5 | 6 | ga('create', 'UA-30968842-1', 'auto'); 7 | ga('require', 'displayfeatures'); 8 | ga('require', 'linkid', 'linkid.js'); 9 | ga('send', 'pageview'); 10 | -------------------------------------------------------------------------------- /team.html: -------------------------------------------------------------------------------- 1 | 2 | 3 |
4 | 5 |We make every effort to keep the documentation readable and up-to-date, so it is often the first place to go for help. But we also provide other resources if you are having trouble using Astropy.
53 | 54 |The best way to get help is usually by asking questions of the Astropy user and development community.
60 | 61 |If you encounter something you beleive to be a mistake, error, or bug, the best way to get it addressed is to report it on the github issue tracker. If you aren't sure if something is a bug or not, feel free to ask on the mailing lists. If you believe you know how to fix the problem, you can also use github to issue pull requests to correct them (see the section on contributing code for more information).
75 | 76 | Report an Issue 77 | 78 |53 | Dear colleagues, 54 |
55 |56 | We are very happy to announce the third major public release (v0.4) of the astropy package, a core Python package for Astronomy: 57 |
58 |59 | http://www.astropy.org 60 |
61 |62 | Astropy is a community-driven package intended to contain much of the core functionality and common tools needed for performing astronomy and astrophysics with Python. 63 |
64 |65 | New and improved major functionality in this release includes: 66 |
76 | In addition, hundreds of smaller improvements and fixes have been made. An overview of the changes is provided at: 77 |
78 |79 | http://docs.astropy.org/en/stable/whatsnew/0.4.html 80 |
81 |82 | Instructions for installing Astropy are provided on our website, and extensive documentation can be found at: 83 |
84 |85 | http://docs.astropy.org 86 |
87 |88 | In particular, if you use Anaconda, you can update to v0.4 with: 89 |
90 |91 | conda update astropy 92 |93 |
94 | Please report any issues, or request new features via our GitHub repository: 95 |
96 |97 | https://github.com/astropy/astropy/issues 98 |
99 |100 | Over 80 developers have contributed code to Astropy so far, and you can find out more about the team behind Astropy here: 101 |
102 |103 | http://www.astropy.org/team.html 104 |
105 |106 | If you use Astropy directly - or as a dependency to another package - for your work, please remember to include the following acknowledgment at the end of papers: 107 |
108 |This research made use of Astropy, a community-developed core Python package for Astronomy (Astropy Collaboration, 2013).
109 | 110 |where (Astropy Collaboration, 2013) is a citation to the Astropy Paper (ADS - 111 | BibTeX).
112 |113 | Please feel free to forward this announcement to anyone you think might be interested in this release. 114 |
115 |116 | We hope that you enjoy using Astropy as much as we enjoyed developing it! 117 |
118 |
119 | Thomas Robitaille, Erik Tollerud, and Perry Greenfield
120 | on behalf of The Astropy Collaboration
121 |
53 | Dear colleagues, 54 |
55 |56 | We are very happy to announce the fourth major public release (v1.0) of the astropy package, a core Python package for Astronomy: 57 |
58 |59 | http://www.astropy.org 60 |
61 |62 | Astropy is a community-driven Python package intended to contain much of the 63 | core functionality and common tools needed for astronomy and astrophysics. 64 |
65 |66 | New and improved major functionality in this release includes: 67 |
79 | In addition, hundreds of smaller improvements and fixes have been made. An overview of the changes is provided at: 80 |
81 |82 | http://docs.astropy.org/en/stable/whatsnew/1.0.html 83 |
84 |85 | Astropy v1.0 is a special release that we are denoting a Long Term Support (LTS) 86 | release, which means that we will be supporting it with bug fixes for 87 | the next two years, rather than the usual six months. More information about 88 | this can be found at the link above. 89 |
90 |91 | Instructions for installing Astropy are provided on our website, and extensive documentation can be found at: 92 |
93 |94 | http://docs.astropy.org 95 |
96 |97 | In particular, if you use the Anaconda Python Distribution, you can update to v1.0 with: 98 |
99 |100 | conda update astropy 101 |102 |
103 | Whereas if you usually use pip, you can do: 104 |
105 |106 | pip install astropy --upgrade 107 |108 |
109 | Please report any issues, or request new features via our GitHub repository: 110 |
111 |112 | https://github.com/astropy/astropy/issues 113 |
114 |115 | Over 122 developers have contributed code to Astropy so far, and you can find out more about the team behind Astropy here: 116 |
117 |118 | http://www.astropy.org/team.html 119 |
120 |121 | If you use Astropy directly for your work, or as a dependency to another 122 | package, please remember to include the following acknowledgment at the end of 123 | papers: 124 |
125 |This research made use of Astropy, a 126 | community-developed core Python package for Astronomy (Astropy Collaboration, 127 | 2013).
128 | 129 |where (Astropy Collaboration, 2013) is a citation to the Astropy Paper (ADS - 130 | BibTeX).
131 |132 | Please feel free to forward this announcement to anyone you think might be interested in this release. 133 |
134 |135 | We hope that you enjoy using Astropy as much as we enjoyed developing it! 136 |
137 |
138 | Thomas Robitaille, Erik Tollerud, and Perry Greenfield
139 | on behalf of The Astropy Collaboration
140 |
The Astropy project is made both by and for its users, so we accept contributions of many kinds. We always welcome contributors who will abide by the Python Software Foundation Code of Conduct.
53 | 54 |There are several ways in which you can give us feedback.
60 | 61 |If you are interested in contributing fixes, code or documentation to Astropy (whether the core package or affiliated packages), you should join the astropy-dev mailing list/forum, and start looking at any related issues. In particular, we have introduced a labeling system used across most Astropy-related packages which will allow you to find good starting issues. A good label to start with is Package-novice which means you don't need much prior experience of the package. You can use the following links to find all the issues labelled this way and also labeled by how much work they involve:
73 |You may also want to familiarize yourself with the developer documentation, particularly the coding and documentation guidelines.
79 | 80 |Once you have a change to propose, if it's a simple fix to just a single file, you can even just browse to the appropriate file and use the "edit" button on github. If it's a more complex change, we suggest you follow the developer install instructions, and use that with Astropy's github page to issue a pull request with your changes. If you aren't familiar with github, we suggest you looking over our workflow documentation. Once your code is accepted, you are officially an Astropy contributor and eligible to be included on the author list of future publications.
81 | 82 |If you want to propose a larger change to Astropy, there's a procedure for that: Astropy Proposals for Enhancement (APEs) (modeled after Python's PEPs). The sort of changes that APEs are intended for include plans for new sub-packages, wide-ranging code re-organizations, a new procedure needing review by a lot of the Astropy community, or an informational document on some decision for Astropy that you want remembered. For more background on APEs, check out APE #1 and the APE repository's README. There is also a wiki page on Astropy's github repository that has an overview of the existing APEs.
83 | 84 | 85 |Whether you have an idea for a new Astronomy package, or already have a package that you want to integrate with the Astropy project, you can develop an affiliated package! You'll want to join the astropy-dev list so you can notifying other developers of your intent to develop an affiliated package. Then you can check out the affiliated package guidelines and the template for new affiliated packages to get started. We can even create a repository for your affiliated package in the astropy organization on GitHub, if you ask on the mailing list!
91 | 92 | 93 |The Astropy Project is a community effort to develop a single core 52 | package for Astronomy in Python and foster interoperability between Python 53 | astronomy packages.
54 | 55 |Current Version: 1.0.2
67 |Please remember to acknowledge the use of Astropy!
68 |There are a number of options for installing the astropy package on MacOS X. Astropy can be installed using the 85 | MacPorts or Fink package managers, 86 | and is also included by default in the 87 | Anaconda Python Distribution (more details here), 88 | Enthought Canopy, and 89 | Ureka, which 90 | provide an easy way to get set up with a scientific 91 | Python distribution. MacPorts usually includes new releases almost 92 | immediately, but Anaconda and Canopy may not always include the latest 93 | version. 94 |
95 | You can also install the latest version of Astropy using pip or by downloading the source 96 | code and installing it manually - see the Source tab above for more details. 97 |
98 |There are a number of options for installing the astropy package on Linux. Astropy can be installed on some Linux distributions using the built-in package manager (apt-get, yum, etc.), 101 | and is also included by default in the 102 | Anaconda Python Distribution (see here for instructions on updating to the latest Astropy version), 103 | Enthought Canopy, and 104 | Ureka, which 105 | provide an easy way to get set up with a scientific 106 | Python distribution.
107 |The package managers, Anaconda, and Canopy may 108 | not always include the latest version - in that case you can always 109 | install the latest version of Astropy using pip or by downloading the 110 | source code and installing it manually - see the Source tab above for 111 | more details. 112 |
113 |There are a number of options for installing the astropy package on Windows. 116 | Astropy is included by default in the Anaconda Python 118 | Distribution and Enthought Canopy, 120 | both of which provide an easy way to get set up with a scientific Python 121 | distribution.
122 |However, Anaconda and Canopy may not always include the 123 | latest version of Astropy, so if you need to install the latest 124 | version, you can either use the binary installers available on 125 | PyPI (usually made 126 | available a few days after each release) or you can install Astropy from 127 | source - see the Source tab above for more details. 128 |
To install Astropy from source, you can either use
131 |pip install astropy132 |
Alternatively, you can download a tarball for the latest release of astropy from PyPI, then expand the tarfile and run:
133 |python setup.py install134 |
to build and install the package. For more on installing from source code, see the relevant part of the documentation.
135 |The latest developer code is available on GitHub. If you have git installed you can get the latest version with:
138 |git clone https://github.com/astropy/astropy.git139 |
If you don't have git installed, you can instead download a zip file of the latest development version.
140 |Once you have the latest source code, you can build and install it with:
141 |python setup.py install142 |
For more on installing from source code, see the relevant part of the documentation.
143 |Do none of the above instructions work for your system, or do you need more detailed instructions? Check out the installation instructions in our documentation.
148 |Once you have installed Astropy, you can head over to the documentation for an overview of the 154 | functionality available in Astropy. Each section of the documentation 155 | contains a "Getting started" section that will demonstrate the basic 156 | functionality, and you will then also be able to browse the full 157 | documentation to find out more. 158 |
159 | Get Started with Astropy 160 | 161 |162 | If you run into any issues when using 163 | Astropy, please report them using the 164 | issue tracker. 165 | Finally, If you have any questions regarding using Astropy, or have feedback on how we 166 | can improve the package, please head over to our 167 | feedback and contributing or 168 | help pages.
169 | 170 | Contribute feedback or code 171 | Report issues 172 | 173 |If you use Astropy in your work, we would be grateful if you could include an acknowledgment in papers and/or presentations. See Acknowledging Astropy for details.
178 |You can also purchase apparel and trinkets from fashion.astropy.org, and a portion of the profits go to support the project!
179 |A major part of the Astropy project is the concept of “Affiliated Packages”. An affiliated package is an astronomy-related Python package that is not part of the astropy core package, but has requested to be included as part of the Astropy project’s community. These packages are expressing an interest in Astropy’s goals of improving reuse, interoperability, and interface standards for python astronomy and astrophysics packages.
54 | 55 |If you are developer interested in signing up as an affiliated package, details are at the end of this page.
56 | 57 |
65 |
66 | About: Montage-wrapper is a pure Python module that provides a Python API to the Montage Astronomical Image Mosaic Engine, including both functions to access individual Montage commands, and high-level functions to facilitate mosaicking and re-projecting. Python-montage uses the Astropy core package for reading and writing FITS files.
67 | 68 |Developer: Thomas Robitaille
69 | 70 | 71 | 72 |
77 |
78 | About: Ginga is a viewer for astronomical data FITS (Flexible Image Transport System) files. The Ginga viewer centers around a new FITS display widget which supports zooming and panning, color and intensity mapping, a choice of several automatic cut levels algorithms and canvases for plotting scalable geometric forms.
79 | 80 |Developer: Eric Jeschkee
81 | 82 | 83 | 84 |
90 |
91 | About: APLpy (the Astronomical Plotting Library in Python) is a Python module aimed at producing publication-quality plots of astronomical imaging data in FITS format. The module uses Matplotlib, a powerful and interactive plotting package. It is capable of creating output files in several graphical formats, including EPS, PDF, PS, PNG, and SVG.
92 | 93 |Developers: Thomas Robitaille, Eli Bressert, Adam Ginsburg
94 | 95 | 96 |These packages are still very much in development, and the user interface (API) may not be stable. If you do try these packages, please do report any issues to the developers.
122 | 123 |The following table lists all currently registered affiliated packages. This table is determined from the json file, which is the actual authoritative registry.
129 | 130 || Package Name | 142 |Stable | 143 |Provisional | 144 |PyPI Name | 145 |Web Page | 146 |Code Repository | 147 |Maintainer | 148 |
|---|---|---|---|---|---|---|
| Loading... | 152 |153 | | 154 | | 155 | | 156 | | 157 | | 158 | |
The Stable column indicates whether the package maintainer consider the package to be ready for use. Packages that are under heavy development and for which the user interface is likely to change significantly in the near future are marked as No.
164 |The Provisional column indicates packages that have been provisionally accepted as affiliated packages, but may be removed from the registry in the future if they don't make sufficient progress towards meeting Astropy standards (See below for more).
165 | 166 |If you are a developer of an astronomy package and would like your package to become affiliated with the Astropy project, leave a message on the astropy-dev group requesting affiliated package status. If you are comfortable doing so, you should also create a pull request adding your package to the registry file on the github repository for this web site. The Astropy coordination commitee and community will then consider your package based on the standards below.
172 | 173 |If your package is judged by the coordination committe to meet these standards, it will be added to the affiliated package registry. If the package is not quite at these standards, but working towards them, the package will be given "provisional" status. Provisional packages will be re-evaluated yearly by the coordinating committee, or earlier if the package author requests a review. In this re-evaluation, the committee will look at progress the package has made over the previous year. If it has been advanced sufficiently to meet the standards above, it will be considered a full affiliated package (no longer provisional). If it has made some progress but is not yet up to the standards, provisional status will be renewed for a year. If no progress seems to be being made, the committee will contact the authors and determine what their plans are to improve the situation. Based on that, the committee may decide to renew the provisional status, or remove the package from the registry.
188 | 189 |If you are considering creating a new astronomy package and would like it to be an Astropy affiliated package, we provide a package template to make it much easier to meet these standards. It provides the necessary structure to generate documentation like that used in the astropy package, a ready-to-use testing framework, and a variety of tools that streamline tasks like user configuration, caching downloaded files, or linking C-compiled extensions. More details on this template are available in the usage instructions for the template. 191 |
192 | 193 | 194 | 195 |The Astropy Project is a community effort to develop a core package for astronomy using the Python programming language and improve usability, interoperability, and collaboration between astronomy Python packages. The core astropy package contains functionality aimed at professional astronomers and astrophysicists, but may be useful to anyone developing astronomy software. The Astropy Project also includes "affiliated packages," Python packages that are not necessarily developed by the core development team, but share the goals of Astropy, and often build from the core package's code and infrastructure.
54 |For more details on the plan for the project, you can read the documentation overview, or the original vision from when the project was founded.
55 | 56 |If you use Astropy for work/research presented in a publication (whether directly, or as a dependency to another package), we ask that you cite the Astropy Paper (ADS - 66 | BibTeX). 67 | We provide the following as a standard acknowledgment you can use if there is not a specific place to cite the paper:
68 | 69 |This research made use of Astropy, a community-developed core Python package for Astronomy (Astropy Collaboration, 2013).
70 | 71 |If you wish, you can also include a link to http://www.astropy.org (if the journal allows this) in addition to the above text.
72 | 73 |If you are giving a presentation or talk featuring work/research that makes use of Astropy and would like to acknowledge Astropy, we suggest using this logo on your title slide:
76 | 77 |
78 |
79 | The logo is also available with white text, or the SVG originals can be obtained at the astropy-logo github repository.
80 | 81 |If you are using Astropy as part of a code project (e.g., affiliated packages), a useful way to acknowledge your use of Astropy is with a badge in your README. We suggest this badge:
84 | 85 | 86 | 87 |Which is available at the URL http://img.shields.io/badge/powered%20by-AstroPy-orange.svg?style=flat. If your code is hosted on github, You can place the following in your README.md file to get the badge:
90 | 91 | 92 | [](http://www.astropy.org/) 93 | 94 | 95 |Astropy is under continuous development by a group of professional astronomers and software developers from around the world. The Project is community-driven, with decisions generally made by consensus, but with oversight and organization provided be a three-person coordinating committee.
104 | 105 |If you have contributed to the Astropy project and your name is missing, 221 | please send an email to the coordinators, or open a pull request for the credits document in the astropy repository.
222 | 223 | 224 |Astropy is licensed under a three-clause BSD license. For details, see the licenses/LICENSE.rst file in the astropy repository.
232 |The community of participants in open source Astronomy projects is made up of members from around the globe with a diverse set of skills, personalities, and experiences. It is through these differences that our community experiences success and continued growth. We expect everyone in our community to follow these guidelines when interacting with others both inside and outside of our community. Our goal is to keep ours a positive, inclusive, successful, and growing community.
240 | 241 |As members of the community,
242 | 243 |This code of conduct applies to all community situations online and offline, including mailing lists, forums, social media, conferences, meetings, associated social events, and one-to-one interactions.
253 | 254 |Parts of this code of conduct have been adapted from the PSF code of conduct.
255 | 256 |
The Astropy Community Code of Conduct is licensed under a Creative Commons Attribution 4.0 International License. We encourage other communities related to ours to use or adapt this code as they see fit.