hosted by CEDAR HepForge

Ticket #185 (new task)

Opened 2 years ago

Last modified 1 month ago

Test and document procedure for using Rivet on the Grid

Reported by: buckley Assigned to: fsiegert
Priority: major Milestone: Release 1.2.2
Component: General Version:
Keywords: Cc:

Description

We definitely want to be able to use Rivet on the Grid (we were asked about this at HERA-LHC), and in principle there's nothing to stop it from working. However, the shared libraries make life a bit harder - we probably need to do something similar to Herwig++, who tar up all the libraries (with .la files removed), put them on a Web server and send a Grid job script which starts with wget ...; tar xzf ...!

Once we've worked out a procedure that works, it should be written up on a wiki page.

Change History

06/07/09 15:39:20 changed by buckley

  • milestone changed from Version 1.2 to 1.1.4 release.

01/03/10 18:58:29 changed by buckley

  • milestone changed from Version 1.2.0 to Version 1.3.0.

22/04/10 14:31:34 changed by buckley

  • milestone changed from Release 1.3.0 to Release 1.2.2.

21/06/10 23:58:56 changed by buckley

  • owner changed from jmonk to fsiegert.

Frank, since you actually have a script that does this, is there any chance you can throw together a minimal wiki page to document the process? If the script can be added to Rivet, even better! It would be really nice to finally tick off this annoying ticket, but I'm not the person to do it ;)

28/06/10 09:57:25 changed by fsiegert

I'm not quite sure what we want that is specific to Rivet? My "scripts" all just do the normal Grid stuff around a normal Rivet job.

The only thing that might be worth thinking about is whether we should add Rivet to some VO's software installation (pheno sounds most natural) such that users could require its presence on the node instead of having to send it with them (or relying on /afs). On the other hand we could piggy-back on ATLAS's software installation, which (as far as I can tell) is also usable by non-ATLAS users and includes a complete Rivet copy (although currently its share directory is broken, but I've reported that to the ATLAS kit mailing list).

28/06/10 10:52:13 changed by buckley

Piggybacking on ATLAS sounds fine, although the old HepMC version will make life annoying for some analyses. For that and other reasons (e.g. we do validation and tuning runs with unreleased versions), I think we should also document how to distribute a personal Rivet build with plugin analyses, personal HepMC, fastjet, etc. builds, and have it work properly. That probably falls under "normal Grid stuff", but it's a long-term blank spot in my knowledge, and I guess will be a blocker for others, too. I've set up a RivetOnGrid wiki page... if you can put anything informative in there, it would be a big help. Thanks :)