rustsim-transit 0.0.1

Public-transit primitives for rustsim: stops, routes, schedules, boarding/alighting queues, dwell times, headway control
Documentation
  • Coverage
  • 100%
    111 out of 111 items documented0 out of 51 items with examples
  • Size
  • Source code size: 31.84 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 1.42 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 1m 8s Average build duration of successful builds.
  • all releases: 1m 8s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Repository
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • federicomarcantognini

Public-transit primitives for rustsim.

This crate provides the minimum set of types needed to model scheduled shared-ride services (bus, tram, metro, rail, ferry, shuttle) sitting above the generic rustsim-traffic link network. It is deliberately agnostic to how a transit vehicle physically moves (that is delegated to rustsim-vehicle or a custom controller) — it only models the service layer.

Core concepts:

  • [Stop] — a named point in space with a finite capacity for waiting passengers.
  • [Route] — an ordered sequence of stops with a scheduled headway or explicit departure times.
  • [TransitVehicle] — a service instance with a capacity and a list of current passenger IDs.
  • [Boarding] — FIFO queue discipline at each stop.
  • [Schedule] — either a fixed-headway or explicit-timetable departure pattern.
  • [dwell] — a linear dwell-time model used to compute how long a vehicle sits at a stop.
  • [policy] — explicit queue, dispatch, and dwell policy contracts.