This allows a simple overriding of event numbers to be in sequence from one
enabling pile-up events to be the same between different samples.


Former-commit-id: f313a615baed70b76fb9efd66e56699012dccae4

python/RunDependentConfig.py, share/RunNumberOverride.py - tweaks to EvtIdModifierSvc configuration.  Second try at also setting the timestamp in digitization jobs when the the run number is overridden. ATCONDDB-21. Tagging: Digitization-01-14-03 (Digitization-01-14-03)

	* python/RunDependentConfig.py, share/RunNumberOverride.py -
	tweaks to EvtIdModifierSvc configuration.  Second try at also
	setting the timestamp in digitization jobs when the the run number
	is overridden. ATCONDDB-21

	* Tagging: Digitization-01-14-03

2015-03-19  John Chapman  <John.Chapman@cern.ch>

	* share/RunNumberOverride.py - set both
	EventSelector.OverrideRunNumberFromInput and
	EventSelector.OverrideRunNumber both to be true. As suggested by
	RD in ATLASSIM-1891. First go at setting the timestamp based on
	looking up the run number (ATCONDDB-21), there will be further
	iterations.

	* Tagging: Digitization-01-14-02

2015-03-19  John Chapman  <John.Chapman@cern.ch>
...
(Long ChangeLog diff - truncated)

python/DigitizationReadMetaData.py - tweak code to check if GeoModelSvc has already been created before trying to check its properties. ATLASRECT-841. Tagging: Digitization-01-10-02 (Digitization-01-10-02)