You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
introduce "scaling" config param in "global" config section.
change the "dependent" params (flowCapFactor, storCapFactor, countsScaleFactor, ...) such that they only correct the global parameter. This could either be as an additional multiplicator. Or as an override. The latter might be easier to refactor, since one could set the default to "null" and then, if these params are not set explicitly, they are set from the global param. On the other hand, this would mean automagic, which in general we do not like.
Make sure that outputs are scaled. For example, emissionsByM should be scaled up to 100%.
For the "tables" (trips, persons, legs, acitivites, etc.), we could add "weights" to the individual persons. For example, for a scaling of 0.1 the weights would be uniformly "10". Many surveys have weights for individual records, so use the same approach here.
The text was updated successfully, but these errors were encountered:
Should include the following:
The text was updated successfully, but these errors were encountered: