First working interface
Added appropriate index (RunIndex, LuminosityBlockIndex or StreamID) needed from the threaded framework.
Conform to new Principal types constructors which require passing in the appropriate index instance (RunIndex, LuminosityBlockIndex or StreamID). The index is needed for the threaded framework.
Allowed default value for StreamID in constructor in order to match the signature of the previous API.

This avoids having to deal with porting changes to the EventPrincipal constructor calls outside of the framework (there are 2 such cases). When we move to the threaded processing those cases will have to be modified anyway to account for multiple Events running simultaneously.
Provide access to the indexes (RunIndex, LuminosityBlockIndex or StreamID).

These indexes are needed to access per transition data in the threaded framework.
Fixed spacing issue
Three otherwise unrelated framework changes needed for the new mixing feature for premixed pileup stored as raw data..

1) Add a new function, setRunAndLumiNumber, to class EventPrincipal.

2) Remove an unused data member, procPset_, from class WorkerParams.

3) The current class "Schedule" does (at least) three different things:
a) Manage the schedule (e.g. paths, end paths, etc.)
b) Manage unscheduled (i.e. on demand) execution of modules
c) Manage the workers, which in turn manage the modules.
Functions b) and c) are removed from "Schedule" and moved to a new class, "WorkerManager".

This tagset has been fully tested. All relvals pass.

--- Tagset history ---
2013-06-13 20:31:50 - Queued by wmtan.
Improve exception message for unscheduled circular dependences

--- Tagset history ---
2013-06-19 18:03:39 - Queued by wdd.
Adapted to use new consumes API
Add missing dictionaries (132522, 132552, 132467)

Signed-off-by: David Abdurachmanov <David.Abdurachmanov@cern.ch>
A new feature whose purpose is to allow the DataMixingModule to mix premixed pileup that is stored as raw data.  A new python configuration file is added to DataMixingModule to support this.
The C++ changes in this tagset are also needed for this feature, but are much more general than that.  What the C++ changes really do is to give the DataMixingModule the ability to run producers (or filters) on demand in the secondary event (the event read by the secondary input source).
The (regular) MixingModule could be easily have given the same capability with trivial changes to the C++ code in SimGeneral/MixingModule.  This is not done because it introduces an undesirable dependency on an unrelated feature (new TrackingParticle), which also touches SimGeneral/MixingModule.

--- Tagset history ---
2013-06-14 21:59:44 - Queued by wmtan.
Adapt to the new multithreaded API.
Adapt to a minor pending change in the framework, by freezing the product registry through a non-const pointer, rather than a const pointer.  The "setFrozen()" function is currently a const function, although it modifies the class.  For thread safety reasons, mutable members of the ProductRegistry will be made non-mutable, making setFrozen() a non-const function.  When that happens, this package will no longer compile.
This tag has no dependency on that framework change, because the non-const pointer is already supported, so it can be picked up before that framework change.  This tagset does have other dependencies due to prior tags on Mixing/Base.

--- Tagset history ---
2013-06-26 01:15:55 - Queued by wmtan.
Adapt to a minor pending change in the framework, by freezing the product registry through a non-const pointer, rather than a const pointer.  The "setFrozen()" function is currently a const function, although it modifies the class.  For thread safety reasons, mutable members of the ProductRegistry will be made non-mutable, making setFrozen() a non-const function.  When that happens, this package will no longer compile.
This tag has no dependencies, because the non-const pointer is already supported, so it can be picked up before the framework change.

--- Tagset history ---
2013-06-26 01:13:29 - Queued by wmtan.
prepare for the multithreaded framework by making the mutable data members of ProductRegistry nonmutable, and doing the same for some of the mutable data members of other registries. All member functions that modify these data members that were "const" functions were changed to non-const.

--- Tagset history ---
2013-06-26 20:24:28 - Queued by wmtan.
2013-06-26 20:30:35 - Commented by wmtan: All these tags, and those of all dependencies, were committed and tagged in CVS before the git migration.
Moved functionality from OutputWorker to OutputModuleCommunicator

The Schedule class was doing a dynamic_cast<OutputWorker> on all workers in order to communicate with the OutputModule. This will not work when we go to the threaded framework since there will be several different OutputModule types with different workers. The solution was to abstract the communication with the OutputModule into a OutputModuleCommunication base class.
Revert "Remove PackageList.cmssw"

This reverts commit 911204040085b7eebd478484efc06feb64f53e20.
Make unit test fail immediately if one of the cmsRun commands fail
Fix unit test errors
Fix unit test errors