Project

General

Profile

Feature #8846

Support for handling branch aliases

Added by Marc Paterno over 4 years ago. Updated over 1 year ago.

Status:
Accepted
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
05/18/2015
Due date:
% Done:

0%

Estimated time:
32.00 h
Scope:
Internal
Experiment:
-
SSI Package:
Duration:

Description

As a result of the need to keep automatically-generated branch names unique, branch names end up being large. To make interactive use of art/ROOT data files more convenient, we want to support branch aliases.

The person running the program is the best to control what the branch aliases are. Issues to decide upon include:
  1. Where does this happen?
  2. How do aliases get transferred from input to output file?
  3. What happens when there is a collision?
  4. Do we handle collisions between the input and the current job differently from collisions within the current job?

Having the configuration of the branch alias specified in the output module makes it easy to deal with providing an alias for a product that came from an input file.

History

#1 Updated by Marc Paterno over 4 years ago

  • Estimated time set to 32.00 h

Tasks include:

  1. Providing ROOT macro to alias branches for an interactive session
  2. When executing art, provide mechanism to specify fixed branch aliases.

#2 Updated by Christopher Green over 4 years ago

  • Status changed from New to Accepted

#3 Updated by Christopher Green over 4 years ago

  • Target version set to 1.18.00

#4 Updated by Christopher Green almost 4 years ago

  • Target version changed from 1.18.00 to 834

#5 Updated by Marc Paterno almost 4 years ago

  • Target version changed from 834 to 2.01.00

The feasibility and time estimate needs to be revisited in the context of ROOT 6.

#6 Updated by Kyle Knoepfel over 3 years ago

  • Target version changed from 2.01.00 to Vega

#7 Updated by Kyle Knoepfel over 1 year ago

  • Target version changed from Vega to Capella


Also available in: Atom PDF