Skip to main content

uproot extension for reading custom classes

Project description

uproot-custom

This is a prototype repository of an extension that allows uproot to read custom classes from ROOT files.

uproot can already read some custom classes directly. However, in some cases, custom classes are too complex for uproot to read, such as when their Streamer methods are overridden or some specific data members are not supported by uproot.

This extension privides a Reader interface and allows you to read such custom classes by providing your own Reader. The Reader interface defines how to read the data members of a class from the binary stream.

Design overview

In ROOT, data are stored in a tree structure. For example, when a custom class is defined as:

class TMySubClass : public TObject {
    int m_index;
    float m_x;
};

class TMyClass : public TObject {
    double m_energy;
    std::vector<MySubClass> m_daughters;
};

The data tree is:

graph TD
    A([TMyClass]) --> B(double m_energy)
    A --> C(std::vector&lt;TMySubClass&gt; m_daughters)
    C --> D([TMySubClass])
    D --> E(int m_index)
    D --> F(float m_x)

To handle the tree-like data structure, Reader is introduced. It consists of Python and C++ parts. The Python part is responsible for generating the information tree, constructing C++ readers, and reconstructing data to awkward array. The C++ part is responsible for reading the data members of the class from the binary stream.

Generate information tree

uproot can read these structure information from the ROOT file, but not in tree format. So the first step is to generate an information tree from the ROOT file. The information tree is a nested structure that contains the data members of the class, including types, names and children if any.

Construct C++ readers

According to the information tree, we can instantiate C++ readers and combine them into a tree structure. The top reader drives its sub-readers to read data recursively. After the reading process, readers obtain the results from their sub-readers recursively, then the top reader returns the final result.

Reconstruct data to awkward array

Since embedding arrays together into awkward array in C++ is not straightforward, we left this task to Python. After the C++ reader returns the result, we can reconstruct the data into awkward array according to the information tree.

Predefined readers

uproot-custom provides some predefined readers for common ROOT classes:

Reader Description
BasicTypeReader Reads basic types like int, float, double, etc.
TObjectReader Skip TObject header when reading classes that inherit from TObject.
TStringReader Reads TString
STLSeqReader Reads std::vector, std::array, etc.
STLMapReader Reads std::map, std::unordered_map, etc.
STLStringReader Reads std::string
TArrayReader Reads TArray types like TArrayI, TArrayF, TArrayD, etc.
ObjectReader Reads custom classes that inherit from TObject.
CArrayReader Reads C-style arrays like int[]
EmptyReader A reader that does nothing. Some branches may not have any data, and the information of the corresponding class will not be stored in the ROOT file. In this case, EmptyReader is used to skip the branch.

Implement your own Reader

Full example

A complete example of how to impolement your own readers is available in the example directory of this repository.

Pre-requisites

Make sure you have GCC>13.1/Clang>=16.0.0/MSVC>=19.31, cmake installed on your system.

  1. Create a Python project and install uproot-custom:

    mkdir my_reader
    cd my_reader
    python3 -m venv .venv
    source .venv/bin/activate
    pip install uproot-custom
    
  2. Create a pyproject.toml file in the root directory of your project:

    [build-system]
    requires = ["scikit-build-core>=0.11", "pybind11>=2.10.0", "uproot-custom"]
    build-backend = "scikit_build_core.build"
    
    [project]
    name = "my-reader"
    requires-python = ">=3.9"
    dependencies = ["uproot-custom"]
    version = "0.1.0"
    
    [tool.scikit-build]
    wheel.packages = ["my_reader"]
    build-dir = "build/{wheel_tag}"
    cmake.source-dir = "cpp"
    cmake.build-type = "Debug" # Comment for release builds
    
    [tool.black]
    exclude = "/(build|dist|env|.git|.tox|.eggs|.venv)/"
    line-length = 95
    target-version = ['py39', 'py310', 'py311', 'py312', 'py313']
    

    you can change the name, version, and other fields as you like.

Reader interface

For a custom Reader, a C++ part and a Python part are both required.

For C++ part, the constructor must inherit from IElementReader, and these methods must be implemented:

  • void read(BinaryBuffer& buffer): Read data from the binary buffer.
  • py::object data() const: Return the data as a Python object. You can return anything defined in pybind11, such as py::tuple, py::list, py::array_t, etc.

For Python part, the class must inherit from uproot_custom.BaseReader and implement the following class methods:

  • gen_tree_config: Generate a configuration dictionary for the reader based on the information tree. It should return a dictionary if you want your reader to be used, otherwise return None.
  • get_cpp_reader: Identify the tree configuration and return the C++ reader instance if it matches, otherwise return None.
  • reconstruct_array: Reconstruct the raw data to an awkward array according to the tree configuration.

Implement the C++ reader

  1. Create a cpp directory in the root directory of your project, and create a my_reader.cc file in it.

  2. In my_reader.cc, include the necessary headers and implement your reader class. For example:

    #include "uproot-custom/uproot-custom.hh"
    using namespace uproot;
    
    class MyReader : public IElementReader {
        public:
            // Must at least receive a name
            MyReader( std::string name )
                : IElementReader(name), m_data( std::make_shared<std::vector<int>>() ) {}
    
            // Implement these methods
            void read( BinaryBuffer& buffer ) {
                // Read data from the buffer
                // Implement your reading logic here
            }
    
            py::object data() const {
                // Return the data as a Python object
                return make_array( m_data );
            }
    
        private:
            const std::string m_name;
            std::shared_ptr<std::vector<int>> m_data; // Example data member
    };
    

    then declare the C++ module in the same file:

    PYBIND11_MODULE( my_reader_cpp, m ) {
        register_reader<MyReader>(m, "MyReader");
    }
    

    if the constructor requires more parameters, register it with the constructor signature (except the name):

    // Constructor signature:
    MyReader( std::string name, bool param1, std::vector<IElementReader> sub_readers )
    
    // Register the reader with the constructor signature:
    PYBIND11_MODULE( my_reader_cpp, m ) {
        register_reader<MyReader, bool, std::vector<IElementReader>>(m, "MyReader");
    }
    

[!IMPORTANT] Use std::shared_ptr for data members in your reader class, as uproot-custom will manage the memory of the data members. This is important to avoid memory leaks and ensure proper cleanup.

  1. Create a CMakeLists.txt file in cpp directory:

    cmake_minimum_required(VERSION 3.20)
    
    if(CMAKE_VERSION VERSION_GREATER_EQUAL 3.27)
        cmake_policy(SET CMP0148 NEW)
    endif()
    
    set(CMAKE_EXPORT_COMPILE_COMMANDS ON)
    set(CMAKE_CXX_STANDARD 20)
    
    project(${SKBUILD_PROJECT_NAME}
        VERSION ${SKBUILD_PROJECT_VERSION}
        LANGUAGES CXX
    )
        
    set(PYBIND11_NEWPYTHON ON)
    find_package(pybind11 REQUIRED)
    find_package(uproot-custom REQUIRED)
    
    pybind11_add_module(my_reader_cpp
        my_reader.cc
        # Add other source files here if needed
    )
    
    target_link_libraries(my_reader_cpp PRIVATE uproot-custom)
    
    if(DEFINED SKBUILD_PROJECT_NAME)
        install(
            TARGETS my_reader_cpp
            LIBRARY DESTINATION ${SKBUILD_PROJECT_NAME}
        )
    endif()
    

Implement the Python reader

  1. Create a my_reader directory in the root directory of your project, and create a __init__.py file in it.

  2. In __init__.py, import the C++ module and implement your Python reader class:

    from . import my_reader_cpp as _cpp
    from uproot_custom import BaseReader
    
    
    class MyReader(BaseReader):
        @classmethod
        def gen_tree_config(
            cls,
            top_type_name: str,
            cls_streamer_info: dict,
            all_streamer_info: dict,
            item_path: str = "",
        ) -> dict | None:
            """
            Identify the node in the information tree,
            return the configuration dictionary if the node is matched,
            otherwise return None.
            """
    
        @classmethod
        def get_cpp_reader(cls, tree_config) -> _cpp.MyReader | None:
            """
            Identify the tree_config,
            if it is matched, return the C++ reader instance,
            otherwise return None.
            """
    
        @classmethod
        def reconstruct_array(cls, raw_data, tree_config):
            """
            Reconstruct the raw data to an `awkward` array according to the tree_config.
            """
    

    ![NOTE] The @classmethod is not necesarry, but when a regular member method is used, you should pass the instance of the class to registered_readers.

Register the reader

Register branch path

The default interpretation uproot_custom.AsCustom needs to know which branch to read with custom readers. You can export the branch path with:

import uproot
from uproot_custom import regularize_object_path

f = uproot.open("my_file.root")
branch = f["path/to/my_branch"]

print(regularize_object_path(branch.object_path))

This will print the regularized object path like /my_tree:my_branch. Then you can add it to the AsCustom.target_branches set:

from uproot_custom import AsCustom

AsCustom.target_branches.add("your-branch-path")

Register the reader

To let uproot_custom.AsCustom know your reader, you need to register it:

from uproot_custom import registered_readers
from my_reader import MyReader

registered_readers.add(MyReader)

Then you can use uproot to read the custom class as usual.

[!TIP] It is recommended to do the registration in your project __init__.py, so that you can use your custom reader as long as you import your project.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

uproot_custom-1.0.0b0.tar.gz (57.2 kB view details)

Uploaded Source

Built Distributions

