[Rivet] installing rivet as a user

[Emily Nurse]

Hi Andy,

I'm trying to act as a typical CDF user on a CDF machine who wants to  
write a Rivet routine.

To start off I installed Rivet using the rivet-bootstrap script,  
which now works.

Now I am considering the option of using this (or a system) install  
of Rivet on a CDF machine and getting analysis authors to add a  
routine using the standalone analysis instructions here:
http://projects.hepforge.org/rivet/trac/wiki/RivetAnalysis

I was thinking it may be easier for the "user" to have very explicit  
instructions in this section. e.g. to do the following:

(1) download and unpack Rivet tarball
(2) Add analysis code and edit ... (this step is already explicitly  
explained).
(4) run g++ -I./include -l/rivet-install-directory/ ... (rather than  
saying "you may need to specify various include paths")
(4) Set the env variables xxx
(5) Run with command yyy

Obviously with the caveat that the user needs to find out the  
directory Rivet/genser etc are installed. That would be in my CDF/D0  
specific instructions.

Most of this stuff is already on this page, or somewhere else but it  
would be nice to have it explicitly spelt out in one place.

Do you mind if I edit this page to make it more explicit? ie/ treat  
it as instructions for someone who wants to add a routine on a system  
where Rivet is already installed? I could split it into two pages,  
"Writing your own analysis" and "writing a standalone analysis" the  
latter could have these explicit instructions, since the former is  
still valid if someone is using the rivet-bootstrap script and  
installing everything themselves.

A couple of other things I noticed:

(1) The links to code in the "Examples" section in http:// 
projects.hepforge.org/rivet/trac/wiki/RivetAnalysis are broken
(2) I think it'd be simpler to get rid of the code snippet under:  
"Life will probably be easiest if you base your loader file on src/ 
Analysis/StdAnalyses.cc: here's the crucial bit, for your browsing  
pleasure:"
and just have the MyLoader.cc example, since its very straightforward  
to copy and paste that example code into a file. (Is it worth having  
such a file in the package - that the user just edits with the  
analysis routine name?)
(3) I ran with the -histotype ROOT option as most people here won't  
have used Aida files, but nothing got filled in the root output, is  
this functionality working?

Thanks,
Emily.


On 25 Mar 2008, at 07:44, Andy Buckley wrote:

> Emily Nurse wrote:
>> Hi Andy,
>>
>> How are we suggesting that people test their own routines? Should  
>> they
>> install rivet using the rivet-bootstrap script, then add their own
>> source code, or edit ExampleAnalysis.cc? Then just type make; make
>> install; in the Rivet directory?
>
> Better to avoid modifying the Rivet library by making their/your  
> own Analysis
> subclass: see http://projects.hepforge.org/rivet/trac/wiki/ 
> RivetAnalysis
>
> Andy
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> http://www.hepforge.org/lists/listinfo/rivet

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.hepforge.org/lists-archive/rivet/attachments/20080327/6035c404/attachment.htm