|
- Timestamp:
-
Sep 23, 2015, 3:52:04 PM (9 years ago)
- Author:
-
Bijan Chokoufe Nejad
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v2
|
v3
|
|
101 | 101 | overlapping combinations are excluded. In particular, if a composite particle in |
102 | 102 | the first argument has a constituent in common with a composite particle in the |
103 | | second argument, the combination is dropped. So `combine [incoming lepton, |
104 | | lepton]` constructs all mutual pairings of an incoming lepton with an outgoing |
| 103 | second argument, the combination is dropped. So `combine [incoming lepton, lepton]` constructs all mutual pairings of an incoming lepton with an outgoing |
105 | 104 | lepton, in case `lepton` is an appropriate alias. |
106 | 105 | |
… |
… |
|
111 | 110 | beginning, but for larger subevents, the result is obviously different. |
112 | 111 | |
113 | | The shorthand operator `+` can be also used multiple times, e.g. `[u + d + s]`. |
| 112 | `combine` also has an shorthand operator `+` that can be used multiple times, e.g. `[u + d + s]`. |
114 | 113 | Finally, this can also take a `condition` |
115 | 114 | {{{ |
… |
… |
|
153 | 152 | sort by observable [particles, ref_particle] |
154 | 153 | }}} |
| 154 | `sort` surprisingly sorts the subevent by ''increasing'' value of the observable. So if you want the highest values first, add a minus sign in front of your `observable`. |
155 | 155 | |
156 | 156 | join:: |
… |
… |
|
159 | 159 | join [particles, new_particles] |
160 | 160 | }}} |
161 | | Append the particles of `new_particles` to `particle`, i.e. join the two sets. |
| 161 | Append the particles of `new_particles` to `particles`, i.e. join the two sets. |
162 | 162 | No overlapping entries will be produced. |
163 | 163 | |
… |
… |
|
189 | 189 | ||`Phi`|| unary: absolute azimuthal angle in lab frame || |
190 | 190 | || || binary: Azimuthal distance of two particles in lab frame || |
191 | | ||`Rap`, `Eta` || unary: Rapidity/Pseudorapidity || |
192 | | || || binary: Rapidity/Pseudorapidity difference || |
| 191 | ||`Rap`, `Eta` || unary: Rapidity / Pseudorapidity || |
| 192 | || || binary: Rapidity / Pseudorapidity difference || |
193 | 193 | ||`Dist`|| binary: `sqrt(DeltaEta^2 + DeltaPhi^2)` || |
194 | 194 | ||`kT`|| binary: `2 * min(E_i^2,E_j^2)*(1-cos(Theta_{ij})` || |
… |
… |
|
210 | 210 | So the syntax is similar to the `cuts` but this time `expr` is usually a |
211 | 211 | real/floating expression instead of a logical/boolean one. With this you can, |
212 | | e.g. build the following histograms |
| 212 | e.g., build the following histograms |
213 | 213 | {{{ |
214 | 214 | #!bash |
… |
… |
|
224 | 224 | events are analyzed or written to file. This does not affect the `cuts` that are |
225 | 225 | used before matrix elements are even evaluated but applies to the complete |
226 | | event, i.e. with potentially parton showers and hadronization: |
| 226 | event, i.e. potentially with parton showers and hadronization: |
227 | 227 | {{{ |
228 | 228 | #!bash |
|