Create a proper podio backend to ensure validity of root based merging

Open
#57 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
backend

Research direction

Start by locating the existing podio frame-based merger and read how its output is produced. Implement a podio backend as an alternative, then benchmark it against the current approach and validate that its root-based merging output is correct.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe.
In development a podio frame based merger was tested but dismissed as it didn't perform very well. This should be reconsidered and implemented as an alternative to benchmark against and validate the output against.

Dominant language
C++
Stars
0
Forks
0
Avg merge
6m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eic/TimeframeBuilder

All issues in eic/TimeframeBuilder

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.