[Rivet] [Rivet-svn] r2850 - in trunk: . bin pyext

Frank Siegert frank.siegert at cern.ch
Fri Feb 25 22:28:36 GMT 2011


Hi Andy,

> Author: buckley
> Date: Thu Dec 16 17:06:03 2010
> New Revision: 2850
>
> Log:
> Various small improvements to histo parsing, histo paths, plot files, etc.
>
> Modified: trunk/pyext/lighthisto.py
> ==============================================================================
> --- trunk/pyext/lighthisto.py	Tue Dec 14 11:47:37 2010	(r2849)
> +++ trunk/pyext/lighthisto.py	Thu Dec 16 17:06:03 2010	(r2850)
> @@ -553,10 +550,12 @@
>                           vm = self.pat_property.match(line)
>                           if vm:
>                               prop, value = vm.group(1,2)
> +                            #print prop, value
>                               ret[section][prop] = value
>                       elif section in ['SPECIAL']:
>                           ret[section] += line
>                   f.close()
> +                break
>           return ret[section]
>
>

Without this "break" it would allow for local overwriting of histogram 
options. Use case: I want to plot the Z pT in the MC_ZJETS analysis, 
which extends from 1 GeV to sqrt(s)/2. For some reason I only want to 
plot from 1 GeV to 100 GeV in my current setup. I could now copy all the 
settings for /MC_ZJETS/Z_pT from MC_ZJETS.plot into a local 
MC_ZJETS.plot file and add my XMin and XMax. But I'd prefer to only have 
to add a MC_ZJETS.plot containing my XMin and XMax, i.e. all options 
which I don't specify there should be taken from the default plotting file.
Does that make sense? Any objections to recreating the old behaviour?

Cheers,
Frank

PS: I think this should be the last one from my side, do we release on 
Monday or have I overlooked something? I need to install this for a 
school soon, and would like to use the 1.5.0 release.


More information about the Rivet mailing list