[Rivet] HEPMC interface being weird in 2.6.0

[Christian Gutschow]

Ok not quite solved apparently and even weirder:

I’ve copied the hepmc file into my working directory to avoid the leading dots and it runs fine. Exact command:

rivet --ignore-beams --pwd -a ATLAS_2017_I1624693 -H MyOut260.yoda jets.hepmc2g 

Among other things, this routine fills a 2D histograms, and rather than defining the binning manually, I want to book via reference data, which should be doable for 2Ds as of 2.6.0. So I replace this guy

_dalitz = bookHisto2D( "dalitz", 20, -1., 1., 20, -1., 1.);

with this guy

_dalitz  = bookHisto2D(3, 1, 1);
 
in the *routine code* and recompile.

All good so far. Running the same command as above and now it immediately gives up, saying

Could not read from 'jets.hepmc2g'

What. Mind blown.

How is the HEPMC-input file handling correlated with the histogram booking in this way? Any ideas!?

Cheers,
Chris



> On 24 Apr 2018, at 12:03, Christian Gutschow <chris.g at cern.ch> wrote:
> 
> Ahh, yeah it didn’t like the leading dots in "../jets.hepmc2g"
> 
> Thanks Andy! I can work around that :)
> 
> Cheers,
> Chris
> 
> 
>> On 24 Apr 2018, at 11:30, Andy Buckley <andy.buckley at cern.ch> wrote:
>> 
>> Aha, I just ran into the same thing.
>> 
>> Your filename has a dot in the "stem" before the .hepmc* bit, right? Looks like I need to be cleverer in my path parsing to work out if there's a .gz on the end. Probably also an issue in YODA 1.7.
>> 
>> Andy
>> 
>> Dr Andy Buckley, Lecturer / Royal Society University Research Fellow
>> Particle Physics Experiment Group, University of Glasgow
>> On Apr 24 2018, at 8:04 am, Christian Gutschow <chris.g at cern.ch> wrote:
>> 
>> Hi Andy,
>> 
>> I was using:
>> 
>> rivet —ignore-beams -a MyAnalysis —pwd jets.hepmc2g
>> 
>> Nothing too controversial I would have thought...
>> 
>> Cheers,
>> Chris
>> 
>> 
>> Sent from my iPhone
>> 
>> On 23 Apr 2018, at 23:33, Andy Buckley <andy.buckley at cern.ch> wrote:
>> 
>> I'm using custom routines and 2.6.0 without problems. What exact command are you running? Don't think we changed any command-line flag parsing, but I can't think of anything else...
>> 
>> Andy
>> 
>> Dr Andy Buckley, Lecturer / Royal Society University Research Fellow
>> Particle Physics Experiment Group, University of Glasgow
>> On Apr 23 2018, at 4:17 pm, Christian Gutschow <chris.g at cern.ch> wrote:
>> 
>> Hi,
>> 
>> I have a case where using 2.6.0 I can run a standard routine, say MC_JETS, on a local HEPMC file just fine, but when I want to run a custom routine on the same file, it gives up immediately saying:
>> 
>> Could not read from 'jets.hepmc2g'
>> 
>> Same behaviour even if I zip the file. When I switch back to 2.5.4, it works again using both routines.
>> 
>> Any ideas what’s changed / how to fix this?
>> 
>> (I’m using HEPMC 2.06.09)
>> 
>> Cheers,
>> Chris
>> 
>> 
>> —
>> 
>> Dr. Christian Gütschow
>> 
>> Department of Physics and Astronomy
>> University College London
>> Gower Street
>> London WC1E 6BT
>> 
>> 
>> 
>> _______________________________________________
>> Rivet mailing list
>> Rivet at projects.hepforge.org
>> https://www.hepforge.org/lists/listinfo/rivet
>> _______________________________________________
>> Rivet mailing list
>> Rivet at projects.hepforge.org
>> https://www.hepforge.org/lists/listinfo/rivet
> 
> 
> 
> 
>  —
> 
>  Dr. Christian Gütschow
> 
>  Department of Physics and Astronomy
>  University College London
>  Gower Street
>  London WC1E 6BT
> 
> 
> 
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> https://www.hepforge.org/lists/listinfo/rivet




 —

 Dr. Christian Gütschow

 Department of Physics and Astronomy
 University College London
 Gower Street
 London WC1E 6BT