This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
2013:groups:tools:eventformats [2013/06/19 12:03] eric.conte [Some ideas to discuss] |
2013:groups:tools:eventformats [2013/06/20 09:10] eric.conte [Some ideas to discuss] |
||
---|---|---|---|
Line 26: | Line 26: | ||
===== Some ideas to discuss ===== | ===== Some ideas to discuss ===== | ||
- | * Using text format (theorist-friendly format :-D). ROOT is rejected ; STDHEP seems to be obsolete. | + | * Using text format. ROOT is rejected ; STDHEP seems to be old. |
* 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: | * 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: | ||
Line 58: | Line 58: | ||
</LesHouchesEvents> | </LesHouchesEvents> | ||
- | * Possibility to store hard-process states and reco objects in a same file. | + | * Possibility to store hard-process states, hadrons and reco objects in a same file. |
- | * 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). | + | * The generation step (hard-process, shower, reco) will be specified by the status-code. |
* 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 80: | Line 80: | ||
</muons> | </muons> | ||
... | ... | ||
- | | + | |
* List of relevant observables for each object collection must be defined. | * 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') ? |