Global Setting Shared Object

[Christian-B]

There are several many setting which are fixed in the whole system and which do not change over time except for during sim.setup and sim.reset.

Instead of passing these up and down all over the place have a singleton objected shared with everything that holds these.

It will have an interface much like a read only dictionary with a few clearly marked set methods that should only be called from config handler and unit/integration tests.

Values to put in here include.
TimeScaleFactor
MachineTimeStep or the user defined on if we allow multiple ones

All the report and application data folders

It may well hold ALL values set by the cfg files to keep these is on well defined place.

Undecided if it would hold settings decided by the simulator such as the runtime to plan or save data for.

It should NOT hold options created by one algorithm to be passed to the next.

[Christian-B]

Discussing with @dkfellows it is probably better to place hardware descriptions at the top level of the Machine Objects

[Christian-B]

SpiNNakerManchester/SpiNNMachine#215 starts work of moving the Values required before a real Machine obtained to cfg

[Christian-B]

Fixed with SpiNNakerManchester/SpiNNMachine#217