Steering Rivet

At some level this is the users responsibility, and the Rivet library should have a clean enough interface that people can use it from many applications.

However, we do require such an interface ourselves for use by JetWeb?. This is a separate HepForge? project called RivetGun.

Below is some remaining discussion which is rivet-relevant and not covered elsewhere yet.

Processes

A Model does not in fact necessarily uniquely define a subprocess, since (for example) a particular Model may describe several physical processes (e.g. you might use a single set of parameters to describe minimum bias and low ET jet running) and several subprocesses may be required to simulate a single physical process in a given Model (e.g. resolved and direct photoproduction).

Thus the Rivet steering mechanism should be able to work out, from the input Model, what process(es) it needs to run. This may include more than one event generation loop.

Of course, the generator specific parts of this should be obtained by the Steering from the RivetGenerators interface.