[Rivet] Problems with Rivet2

Chris Pollard cpollard at cern.ch
Thu Sep 18 10:32:21 BST 2014


Hi Dominic,

The dvips problem seems to be an issue with the latex installation, not
Rivet. I myself don't know how to debug this, but...

Could you give some details about the issues you ran into installing on
CentOS6? The 2.1.2 bootstrap worked without a hitch on the two linux
machines I've run it on.

Chris

On Thu, Sep 18, 2014 at 10:23 AM, Dominic Hirschbuehl <dhirsch at mail.cern.ch>
wrote:

> Hi Andy, all,
>
> I still cannot produce Rivet2 plots with Centos6 / SLC6.
> Are there any ideas, how it could work.
> On lxplus I get:
> Plotting PowhegPDF/ATLAS_2012_I1094568/vetoJetPt_Qsum_4.dat (0
> remaining)
> dvips: ! Couldn't find header file: tex.pro
> dvips: ! Couldn't find header file: tex.pro
> dvips: ! Couldn't find header file: tex.pro
> dvips: ! Couldn't find header file: tex.pro
> dvips: ! Couldn't find header file: tex.pro
> dvips: ! Couldn't find header file: tex.pro
> dvips: ! Couldn't find header file: tex.pro
>
>
> I really need urgently these plots and I don't know what to do.
> I also tried to compile Rivet2 myself on our Centos6 machine, but this
> also doesn't work.
>
> Any help is more than welcome
>  Dominic
>
> On Tue, Sep 02, 2014 at 04:51:01PM +0100, Andy Buckley wrote:
> > On 02/09/14 16:31, David Bjergaard wrote:
> > > It may or may not be helpful, but I've seen weird stuff like this when
> > > asetup or ATLAS tools clobber the PATH so badly that things break.
> > > Restarting from a clean shell (and setting up again) usually does the
> > > trick.
> > >
> > > Is there a way to setup something like 'localSetupRivet' to avoid all
> of
> > > the extra stuff set by asetup?
> >
> > Not that I know of. Using the ATLAS localSetupPython <some obscure
> > version code> can be a convenient way to set up a better compiler &
> > Python than the SLC default, and then you can build your own Rivet (or
> > maybe use the Genser one) but I *hoped* that the setup provided by
> > Athena would be functional for plotting as well as running Rivet and
> YODA.
> >
> > If you have any idea how to get a localSetupRivet into the ATLAS system,
> > that would be great to have and would lower the entry barrier a little
> > more: always important.
> >
> > Andy
> >
> >
> >
> > > Andy Buckley <andy.buckley at cern.ch> writes:
> > >
> > >> Hi Dominic,
> > >>
> > >> Actually the (non-ATLAS) Rivet mailing list is the best place to ask:
> > >> I've CC'd that now.
> > >>
> > >> But I don't know why this is happening. There are sometimes problems
> > >> with latex installations and how they specify the max memory allowed
> by
> > >> a document build (sometimes this is large (by 1980s standards) for
> > >> plotting because there are lots of points and lines on plots). But
> that
> > >> thing with the CentOS machine saying that latex isn't in your path...
> > >> that is weird.
> > >>
> > >> Has anyone else got suggestions?
> > >>
> > >> Andy
> > >>
> > >>
> > >> On 02/09/14 15:37, Dominic Hirschbuehl wrote:
> > >>> Hi Andy, James,
> > >>>
> > >>> Thorsten told me, to write to you, if I have problems with Rivet.
> > >>> Unfortuntaly I don't have much time to really dig into the problems.
> > >>>
> > >>> I first try to use the Rivet version in Athena:
> > >>> asetup devval,64,rel1,slc6
> > >>>
> > >>> I got out a yoda file from the Rivet run ( I will have more
> questions in
> > >>> the next days concering this) but the if I run
> > >>> [hirsch at electron run]$ rivet-mkhtml
> 111003.tt_dilep_hpp_HERA15_7TeV.aida.yoda -o ~/www/Rivet
> > >>>
> > >>> Making 20 plots
> > >>> Plotting
> /common/home/hirsch/www/Rivet/ATLAS_2012_I1094568/d01-x01-y01.dat (19
> remaining)
> > >>> ...
> > >>> dvips: ! DVI file can't be opened.
> > >>> dvips: ! DVI file can't be opened.
> > >>> .. and many more
> > >>>
> > >>>
> > >>> I tried also  to run:
> > >>> rivet-mkhtml 111003.tt_dilep_hpp_HERA15_7TeV.aida.yoda -o
> ~/www/Rivet --pdf
> > >>> with the same output and
> > >>> rivet-mkhtml 111003.tt_dilep_hpp_HERA15_7TeV.aida.yoda -o
> ~/www/Rivet --ps
> > >>> with this output
> > >>> dvips: ! DVI file can't be opened.
> > >>> dvips: ! DVI file can't be opened.
> > >>> dvips: ! DVI file can't be opened.
> > >>> dvips: ! DVI file can't be opened.
> > >>> dvips: ! DVI file can't be opened.
> > >>> dvips: ! DVI file can't be opened.
> > >>> dvips: ! DVI file can't be opened.
> > >>> convert: unable to open image `d01-x01-y01.ps': No such file or
> > >>> directory @ blob.c/OpenBlob/2480.
> > >>> convert: missing an image filename `d01-x01-y01.png'
> @convert.c/ConvertImageCommand/2800.
> > >>>
> > >>>
> > >>> Then I thought I can install Rivet on my own machine (CentOS release
> 6.3 (Final)).
> > >>> The installation worked fine, but I get then the following:
> > >>>
> > >>> hirsch at physd922hirschb files]$ rivet-mkhtml
> 111003.tt_dilep_hpp_HERA15_7TeV.yoda -o ~/www/Rivet
> > >>> ERROR: required program 'latex' could not be found. Exiting...
> > >>>
> > >>> But:
> > >>> [hirsch at physd922hirschb files]$ which latex
> > >>> /usr/bin/latex
> > >>>
> > >>> I have no idea how to proceed.
> > >>>
> > >>> Cheers
> > >>>   Dominic
> > >>>
> > >>>
> > >>>
> >
> >
> > --
> > Dr Andy Buckley, Royal Society University Research Fellow
> > Particle Physics Expt Group, University of Glasgow / PH Dept, CERN
>
> --
>  /---------------------------------------------------------------------\
> |                     Dr. Dominic Hirschbuehl                           |
>  \   Bergische Universitaet Wuppertal - Exp. Elementarteilchenphysik   /
>  /  hirsch at physik.uni-wuppertal.de / dominic.hirschbuehl at cern.ch       \
> |       office : D.09.22    phone  : 0049 - 202 - 439 - 3751           |
>  \---------------------------------------------------------------------/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.hepforge.org/lists-archive/rivet/attachments/20140918/56006f29/attachment.html>


More information about the Rivet mailing list