| Difference between 'load' and 'timetableLoad' [message #784] |
Wed, 23 May 2012 15:21  |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Hi all,
there are two attributes at <formationTT>: 'load' and 'timetableLoad'.
What is the difference between them?
> load: the real load of the formation while in use
Should 'real' it mean "in contrary to the formation as given at
rollingstock" or should it mean the actual load of a certain day after the
train did actually run? If the latter is meant, it would be a brake in the
philosophy because these 'actual', 'driven' data can be different for each
day and we would then consequently also need attributes like
'actualLength', 'actualMass', 'actualFormation',
'actualBrankingSettings'... At last everything can differ from the
timetable so to provide attribute for the 'driven' parameters would mean
to copy _each_ attribute.
Since the name of the Scheme is 'timetable', one should assume that all of
its descendants are 'timetable' attributes... A timetable is alway a kind
of planning in advance - the data of the already driven trains we do not
call timetable.
From our point of view, 'load' and 'timetableLoad' are redundant. So far,
we only use 'load' but not 'timetableLoad'. Since FBS is a pure planning
system, we only know the load planned in advance and never know the real
load of a train at a certain day. Does that mean that we rather should use
'timetableLoad'?
Best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
