corridor

attributes

entities

class CorridorEntity(name: str = None)

Bases: EntityGroup

attributes: Dict[str, AttributeField] = {'cargo_flow': <movici_simulation_core.core.attribute.AttributeField object>, 'co2_emission': <movici_simulation_core.core.attribute.AttributeField object>, 'delay_factor': <movici_simulation_core.core.attribute.AttributeField object>, 'energy_consumption': <movici_simulation_core.core.attribute.AttributeField object>, 'from_nodes': <movici_simulation_core.core.attribute.AttributeField object>, 'line2d': <movici_simulation_core.core.attribute.AttributeField object>, 'max_volume_to_capacity': <movici_simulation_core.core.attribute.AttributeField object>, 'nox_emission': <movici_simulation_core.core.attribute.AttributeField object>, 'passenger_car_unit': <movici_simulation_core.core.attribute.AttributeField object>, 'passenger_flow': <movici_simulation_core.core.attribute.AttributeField object>, 'to_nodes': <movici_simulation_core.core.attribute.AttributeField object>, 'travel_time': <movici_simulation_core.core.attribute.AttributeField object>}
cargo_flow
co2_emission
delay_factor
energy_consumption
from_nodes
line2d
max_volume_to_capacity
nox_emission
passenger_car_unit
passenger_flow
to_nodes
travel_time
class CorridorTransportSegmentEntity(name: str = None)

Bases: TransportSegmentEntity

attributes: Dict[str, AttributeField] = {'co2_emission': <movici_simulation_core.core.attribute.AttributeField object>, 'energy_consumption': <movici_simulation_core.core.attribute.AttributeField object>, 'lengths': <movici_simulation_core.core.attribute.AttributeField object>, 'nox_emission': <movici_simulation_core.core.attribute.AttributeField object>, 'passenger_car_unit': <movici_simulation_core.core.attribute.AttributeField object>, 'travel_time': <movici_simulation_core.core.attribute.AttributeField object>}
co2_emission
energy_consumption
lengths
nox_emission
passenger_car_unit
travel_time
class DemandNodeEntity(name: str = None)

Bases: PointEntity

attributes: Dict[str, AttributeField] = {'cargo_demand': <movici_simulation_core.core.attribute.AttributeField object>, 'passenger_demand': <movici_simulation_core.core.attribute.AttributeField object>}
cargo_demand
passenger_demand

model

class Model(model_config: dict, validate_config=True)

Bases: TrackedModel

Implementation of the corridor model

epsilon = 1e-12
classmethod get_schema_attributes() Iterable[AttributeSpec]
initialize(state: TrackedState) None

The initialize method is called when all of the state’s INIT attribute arrays are filled with data. This may be during the model engines initialization phase or during t=0. Data that is required for the model to initialize attribute may be published in another model’s t0-update, and the TrackedModelAdapter can wait for this to happen before calling initialize. When the simulation progresses to t>0 before the model’s INIT attributes have been filled, an Exception is raised, indicating that the model was not ready yet.

Model.initialize may raise NotReady to indicate that it does not have its required input data yet. This is for example useful if a model has a number OPT`ional required attributes of which at least one must be set. The model would check whether this is the case, and raise `NotReady if it is not. Once a model has succesfully run its initialize method, this method will not be called again for the duration of the simulation.

Parameters:

state – The model’s TrackedState object, managed by the TrackedModelAdapter

setup(state: TrackedState, settings: Settings, **_) None

In setup, a model receives a state object, it’s config and other parameters. The goal of setup is to prepare the state by giving it information of the attributes it needs to track (by subscribing (INIT/SUB/OPT) or publishing (PUB) attributes) from which datasets. These attributes may be grouped together in EntityGroup classes or created directly. The main entry points for registering are:

  • state.add_dataset() for registering a bunch of EntityGroup classes for a certain dataset name at once

  • state.add_entity_group() for registering a single EntityGroup class (or instance) for a dataset name

  • state.register_attribute() for registering a single attribute in a dataset/entity_group combination

During setup there is no data available in the state. These will be downloaded automatically by the TrackedModelAdapter. However, additional datasets may be requested directly through the init_data_handler parameter.

Parameters:
  • state – The model’s TrackedState object, managed by the TrackedModelAdapter

  • settings – global settings

  • schema – The AttributeSchema with all registered attributes

  • init_data_handler – an InitDataHandler that may be used to retrieve additional datasets

  • logger – a logging.Logger instance

shutdown(state: TrackedState) None

Called when a simulation ends (either due to it being finished or one of the models raises an exception). The model may implement this method to clean up local resources. This method may be called before the initialize and update methods have been called the first time

update(state: TrackedState, moment: Moment) Moment | None

The update method is called for every update coming from the model engine. However it is only called the first time once all PUB attributes have their arrays filled with data. When the simulation progresses to t>0 before the model’s SUB attributes have been filled, an Exception is raised, indicating that the model was not ready yet.

Parameters:
  • state – The model’s TrackedState object, managed by the TrackedModelAdapter

  • moment – The current simulation Moment

Returns:

an optional Moment indicating the next time a model want to be woken up, as per the model engine’s protocol

convert_v1_v2(config)

Module contents

Corridor

alias of Model