Linear Collider Forum

Home » Software Tools » LCIO » Meeting Minutes
Minutes of Meeting 2004-06-21 [message #114 is a reply to message #112] Mon, 05 July 2004 00:54 Go to previous messageGo to previous message
Messages: 233
Registered: January 2004
Location: DESY, Hamburg

1) Status f77, Java, C++

2) New developments
a) user extensions
b) transient collections
and multiple containment
c) parameters for collections
events and runs

3) Release plans

4) Other points


1) HV: extended and modified fortran examples to be (almost fully)
compatible with the C++ examples.
added documentation for reconstruction data model .
modified array indices to be consistently (1,n)
added LCStrVec for user extensions in C++ and f77

TJ: experimented with Java code for the LCRelations to see how
the interface can be made easy to use and efficient to access
relations in both directions.
also experimenting with user interfaces for other classes, e.g.
stdhep, is there a need for an additional interface that is
exposed to the users or not ?

FG: implemented subdetectorHitNumbers[] and subdetectorEnergies[]
for tracks and clusters respectively and radiusOfInnermostHit for
changed int type to flag word for tracks, clusters and
reconstructed particles.
all changes for java, c++, f77.

2) a) Agreement that we would like to have a simple version of user
extension objects, provided that they can be described with our
current XML-dtd.

b) TJ: having mutliple containment of an element in several
collections, is possible in Java anyhow; another way of passing
subcollections between modules would be to add predecate classes
similar to what is available in the LCD-software.
FG: wants to have a look at predecate approach to understand the

TJ: wants the possibility to add 'anything' to the event and LCIO
should simply ignore unknown data types during writing.
FG: flagging sth. as transient is more general, i.e. users can
also flag collections of exisiting LCIO classes as transient.
for C++ 'anything' has to be limited to 'anything inheriting from
need to make sure that LCIO doesn't crash when sth. unknown is
in the event !
all: agreement to add some transient flag to LCCollection.

c) FG: proposes to have simply LCParameters class, holding named
attributes of the base types int, float, string, that can be added
to the LCRun, LCEvent and LCCollection. this can then be used for
example to define the meaning of bits in the type word of tracks,
clusters and recontructed particles.
TJ: need a way to assign/map attributes like 'bit0' to a
particular type of data, i.e. tracks.
FG: would have to be done via meaningful names, e.g.
'TrackTypeBitTPC = 0'
TJ: would like a way to decode this information automatically and
transparent to the user.
FG: don't konw whether this is possible, will probably always need
some additional information from somewhere else.
TJ: could maybe use XML description for that
FG: will implement something so that all can see how things might
work in practise.

3) all: agreement to have another beta release before the Victoria
workshop (July 28) that has all the main new features and data
classes in it

4) plans to have an LCIO meeting at SLAC in the second week of
August (9-13)
Read Message
Read Message icon2.gif
Read Message feedback.gif
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic:segfaulting PIDHandler in python
Goto Forum:

Current Time: Tue Mar 19 19:47:52 Pacific Daylight Time 2019
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.1.
Copyright ©2001-2010 FUDforum Bulletin Board Software