[Rivet] Pluggable analyses branch

Andy Buckley andy.buckley at durham.ac.uk
Wed Sep 12 16:34:29 BST 2007


Lars Sonnenschein wrote:
> Hello Andy
> thank you. It is compiling and linking now.
> Unfortunately the head version of RivetGun 
> (even after I added there the needed Rivet INC path) complains:

> Is the Commandline code incompatible with the pluggable Rivet code?

Yes :) I've only changed Rivet, and these changes affect the whole 
analysis handling mechanism, as used by RivetGun. I'll soon work on a 
RivetGun branch to work with the new Rivet, but for now you can write a 
HepMC event file using e.g. "rivetgun ... -o events.hepmc" and process 
it with "rivet ... events.hepmc". Can you check that this works for you 
and then I'll merge the branch back to trunk once RivetGun is compatible.

If you haven't run "make install" for Rivet, then you'll need something 
like "RIVET_ANALYSIS_PATH=./src/Analysis/.libs ./src/rivet ..." so that 
it searches the right directory to find the standard analysis library. 
You could make your own analysis library, libRivetFoo.so, put it in any of

  * the current directory
  * the directory where libRivet.so is installed
  * a directory listed in RIVET_ANALYSIS_PATH
  * a directory listed in RIVET_ANALYSIS_PATH

and rivet will use its analyses if they provide the same loading 
mechanism as libRivetAnalysisStd.

> P.S.: I will come October 9 to Durham.

Cool - see you soon, then.

Andy


More information about the Rivet mailing list