StructNtuple making

Introduction

User analysis of NIKHEF Top group requires data format from AOD/D2PD to so-called StructNtuple. The intermittent by-product is so-called AMAEvent. The size ratio of AOD:AMAEvent:StructNtuple is roughly 100:10:1.

The conversion from AOD/D2PD to AMAEvent requires Athena framework and as the AOD/D2PD are widely distributed on the Grid; while the step from AMAEvent to StructNtuple needs only ROOT environment (in principle). For the collision data, we decided to start D2PD instead of AOD as the non-interesting events for Top analysis have been skimmed, slimmed and ...; while for MC samples, one needs to start from AOD.

Here after, the technical steps to go through for the AMAEvent/StructNtuple generations are described together with instructions to take actions on those steps.

The job submission tools is based on Ganga using the WMS for job brokering to the Grid.

Workflow

Actions

Freezing AMAAthena release

All the code change in AMAUser/AMACore/AMAAthena should be consolidated with all possible dependencies clearly defined in SVN.

Freezing AMA configurations

Following the frozen of AMAAthena release, the proper configuration file for AMAEvent and StructNtuple generations should be also made available and frozen.

Installing Athena at NIKHEF

When a new Athena release is needed and not installed at NIKHEF's /data/atlas, install it first.

Making UserArea tarball

This step contains 2 works:

  1. making a self-contained UserArea tarball to be shipped along with the job to the remote grid worker nodes.
  1. converting the AMA configuration files into standalone Athena job options, those job options are only for AMAEvent Making.