VIPRA Simulation

[GoodenoughR]

VIPRA Simulation

Needed Functionality:

• Base Functionality:
  • Behavior Model -> (needs updating to work with new implementation)
  • Policy Model -> (not implemented)
  • Input Handling [maps, pedestrians, simconfig] -> (Functional, needs testing, xml input loader versions need updated)
  • Output Handling -> (Functional, needs testing, xml output handlers need updated)
  • Code Generation -> (Functional, needs to be tested with full system)
  • Main Simulation -> (in progress)
• Module Implementations:
  • Extendable Interfaces Definitions -> (in progress)
  • Airplane Obstacle Set -> (in progress)
  • Calm Goals -> (in progress)
  • Calm Pedestrian Set -> (in progress)
  • Calm Pedestrian Dynamics Model -> (in progress)

Discussion Points:

1. How are pedestrians loaded/initialized? Originally, a pedestrians json file was loaded with their initial positions, as well as their initial model specific attributes. This requires a different pedestrians file for each model.
2. Map Loaders: Should we add a new module type that is responsible for loading map files? Each map loader can handle a different type of map (polygon, point, etc), the obstacle sets take the data from the map loader.
3. Are we implementing MPI?
4. How is documentation handled?
5. Coding standard?

[GoodenoughR]

Discussion point

5. Do we need a separate module for diff eq solver, or was that a part of the pedestrian model?

[ashok0srinivasan]

We should have a separate module for that.

• Ashok Srinivasan

On Thu, Oct 20, 2022 at 1:23 PM Rolland Goodenough @.***> wrote:

Discussion point

5. Do we need a separate module for diff eq solver, or was that a part of the pedestrian model?

— Reply to this email directly, view it on GitHub https://github.com/vipra-uwf/vipra/issues/75#issuecomment-1286098956, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACPNH5HKXZS4QF3NLXCMFILWEGS2TANCNFSM6AAAAAARHQY2FA . You are receiving this because you are subscribed to this thread.Message ID: @.***>