[Rivet] yoda2root

[Hannes Jung]

Hi Andy

thanks a lot for your reply, and happy new year :)

I tried with your suggestion, this is what happens:
------------
~/jung/cvs/myrivet2/DYjets/files-Jindrich/test> export PYTHONPATH=$PYTHONPATH:/sw/lib/root
~/jung/cvs/myrivet2/DYjets/files-Jindrich/test> echo $PYTHONPATH
/Users/jung/jung/cvs/rivet-2.6.0/lib/python2.7/site-packages:/Users/jung/jung/cvs/rivet-2.6.0/lib/python2.7/site-packages::/sw/lib/root
~/jung/cvs/myrivet2/DYjets/files-Jindrich/test> yoda2root Pythia.root
Fatal Python error: PyThreadState_Get: no current thread
zsh: abort      yoda2root Pythia.root
------------

Hm.... I didn't had it working before ... so it was my first test :)

Thanks a lot
cheers
Hannes


> On 9. Jan 2018, at 15:54, Andy Buckley <andy.buckley at cern.ch> wrote:
> 
> Hi Hannes,
> 
> So the configuration seems to have detected your ROOT installation and been happy with it. The problem is at runtime: did you have this working before?
> 
> ROOT's Python interface is not installed into the Python search path for some reason, so all (?) users need to add the ROOT library directory to their PYTHONPATH. I think if you do that then it should work ok.
> 
> I tested with ROOT6, and there have been some Python API changes between those versions, but I think we've managed to handle both... and your build log suggests that there wasn't a compilation problem, so hopefully everything will be fine once the path is set to point at ROOT.
> 
> Andy
> 
> Dr Andy Buckley, Lecturer / Royal Society University Research Fellow
> Particle Physics Experiment Group, University of Glasgow
> 
> On Dec 30 2017, at 5:51 pm, Hannes Jung <hannes.jung at desy.de> wrote: 
> Dear experts
> 
> I am trying to use yoda2root with the latest version 2.6.0
> and get the following error:
> ----------------
> ~/jung/cvs/myrivet2/DYjets/files-Jindrich> yoda2root Pythia.yoda
> Traceback (most recent call last):
>   File "/Users/jung/jung/cvs/rivet-2.6.0/bin/yoda2root", line 26, in <module>
>     import ROOT
> ImportError: No module named ROOT
> ----------------
> 
> I didn't see any error in the installation, below is a part from the configure
> 
> Any idea, what goes wrong ?
> Thanks a lot, and best wishes for 2018
> 
> Cheers
> Hannes
> 
> PS:
> Part from the configuration of yoda:
> ------------------
> checking how to hardcode library paths into programs... immediate
> checking if the g++ -std=c++11 compiler accepts the -pedantic flag... yes
> checking if the g++ -std=c++11 compiler accepts the -Wall flag... yes
> checking if zlib is wanted... yes
> checking for inflateEnd in -lz... yes
> checking zlib.h usability... yes
> checking zlib.h presence... yes
> checking for zlib.h... yes
> checking for root-config... /Users/jung/bin/root-config
> checking ROOT version... 5.34/34 (5,34,34)
> configure: Building extra ROOT compatibility tools
> checking for python... /usr/bin/python
> checking for a version of Python >= '2.1.0'... yes
> checking for a version of Python >= '2.7.3'... yes
> checking for the distutils Python package... yes
> checking for Python include path... -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7
> checking for Python library path... -L/System/Library/Frameworks/Python.framework/Versions/2.7/lib -lpython2.7
> checking for Python site-packages path... /Library/Python/2.7/site-packages
> checking python extra libraries...
> checking python extra linking flags...
> checking consistency of all components of python development environment... yes
> checking for python version... 2.7
> checking for python platform... darwin
> checking for python script directory... ${prefix}/lib/python2.7/site-packages
> checking for python extension module directory... ${exec_prefix}/lib/python2.7/site-packages
> checking for Cython >= 0.23.5... no
> checking for pyext/yoda/core.cpp... yes
> checking if the g++ -std=c++11 compiler accepts the -Wno-unused-but-set-variable flag... no
> checking if the g++ -std=c++11 compiler accepts the -Wno-sign-compare flag... yes
> checking if the g++ -std=c++11 compiler accepts the -Wno-strict-prototypes flag... yes
> configure: All Python build checks successful: 'yoda' Python extension will be built
> checking for doxygen... /sw/bin/doxygen
> checking that generated files are newer than configure... done
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating Doxyfile
> config.status: creating include/Makefile
> config.status: creating include/YODA/Makefile
> config.status: creating src/Makefile
> config.status: creating src/tinyxml/Makefile
> config.status: creating src/yamlcpp/Makefile
> config.status: creating tests/Makefile
> config.status: creating pyext/Makefile
> config.status: creating pyext/setup.py
> config.status: creating pyext/yoda/Makefile
> config.status: creating bin/Makefile
> config.status: creating bin/yoda-config
> config.status: creating yodaenv.sh
> config.status: creating yoda.pc
> config.status: creating include/YODA/Config/DummyConfig.h
> config.status: include/YODA/Config/DummyConfig.h is unchanged
> config.status: creating include/YODA/Config/YodaConfig.h
> config.status: include/YODA/Config/YodaConfig.h is unchanged
> config.status: creating include/YODA/Config/BuildConfig.h
> config.status: include/YODA/Config/BuildConfig.h is unchanged
> config.status: executing depfiles commands
> config.status: executing libtool commands
> 
> ************************************************************
> YODA CONFIGURED!
> 
> Now build and install (to the /Users/jung/jung/cvs/rivet-2.6.0 tree) with e.g.
> make -j2 && make -j2 install
> ************************************************************
> ------------------
> 
> 
> ***********************************************************************
> Hannes Jung 
> Email: Hannes.Jung at desy.de <mailto:Hannes.Jung at desy.de> 
> mobile :+49 40 8998 93741
> http://www.desy.de/~jung <http://www.desy.de/~jung>                                        
> Tel: +49 (0) 40 8998 3741         
> Fax: +49 (0) 40 8994 3741
> DESY, CMS 01B/02.213
> Notkestr.85, 22603 Hamburg, FRG   
> ***********************************************************************
> 
> 
> 
> 
> 
> _______________________________________________ 
> Rivet mailing list 
> Rivet at projects.hepforge.org 
> https://www.hepforge.org/lists/listinfo/rivet

***********************************************************************
Hannes Jung 
Email: Hannes.Jung at desy.de 
mobile :+49 40 8998 93741
http://www.desy.de/~jung                                        
Tel: +49 (0) 40 8998 3741         
Fax: +49 (0) 40 8994 3741
DESY, CMS 01B/02.213
Notkestr.85, 22603 Hamburg, FRG   
***********************************************************************





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.hepforge.org/lists-archive/rivet/attachments/20180109/14c34fee/attachment.html>