Skip to content

Ability to control the allowed state transitions during a simulation #283

Description

@FlxPo

For now all state transitions are considered possible at each step of the simulation, and transitions are only driven by utility differences between states (a state a is a combination of a sequence of activities, destinations and modes). We know some of the transitions take more time than others to take place: it's easier for people to change modes than to change work, for example.

The long term solution to improve our model is to explicitly model different transition costs (see #196). In the meantime, we can start enabling or disabling transitions manually, so that we can recreate simplified state change dynamics: mode changes are allowed from iteration 5, then destination changes from iteration 8, then activity sequences from iteration 11.

Related issues : #145, #147, #148.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions