|
| 1 | +### Title |
| 2 | + |
| 3 | +### Project Team |
| 4 | + |
| 5 | +Nathaniel Starkman (NS) |
| 6 | + |
| 7 | + |
| 8 | +### Project Description |
| 9 | + |
| 10 | +Continue role as astropy core maintainer and as the cosmology maintainer, |
| 11 | +working to expand cosmology compatibility with 3rd party libraries. |
| 12 | + |
| 13 | +`astropy.cosmology` does not plan to add a Boltzmann code nor other highly |
| 14 | +technical domain-specific tools. Many useful 3rd party cosmology codes already |
| 15 | +exist, e.g Boltzmann solvers like CLASS, for these purposes. Currently |
| 16 | +`astropy.cosmology` has limited-to-no interoperability with these commonly-used |
| 17 | +libraries. As maintainer, I will prioritize improving interoperability, |
| 18 | +enabling, e.g. someone to create a cosmology instance in Astropy and run on |
| 19 | +that cosmology the CLASS Boltzmann solver. |
| 20 | + |
| 21 | + |
| 22 | +### Project / Work |
| 23 | + |
| 24 | +Continue role as `astropy.cosmology` maintainer: |
| 25 | + |
| 26 | +- Contribute bug fixes and develop new features |
| 27 | +- Pull Request reviews and Issue triaging |
| 28 | +- Participate as a mentor to new contributors, as a part of a possible formal |
| 29 | + contributor-to-maintainer training program |
| 30 | +- Continue developing a roadmap for the subpackage (GitHub Project in progress, |
| 31 | + with ~171 complete and ~141 current, and many more planned) |
| 32 | +- Develop new contributed tutorial content on astropy.cosmology |
| 33 | + |
| 34 | +The `astropy.cosmology` package has very few (known) bugs and is mature, so it |
| 35 | +receives relatively few Pull Requests and Issues. Consequently, NS anticipates |
| 36 | +that interoperability improvements will occupy the majority of the budgeted |
| 37 | +time. |
| 38 | + |
| 39 | + |
| 40 | +Planned interoperability improvements for `astropy.cosmology`: |
| 41 | + |
| 42 | +- Entry-point support to astropy’s Unified I/O, which is in `astropy.io`. NS |
| 43 | + will base this improvement on an existing reference implementation of his. |
| 44 | + Entry-point support in Unified I/O will have use beyond `astropy.cosmology`, |
| 45 | + e.g. allowing 3rd party formats to be available for I/O in `astropy.table`. |
| 46 | +- Prioritize adding I/O support for the following tools: [CLASS] |
| 47 | + (http://class-code.net) and [Colossus] |
| 48 | + (https://bdiemer.bitbucket.io/colossus/cosmology_cosmology.html), adding |
| 49 | + others as time permits. |
| 50 | + |
| 51 | + |
| 52 | +### Approximate Budget |
| 53 | + |
| 54 | +Target budget: $12,000 for 2 hours/week of work at $120/hour (rate negotiable). |
| 55 | +Minimum budget: $6,000 for 2 hours/week of work at $60/hour. |
| 56 | + |
| 57 | +### Approved Budget |
| 58 | + |
| 59 | +$12,000.00. |
0 commit comments