Meeting Minutes ‐ Simulation

List of Simulation Meeting Minutes

• 2025-09-17: Sim Tech Stack Discussion
• 2025-09-20: Sim Sync Up Meeting
• 2025-09-24: Sim Task Assignments for Iteration 2
• 2025-10-16: Sim Task Planning for Iteration 3
• 2025-10-29: Sim Sync Up Meeting 2
• 2025-01-13: Sim Task Assignments for Iteration 8

Sim Tech Stack Discussion

Wednesday, September 17th, 2025

Attendance:

• Sumer Abd Alla
• David Carciente
• Thomas Mahut
• Vinisha Manek
• Ambrose McLaughlin
• Christopher Mezzacappa
• Brian Tkatch

Absent: None

Note takers: Sumer Abd Alla

Notes:

• Meeting started with discussions on how the sim could be implemented
  • David explained what a Geographic Information System is and the elements its composed of (map and set of points).
  • The team discussed how the set of points would be referenced and how they can be used.
  • A debate was made whether the sim should have the same kind of coordinates (lat/long) with the frontend or its own set of points identifying specific points on a matrix representing the map. It was decided that it would be the same coordinates to directly communicate with the frontend and provide it locations.
  • Thomas summarized the use of Mapbox in a previous project and the team seemed to agree to use its Montreal OpenStreetMap data to access Montreal's map routes and generate the routes locally. This would remove the use of its API calls to generate routes as we would quickly pass its rate limit.
  • Sim would send a diff of changes to the front instead of the whole frame.
• Tech Stack Discussion
  • The team decided to use Python for the sim as it has good libraries and frameworks that could be used for this project.
  • Research was made around SimPy and the team seemed all on board for it.
  • Ambrose gave a summary of the bike simulation repo he tested on with Bixi data.

Action Items:

• Look into helper tools for OSM data
• Familiarize ourselves with Ambrose's repo
• Research python tools and libraries

Sim Sync Up Meeting

Saturday, September 20th, 2025

Attendance:

• Sumer Abd Alla
• David Carciente
• Vinisha Manek
• Ambrose McLaughlin
• Christopher Mezzacappa

Absent: None

Note takers: Sumer Abd Alla

Notes:

• Simpy Introduction
  • Ambrose presented his experiments with simpy and analyzed the code with us.
  • Introductions of the main components and functionalities of simpy were done.
  • His example provided a way to understand how the sim could work. It showed the relationship between sim time and real time, the use of an observer pattern through the FrameEmitter and the use of threading to ensure multiple entities can work at the same time.
  • The example was tested with a clock entity for easier understanding.
• Recall of Thursday Meeting
  • A debate was made on how sim data would be passed to the frontend on Thursday after the scrum meeting. Event driven vs. frame driven.
  • Vinisha and Ambrose summarized the ideas made during that meeting.
  • Event driven was decided to be unreliable. If a frame change was missed during the process, this could heavily affect the user experience as it could miss a change.
  • Frame driven seemed better in this case by sending a diff at every sim time to update the front.
• Walkthrough of User Stories and ACs
  • As a team, we went through the list of created user stories and read the existing acceptance criteria.
  • We tried to determine what tasks would be needed for the sim team for each of them. This gave us an idea of what we might need to do for them.
  • Failure logging was brought up. The team decided that further discussions would need to be made to decide which sub-team would need to deal with those.
  • As no user story directly instructs to create the sim logic, we will need to determine later when this should be implemented in the background.

Action Items:

• Familiarize ourselves with the Simpy repository
• Make a block diagram of the simpy repository code (Ambrose)
• Discuss with other sub-teams on how we want to work with logs and who will take ownership of them
• Finish ACs in the Product Backlog spreadsheet.

Sim Task Assignments for Iteration 2

Wednesday, September 24th, 2025

Attendance:

• Sumer Abd Alla
• David Carciente
• Thomas Mahut
• Vinisha Manek
• Ambrose McLaughlin
• Christopher Mezzacappa

Absent: None

Note takers: Sumer Abd Alla

Notes:

• The main purpose of the meeting was to assign points/hours to each sim related task and assign them to a team member.
  • Points were assigned to a task according to its complexity and on if research was required.
  • Points were according to Fibonacci numbers.
  • Since these tasks will be part of the first iteration with coding involved, tasks started at a minimum of 2.
  • Tasks with a value of 8 include those with big unknowns and would require research.
  • Tasks were assigned to members according to their knowledge or interest in them.
• Summaries for each task were made following the task issue template.
• It was determined that routes should be provided in geoJSON to frontend for easy communication

Action Items:

• Create task issues for the sim team on the repo.
• Discuss with other sub-teams how data should be transferred between each other.
• Start drafting data models with other sub-teams.

Sim Task Planning for iteration 3

Thursday, October 16th, 2025

Attendance:

• Sumer Abd Alla
• David Carciente
• Ambrose McLaughlin

Absent:

• Vinisha Manek
• Christopher Mezzacappa

Note takers: Sumer Abd Alla

Notes:

• The main purpose of the meeting was to assess the currently planned tasks and decide if any more are needed for user stories 7 to 13.
  • David summarized the route ADT PR he pushed to allow the sim behavior interface task to be started.
  • The team went through the five extra tasks created related to US-8 and US-9 and clarified what would be needed for each.
  • A new task was added in US-9 for implementing the logic of scheduled tasks for the simulation.
  • Points were assigned to each task.
  • Summaries for each task were made following the task issue template.

Action Items:

• Create task issues for the sim team on the repo.
• Determine how defining the JSON schema would be done by the sim team if backend is validating it.
• Validate new tasks with others and finalize assigning tasks with them

Sim Sync Up Meeting 2

Wednesday, October 29th, 2025

Attendance:

• Sumer Abd Alla
• David Carciente
• Thomas Mahut
• Vinisha Manek
• Ambrose McLaughlin
• Christopher Mezzacappa
• Giuliano Verdone

Absent: None

Note takers: Sumer Abd Alla

Notes:

• Team Task Updates
  • Ambrose is working on the sim behavior interface
  • Chris is finalizing his scenario JSON PR by completing tests
    • Having issues with installing all python dependencies
  • Vini will focus on frontend tasks and E2E tests for ATs this iteration
  • David started looking into the implementation for scheduled tasks. The team discussed how tasks appearing at specific ticks will work with the sim environment
  • Sumer will work on the sim bug task with multiple instances in the next week due to midterms
• The team assigned missing tasks to members according to priority and time
• Discussed with Giuliano how backend will communicate with the sim and use our entities

Action Items:

• Finish assigning sim tasks between members
• Research tech stacks for E2E tests
• Ambrose will look into all ATs expected to be completed this release and make sure sim has done all that is needed for them

Sim Task Assignments for Iteration 8

Tuesday, January 13th, 2025

Attendance:

• Sumer Abd Alla
• Thomas Mahut
• Vinisha Manek
• Ambrose McLaughlin
• Christopher Mezzacappa

Absent:

• David Carciente

Note takers: Sumer Abd Alla

Notes:

• The main purpose of the meeting was to assign tasks to team members to complete for iteration 8
• The team went through currently opened tasks to see how we should separate them between us
• Bug issue #331 was retested and confirmed to have been resolved.
• Two new tasks were created to enhance the simulation

Action Items:

• Ask the stakeholder for an estimated amount of time to service a battery swap task