How jalal1/tareek works
TAREEK turns county-level configuration into regional MATSim travel simulations and validation reports. The principal workflow is configuration → open-data acquisition → network construction → synthetic demand and daily plans → MATSim execution → traffic-count evaluation. Survey processing, spatial/activity models, persistent data, transit availability, freight analysis, and the configuration web app are distinct capabilities. Pipeline links are based on README documentation and SOURCE INDEX references; unsampled implementations are represented only at supported directory or module paths.
Main entry points: run_experiment.py Experiment Runner · plan_generator.py Activity Plans · survey_manager.py Survey ETL · network_generator.py Road and Transit Network
Components 22
Configuration
- Config Wizard
webapp/frontend/js/app.js - Wizard Backend
webapp/backend/main.py - Region Config
config/config.py - Experiment Runner
run_experiment.py
Data and Network
- Survey ETL
data_sources/survey_manager.py - Census and OD Data
data_sources - POI Locations
models/poi_manager.py - GTFS Feeds
data_sources/gtfs_manager.py - Road and Transit Network
matsim/network_generator.py - DuckDB Data Store
utils/duckdb_manager.py
Travel Demand
- Demand Budget
models/demand_budget.py - Activity Plans
models/plan_generator.py - Nonwork Demand
models/plan_generator_nonwork.py - Mode Choice
models/mode_choice.py
Simulation and Evaluation
- MATSim Run
matsim/runner.py - Traffic Counts
matsim/counts_generator.py - Validation and Reports
matsim/evaluator.py
Extensions
- Freight Modeling
estimators/freight_estimator.py
Other components
- Modeler
- Transit Feed Catalog
- Open Data Services
- MATSim Engine
Connections 27
- Modeler → Config Wizard: configures region
README.md - Config Wizard → Wizard Backend: submits settings
- Wizard Backend → Region Config: exports config
README.md - Modeler → Region Config: selects counties
README.md - Region Config → Experiment Runner: starts experiment
README.md - Experiment Runner → Survey ETL: loads surveys
run_experiment.py - Experiment Runner → Census and OD Data: gets regional data
README.md - Experiment Runner → Road and Transit Network: builds network
run_experiment.py - Experiment Runner → Activity Plans: generates plans
run_experiment.py - Experiment Runner → Nonwork Demand: generates demand
run_experiment.py - Experiment Runner → MATSim Run: runs simulation
run_experiment.py - Experiment Runner → Validation and Reports: evaluates run
run_experiment.py - Survey ETL → DuckDB Data Store: saves survey data
- POI Locations → DuckDB Data Store: reads and writes
models/poi_manager.py - GTFS Feeds → Transit Feed Catalog: discovers feeds
data_sources/gtfs_manager.py - GTFS Feeds → DuckDB Data Store: loads feed data
data_sources/gtfs_manager.py - Road and Transit Network → GTFS Feeds: uses transit feeds
matsim/network_generator.py - Road and Transit Network → Open Data Services: downloads road data
README.md - Census and OD Data → Open Data Services: fetches census data
README.md - Activity Plans → Survey ETL: uses travel patterns
models/plan_generator.py - Activity Plans → POI Locations: assigns locations
models/plan_generator.py - Activity Plans → Mode Choice: chooses modes
models/plan_generator.py - Activity Plans → Demand Budget: uses demand budget
models/demand_budget.py - Nonwork Demand → Survey ETL: uses survey patterns
models/plan_generator_nonwork.py - MATSim Run → MATSim Engine: executes simulation
README.md - Validation and Reports → Traffic Counts: compares counts
README.md - Experiment Runner → Freight Modeling: optional analysis