List of Abstracts Submitted for ROOT 2002

The following abstracts have been submitted for the ROOT 2002 workshop:

40 abstracts

name institute experiment

Fons Rademakers CERN alice
Status of ROOT in the areas of PROOF and GRID interfacing.

Rene Brun CERN alice
ROOT Status. Recent developments

Eddy Offermann Renaissance Technologies -
TMatrix class == At Renaissance Technologies, the ROOT framework is used to test new ideas for predicting price moves of financial instruments. Researchers can easily insert their new predictive sources into a simulator by supplying a C++ script to ROOT/CINT. This package requires a significant amount of matrix manipulations. Therefore, we are in the process of extending the functionality of the TMatrix class, originally developed by Oleg E. Kiselyov

Pieter Meulenhoff KPN Research -
We are using ROOT to store and analyse data from a wide range of ICT platforms in order to get detailed insight in their behaviour. A very successfull application is MLPA (Multi Layer Packet Analysis), a software tool based on ROOT. MLPA is used to monitor and analyse the quality and performance of \'i-mode\': a new version of wireless Internet based on the GPRS network (a packet switched wireless network). MLPA captures and stores the \'Key Performance Indicators\' of i-mode/GPRS traffic in ROOT format. Using this data we can do analysis like calculation of \'Quality of Service\', marketing information, network planning and fraud detection.

Chris Crawford MIT-LNS MIT-Bates
Commissioning BLAST with ROOT ROOT has been sucessfully employed in the environment of a medium energy nuclear experiment, BLAST, with limited resources for software. Most aspects of the experiment, including slow controls, data aquisition, simulation, and analysis have been integrated into the ROOT framework, making use of its tree, histrogram, matrix, GUI, sockets, and MySQL features. We started commissioning BLAST in June, and will show how ROOT is specially useful in this unique and transient phase.

Reiner Rohlfs ISDC INTEGRAL
Image Display and AstroRoot An image display with good performance and powerful color selection is very important for astronomical data analysis. I will demonstrate the new image class TASImage which was developed with these requirements in mind. TASImage is available in ROOT version 3.03.08 and can be used not only for astronomical data. But this image class will be the base for further astronomical image displays with astronomical coordinate systems and access to FITS files. We plan to maintain a AstroRoot library with ROOT classes useful for astronomical data analysis like a AstroImage. A first version of AstroROOT is available with functions to read and write FITS files within ROOT.

Wouter Verkerke UC Santa Barbara babar
RooFit is a library of C++ classes that facilitate data modelling in the ROOT environment. Mathematical concepts such as variables, (probability density) functions and integrals are represented as C++ objects. The package provides a flexible framework for building complex fit models through classes that mimic math operators, and is straightforward to extend. For all constructed models RooFit provides a concise yet powerful interface for fitting (binned and unbinned likelihood, chi^2), plotting and toy Monte Carlo generation as well as sophisticated tools to manage large scale projects. RooFit has matured into an industrial strength tool capable of running BaBars most complicated fits. We are currently in the final stages of separating RooFit from BaBar and to provide it as a HEP-wide accessible OpenSource tool hosted SourceForge. The migration is expected to be complete by the time of the workshop.

Philippe Canal Fermilab -
Presentation of the improvement of the ROOT I/O sub-system regarding reading and writing instances of classes that have not been instrumented for ROOT. We will present the new features as well as the implementation that made them possible.

Philippe Canal Fermilab -
Presentation of the new features available in TTree::Draw

William Tanenbaum Fermilab cms
The C++ Software Simulation/Reconstruction/Analysis Framework used by the Compact Muon Solenoid (CMS) at the LHC has now been converted from Objectivity to ROOT/IO for persistent data storage. The conversion was done without a significant redesign of the persistent objects. Issues that arose during the conversion will be discussed, as well as a comparison of ROOT and Objectivity.

Masaharu Goto Agilent Technologies CINT
(Preliminarily) CINT evolves as usage of ROOT framework grows. Tips and progresses about frequently asked questions in ROOT/CINT mailing list (STL, va_arg, etc...) will be discussed.

Andrei Gheata CERN alice
The new ROOT geometry package is a tool designed for building, browsing, tracking and visualizing a detector geometry. The code works standalone with respect to any tracking Monte-Carlo engine, therefore it does not contain any constraints related to physics. However, the package defines a number of hooks in order to ease-up tracking, allowing user-defined objects to be attached to the basic architectural structures. The modeling functionalities were designed to optimize particle transport thorough complex geometries and they are accessible in an easy and transparent way. The package is currently under development and new features will be implemented, but the basic functionality has already been extensively tested on several detector geometries. The final goal is to be able to use the same geometry for several purposes, such as tracking, reconstruction or visualization, taking advantage of the ROOT features related to bookkeeping, I/O, histograming, browsing and graphical interfaces.

Perevoztchikov Victor BNL atlas
Automated support for STL containers without using code generated by rootcint. abstract In this paper we present generic approach of working with STL containers, vector and list. Special interface class TSTLCont, allows wide access to these containers without concrete instantiation of templates. Iteration over containers, adding, deletion and I/O of entries is allowed in a completely general way. It gives the posibility of ROOT I/O, TTree spliting and merging , without code generation by rootcint.

Perevoztchikov Victor BNL atlas
General purpose ROOT utilities. abstract Some ROOT utilities was developped for general usage. These utilities are experiment independent: - General helix object: THelixTrack, with fitting, steping, crossing and nearest points; - Iteration over TTree files: TTreeIter; - General wild card iteration via set of files and directories : TDirIter; - Heap memory statistics: TMemStat; - Unix time transformations: TUnixTime.

Perevoztchikov Victor BNL atlas
ROOT foreign class I/O in the LCG framework. abstract The general I/O application in the LCG framework is developped. It is based on ROOT foreign classes and formally ROOT independent. Also cross references of non ROOT classes between different files is proposed, as a generalization of TRef approach.

Valeri Fine Brookhaven National Laboratory atlas
Cross-Platform Qt-Based Implementation of Low Level ROOT Graphical Layer. A version of the ROOT analysis framework based on the cross platform GUI package ``Qt\'\' from Trolltech will be presented. Qt-based ROOT consists of a standard ROOT installation with the addition of two additional shared libraries, libQt and libQtGui. Even though there were successful attempts to build applications based on ROOT and Qt packages they have not affected the ROOT itself. It still needed to contain the separate platform depended (X11 or Win32) parts. That is not easy to maintain and error prone. The present approach allows the ROOT developer as well as ROOT user to work with code that has no X11/ WIN32 graphics subsystem dependencies and at the same time opens unrestricted access to a rich set of ready-to-use commercial and free GUI Qt-based widgets. The Qt-based version was tested on Unix and Windows and available from the US Atlas group CVS repository

Oliver Kuehlert Uni Marburg / MPI-K 8Li
Our realtime measurement system ELISABET is based upon RTLinux and ROOT. The communication between the ROOT GUI widgets and the realtime kernel threads is done by FIFOs. There are some interface classes using the ROOT thread-system. The collected data can be analysed immediately.

Pere Mato CERN lhcb
Using ROOT classes in Python We present a prototype of interfacing the ROOT framework with the Python scripting language. This interface has been implemented as a Python extension module and it facilitates the interaction of any ROOT class, either from the Python shell prompt or within a Python script. This ROOT/Python gateway has been developed in a generic way, without the need of wrapping each class individually, by means of using the ROOT/CINT object dictionary and providing a generic mapping between the ROOT types and the Python types. Extending Python with the ROOT classes would allow us rapid development of applications integrating ROOT together with any of the numerous off-the-self software components in many domains areas that also come with their Python extension module.

David Chamont LLR - Ecole Polytechnique cms
USE OF ROOT I/O TREES FOR THE GENERATION OF CMS CROSSINGS. The simulation of CMS raw data requires the reading of few hundred random events from a very large chain of trees, and requires their pileup in memory. It is quite unusual inside ROOT to take the events NOT sequentially and to treat them NOT one by one. Also, we kept the original data classes unmodified as far as possible, taking profit of the new ROOT I/O support for foreign classes. We will show where ROOT I/O has proved useful and discuss deficiencies.

Subir Sarkar INFN-Rome cdf
JavaRoot: An Automatic Java Native Interface to Root JavaRoot is an attempt to generate Java Native Interface (JNI) to the Root classes automatically, using the native Root introspection API. The resulting interface allows Java and Jython programs transparent access to the Root libraries for application development and rapid prototyping. The features already available in JavaRoot as well as the important ones missing in the present version will be discussed. JavaRoot will be demonstrated with Root tutorial examples written in Java and Jython. Benchmark results will also be presented by implementing a part of the original Root benchmark suite.

