Welcome to ytree.

ytree is a tool for working with merger-tree data from multiple sources. ytree is an extension of the yt analysis toolkit and provides a similar interface for merger-tree data that includes universal field names, derived fields, and symbolic units. ytree can create merger-trees from Gadget FoF/Subfind catalogs, either for all halos or for a specific set of halos. ytree is able to load in merger-tree from the following formats:

• consistent-trees
• Rockstar halo catalogs without consistent-trees
• merger-trees made with ytree

All formats can be saved with a universal format that can be reloaded with ytree. Individual trees for single halos can also be saved.

Table of Contents

• Installation
• What version do I have?
• Sample Data
• Working with Merger-Trees
  • Loading Merger-Tree Data
  • Working with Merger-Tree Data
  • Saving Arbors and Trees
• An Important Note on Comoving and Proper Units
• Fields in ytree
  • The Field Info Container
  • Fields on Disk
  • Alias Fields
  • Derived Fields
  • Analysis Fields
• Making Merger-trees from Gadget FoF/Subfind
  • Computing a Full Merger-tree
  • Computing a Targeted Merger-tree
  • Optimizing Merger-tree Creation
• Community Code of Conduct
• Contributing to ytree
• Developer Guide
  • Contributing in a Nutshell
  • Testing
  • Adding Support for a New Format
• Help
• API Reference
  • Working with Merger-Trees
  • Making Merger-Trees
  • Internal Classes

Citing ytree

If you use ytree in your work, please cite it as “ytree, written by Britton Smith and the yt project” with a footnote pointing to http://ytree.readthedocs.io.

Search

• Search Page