Skip to content

Commit 2d95d37

Browse files
committed
Adding funding proposals for Cycle 4. One for astroquery and one for specutils work.
1 parent 5cb6eed commit 2d95d37

File tree

2 files changed

+176
-0
lines changed

2 files changed

+176
-0
lines changed
Lines changed: 95 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
### Title
2+
Cycle 4 Funding: Making Australian astronomical datasets accessible
3+
4+
### Project Team
5+
AAO Research Data & Software, Macquarie University (rds.org.au)
6+
7+
The foundation of the AAO Research Data & Software (RDS) team is built upon over
8+
40 years of supporting astronomical observatories in Australia. This software
9+
development experience ranges from controlling telescopes and their instruments,
10+
to building data reduction pipelines, to developing and implementing tools that
11+
store, manage, and analyse data. The RDS team aims to be at the forefront of
12+
research software and data engineering. We look for the best technology to solve
13+
a problem, but at the same time realise that software is not innovative or useful
14+
if it cannot be maintained, extended, or scaled. We appreciate the benefits that
15+
a holistic view of a software ecosystem can bring, but also recognise that a
16+
"deep dive" might be necessary to solve a complex problem. And while our historical
17+
strength has an astronomical flavour, our skills and expertise are increasingly
18+
recognised across research disciplines. Some of our current and recent projects
19+
include the Data Central Science Platform, including Virtual Observatory services;
20+
VLT MAVIS Data Reduction pipeline design and development; our state-of-the-art
21+
Pipelines as a Web Service (PAWS) system; and our recently completed ESO VLT
22+
Pipelines development and maintenance project.
23+
24+
We propose the following individuals for this project, although other team members
25+
can be involved if needed:
26+
27+
* James Tocknell
28+
* Anthony Horton
29+
* Brent Miszalski
30+
* Nuria Lorente
31+
* Simon O'Toole
32+
33+
Although this is our first proposed contribution to astropy as a team, some of
34+
our members have made individual contributions over the years. Moreover, given
35+
the use that we make of astroquery in our Data Central science platform
36+
components in particular, we are keen to further contribute to astroquery
37+
infrastructure, not just through this proposal, but also in the longer term.
38+
39+
### Project Description
40+
The astroquery package has become a popular touchstone for observational
41+
astronomers to find data, being used by more than 4000 github repositories (The
42+
Astropy Collaboration et al. 2022, 935, 167). Apart from astroquery.casda,
43+
Australian astronomical data are conspicuously absent from astroquery. In this
44+
project we address this shortcoming by adding access to the Anglo-Australian
45+
Telescope (AAT) Archive and several other Australian large survey datasets hosted
46+
by Data Central (https://datacentral.org.au): images, catalogues and spectra.
47+
Enhancing the visibility and accessibility of Australian datasets is critically
48+
important to complement multi-wavelength and multi-messenger observations from
49+
upcoming Southern Hemisphere facilities such as the Vera Rubin Observatory (VRO),
50+
Cerenkov Telescope Array (CTA) and the Square Kilometre Array (SKA).
51+
52+
While many of the datasets we plan to add are accessible via VO services, many
53+
astronomers find VO services very difficult to interact with. Adding them to their
54+
own dedicated astroquery module would alleviate their anxieties about using these
55+
services. The AAT archive, on the other hand, is not currently accessible via a
56+
VO service and this work would allow for robust programmatic access for the
57+
first time.
58+
59+
We also propose to address a longstanding problem in the preparation of multi-object
60+
spectroscopy (MOS) observations by adding the Cone of Darkness algorithm
61+
(Lorente 2014, ASPC 485, 95) to select blank sky positions. This automates a
62+
tedious task in a robust manner for any input astroquery catalogue.
63+
64+
65+
### Project / Work
66+
1. Data Central catalogues, images and spectra are accessible, respectively, via
67+
TAP, SIA and SSA services hosted by Data Central. We plan to provide access via
68+
a dedicated astroquery.datacentral module. The module would also include an API
69+
to access the AAT archive, also hosted by Data Central. The AAT archive hosts data
70+
from several instruments, the most prominent of which are MOS observations taken
71+
with the 2dF and 6dF facilities, amassing vast quantities of spectroscopic data.
72+
Via improvements to the archive API endpoints, we plan to provide access to the
73+
individual fibre tables of MOS observations, providing unprecedented access to
74+
this rich spectroscopic database. In the case of 2dF-AAOMega observations, users
75+
may then request automatic reductions of queried spectra via our Pipeline As a
76+
Web Service (PAWS) system.
77+
78+
1. Addition of the Cone of Darkness algorithm involves porting the C++ code and
79+
tests to astroquery such that any input catalogue (also obtained with astroquery)
80+
may be used to select sky positions. High proper motion stars may be excluded
81+
with an optional GAIA DR3 query.
82+
83+
84+
### Approximate Budget
85+
This funding application is to cover staff time. We estimate 420 hours of effort
86+
are required to complete this project, which at an hourly rate of USD$145/hour
87+
gives a budget of USD$60,900.
88+
89+
This effort estimate will be refined, and the minimum useful time to carry out
90+
some of the proposed work will be determined and added here during the iteration
91+
period.
92+
93+
94+
### Period of Performance
95+
We expect the period of performance to be two years.
Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
### Title
2+
Cycle 4 Funding: Realising the full potential of specutils via an extensible
3+
interface for community contributed algorithms
4+
5+
### Project Team
6+
AAO Research Data & Software, Macquarie University (rds.org.au)
7+
8+
The foundation of the AAO Research Data & Software (RDS) team is built upon over
9+
40 years of supporting astronomical observatories in Australia. This software
10+
development experience ranges from controlling telescopes and their instruments,
11+
to building data reduction pipelines, to developing and implementing tools that
12+
store, manage, and analyse data. The RDS team aims to be at the forefront of
13+
research software and data engineering. We look for the best technology to solve
14+
a problem, but at the same time realise that software is not innovative or useful
15+
if it cannot be maintained, extended, or scaled. We appreciate the benefits that
16+
a holistic view of a software ecosystem can bring, but also recognise that a
17+
"deep dive" might be necessary to solve a complex problem. And while our historical
18+
strength has an astronomical flavour, our skills and expertise are increasingly
19+
recognised across research disciplines. Some of our current and recent projects
20+
include the Data Central Science Platform, including Virtual Observatory services;
21+
VLT MAVIS Data Reduction pipeline design and development; our state-of-the-art
22+
Pipelines as a Web Service (PAWS) system; and our recently completed ESO VLT
23+
Pipelines development and maintenance project.
24+
25+
We propose the following individuals for this project, although other team members
26+
can be involved if needed:
27+
28+
* James Tocknell
29+
* Anthony Horton
30+
* Brent Miszalski
31+
* Nuria Lorente
32+
* Simon O'Toole
33+
34+
### Project Description
35+
The latest version of specutils includes useful common analysis tasks for
36+
astronomical spectra.
37+
To realise its potential as a fully-fledged contributor to scientific workflows,
38+
spectutils would greatly benefit from the addition of a generic capability for
39+
advanced users to supply their own tailored algorithms (i.e. code) to be used in place of
40+
the defaults.
41+
We would like to add this capability to specutils, allowing users to apply
42+
advanced analysis and algorithms to specutils spectra via a regularlised
43+
interface. This interface would be analagous to how astroquery provides a
44+
regularised interface to access VO and other web services. It will provide the
45+
opportunity for the community to contribute their own algorithms, e.g. relating
46+
to large community spectroscopic surveys, or other generic methods. This would go
47+
a long way towards providing a sustainable central repository for analysis
48+
algorithms outside of traditional legacy environments (e.g. IRAF). In this
49+
project we propose implementing the generic interface and will provide an example
50+
implementation of cross-correlation of spectra using Fast Fourier Transforms.
51+
52+
### Project / Work
53+
1. We plan to introduce into specutils a regularised framework for user contributed
54+
algorithms. We have experience in contributing to specutils loaders, used by
55+
our team to ingest spectra into Data Central.
56+
57+
1. An example contributed algorithm will be provided, namely a Fast Fourier
58+
Transform (FFT) cross-correlation. This consists of two steps:
59+
60+
2. Interpolating the spectra and templates to a common (log) wavelength binning;
61+
2. Computing the FFTs, inverting the combined result, and shifting the output
62+
such that it aligns with the redshift bins. We will adapt existing code
63+
developed by our team when porting the MARZ redshifting code
64+
(Hinton et al. 2016, A&C, 15, 61) from Javascript to Python. The code has been
65+
thoroughly tested and validated, addressing the shortcomings of the original codebase.
66+
67+
### Future Work
68+
We are keen to make substantial contributions to specutils in the future.
69+
70+
### Approximate Budget
71+
This funding application is to cover staff time. We estimate 630 hours of effort
72+
are required to complete this project, which at an hourly rate of USD$140/hour
73+
gives a budget of USD$88,200.
74+
75+
This effort estimate will be refined, and the minimum useful time to carry out
76+
some of the proposed work will be determined and added here during the iteration
77+
period.
78+
79+
80+
### Period of Performance
81+
We expect the period of performance to be two years.

0 commit comments

Comments
 (0)