(Send mail to the whole RTF team)
This is quoted from an email sent by David Quarrie to atlas-sw and
atlas-phys mailing lists, also archived
here (password protected) or here.
RTF mandate
The mandate of the RTF was to perform a design iteration on
the reconstruction, revisiting the granularity of the algorithms and
the event data model in the light of experience gained with the
existing design and feedback from additional requirements such as those
from the HLT. The redesign is to take a "top down" approach that should
take advantage of the existing design, but not be constrained by it.
The deliverable will be a design document containing conceptual class
diagrams for the event data model and dataflow diagrams to show the
main algorithm building blocks and how they fit together with the EDM.
Open Meetings
Soon after the RTF was set up, two open meetings were organised, to
give the software and physics communities an opportunity to provide
input to the RTF and to promote open discussion on reconstruction
requirements, use cases and design. The OAagenda of these two meetings,
with attached talks, are here:
Private Meetings
The RTF meets at least weekly by phone and every 2-3 weeks
face-to-face. Experts are invited as needed.
Work plan
The first thing done by the RTF was to draw up a prioritised "to do"
list. This was based on the mandate, the experience of the team
members, several discussions that the team members have had with
individuals, and not least the input received from the open meetings.
Simon George
Last modified: Wed Mar 12 11:17:41 GMT 2003