-
Notifications
You must be signed in to change notification settings - Fork 0
Glossary
This glossary defines key terms and concepts used throughout the project. This glossary includes both Bixi specific terms and terminology, and also technical terminology used within the context of this project.
In the real and simulated Bixi networks, to assign a task is to delegate the responsibility of that task to a resource. In the real Bixi network, resources are not necessarily informed of this assignment as soon as it is made. In the simulated network, resources are informed of this assignment as soon as it is made.
A frame that only contains information that has changed between the previous tick and the given tick of a running simulation.
In the real Bixi network, to dispatch a task is to inform a resource of a new task assignment. In the Bixi network simulation, resources are informed of new task assignments as soon as tasks are assigned, and so the terms "dispatch" and "assign" become interchangeable in this context.
In the context of the Bixi network simulation, dispatch delay is the time between the moment at which the user dispatches / assigns a task to a resource on the client side and the moment at which this dispatch is received by backend (and thus by the simulation) and has an actual effect on the behaviour of entities in the simulation.
A person responsible for assigning / dispatching tasks to resources.
A space for a bike to be parked at or retrieved from at a station. Docks do not exist as entities in the context of the Bixi network simulation.
A entity is anything with distinct and independent existence that may be involved in interactions in the Bixi network simulation. Examples of types of entities include resources, stations, and tasks.
Stands for "frames per second" and refers to the rate at which the backend / simulation sends frames to the frontend for rendering. Not to be confused with RPS, or "renders per second".
A Python / JavaScript object containing information on entities in a running simulation at a given point in time (tick). A frame either contains all entity information at a given tick (this is a key frame or only information that has changed between the previous tick and the given tick (this is a diff frame). The use of the word frame alone most likely refers to a diff frame in the context of this project, given that diff frames are more common than key frames.
A frame that contains all information at a given tick of a running simulation.
A resource is a driver-vehicle pair representing a field-agent and their associated vehicle. Resources are tracked throughout the simulation travelling between stations to complete battery swap tasks.
The path that a resource takes to some location in order to service a task assigned to them. In the context of the Bixi network simulation, each resource may or may not have a route that directs them to the station at which their next task is located.
Stands for "renders per second" and refers to the rate at which the frontend refreshes the positions of entities on the map. Not to be confused with FPS, or "frames per second", which is the rate at which simulation frames are forwarded to the frontend. The frontend can achieve a higher RPS than the provided FPS by performing intermediate position interpolation.
A scenario is the set of initial conditions / behaviour parameters for a simulation. Many (different) simulations can be run from the same scenario.
A simulation in the context of this project is a series of events that are meant to represent the behaviour of the actual Bixi network. A simulation is either in progress (evolving from the given scenario, and reacting to user input) or completed, in which case a simulation is represented as simply a collection of sequential states of an imitation Bixi network.
In the Bixi network, stations are made up of docks and a terminal. There may or may not be a bike at every dock at a station. In the context of the Bixi network simulation, stations are simply locations at which battery swap tasks may exist - individual docks and terminals don't exist as simulation entities.
In the context of the Bixi network (or simulation of this network), a task an atomic piece of work that a resource must carry out to support the network.
A machine from which Bixi customers can rent a bike at a station. Terminals do not exist as entities in the context of the Bixi network simulation.
Simulation Meeting Minutes
Frontend Meeting Minutes
Backend Meeting Minutes
Risks
User Consent and End-User License Agreement
Legal and Ethical Issues
Economic
Budget
Personas
Diversity Statement
Overall Architecture and Class Diagrams
Infrastructure and Tools
Name Conventions
Testing Plan and Continuous Integration
Security
Performance
Deployment Plan and Infrastructure
Missing Knowledge and Independent Learning
Glossary
Mockups
UI Evolution
Logging
Metrics
VeloSim Observability & Performance Insights
User Manual
Usability Tests