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 | ||
2015:groups:tools:lhaad:proposal [2015/06/23 18:54] nishita.desai [Open Questions/Comments] |
2015:groups:tools:lhaad:proposal [2015/07/03 07:15] suchita.kulkarni |
||
---|---|---|---|
Line 3: | Line 3: | ||
====== Open Questions/Comments ====== | ====== Open Questions/Comments ====== | ||
- D: Maybe the overall description comment should start with '###' as in Python to distinguish from normal '#' comments which the parser should just ignore | - D: Maybe the overall description comment should start with '###' as in Python to distinguish from normal '#' comments which the parser should just ignore | ||
- | * S: The proposal concerning '#' is a really tricky thing. I am not sure we should do this. However, at the moment I don't have a better proposal. | + | * S: The proposal concerning '#' is a really tricky thing. How about including three single quotes like in python docstrings? or /* description*/ like in c++ |
- D: See 'detectorobj' description: A 'take external' selection could clearly point out those objects which have to be defined on a fundamental level in whatever program one uses | - D: See 'detectorobj' description: A 'take external' selection could clearly point out those objects which have to be defined on a fundamental level in whatever program one uses | ||
- D: What is the difference between 'doc' and 'code'? Can't the 'doc' contain everything, including the code? | - D: What is the difference between 'doc' and 'code'? Can't the 'doc' contain everything, including the code? | ||
- | * 'doc' is a link to a human-readable document. 'code' is the name of the function/link to the function (for when they make a library of functions). | + | * N: 'doc' is a link to a human-readable document. 'code' is the name of the function/link to the function (for when they make a library of functions). |
- D: What is the purpose of 'eff' in the cuts and what distinguishes a 'trigger' selection from a normal 'select'? | - D: What is the purpose of 'eff' in the cuts and what distinguishes a 'trigger' selection from a normal 'select'? | ||
- | * There is no difference between 'trigger' and 'cut'. In the original version, one could have aribitrary xml tags, so I thought it'd be nice to have explicit names. Now, everything should be a 'cut'. | + | * N: There is no difference between 'trigger' and 'cut'. In the original version, one could have aribitrary xml tags, so I thought it'd be nice to have explicit names. Now, everything should be a 'cut'. |
- | * The eff is an estimated efficiency for things like the trigger/b-tagging etc. provided by the experiments. We should in principle also allow inclusion of efficiency tables instead of a single number. | + | * N: The eff is an estimated efficiency for things like the trigger/b-tagging etc. provided by the experiments. We should in principle also allow inclusion of efficiency tables instead of a single number. |
- D: In cuts, I again would rather use 'take' instead of 'contains': if 'B' uses the events from A, then 'A takes the events from B' (but 'B contains the events from A, as A applies more cuts') | - D: In cuts, I again would rather use 'take' instead of 'contains': if 'B' uses the events from A, then 'A takes the events from B' (but 'B contains the events from A, as A applies more cuts') | ||
- | * Maybe 'include' instead of 'take'? The idea behind 'contains' was a generic inheritance (not just for cuts) where any block can inherit from any other. | + | * N: Maybe 'include' instead of 'take'? The idea behind 'contains' was a generic inheritance (not just for cuts) where any block can inherit from any other. |
- D: Is it possible to use '|' instead of .OR.? the dot to me always refers to a member of a class. | - D: Is it possible to use '|' instead of .OR.? the dot to me always refers to a member of a class. | ||
- | * I don't see why not (or even a c-like || which is easier for a human to read than a single |). | + | * N: I don't see why not (or even a c-like || which is easier for a human to read than a single |). |
Line 53: | Line 53: | ||
info analysis | info analysis | ||
# Details about experiment | # Details about experiment | ||
- | id ATLAS-2014-XXX | + | id SUSY-2013-15 |
publication JHEP11(2014)118 | publication JHEP11(2014)118 | ||
sqrtS 8.0 | sqrtS 8.0 | ||
lumi 20.0 | lumi 20.0 | ||
+ | arXiv 1407.0583 | ||
+ | hepdata https://atlas.web.cern.ch/Atlas/GROUPS/PHYSICS/PAPERS/SUSY-2013-15/ | ||
</code> | </code> | ||
<code autoconf> | <code autoconf> | ||
Line 183: | Line 185: | ||
==== results ===== | ==== results ===== | ||
==== cutflow ===== | ==== cutflow ===== | ||
+ | <code autoconf> | ||
+ | info MCsamples | ||
+ | ### All information concerning signal and background generation goes here | ||
+ | signal Sherpa1.4.1 stop-pair | ||
+ | background POWHEG ttbar mtop = 172.5 NLO | ||
+ | table maasinfo | ||
+ | doc http://singalgenerator.generate | ||
+ | doc _benchmark_SLHA_ | ||
+ | doc _MG5_model_files_ | ||
+ | </code> | ||
==== table ===== | ==== table ===== | ||
- | + | <code autoconf> | |
+ | table massinfo | ||
+ | cut pdgid mass | ||
+ | tN_diag 1000022 1 | ||
+ | 1000006 700 | ||
+ | </code> | ||
====== Examples ====== | ====== Examples ====== | ||
==== ATLAS, 1 Lepton Stop Search ==== | ==== ATLAS, 1 Lepton Stop Search ==== | ||
[[http://arxiv.org/abs/1407.0583|Link]] | [[http://arxiv.org/abs/1407.0583|Link]] | ||
- |