How torukmaktoalpha/food-demand-simulation works
File structure
• Top level
• public/: static HTML (index.html), manifest.json, robots.txt
• src/: React source code
• package.json / package-lock.json: npm dependencies (React, React Router, ml-kmeans, etc.)
• tailwind.config.js (unused or placeholder—styles live in custom CSS)
• src/ key files
• App.js: main simulation & visualization entry point
• SanFranciscoFoodDemandSimulation.js: core simulation engine
• ResultsPage.js: demand analysis view
• KMeansAnalysis.js: clustering logic & store-placement suggestions
• StoreAnalysis.js: optional summary module
• index.js, App.css, index.css: bootstrap React and global styles
• No backend or database folders—everything runs client-side.
README for additional insights
• Confirms dynamic simulation, interactive visualization, demand analysis, K-Means clustering, modern UI, React Router navigation.
• No server or data persistence—state is ephemeral in the browser.
Detail
• Static asset hosting boundary (public folder) vs. the runtime JS bundle
• React Router as the “glue” between pages
• Call out that all processing (simulation, clustering) occurs client-side