Caterpillar Project Docs
  • Introduction
  • Available Data
  • Access & Authorship Policies
  • FAQ
  • Technical
    • Overview & Basic Approach
    • Initial Conditions
    • Parent Simulation
    • Zooming In
    • Halo Identification
    • Merger Trees
    • Semi-Analytic Models
  • Usage
    • Data Access
    • Analyzing Data
    • Help & Support
Powered by GitBook
On this page
  • Particle Data
  • Halo Catalogues
  • Merger Trees

Was this helpful?

Available Data

Particle Data

The core N-body code used to run Caterpillar was a combination of P-Gadget3 and Gadget-4. The output of the simulation runs is the typical Gadget HDF5 output and should be compatible with all other downstream post-processing tools available in the community. These outputs are available at all 320 snapshots of the simulation from z = 127 to z = 0 with < 50 Myr resolution from z = 6 to z = 0.

For details, please see either our flagship paper or our Technical pages.

Owing to the extreme size of the runs, particle data (z > 0) is only available upon request.

Halo Catalogues

We used a modified version of ROCKSTAR included full iterative unbinding but the outputs are consistent with the nominal outputs from standard ROCKSTAR catalogues. Please see the documentation at the Rockstar repository for details (See Section 4. Outputs). There are however a few important caveats relating to our outputs which differ from the nominal outputs.

e.g. M_grav vs. Mvir vs npart*m_p

These can be made available upon request.

Merger Trees

The chosen merger tree system used is consistent-trees. Please see the consistent-trees README for direct information pertaining to its running and output.

PreviousIntroductionNextAccess & Authorship Policies

Last updated 6 years ago

Was this helpful?