search

riebl / artery

OMNeT++ V2X simulation framework for ETSI ITS-G5
GNU General Public License v2.0
203 stars 129 forks source link

Vehicle types supported by artery #286

Closed Ambica2022 closed 1 year ago

Ambica2022 commented 1 year ago

Hi,

What are the different vehicle types does artery supports? And how to model a new vehicle type in artery?

Best Regards, Ambica

awillecke commented 1 year ago

Hi,

Artery can spawn different OMNet++ nodes, such as inet.Car or inet.PlainVehicle, when a vehicle of any type is departing in SUMO using the MultiTypeModuleMapper in a probabilistic fashion. Also, persons are supported. If you would like to create a new vehicle type, you could for example create a new NED module, which inherits from the inet.Car, add submodules as you like and tell the mapper to spawn those.

If you refer to the vehicle types of SUMO, Artery is not yet able to distinguish between those and considers them all the same AFAIK.

Best regards Alex

Ambica2022 commented 1 year ago

Hi,

Then Artery treats car and motorcycle in a similar way, isn't it? or do we need to create middleware for motorcycles in artery? My scenario contains few cars and few motorcycles.

Best Regards, Ambica

awillecke commented 1 year ago

Cars and motorcycles are both vehicles and will be handled the same by the ModuleMapper. If a communicating node with a middleware is created, you can, however, influence which services are run using filters. If, in your SUMO scenario, motorcycles and normal vehicles are distinguishable by name, you could match that name using filters and instantiate services differently. This may be enough to fulfill your requirements.

Best regards Alex

Ambica2022 commented 1 year ago

Thank you Alex