Architecture team and Intercategory designinterface Makoto Asai SLAC

Architecture team and Inter-category design/interface Makoto Asai (SLAC) 10/Oct/2002 Geant 4 delta-review 10/10/2002 G 4 deltareview Architecture team & inter-category design/interface

Outline This presentation addresses to the recommendation #4. 7 There should be an overall design authority to coordinate and review the design from individual working groups. Architecture team was officially formed in July 2001 (TSB-15), and is continuously active since then. In this presentation, I will summarize activities done and currently undergoing in Architecture team. 10/10/2002 G 4 delta-review Architecture team & inter-category design/interface 2

Outline Architecture team Makoto Asai (coordinator) Gabriele Cosmo Hisaya Kurashige Hans-Peter Wellisch John Apostolakis (ex-officio) Architecture team had video- and phone-meetings and mini-workshops in addition to E-mail discussions for issues Affecting to more than one categories Concerning to the major requirements which are not relevant to address to one particular working group For the discussion of individual issue, Architecture team invites developers in corresponding working groups. 10/10/2002 G 4 delta-review Architecture team & inter-category design/interface 3

Items discussed at A-team Event biasing and tally Cuts per region G 4 Exception G 4 VTrajectory Maintenance of User Requirements Document Foreseen items G 4 Step Global test suites Maintenance of design documents 10/10/2002 G 4 delta-review Architecture team & inter-category design/interface 4

Event biasing and tally Requirements from anonymous users Affects on Run, Event, Readout, Digits+Hits, Tracking, Track, Geometry, Particle and Processes categories Mini-workshop @ SLAC, November 2001 Design study for tally is on going while several implementation of various event biasing options have already been done and released in Geant 4 4. 1 (Jul. 2002) Need to be discussed Validation procedures 10/10/2002 G 4 delta-review Architecture team & inter-category design/interface 5

Cuts per region Requirement first from Ba. Bar, and then from Atlas and CMS Affects on Run, Tracking, Track, Geometry, Particle and Processes categories First “tentative” implementation for “Cuts per material” in Geant 4 4. 0 (Dec. 2001) Mini-workshop @ CERN, June 2002 Solid design was completed and release is planned in Geant 4 5. 0 (Dec. 2002) 10/10/2002 G 4 delta-review Architecture team & inter-category design/interface 6

G 4 Exception Requirements from anonymous users Improve amount and quality of information when G 4 Exception occurs Avoid unnecessary core dump User handle, e. g. to store histograms, before core dump Affects on ALL categories New scheme was fixed and migration is on going Different behavior for different severity Core dump Run abortion Event abortion Warning New abstract class for exception handling, which user 10/10/2002 G 4 delta-review Architecture team & inter-category design/interface 7

G 4 VTrajectory Requirements from anonymous users Draw smoothly curved trajectory Pick trajectory information via event display Select trajectories to be drawn by user’s criteria l e. g. trajectories only Pt > 5 Ge. V/c Trace back generation hierarchy Store user information in more convenient way Affects on Event, Tracking, Geometry, Graphics-reps, Intercoms, Interfaces and Visualization categories First draft of global design was made and currently under examination of working groups 10/10/2002 G 4 delta-review Architecture team & inter-category design/interface 8

Summary Architecture team is effectively active to take responsibilities to Coordination of global design Coordination of general requirements Management of global quality of the product 10/10/2002 G 4 delta-review Architecture team & inter-category design/interface 9