Athena Developer Guide

More documents

Recommendations

Info

$' \^' I$

Athena Appendix C Design considerations Version/Issue: 2.0.0 because they can be used by a range of different algorithms. We could have various types of tracking algorithm all using the same data as input and producing similar data as output. On the contrary, the intermediate data types can be designed to be very algorithm dependent. The way we have chosen to communicate between the different Algorithms which constitute our physics algorithm is by using the transient event data store. This allows us to have low coupling between them, but other ways could be envisaged. For instance, we could implement specific methods in the algorithms and allow other “friend” algorithms to use them directly. Concerning the relationships between data objects, it is strongly discouraged to have links from the input data objects to the newly produced ones (i.e. links from hits to tracks). In the other direction this should not be a problem (i.e from tracks to constituent hits). For data types that we would like to save permanently we need to implement a specific Converter. One converter is required for each type of data and each kind of persistency technology that we wish to use. This is not the case for the data types that are used as intermediate data, since these data are completely transient. C.4.3 Mathematics and other utilities It is clear that to implement any algorithm we will need the help of a series of utility classes. Some of these classes are very generic and they can be found in common class libraries. For example the standard template library. Other utilities will be more high energy physics specific, especially in cases like fitting, error treatment, etc. We envisage making as much use of these kinds of utility classes as possible. Some algorithms or algorithm-parts could be designed in a way that allows them to be reused in other similar physics algorithms. For example, perhaps fitting or clustering algorithms could be designed in a generic way such that they can be used in various concrete algorithms. During design is the moment to identify this kind of re-usable component or to identify existing ones that could be used instead and adapt the design to make possible their usage. page 186
Athena Version/Issue: 2.0.0 Appendix D Installation guide 19.6 Overview Installation of Athena at a remote site involves the following major components. 1. Installation of external packages. These should generally be very stable such that this procedure need not be repeated very frequently. 2. Installation of the GAUDI package. This is currently being modified frequently, and typically a new version is necessary for each Athena release. It is obviously hoped that eventually this will reach a level of functionality where installation of a new version will not be necessary for every Athena release. 3. Installation of the ATLAS release. 19.6.1 Acknowledgements The following abreviated guide is a summary of more detailed information that is available from the following sources: 1. Kristo Karr (Affiliation?) has put together a set of web pages that details installation instructions for various ATLAS releases accessible from the Trigger Web page at: URL The most recent set of such instructions (for ATLAS release 1.2.2) are located at: http://atddoc.cern.ch/Atlas/EventFilter/documents/importing_athena_122.html page 187
Page 1 and 2:
ATLAS Athena The ATLAS Common Frame
Page 3 and 4:
Athena Table of Contents Version/Is
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Athena Chapter 1 Introduction Versi
Page 11 and 12:
Athena Chapter 1 Introduction Versi
Page 13 and 14:
Athena Chapter 2 The framework arch
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Athena Chapter 3 Release notes Vers
Page 21 and 22:
Athena Chapter 4 Establishing a dev
Page 23 and 24:
Athena Chapter 5 Writing algorithms
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Athena Chapter 6 Scripting Version/
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Athena Chapter 7 Accessing data Ver
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Athena Chapter 8 StoreGate - the ev
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Athena Chapter 9 Data dictionary Ve
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Athena Chapter 10 Detector Descript
Page 77 and 78:
Athena Chapter 11 Histogram facilit
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Athena Chapter 12 N-tuple and Event
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Athena Chapter 13 Framework service
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Athena Chapter 14 Tools and ToolSvc
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136: Athena Chapter 14 Tools and ToolSvc
Page 137 and 138: Athena Chapter 15 Converters Versio
Page 147 and 148: Athena Chapter 16 Visualization Ver
Page 149 and 150: Athena Chapter 17 Physical design i
Page 157 and 158: Athena Chapter 18 Framework package
Page 169 and 170: Athena Chapter 19 Analysis utilitie
Page 171 and 172: Athena Version/Issue: 2.0.0 Appendi
Page 173 and 174: Athena Appendix B Options for stand
Page 181 and 182: Athena Appendix C Design considerat
Page 183 and 184: Athena Appendix C Design considerat
Page 185: Athena Appendix C Design considerat
Page 189 and 190: Athena Version/Issue: 2.0.0 19.6.6
Page 191 and 192: Athena Version/Issue: 2.0.0 A AIDA
Page 193 and 194: Athena Version/Issue: 2.0.0 of N-tu
Page 195: Athena Version/Issue: 2.0.0 ROOT 17
show all

Athena Developer Guide

Create successful ePaper yourself

Delete template?

Save as template?