<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
I compiled a couple of features people would like to see when<br>
using rivet.<br>
<br>
<br>
The default behaviour should probably be to have histograms<br>
for each item in the weightcontainer.<br>
Sherpas, Herwigs and Pythias would like to tell<br>
Rivet which weightnames of the container in hepmc<br>
they want histograms for as they tend to abuse the weight<br>
containers for debug info etc. This should be done using<br>
regexes just like the -m -M switches, I would propose<br>
-W and -w for that purpose.<br>
<br>
Similarly for plotting. The whole nominals central weight discussion<br>
could be circumvented if we <br>
<ul>
<li>check on initialisation if there is more than one weight in
the first place<br>
</li>
<li>treat all weights the same, i.e. always write out
PATH[weightname]</li>
<li>tell the plotter what the central weight is --- if there is
more than 1</li>
<li>If there is just one histogram per observable only plot that
of course<br>
</li>
</ul>
<p>In that way one would be most flexible whilst retaining the
rivet2<br>
cmdline of rivet-mkhtml bla.yoda<br>
</p>
<p>For the multiweightcase one could do</p>
<p>rivet-mkhtml -c "Weight" -e MUR -E PDF_2610 output.yoda<br>
</p>
<p>i.e. specify the central weightname and use regex magic to
determine what goes into <br>
the envelope and what does not.<br>
</p>
<p>That would also make rivet immune to changs in the standard
naming<br>
for variations. From the feedback I got here, people are not too
happy<br>
having to obey to the MUF_MUR_PDF naming scheme.<br>
</p>
<br>
Any non-trivial thoughts on that? ;)<br>
<br>
Holger<br>
<br>
</body>
</html>