tangos#
tangos builds a database of summary data for your own cosmological and zoom simulations – masses, profiles, images, star formation histories, merger trees – so that questions spanning an entire simulation are answered in milliseconds, without touching the raw particle data again. It is the same idea as the public Eagle and MultiDark databases, for your own runs.
You can then explore that database from python, or from a web browser:
Start here#
New to tangos? You do not need any simulation data to learn what tangos does, and almost nothing here needs pynbody either – only one call in the quick-start, which says so where it appears. Install it, download the ready-made tutorial database, and query it:
Installation – tangos and the tutorial database, in three steps.
The tangos data model – simulations, timesteps, objects, properties and links. Fifteen minutes here saves hours later, because every other page assumes it.
Quick-start – find a halo, read its properties, plot an image of a galaxy.
Time series and populations – follow a halo back through its progenitors and plot how it grew.
Live calculations – the language that makes the database more than a table of numbers.
The web interface – the same database in a browser.
Building a database from your own simulation starts at making your first database, which covers the supported simulation codes and halo finders. You will need the raw simulation output and a reader for it, usually pynbody.
Configuring tangos – where the database lives, what gets written, how the merger trees are thinned – is covered in configuration.
Acknowledging the code#
When using tangos, please acknowledge it by citing the release paper: Pontzen & Tremmel, 2018, ApJS 237, 2. DOI 10.3847/1538-4365/aac832; arXiv:1803.00010. Optionally you can also cite the Zenodo DOI for the specific version of tangos that you are using, which may be found here.