How dnzengou/tariffs-impact-simulation-game works
Project type and purpose
• This is a purely client-side, static web application (no backend server or database) for running interactive “Liberation Day” tariff‐impact simulations.
• Users load one of several HTML entry points (e.g., index.html, tariff-simulator.html, abm-ca-simulations.html), adjust parameters in the browser UI, run Monte Carlo–style or ABM simulations in Web Workers, and view results via D3.js visualizations.
File structure
• Top-level HTML pages:
• index.html – landing page
• tariff-simulator.html – main tariff sim UI
• abm-ca-simulations.html – agent-based model UI
• various backup HTML files for previous versions
• script.js – application logic orchestrating UI events, sending tasks to workers, handling results
• worker.js, worker-simu.js – Web Worker scripts that perform the core simulation computations off the main thread
• worker_tariff-simulator.html.js – likely a generated/inline worker loader for tariff-simulator
• No server code or configuration files – project is hosted statically on GitHub Pages or Netlify
README for additional insights
• Confirms tech stack: HTML, CSS, vanilla JavaScript, D3.js
• Emphasis on lightweight, browser‐only deployment, user‐adjustable parameters, D3 visualizations
a. Main Components
• Hosting Platform (GitHub Pages / Netlify)
• Client Browser Environment
• UI Layer (HTML + CSS; parameter controls, buttons)
• App Controller (script.js)
• Web Worker Pool (worker.js, worker-simu.js) – simulation engine
• Visualization Engine (D3.js) – charting, graphs
• (Optional) Configuration/Parameter Model (in-memory JS objects)
b. Relationships & Data Flows
1. Browser requests the static files from Hosting Platform
2. UI Layer renders HTML forms/sliders & captures user input
3. App Controller reads parameters and spawns one or more Web Workers, passing input via postMessage
4. Web Workers perform compute‐intensive simulations and postMessage results back
5. App Controller receives simulation data and invokes D3.js routines to render visualizations in the DOM
6. User interacts further, possibly re-running simulations or altering views
c. Architectural Patterns & Principles
• Single-Page / Multi-Entry Static App pattern – separate HTML shell pages, each with its own script loader
• Separation of concerns – UI vs. compute logic handled in Web Workers
• Asynchronous messaging (main thread ↔ workers) to keep UI responsive
• Modular JavaScript – script.js orchestrator, worker.js compute modules, D3 for visualization
d. Key Technologies & Libraries
• HTML5, CSS3 – markup & styling
• Vanilla JavaScript – core application logic (script.js)
• Web Workers (worker.js, worker-simu.js) – parallel simulation computing
• D3.js – dynamic, data-driven visualizations
• Static hosting (GitHub Pages / Netlify)