If you're not sure about the file name format, learn more about wheel file names.

uproot_custom-1.0.0b0-cp313-cp313-manylinux_2_34_x86_64.whl (162.2 kB view details)

Uploaded CPython 3.13manylinux: glibc 2.34+ x86-64

uproot_custom-1.0.0b0-cp312-cp312-manylinux_2_34_x86_64.whl (162.3 kB view details)

Uploaded CPython 3.12manylinux: glibc 2.34+ x86-64

uproot_custom-1.0.0b0-cp311-cp311-manylinux_2_34_x86_64.whl (162.0 kB view details)

Uploaded CPython 3.11manylinux: glibc 2.34+ x86-64

uproot_custom-1.0.0b0-cp310-cp310-manylinux_2_34_x86_64.whl (160.6 kB view details)

Uploaded CPython 3.10manylinux: glibc 2.34+ x86-64

uproot_custom-1.0.0b0-cp39-cp39-manylinux_2_34_x86_64.whl (160.7 kB view details)

Uploaded CPython 3.9manylinux: glibc 2.34+ x86-64

File details

Details for the file uproot_custom-1.0.0b0.tar.gz.

File metadata

  • Download URL: uproot_custom-1.0.0b0.tar.gz
  • Upload date:
  • Size: 57.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.12.9

File hashes

Hashes for uproot_custom-1.0.0b0.tar.gz
Algorithm Hash digest
SHA256 589e9148da1fefbaf0a35b864665c0e2f06005ed1b067b370dea47c2196db719
MD5 2e42539e4fab482f88f4b72eda8a78dc
BLAKE2b-256 d3b34fcb808d6f174aa57d8b8ad8186995b852850ff8dd69af50088fb21a757b

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.0.0b0.tar.gz:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.0.0b0-cp313-cp313-manylinux_2_34_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.0.0b0-cp313-cp313-manylinux_2_34_x86_64.whl
Algorithm Hash digest
SHA256 a695d9cef214312ca1b0b6adcd83081944d1a61162a3d241083e296e8873158a
MD5 0a6b8aea7ef1b2f692f084873cf63f21
BLAKE2b-256 449adb630a8298eedbef7c0df90e32fe664c1ed9effcb082029f525c11b86c9a

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.0.0b0-cp313-cp313-manylinux_2_34_x86_64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.0.0b0-cp312-cp312-manylinux_2_34_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.0.0b0-cp312-cp312-manylinux_2_34_x86_64.whl
Algorithm Hash digest
SHA256 1fa644b15d41886eff013cf140f9333bc5c233351ddc04e3f986f841ba2526e0
MD5 33cc1d299784a6dde5861b5177690854
BLAKE2b-256 d1e09805c7cd557b69455f3da1e08cf318737764b53d23b3008ef5776a57deef

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.0.0b0-cp312-cp312-manylinux_2_34_x86_64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.0.0b0-cp311-cp311-manylinux_2_34_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.0.0b0-cp311-cp311-manylinux_2_34_x86_64.whl
Algorithm Hash digest
SHA256 2a737af010f02190e793da84956933cc2954ab9b91a40120ea04850a0e615c7d
MD5 c834bd73cfced6af359004b4cc2f3748
BLAKE2b-256 b26a9cfafe00f5c2d4377e80287923a20587e651720d049bf2fe6a60b4167192

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.0.0b0-cp311-cp311-manylinux_2_34_x86_64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.0.0b0-cp310-cp310-manylinux_2_34_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.0.0b0-cp310-cp310-manylinux_2_34_x86_64.whl
Algorithm Hash digest
SHA256 3adea1f29ce37be5fb92de0bc53746556d0737f86e76efac4cde1062548e7fdf
MD5 6e70318bcd00ced7f840667f770363dd
BLAKE2b-256 f509feac7d3053de3b1349eb420b0ae4ffe85b711806baaeeb5417f1bbe40dac

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.0.0b0-cp310-cp310-manylinux_2_34_x86_64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file uproot_custom-1.0.0b0-cp39-cp39-manylinux_2_34_x86_64.whl.

File metadata

File hashes

Hashes for uproot_custom-1.0.0b0-cp39-cp39-manylinux_2_34_x86_64.whl
Algorithm Hash digest
SHA256 f5a1400d659e4996e7c2103d2dc8ceae45b437e2d2e48453f0da353ed71542af
MD5 47ea7b946161e15be42622ddb1409dab
BLAKE2b-256 9f6c8d5f490c16a57e5219d0b51ad9c3779a05ee6f06b984722db4b577d297a3

See more details on using hashes here.

Provenance

The following attestation bundles were made for uproot_custom-1.0.0b0-cp39-cp39-manylinux_2_34_x86_64.whl:

Publisher: python-publish.yml on mrzimu/uproot-custom

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page