How timothylee58/jalur-apexgp works
Jalur APEXGP is a public Sepang race-weekend strategy simulator with companion fan, data, and trip-planning features. The main workflow is selecting a session and scenario in the strategy UI, fetching blended weather, generating conservative and aggressive tyre/stint reads, then displaying confidence and pit windows; unmodified live reads are logged. The README also documents chat, picks, telemetry, standings, accuracy, and transit capabilities. Some of those implementations were not sampled, so their internal links are omitted rather than inferred.
Main entry points: main.py FastAPI app · predict.py Prediction route · telemetry.py Telemetry API · rag_service.py Context retrieval
Components 29
Strategy experience
- Strategy page
frontend/app/predict/page.tsx - Scenario controls
frontend/app/predict/PredictClient.tsx - Prediction hook
frontend/hooks/usePrediction.ts - API client
frontend/lib/api.ts
Strategy services
- FastAPI app
backend/app/main.py - Prediction route
backend/app/api/routes/predict.py - Weather blend
backend/app/services/weather_service.py - Strategy simulator
backend/app/services/strategy_service.py - Prediction models
backend/app/schemas/prediction.py - MLflow tracking
backend/app/core/mlflow_client.py - Read accuracy
backend/app/services/accuracy_service.py
Race data features
- Schedule and standings
backend/app/services/jolpica_service.py - Telemetry views
frontend/components/telemetry/TelemetryDashboard.tsx - Telemetry API
backend/app/api/routes/telemetry.py - Telemetry pipeline
backend/app/services/telemetry_pipeline.py
Fan experiences
- Race engineer chat
frontend/components/chat/RaceEngineerChat.tsx - Chat API
backend/app/api/routes/chat.py - Context retrieval
backend/app/services/rag_service.py - Knowledge corpus
backend/app/services/knowledge_base.py
Picks and access
- Race picks
frontend/app/picks/PicksClient.tsx - Picks API
backend/app/api/routes/picks.py - Transit access
frontend/components/tickets/TransitAccessPanel.tsx - Transit API
backend/app/api/routes/transit.py - Live transit ETL
backend/app/services/transit_service.py
Other components
- Race fan
- Open-Meteo
- MLflow service
- Jolpica API
- Government GTFS
Connections 33
- Race fan → Strategy page: opens
README.md - Strategy page → Scenario controls: renders
- Scenario controls → Prediction hook: requests reads
- Prediction hook → API client: calls API
- API client → FastAPI app: calls backend
README.md - FastAPI app → Prediction route: routes requests
backend/app/main.py - Prediction route → Weather blend: gets snapshot
backend/app/api/routes/predict.py - Weather blend → Open-Meteo: fetches forecast
README.md - Prediction route → Strategy simulator: builds prediction
backend/app/api/routes/predict.py - Prediction route → Prediction models: uses models
backend/app/api/routes/predict.py - Strategy simulator → Prediction models: returns model
backend/app/schemas/prediction.py - Prediction route → MLflow tracking: logs live read
backend/app/api/routes/predict.py - MLflow tracking → MLflow service: records runs
README.md - Prediction route → Read accuracy: records snapshot
backend/app/api/routes/predict.py - Race fan → Race engineer chat: asks questions
- Race engineer chat → Chat API: sends prompt
- FastAPI app → Chat API: routes requests
backend/app/main.py - Chat API → Context retrieval: streams answers
backend/app/api/routes/chat.py - Context retrieval → Knowledge corpus: retrieves context
backend/app/services/rag_service.py - Context retrieval → Schedule and standings: loads live standings
backend/app/services/rag_service.py - Race fan → Telemetry views: explores telemetry
- FastAPI app → Telemetry API: routes requests
backend/app/main.py - Telemetry API → Telemetry pipeline: builds telemetry
backend/app/api/routes/telemetry.py - Telemetry API → Telemetry views: serves telemetry
- Race fan → Race picks: submits picks
- FastAPI app → Picks API: routes requests
backend/app/main.py - Race picks → Picks API: uses picks API
- Race fan → Transit access: checks access
- FastAPI app → Transit API: routes requests
backend/app/main.py - Transit access → Transit API: requests ETL read
- Transit API → Live transit ETL: gets live access
backend/app/api/routes/transit.py - Live transit ETL → Government GTFS: reads GTFS feeds
README.md - Schedule and standings → Jolpica API: fetches results
backend/app/services/jolpica_service.py