Theoretical Astrophysical Observatory

The Theoretical Astrophysical Observatory (TAO) houses queryable data from multiple cosmological dark matter numerical simulations and galaxy formation models, in a database optimised for rapid access. TAO boasts a clean and intuitive web interface. It avoids the need to have the user program SQL queries by providing a custom point-and-click interface for selecting galaxies and their properties, which auto-generates the query code in the background. Query results can be funnelled through additional “modules” and sent to the Swinburne OzSTAR supercomputer for further processing and manipulation. These include the ability to:

It uses a cloud-based architecture that offers Infrastructure as a service (IaaS), Data as a service (DaaS), and Software as a service (SaaS). It is configured in such a way that additional modules can be built and easily inserted into the data chain as needs require in the future. Refer to Bernyk et al., The Astrophysical Journal Supplement Series 223.1 (2016) for additional details.

The development of TAO V1.0 started mid-2012 by NeCTAR funding under the Virtual Labs project. The first version was released on the 24th March 2014. The first version of the node was co-developed by Swinburne University of Technology and Intersect Australia Limited. The following list summarises the different major releases and the main features delivered within each release:

TAO architecture is partitioned into three tiers:

The main TAO database, science modules, and results storage space are located on the OzSTAR supercomputer at Swinburne University. The user interface and Table Access Protocol (TAP) server are hosted on a separate web server and accept job requests. Jobs are queued on the supercomputer via the jobs scheduler. Upon the job completion results are available for download over the internet.

The technology currently used:

Hardware arrangement:

TAO is the only node at the moment that provides professional grade support (via asvo.atlassian.net with less than 48 hours SLA) and externally hosted documentation and tutorials.

The primary stakeholders: