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 07:57] eric.conte [Some ideas to discuss] |
2013:groups:tools:eventformats [2013/06/20 09:10] eric.conte [Some ideas to discuss] |
||
---|---|---|---|
Line 17: | Line 17: | ||
===== Motivations ===== | ===== Motivations ===== | ||
- | * defining a format sample for jet-clustering output (without fast-simulation detector). | + | * defining a format for jet-clustering output (without fast-simulation detector). |
- | * LHCO contains too few information for performing sophisticated analysis. Need to add more variables. | + | * defining a format which extends the LHCO content (too few information for performing sophisticated analysis). |
- | * LHCO does not take into account all Delphes3 potential. | + | * the new format will take into account all Delphes 3 potential. |
===== Some ideas to discuss ===== | ===== Some ideas to discuss ===== | ||
- | * Using text format (theorist-friendly format :-D). ROOT is rejected. | + | * Using text format. ROOT is rejected ; STDHEP seems to be old. |
- | * Keeping the structure of the existing LHE Format (arXiv:hep-ph/0609017) and its XML tags. Name of the format extension: eLHE (e for 'extended') ? Reminder: | + | * 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 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. | + | * The generation step (hard-process, shower, reco) will be specified by the status-code. |
- | * Optional substructure in <event> block: defining a XML for each collection of objects. Several collections of a same objects (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. |
<hardprocess> | <hardprocess> | ||
+ | ... | ||
</hardprocess> | </hardprocess> | ||
<jets> | <jets> | ||
+ | ... | ||
</jets> | </jets> | ||
<jets name="substructure John Hopkins algo"> | <jets name="substructure John Hopkins algo"> | ||
+ | ... | ||
</jets> | </jets> | ||
<electrons> | <electrons> | ||
+ | ... | ||
</electrons> | </electrons> | ||
<muons> | <muons> | ||
+ | ... | ||
</muons> | </muons> | ||
... | ... | ||
- | | ||
+ | * List of relevant observables for each object collection must be defined. | ||
+ | |||
+ | * Name of the format extension: eLHE (e for 'extended') ? |