Veins 和 SUMO：为车辆分配多个模块类型或将行人包含在车辆内
我正在使用静脉5.1，可能被迫保留它。我希望将多个（2）个不同的Omnet .Ned。已分配给单相扑车。需要2个具有完全相同的移动性模式和出发时间的模块。
根据评论（第132行和traciscenariomanager.cc中的关注），只能将单个模块类型分配给车辆类型。 可以更改吗？
我认为另一种解决方案是让2名乘客乘坐车辆并为每个车辆分配一个模块类型。 我尝试了以下操作：
<vehicle id="0" type="non" route="1" depart="0"/>
<person id="p0" type="ue1" depart="triggered">
<ride to="1/1to1/2" lines="0"/>
</person>
<person id="p1" type="ue2" depart="triggered">
<ride to="1/1to1/2" lines="0"/>
</person>
使用SUMO-GUI运行Sumo模拟时，乘客确实会出现，但在Omnet模拟中未分配一个模块类型。 Omnetpp.ini中的代码是正确的。车辆将被分配正确的模块类型。
可以包括乘客吗？
我尝试让2辆具有相同路线和出发时间的车辆，但这导致相扑在2辆车之间造成延迟，并且似乎不是一种选择。
感谢您的帮助！
I am using Veins 5.1 and might be forced to keep it. I would like to have multiple (2) different OMNeT .ned modules to be assigned to a single SUMO vehicle. 2 modules with the exact same mobility pattern and departure time are needed.
According to the comment ( line 132 and following in TraCIScenarioManager.cc ) only a single module type can be assigned to a vehicle type.
Could this be changed?
I think an alternative solution would be to have 2 passengers ride the vehicle and assign a module type to each of them.
I tried the following:
<vehicle id="0" type="non" route="1" depart="0"/>
<person id="p0" type="ue1" depart="triggered">
<ride to="1/1to1/2" lines="0"/>
</person>
<person id="p1" type="ue2" depart="triggered">
<ride to="1/1to1/2" lines="0"/>
</person>
The passengers do show up when running the SUMO simulation with sumo-gui but do not get assigned a module type in the OMNeT simulation. The code in the omnetpp.ini is correct. A vehicle would get assigned the correct module type.
Would it be possible to include the passengers?
I tried having 2 vehicles with identical routes and departure times, but that caused SUMO to create a delay between the 2 vehicles and does not seem to be an option.
Thank you for your help!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
看起来我找到了解决方法：
INET提供了一个附加的摩托模块。
使用静脉电动性的一个模块可以创建另一个模块，而新创建的模块则可以使用附件。
Looks like I found a workaround:
INET provides an AttachedMobility module.
The one module that uses VeinsInetMobility can create the other module and the newly created module can then use AttachedMobility.