Skip to content

Commit 68543d6

Browse files
authored
Merge pull request #1 from aperiosoftware/cycle4-edits
Small edits
2 parents 4890036 + fbb2b25 commit 68543d6

File tree

1 file changed

+29
-11
lines changed

1 file changed

+29
-11
lines changed

finance/proposal-calls/cycle4/aperio_general.md

Lines changed: 29 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ This could also fund other individuals working at Aperio Software as required.
1313

1414
This project covers a number of different areas of work around the Astropy project:
1515

16-
* Maintenance and development of new features in sub-packages in the core astropy package as well as coordinated packages for which we are maintainers
16+
* Maintenance and development of new features in sub-packages in the core astropy package as well as coordinated packages for which Robitaille and Mumford are maintainers
1717
* Contributions to other parts of the core astropy package and coordinated package ecosystem.
1818
* Participation in the release team, including carrying out releases in the core package and working on general infrastructure for releases
1919
* Maintainance and development of the shared OpenAstronomy tooling and infrastructure
@@ -23,42 +23,60 @@ This project covers a number of different areas of work around the Astropy proje
2323

2424
#### `astropy.io.fits`
2525

26-
This proposal will fund Tom in his role as a maintainer of `astropy.io.fits`. Our focus will be on continuing to resolve bugs specifically related to the refactoring of the compression module and improve performance, as well as more general maintenance of the sub-package. There are currently over [160 open issues](https://github.com/astropy/astropy/issues?q=is%3Aopen+is%3Aissue+label%3Aio.fits) for the io.fits sub-package alone, and therefore no shortage of work.
26+
This proposal will fund Robitaille for his work co-maintaining `astropy.io.fits`, continuing funding that was awarded to him to start working on this in 2023. The priorities for this work will be:
27+
* Resolving bugs related to the refactoring of the image compression module and work on improving
28+
performance to be on par or better than the performance of the previous module.
29+
* Continue work on the refactoring of ``CompImageHDU`` to inherit from ``ImageHDU``, and once
30+
completed, carry out extensive testing with real-world data and code to make sure the new code
31+
is robust. Once these changes are released to users, address bug reports related to this change.
32+
* Triage and start addressing other existing issues. At the time of writing, there are currently over
33+
[160 open issues](https://github.com/astropy/astropy/issues?q=is%3Aopen+is%3Aissue+label%3Aio.fits) for the io.fits sub-package alone.
2734

28-
#### `astropy.visualization.wcsaxes`
35+
#### `astropy.timeseries`
2936

30-
We shall continue maintaining the [astropy.visualization.wcsaxes](https://docs.astropy.org/en/stable/visualization/wcsaxes/) sub-package, which is used to make plots of a wide range of different data with any APE 14-compliant WCS.
31-
We will work on some of the [open issues](https://github.com/astropy/astropy/issues?q=is%3Aopen+is%3Aissue+label%3Avisualization.wcsaxes) as well as new issues that come up, and will also investigate ways of improving the performance of the plotting.
37+
Robitaille will continue co-maintaining the [astropy.timeseries](https://docs.astropy.org/en/stable/visualization/wcsaxes/) sub-package as required. The priorities will be:
38+
* Improving performance and memory usage
39+
* Encouraging adoption in other packages and investigating how the sub-package can be improved to facilitate this
40+
* Exploring how to provide functionality to cater for data cubes with a time axis rather than just plain time series tables.
3241

33-
#### `astropy.timeseries`
42+
#### `astropy.visualization.wcsaxes`
3443

35-
We shall continue maintaining the [astropy.timeseries](https://docs.astropy.org/en/stable/visualization/wcsaxes/) sub-package as required.
44+
Robitaille and Mumford will continue to maintain the [astropy.visualization.wcsaxes](https://docs.astropy.org/en/stable/visualization/wcsaxes/) sub-package, which is used to make plots of a wide range of different data with any APE 14-compliant WCS. The priorities for this sub-package will be:
45+
* Improving performance; very little effort has been made to date to make ``WCSAxes`` as fast as possible, focusing instead on providing good support for APE-14-compliant WCSes. However, there are a number of use cases where performance is becoming a bottleneck (for example in interactive visualizations), so we will focus on profiling and improving performance across the sub-package.
46+
* Fixing issues that have ben reported by users. There are currently over 40 [open issues](https://github.com/astropy/astropy/issues?q=is%3Aopen+is%3Aissue+label%3Avisualization.wcsaxes), so we will focus on bringing this number down and improving the stability and reliability of the sub-package overall.
3647

3748
#### reproject
3849

39-
The [reproject](https://github.com/astropy/reproject) coordinated package, implements different image reprojection algorithms. As well as continuing general maintainance of this project we expect to continue the development work undertaken with the previous funding. The main areas of development for reproject in this funding cycle will be further and deeper integration of [dask](https://www.dask.org) into reproject to improve performance and memory usage when reprojecting large data.
50+
The [reproject](https://github.com/astropy/reproject) coordinated package, implements different image reprojection algorithms. The main areas for future development are:
51+
* Continuing work on integrating the use of [dask](https://www.dask.org) into reproject to improve performance and memory usage when reprojecting large data, and ensure that this can be used for real-world applications of reprojecting and mosaicking larger-than-memory datasets.
52+
* Fixing issues reported by users, in particular ensuring that reproject works properly for state-of-the-art high resolution data (e.g. https://github.com/astropy/reproject/issues/199).
53+
* Exploring other reprojection algorithms that could be integrated into reproject.
4054

4155
#### astropy-healpix
4256

4357
[astropy-healpix](https://github.com/astropy/astropy-healpix) is a stable package which requires minimal maintanance. As part of this proposal we shall continue to triage issues, review pull requests and do releases as needed.
4458

59+
#### Release team
60+
61+
Robitaille is a member of the Astropy project release team, which is responsible for carrying out releases of the core package as well as coordinating release infrastructure across the project. Part of the funding will therefore be used to continue supporting these efforts.
62+
4563
#### OpenAstronomy shared infrastructure
4664

47-
The OpenAstronomy project holds some infrastructure projects shared between Astropy, SunPy and other packages. As part of this proposal we shall continue to contribute to and maintain the following projects:
65+
The OpenAstronomy project holds some infrastructure projects shared between Astropy, SunPy and other packages. As part of this proposal we will continue to contribute to and maintain the following projects:
4866
* https://github.com/OpenAstronomy/github-actions-workflows
4967
* https://github.com/OpenAstronomy/build-python-dist
5068
* https://github.com/OpenAstronomy/sphinx-changelog
5169
* https://github.com/OpenAstronomy/publish-wheels-anaconda
5270

53-
Including collaborating with the Scientific Python project on reducing duplication with their efforts.
71+
This will include collaborating with the Scientific Python project on reducing duplication with their efforts.
5472

5573
#### Participation in general Astropy development
5674

5775
In addition to the specific core sub-packages and coordinated packages mentioned above, we plan to continue contributing in a more general way to the Astropy ecosystem and community. We will respond to issues that we can help with, contribute bug fixes for bugs we encounter or are qualified to fix, help maintain features we have added in the past, participate in developer and other relevant calls when possible, and participate in discussions on the mailing list and in Slack.
5876

5977
#### Moderation and support for Slack/Matrix & Discourse
6078

61-
We shall continue to support the administraion and moderation of the Discourse, slack and Matrix community spaces.
79+
We will continue to support the administraion and moderation of the Discourse, slack and Matrix community spaces.
6280

6381
### Budget
6482

0 commit comments

Comments
 (0)