<div dir="ltr">Hi Guys,<div><br></div><div>I'll also include Roman. Maybe he still has some of his validation plots. </div><div><br></div><div>Cheers,</div><div>Florian</div><div class="gmail_extra"><br><div class="gmail_quote">On 22 March 2015 at 12:09, Holger Schulz <span dir="ltr"><<a href="mailto:holger.schulz@durham.ac.uk" target="_blank">holger.schulz@durham.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span>
On 20/03/15 16:49, Michaela Queitsch-Maitland wrote:
<blockquote type="cite">
<pre>Hi Holger,
The routine was validated using a gluon fusion MiNLO HJJ sample:
mc12_8TeV.181085.PowhegPythia8_AU2CT10_HJJ_MINLO_ggH125_gamgam.evgen.EVNT.e2005
scaled to XS*BR = 19.27*0.00228. No other production modes were included for the validation. The results from the routine were compared against the analysis code (used to derive the unfolding factors for the data) with very good agreement. The plots in the publication were also reproduced by Roman Lysak (ex ATLAS Rivet contact) using the routine. Unfortunately I don’t have the plots from the ‘final’ version of the routine — Roman would have those.
Let me know if you need anymore information.</pre>
</blockquote></span>
Hi Michaela,<br>
<br>
I was trying to find the generator setup bits for this sample
looking into AMI and the svn browser of MC job options.<br>
It would seem as if powheg (==powhegbox???) parton level outputs
(.LHEF) were simply showered with Pythia8<br>
allowing only for H->gamma gamma decays handled by pythia8. What
I am unable to find are the processes<br>
included when running powheg (box?).<br>
<br>
<br>
These are the JOs:<br>
<br>
<ol>
<li><a href="https://svnweb.cern.ch/trac/atlasoff/browser/Generators/MC12JobOptions/trunk/share/DSID181xxx/MC12.181085.PowhegPythia8_AU2CT10_HJJ_MINLO_ggH125_gamgam.py" target="_blank">https://svnweb.cern.ch/trac/atlasoff/browser/Generators/MC12JobOptions/trunk/share/DSID181xxx/MC12.181085.PowhegPythia8_AU2CT10_HJJ_MINLO_ggH125_gamgam.py</a></li>
<li><a href="https://svnweb.cern.ch/trac/atlasoff/browser/Generators/MC12JobOptions/trunk/common/PowhegPythia8_AU2_CT10_Common.py" target="_blank">https://svnweb.cern.ch/trac/atlasoff/browser/Generators/MC12JobOptions/trunk/common/PowhegPythia8_AU2_CT10_Common.py</a></li>
<li><a href="https://svnweb.cern.ch/trac/atlasoff/browser/Generators/MC12JobOptions/trunk/common/Pythia8_Powheg.py" target="_blank">https://svnweb.cern.ch/trac/atlasoff/browser/Generators/MC12JobOptions/trunk/common/Pythia8_Powheg.py</a></li>
<li><a href="https://svnweb.cern.ch/trac/atlasoff/browser/Generators/MC12JobOptions/trunk/common/Pythia8_LHEF.py" target="_blank">https://svnweb.cern.ch/trac/atlasoff/browser/Generators/MC12JobOptions/trunk/common/Pythia8_LHEF.py</a>
----> brick wall</li>
</ol>
As you can see, the latter just looks for files commonly named "<span>events.lhe" --- with no information whatsoever what
these contain.<br>
<br>
This is a bit dangerous. I would assume that the information on
the processes switched on when generating these files is<br>
stored some other place. Maybe ami would be a good place to store
this kind of information globally.<br>
<br>
So yeah, at this point I cannot consider your plugin validated as
I cannot reproduce your results.<br>
<br>
Best,<br>
Holger<br>
<br>
</span><div><div><br>
<blockquote type="cite">
<pre>Cheers,
Michaela
On 19 Mar 2015, at 20:07, Frank Siegert <a href="mailto:Frank.Siegert@cern.ch" target="_blank"><Frank.Siegert@cern.ch></a> wrote:
</pre>
<blockquote type="cite">
<pre>Hi Holger,
with a plain Sherpa H->gamma gamma setup the BRs will be screwed up,
so a factor of 10 can be expected.
There are new options for the upcoming Sherpa 2.2.0 which allow to fix this:
<a href="http://sherpa.hepforge.org/doc/SHERPA-MC-2.2.0.html#HDH_005fWIDTH" target="_blank">http://sherpa.hepforge.org/doc/SHERPA-MC-2.2.0.html#HDH_005fWIDTH</a>
For Sherpa 2.1.1 you are best off running without BR weights
(HDH_BR_WEIGHTS=0) and multiplying with the correct H->gamma gamma BR
manually at the end.
Cheers,
Frank
On 19 March 2015 at 19:54, Holger Schulz <a href="mailto:holger.schulz@durham.ac.uk" target="_blank"><holger.schulz@durham.ac.uk></a> wrote:
</pre>
<blockquote type="cite">
<pre>Hi Michaela,
in preparation of tomorrows release of Rivet we are currently validating the
contrib plugins
and I am having trouble with yours.
Maybe you could tell me your validation procedure, i.e. which MC you ran
with what channels
and so forth.
I am seeing a factor of 10 discrapancy in a sherpa generic H->gamma gamma
setup.
Best,
Holger
_______________________________________________
Rivet mailing list
<a href="mailto:Rivet@projects.hepforge.org" target="_blank">Rivet@projects.hepforge.org</a>
<a href="https://www.hepforge.org/lists/listinfo/rivet" target="_blank">https://www.hepforge.org/lists/listinfo/rivet</a>
</pre>
</blockquote>
</blockquote>
<pre>_______________________________________________
Rivet mailing list
<a href="mailto:Rivet@projects.hepforge.org" target="_blank">Rivet@projects.hepforge.org</a>
<a href="https://www.hepforge.org/lists/listinfo/rivet" target="_blank">https://www.hepforge.org/lists/listinfo/rivet</a>
</pre>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div></div>