Valeriy Onuchin CERN, IHEP IT division
Status of the Carrot development (http://carrot.cern.ch). Based on ROOT framework which is using C++ as scripting language, it has a number of powerful features, including the ability to embed C++ code into HTML pages, run interpreted and compiled C++ macros, dynamically extend framework with external libraries, access and manipulate databases, and generate graphics on-the-fly, among many others.

Federico Carminati CERN alice
The ALICE Offline Project has started back in 1998 the development of an entirely ROOT-based framework, AliRoot. This has been successful and we are now testing it in large scale distributed productions and analysis challenges. The development of this framework is the work of a large distributed community and follows closely the development paradigm adopted by ROOT. This talk will present the development strategy, the achievements and the future plans of AliRoot together with the relations with the LCG project.

Hans Essel GSI GSI Experiment Data Processing
Go4 production version 2: Status and overview Go4 developed at GSI provides an analysis framework including a non blocking GUI. Analysis and GUI run in separate tasks communicating through threads and sockets. The GUI is implemented in Qt using GSI\'s QtROOT interface. A Go4 analysis may use any ROOT features. It can be built by several analysis steps. Each step can be controlled from the GUI, e.g. specification of the IO. The composite event model includes tree/branch management. The Go4 browser/tree viewer handles these trees without limitations in hierarchy.

Denis Bertini GSI-Darmstadt Go4
The Go4 composite event. The Go4 Composite event classes use a composite pattern to provide a simple API that ease the modeling of complex event structures. The IO of composite event objects is provided ( ROOT tree and branches ). The synchronization of the event objects with the TTree data structure is done dynamically via a recursive procedure. Hence the data storage and retrieval is done without explicit programming. Arbitrary hierarchy levels of composite events can be browsed by the GO4Browser.

Mohammad Al-Turany GSI GSI Experiment Data Processing
Go4 GUI: a Multiple Document Interface (MDI)application based on ROOT and GSI\'s QtROOT interface. The further development of GSI\'s QtROOT and the multiple document interface GUI of Go4 will be represented. Through the last one and half year, QtROOT interface has proved to be stable. It is maintainable with minimum effort with the rapidly growing versions of ROOT and Qt. The full functionality of both ROOT and Qt are supported. This made it possible to design and implement the Go4 GUI as an MDI application in an environment where ROOT threads, sockets, and timers are heavily used. The new features available in the Go4 GUI will be demonstrated.

J�rn Adamczewski GSI Go4
The Go4 eventloop framework (analysis steps) The new GSI analysis system Go4 offers a flexible eventloop framework that may process any kind of analysis both in batch mode, and in GUI-controlled multithreaded online mode. Go4 defines a set of event base classes (abstract interface); the user can implement these as experiment typical subclasses. For general tasks (e.g. TTree IO) there are framework plugins provided. The Go4 analysis singleton manages and executes subsequent analysis steps. Each analysis step consists of implementations for event source, input event structure, event processor, output event structure, and event store. An abstract factory pattern creates the step specific event classes on initialization. The setup of each step can be controlled from the Go4 GUI at runtime.

Sergey Linev GSI Darmstadt Go4
Go4Fit package. The main aim of Go4Fit package is to provide powerful and extendable way to model and fit experimental data (mostly beta- and gamma-spectra). The Go4Fit package introduces a set of C++ classes, represented data objects (like histograms), models (shapes like gaussian), minimizer (Minuit) and parameters dependencies. The different types of fit function (Chi-square, maximum likelihood) can be used. The central TGo4Fitter class is developed to contain full setup, necessary to perform one fit. Any set of models can be fit in one minimization process to any number of data objects. Beside minimization Go4Fit offer a fast method to estimate model amplitudes (via matrix calculations). The package is independent of Go4. The user interface is currently CINT. The development of a GUI is underway.

Ivana Hrivnacova IPN, Orsay alice
Title: Virtual Monte Carlo The Virtual Monte Carlo interface allows to run different simulation Monte Carlo programs without changing the user code. The interface classes, now included in Root, concrete implementations for Geant3 and Geant4 and simple examples of usage will be presented. The concept of Virtual Monte Carlo has been developed by the ALICE Software Project. Recently, the relevant packages have been separated from the AliRoot framework and can be used stand-alone. The implementation for Fluka is now under development.

schutz yves - alice
ALICE data organisation, Folders & I/O (Y.Schutz) Alice consists in a set of independent but collaborative detectors. This structure is reflected in the AliRoot framework through individual and independant packages organized at the detector level. In the same spirit the IO structure is segmented at the detector level. During run time objects in memory are posted to a whiteboard, making use of the ROOT TFolder class, and structured by detectors and event objects. A dedicated object provides the necessary services to access and exchange data between cooperating detectors. The tasks to be performed on events (merging, digitisation, reconstruction) are steered by a general service and are also organised by detectors and type of tasks. They are posted to the whiteboard and make use of the ROOT TTask class.

Peter Elmer Princeton University BaBar
BaBar has been using ROOT I/O as the basis for a micro analysis format since 1999. The evolution and experience with this system with ever larger datasets will be described and current topics of interest will be presented. In addition, preliminary studies done to evaluate the use as a contingency plan for the entire event persistency system in BaBar will be discussed.

George Irwin Stanford University Minos
ROOT is an important element in Minos software. We summarize areas where Minos is using ROOT in special ways. These include the data model and event I/O, database interface, signal-slot and GUI extensions. We also cover our interest in new ROOT developments in the areas of geometric modelling, template support and documentation.

Maarten Ballintijn MIT phobos
Presenting PROOF, the Parallel ROOT Facility ============================================ We\'ll present the concepts and ideas underlying the PROOF system. Discuss the implementation and status. We\'ll explain the framework components needed to make use of it. Finally we\'ll show the direction and plans for future developments. Demo of the PROOF system ======================== We\'ll show how to setup and configure a PROOF cluster and how to make an analysis of a large data-set using the selector framework and PROOF.

Mathias Beck AEM/INTEGRAL Science Data Centre INTEGRAL
ROOT at the ISDC ================ INTEGRAL is a gamma ray mission of the European Space Agency (ESA). The satellite will be launched on October 17, 2002. The INTEGRAL Science Data Center (ISDC) will process the data and make it available to the science community. The monitoring of the four main instruments on board of INTEGRAL will be performed at ISDC with the help of display tools that were developped using ROOT. I/O routines for astronomical data formats have been made available in the ROOT framework for interactive scientific analysis.

Isidro Gonzalez Caballero - alice
G4UIRoot is a GUI for GEANT4 built using ROOT toolkit. It fully integrates into Geant4 and brings together the strengths of the GEANT4 user interface and ROOT capabilities. It provides, among other capabilities, a full graphical access (as well as normal command line access) to the Geant4 command tree (including help and tips), separated windows for standar and error ouput, command history saving, and integrated ROOT interpreter. This last feature allows for interactive histograming of the results and may allow in the future a new way to control the simulation at run time.

Mathieu de Naurois LPNHE Paris VII/VIII HESS
I will report on the use of ROOT on the HESS DAQ software. We use ROOT in a multithreaded environement together with CORBA for a distributed object oriented acquisition and for a on-line \"on-the-fly\" analysis.

Richard Dubois SLAC GLAST
GLAST is prototyping the use of Carrot for its System Test facility. We are tying a suite of tests to our code release system, in which multiple test configurations are run for each release. The results are tracked in an Oracle database, including metadata for detailed histogram output from the tests. These test will be compared to standard versions, with those comparisons stored in the database. The Carrot facility is being used to query Oracle to locate the test versions and display the results, both for retrieving histograms on demand, including overplotting the standards; but also to be able to dynamically plot performance metrics out of the database. We will discuss our experiences in developing with Carrot, including issues of security of the Carrot plugin. GLAST uses Gaudi for its C++ framework and Root for persistency. At present, the native Gaudi interface is not suitable for producing analyzable Root files in the persistent data store. We have written custom Algorithms to make the converters for the transient and persistent stores. We will investigate properly using the Converter mechanism. We will also show our current Event layout.

Piergiorgio Cerello - GPCALMA
Computer Assisted Diagnosis in Mammography: a distributed system based on ROOT/PROOF The INFN-CALMA project developed in the past years a neural network based algorithm for the analysis of mammograms. The tool, already used in several hospitals, significantly improved the sensibility of the radiologist\'s diagnosis (about 10%). In order to set up a distributed grid-like system for mammographic screening and telediagnosis, a new architecture, based on ROOT/PROOF is being developed. In addition to the already existing functionality, the ROOT based graphic interface allows interactive actions on the image, required by radiologists. The PROOF functionality will be used for the remote analysis of mammograms: only the selected images (about 1-2%) will be transferred, in real time, to the diagnostic site. A Data and Metadata catalogue must also be configured, most likely using the AliEn-ROOT interface now under development.

Torre Wenaus BNL/CERN atlas
The LCG and ROOT The LHC Computing Grid Project (LCG) will be introduced, with particular attention to the Applications Area of the LCG which is concerned with the development of physics applications software that is common across the LHC experiments. The role of ROOT with respect to the LCG will be described.

Nuno Almeida ADETTI/FCUL atlas
Evaluating queries and data storage on a Grid using ROOT.

Dirk Duellmann CERN IT/DB LCG
The LCG POOL Project and ROOT The LCG POOL project will be presented with particular emphasis on the use of RootI/O as object streaming technology and its integration with other storage technologies such as RDBMS.

name	institute	experiment

Fons Rademakers	CERN	alice
Status of ROOT in the areas of PROOF and GRID interfacing.

Rene Brun	CERN	alice
ROOT Status. Recent developments

Eddy Offermann	Renaissance Technologies	-
TMatrix class == At Renaissance Technologies, the ROOT framework is used to test new ideas for predicting price moves of financial instruments. Researchers can easily insert their new predictive sources into a simulator by supplying a C++ script to ROOT/CINT. This package requires a significant amount of matrix manipulations. Therefore, we are in the process of extending the functionality of the TMatrix class, originally developed by Oleg E. Kiselyov

Pieter Meulenhoff	KPN Research	-
We are using ROOT to store and analyse data from a wide range of ICT platforms in order to get detailed insight in their behaviour. A very successfull application is MLPA (Multi Layer Packet Analysis), a software tool based on ROOT. MLPA is used to monitor and analyse the quality and performance of \'i-mode\': a new version of wireless Internet based on the GPRS network (a packet switched wireless network). MLPA captures and stores the \'Key Performance Indicators\' of i-mode/GPRS traffic in ROOT format. Using this data we can do analysis like calculation of \'Quality of Service\', marketing information, network planning and fraud detection.

Chris Crawford	MIT-LNS	MIT-Bates
Commissioning BLAST with ROOT ROOT has been sucessfully employed in the environment of a medium energy nuclear experiment, BLAST, with limited resources for software. Most aspects of the experiment, including slow controls, data aquisition, simulation, and analysis have been integrated into the ROOT framework, making use of its tree, histrogram, matrix, GUI, sockets, and MySQL features. We started commissioning BLAST in June, and will show how ROOT is specially useful in this unique and transient phase.

Reiner Rohlfs	ISDC	INTEGRAL
Image Display and AstroRoot An image display with good performance and powerful color selection is very important for astronomical data analysis. I will demonstrate the new image class TASImage which was developed with these requirements in mind. TASImage is available in ROOT version 3.03.08 and can be used not only for astronomical data. But this image class will be the base for further astronomical image displays with astronomical coordinate systems and access to FITS files. We plan to maintain a AstroRoot library with ROOT classes useful for astronomical data analysis like a AstroImage. A first version of AstroROOT is available with functions to read and write FITS files within ROOT.

Wouter Verkerke	UC Santa Barbara	babar
RooFit is a library of C++ classes that facilitate data modelling in the ROOT environment. Mathematical concepts such as variables, (probability density) functions and integrals are represented as C++ objects. The package provides a flexible framework for building complex fit models through classes that mimic math operators, and is straightforward to extend. For all constructed models RooFit provides a concise yet powerful interface for fitting (binned and unbinned likelihood, chi^2), plotting and toy Monte Carlo generation as well as sophisticated tools to manage large scale projects. RooFit has matured into an industrial strength tool capable of running BaBars most complicated fits. We are currently in the final stages of separating RooFit from BaBar and to provide it as a HEP-wide accessible OpenSource tool hosted SourceForge. The migration is expected to be complete by the time of the workshop.

Philippe Canal	Fermilab	-
Presentation of the improvement of the ROOT I/O sub-system regarding reading and writing instances of classes that have not been instrumented for ROOT. We will present the new features as well as the implementation that made them possible.

Philippe Canal	Fermilab	-
Presentation of the new features available in TTree::Draw

William Tanenbaum	Fermilab	cms
The C++ Software Simulation/Reconstruction/Analysis Framework used by the Compact Muon Solenoid (CMS) at the LHC has now been converted from Objectivity to ROOT/IO for persistent data storage. The conversion was done without a significant redesign of the persistent objects. Issues that arose during the conversion will be discussed, as well as a comparison of ROOT and Objectivity.

Masaharu Goto	Agilent Technologies	CINT
(Preliminarily) CINT evolves as usage of ROOT framework grows. Tips and progresses about frequently asked questions in ROOT/CINT mailing list (STL, va_arg, etc...) will be discussed.

Andrei Gheata	CERN	alice
The new ROOT geometry package is a tool designed for building, browsing, tracking and visualizing a detector geometry. The code works standalone with respect to any tracking Monte-Carlo engine, therefore it does not contain any constraints related to physics. However, the package defines a number of hooks in order to ease-up tracking, allowing user-defined objects to be attached to the basic architectural structures. The modeling functionalities were designed to optimize particle transport thorough complex geometries and they are accessible in an easy and transparent way. The package is currently under development and new features will be implemented, but the basic functionality has already been extensively tested on several detector geometries. The final goal is to be able to use the same geometry for several purposes, such as tracking, reconstruction or visualization, taking advantage of the ROOT features related to bookkeeping, I/O, histograming, browsing and graphical interfaces.

Perevoztchikov Victor	BNL	atlas
Automated support for STL containers without using code generated by rootcint. abstract In this paper we present generic approach of working with STL containers, vector and list. Special interface class TSTLCont, allows wide access to these containers without concrete instantiation of templates. Iteration over containers, adding, deletion and I/O of entries is allowed in a completely general way. It gives the posibility of ROOT I/O, TTree spliting and merging , without code generation by rootcint.

Perevoztchikov Victor	BNL	atlas
General purpose ROOT utilities. abstract Some ROOT utilities was developped for general usage. These utilities are experiment independent: - General helix object: THelixTrack, with fitting, steping, crossing and nearest points; - Iteration over TTree files: TTreeIter; - General wild card iteration via set of files and directories : TDirIter; - Heap memory statistics: TMemStat; - Unix time transformations: TUnixTime.

Perevoztchikov Victor	BNL	atlas
ROOT foreign class I/O in the LCG framework. abstract The general I/O application in the LCG framework is developped. It is based on ROOT foreign classes and formally ROOT independent. Also cross references of non ROOT classes between different files is proposed, as a generalization of TRef approach.

Valeri Fine	Brookhaven National Laboratory	atlas
Cross-Platform Qt-Based Implementation of Low Level ROOT Graphical Layer. A version of the ROOT analysis framework based on the cross platform GUI package ``Qt\'\' from Trolltech will be presented. Qt-based ROOT consists of a standard ROOT installation with the addition of two additional shared libraries, libQt and libQtGui. Even though there were successful attempts to build applications based on ROOT and Qt packages they have not affected the ROOT itself. It still needed to contain the separate platform depended (X11 or Win32) parts. That is not easy to maintain and error prone. The present approach allows the ROOT developer as well as ROOT user to work with code that has no X11/ WIN32 graphics subsystem dependencies and at the same time opens unrestricted access to a rich set of ready-to-use commercial and free GUI Qt-based widgets. The Qt-based version was tested on Unix and Windows and available from the US Atlas group CVS repository

Oliver Kuehlert	Uni Marburg / MPI-K	8Li
Our realtime measurement system ELISABET is based upon RTLinux and ROOT. The communication between the ROOT GUI widgets and the realtime kernel threads is done by FIFOs. There are some interface classes using the ROOT thread-system. The collected data can be analysed immediately.

Pere Mato	CERN	lhcb
Using ROOT classes in Python We present a prototype of interfacing the ROOT framework with the Python scripting language. This interface has been implemented as a Python extension module and it facilitates the interaction of any ROOT class, either from the Python shell prompt or within a Python script. This ROOT/Python gateway has been developed in a generic way, without the need of wrapping each class individually, by means of using the ROOT/CINT object dictionary and providing a generic mapping between the ROOT types and the Python types. Extending Python with the ROOT classes would allow us rapid development of applications integrating ROOT together with any of the numerous off-the-self software components in many domains areas that also come with their Python extension module.

David Chamont	LLR - Ecole Polytechnique	cms
USE OF ROOT I/O TREES FOR THE GENERATION OF CMS CROSSINGS. The simulation of CMS raw data requires the reading of few hundred random events from a very large chain of trees, and requires their pileup in memory. It is quite unusual inside ROOT to take the events NOT sequentially and to treat them NOT one by one. Also, we kept the original data classes unmodified as far as possible, taking profit of the new ROOT I/O support for foreign classes. We will show where ROOT I/O has proved useful and discuss deficiencies.

Subir Sarkar	INFN-Rome	cdf
JavaRoot: An Automatic Java Native Interface to Root JavaRoot is an attempt to generate Java Native Interface (JNI) to the Root classes automatically, using the native Root introspection API. The resulting interface allows Java and Jython programs transparent access to the Root libraries for application development and rapid prototyping. The features already available in JavaRoot as well as the important ones missing in the present version will be discussed. JavaRoot will be demonstrated with Root tutorial examples written in Java and Jython. Benchmark results will also be presented by implementing a part of the original Root benchmark suite.

Valeriy Onuchin	CERN, IHEP	IT division
Status of the Carrot development (http://carrot.cern.ch). Based on ROOT framework which is using C++ as scripting language, it has a number of powerful features, including the ability to embed C++ code into HTML pages, run interpreted and compiled C++ macros, dynamically extend framework with external libraries, access and manipulate databases, and generate graphics on-the-fly, among many others.

Federico Carminati	CERN	alice
The ALICE Offline Project has started back in 1998 the development of an entirely ROOT-based framework, AliRoot. This has been successful and we are now testing it in large scale distributed productions and analysis challenges. The development of this framework is the work of a large distributed community and follows closely the development paradigm adopted by ROOT. This talk will present the development strategy, the achievements and the future plans of AliRoot together with the relations with the LCG project.

Hans Essel	GSI	GSI Experiment Data Processing
Go4 production version 2: Status and overview Go4 developed at GSI provides an analysis framework including a non blocking GUI. Analysis and GUI run in separate tasks communicating through threads and sockets. The GUI is implemented in Qt using GSI\'s QtROOT interface. A Go4 analysis may use any ROOT features. It can be built by several analysis steps. Each step can be controlled from the GUI, e.g. specification of the IO. The composite event model includes tree/branch management. The Go4 browser/tree viewer handles these trees without limitations in hierarchy.

Denis Bertini	GSI-Darmstadt	Go4
The Go4 composite event. The Go4 Composite event classes use a composite pattern to provide a simple API that ease the modeling of complex event structures. The IO of composite event objects is provided ( ROOT tree and branches ). The synchronization of the event objects with the TTree data structure is done dynamically via a recursive procedure. Hence the data storage and retrieval is done without explicit programming. Arbitrary hierarchy levels of composite events can be browsed by the GO4Browser.

Mohammad Al-Turany	GSI	GSI Experiment Data Processing
Go4 GUI: a Multiple Document Interface (MDI)application based on ROOT and GSI\'s QtROOT interface. The further development of GSI\'s QtROOT and the multiple document interface GUI of Go4 will be represented. Through the last one and half year, QtROOT interface has proved to be stable. It is maintainable with minimum effort with the rapidly growing versions of ROOT and Qt. The full functionality of both ROOT and Qt are supported. This made it possible to design and implement the Go4 GUI as an MDI application in an environment where ROOT threads, sockets, and timers are heavily used. The new features available in the Go4 GUI will be demonstrated.

J�rn Adamczewski	GSI	Go4
The Go4 eventloop framework (analysis steps) The new GSI analysis system Go4 offers a flexible eventloop framework that may process any kind of analysis both in batch mode, and in GUI-controlled multithreaded online mode. Go4 defines a set of event base classes (abstract interface); the user can implement these as experiment typical subclasses. For general tasks (e.g. TTree IO) there are framework plugins provided. The Go4 analysis singleton manages and executes subsequent analysis steps. Each analysis step consists of implementations for event source, input event structure, event processor, output event structure, and event store. An abstract factory pattern creates the step specific event classes on initialization. The setup of each step can be controlled from the Go4 GUI at runtime.

Sergey Linev	GSI Darmstadt	Go4
Go4Fit package. The main aim of Go4Fit package is to provide powerful and extendable way to model and fit experimental data (mostly beta- and gamma-spectra). The Go4Fit package introduces a set of C++ classes, represented data objects (like histograms), models (shapes like gaussian), minimizer (Minuit) and parameters dependencies. The different types of fit function (Chi-square, maximum likelihood) can be used. The central TGo4Fitter class is developed to contain full setup, necessary to perform one fit. Any set of models can be fit in one minimization process to any number of data objects. Beside minimization Go4Fit offer a fast method to estimate model amplitudes (via matrix calculations). The package is independent of Go4. The user interface is currently CINT. The development of a GUI is underway.

Ivana Hrivnacova	IPN, Orsay	alice
Title: Virtual Monte Carlo The Virtual Monte Carlo interface allows to run different simulation Monte Carlo programs without changing the user code. The interface classes, now included in Root, concrete implementations for Geant3 and Geant4 and simple examples of usage will be presented. The concept of Virtual Monte Carlo has been developed by the ALICE Software Project. Recently, the relevant packages have been separated from the AliRoot framework and can be used stand-alone. The implementation for Fluka is now under development.

schutz yves	-	alice
ALICE data organisation, Folders & I/O (Y.Schutz) Alice consists in a set of independent but collaborative detectors. This structure is reflected in the AliRoot framework through individual and independant packages organized at the detector level. In the same spirit the IO structure is segmented at the detector level. During run time objects in memory are posted to a whiteboard, making use of the ROOT TFolder class, and structured by detectors and event objects. A dedicated object provides the necessary services to access and exchange data between cooperating detectors. The tasks to be performed on events (merging, digitisation, reconstruction) are steered by a general service and are also organised by detectors and type of tasks. They are posted to the whiteboard and make use of the ROOT TTask class.

Peter Elmer	Princeton University	BaBar
BaBar has been using ROOT I/O as the basis for a micro analysis format since 1999. The evolution and experience with this system with ever larger datasets will be described and current topics of interest will be presented. In addition, preliminary studies done to evaluate the use as a contingency plan for the entire event persistency system in BaBar will be discussed.

George Irwin	Stanford University	Minos
ROOT is an important element in Minos software. We summarize areas where Minos is using ROOT in special ways. These include the data model and event I/O, database interface, signal-slot and GUI extensions. We also cover our interest in new ROOT developments in the areas of geometric modelling, template support and documentation.

Maarten Ballintijn	MIT	phobos
Presenting PROOF, the Parallel ROOT Facility ============================================ We\'ll present the concepts and ideas underlying the PROOF system. Discuss the implementation and status. We\'ll explain the framework components needed to make use of it. Finally we\'ll show the direction and plans for future developments. Demo of the PROOF system ======================== We\'ll show how to setup and configure a PROOF cluster and how to make an analysis of a large data-set using the selector framework and PROOF.

Mathias Beck	AEM/INTEGRAL Science Data Centre	INTEGRAL
ROOT at the ISDC ================ INTEGRAL is a gamma ray mission of the European Space Agency (ESA). The satellite will be launched on October 17, 2002. The INTEGRAL Science Data Center (ISDC) will process the data and make it available to the science community. The monitoring of the four main instruments on board of INTEGRAL will be performed at ISDC with the help of display tools that were developped using ROOT. I/O routines for astronomical data formats have been made available in the ROOT framework for interactive scientific analysis.

Isidro Gonzalez Caballero	-	alice
G4UIRoot is a GUI for GEANT4 built using ROOT toolkit. It fully integrates into Geant4 and brings together the strengths of the GEANT4 user interface and ROOT capabilities. It provides, among other capabilities, a full graphical access (as well as normal command line access) to the Geant4 command tree (including help and tips), separated windows for standar and error ouput, command history saving, and integrated ROOT interpreter. This last feature allows for interactive histograming of the results and may allow in the future a new way to control the simulation at run time.

Mathieu de Naurois	LPNHE Paris VII/VIII	HESS
I will report on the use of ROOT on the HESS DAQ software. We use ROOT in a multithreaded environement together with CORBA for a distributed object oriented acquisition and for a on-line \"on-the-fly\" analysis.

Richard Dubois	SLAC	GLAST
GLAST is prototyping the use of Carrot for its System Test facility. We are tying a suite of tests to our code release system, in which multiple test configurations are run for each release. The results are tracked in an Oracle database, including metadata for detailed histogram output from the tests. These test will be compared to standard versions, with those comparisons stored in the database. The Carrot facility is being used to query Oracle to locate the test versions and display the results, both for retrieving histograms on demand, including overplotting the standards; but also to be able to dynamically plot performance metrics out of the database. We will discuss our experiences in developing with Carrot, including issues of security of the Carrot plugin. GLAST uses Gaudi for its C++ framework and Root for persistency. At present, the native Gaudi interface is not suitable for producing analyzable Root files in the persistent data store. We have written custom Algorithms to make the converters for the transient and persistent stores. We will investigate properly using the Converter mechanism. We will also show our current Event layout.

Piergiorgio Cerello	-	GPCALMA
Computer Assisted Diagnosis in Mammography: a distributed system based on ROOT/PROOF The INFN-CALMA project developed in the past years a neural network based algorithm for the analysis of mammograms. The tool, already used in several hospitals, significantly improved the sensibility of the radiologist\'s diagnosis (about 10%). In order to set up a distributed grid-like system for mammographic screening and telediagnosis, a new architecture, based on ROOT/PROOF is being developed. In addition to the already existing functionality, the ROOT based graphic interface allows interactive actions on the image, required by radiologists. The PROOF functionality will be used for the remote analysis of mammograms: only the selected images (about 1-2%) will be transferred, in real time, to the diagnostic site. A Data and Metadata catalogue must also be configured, most likely using the AliEn-ROOT interface now under development.

Torre Wenaus	BNL/CERN	atlas
The LCG and ROOT The LHC Computing Grid Project (LCG) will be introduced, with particular attention to the Applications Area of the LCG which is concerned with the development of physics applications software that is common across the LHC experiments. The role of ROOT with respect to the LCG will be described.

Nuno Almeida	ADETTI/FCUL	atlas
Evaluating queries and data storage on a Grid using ROOT.

Dirk Duellmann	CERN IT/DB	LCG
The LCG POOL Project and ROOT The LCG POOL project will be presented with particular emphasis on the use of RootI/O as object streaming technology and its integration with other storage technologies such as RDBMS.

Back to the ROOT Home Page