This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
2013:groups:tools:eventformats [2013/06/19 11:58] eric.conte [Some ideas to discuss] |
2013:groups:tools:eventformats [2013/06/19 12:03] eric.conte [Some ideas to discuss] |
||
---|---|---|---|
Line 28: | Line 28: | ||
* Using text format (theorist-friendly format :-D). ROOT is rejected ; STDHEP seems to be obsolete. | * Using text format (theorist-friendly format :-D). ROOT is rejected ; STDHEP seems to be obsolete. | ||
- | * Prefering extending an existed formt to defining a totally new one (avoiding coding writer and reader functions from scratch). Our choice is to extend the LHE Format (arXiv:hep-ph/0609017) and its structure based on XML tags. Reminder about the LHE structure: | + | * Prefering extending an existing format to defining a totally new one (avoiding developers from coding writer and reader functions from scratch). Our choice is to extend the LHE Format (arXiv:hep-ph/0609017) and its structure based on XML tags. Reminder about the LHE structure: |
<LesHouchesEvents version="X"> | <LesHouchesEvents version="X"> | ||
Line 60: | Line 60: | ||
* Possibility to store hard-process states and reco objects in a same file. | * Possibility to store hard-process states and reco objects in a same file. | ||
- | * The generation step (hard-process, shower, reco) will be specified by the status code. | + | * The generation step (hard-process, shower, reco) will be specified by the status-code. Question: how to manage the hundred possible status-code values in Pythia 8 ? Potentiel solution: adding an ID-code to vertices (see Les Houches session 1). |
* Optional substructure in <event> block: defining a XML tag for each collection of objects. Several collections of a same object kind (jets in the example) can be defined and used. | * Optional substructure in <event> block: defining a XML tag for each collection of objects. Several collections of a same object kind (jets in the example) can be defined and used. | ||
Line 81: | Line 81: | ||
... | ... | ||
| | ||
+ | * List of relevant observables for each object collection must be defined. | ||
+ | |||
* Name of the format extension: eLHE (e for 'extended') ? | * Name of the format extension: eLHE (e for 'extended') ? |