Website for Brackt.com
d4df0b65fb
The LLWS simulator was overestimating favorites and ignoring games that had already been played. Two separate causes: 1. Championship futures were used directly as single-game strength (p1 / (p1 + p2)). A future already compounds the ~6 wins needed to take the title, so this made every individual game as lopsided as the whole tournament and re-compounded that edge round after round. Against a representative 20-team board the favorite priced at 21.8% simulated at 44.9%, and the longest shot fell to ~0%. Futures are now decompressed to single-game Elo via convertFuturesToElo, the same pipeline the other bracket simulators use, and games are played with eloWinProbabilityWithParity. The parity factor was calibrated by sweeping it until a randomized-draw simulation reproduces the board it was fed: at 1000 the favorite simulates at 21.8% and field-wide RMSE drops from 0.062 to 0.003. It is overridable per season via config. 2. The simulator never read playoff_matches, so it re-ran the tournament from an empty bracket every time and shuffled the draw at random each iteration. A recorded loss changed nothing. It now loads the seeded llws_20 bracket, places teams in their real slots, and replays completed games from their recorded result instead of re-simulating them, so an eliminated team correctly drops to zero. When no bracket exists (or it has no participants seeded) it falls back to the previous randomized-draw behavior, and a seeded bracket is authoritative about which side a team is on, so externalId is only required on the pre-bracket path. Guards: a recorded result is only honored when its two participants are the ones the simulation routed into that game, so a corrupt or out-of-order row cannot desynchronize the rest of the bracket; brackets seeding an unknown or duplicated participant now fail loudly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X5vQZMPeokzfMqHQjq1RDZ |
||
|---|---|---|
| .claude | ||
| .forgejo/workflows | ||
| .opencode/plugins | ||
| .production-info | ||
| .storybook | ||
| .vscode | ||
| app | ||
| cypress | ||
| database | ||
| docs | ||
| drizzle | ||
| plans | ||
| public | ||
| scripts | ||
| server | ||
| test-fixtures/baselines | ||
| .dockerignore | ||
| .env.example | ||
| .gitignore | ||
| .npmrc | ||
| .nvmrc | ||
| .oxlintrc.json | ||
| AGENTS.md | ||
| BETTERAUTH_MIGRATION.md | ||
| CLAUDE.md | ||
| components.json | ||
| cypress.config.js | ||
| docker-compose.yml | ||
| Dockerfile | ||
| drizzle.config.ts | ||
| instrument.server.mjs | ||
| oxlint.json | ||
| package-lock.json | ||
| package.json | ||
| plan.md | ||
| react-router.config.ts | ||
| README.md | ||
| server.ts | ||
| TESTING.md | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| tsconfig.server.json | ||
| tsconfig.vite.json | ||
| vite.config.ts | ||
| vitest.config.ts | ||
| vitest.shims.d.ts | ||
Welcome to React Router!
A modern, production-ready template for building full-stack React applications using React Router.
Features
- 🚀 Server-side rendering
- ⚡️ Hot Module Replacement (HMR)
- 📦 Asset bundling and optimization
- 🔄 Data loading and mutations
- 🔒 TypeScript by default
- 🎉 TailwindCSS for styling
- 💾 PostgreSQL + DrizzleORM
- 📖 React Router docs
Getting Started
Installation
Install the dependencies:
npm install
Development
Copy .env.example to .env and provide a DATABASE_URL with your connection string.
Run an initial database migration:
npm run db:migrate
Start the development server with HMR:
npm run dev
Your application will be available at http://localhost:5173.
Building for Production
Create a production build:
npm run build
Deployment
Docker Deployment
To build and run using Docker:
# For npm
docker build -t my-app .
# Run the container
docker run -p 3000:3000 my-app
The containerized application can be deployed to any platform that supports Docker, including:
- AWS ECS
- Google Cloud Run
- Azure Container Apps
- Digital Ocean App Platform
- Fly.io
- Railway
DIY Deployment
If you're familiar with deploying Node applications, the built-in app server is production-ready.
Make sure to deploy the output of npm run build
├── package.json
├── package-lock.json (or pnpm-lock.yaml, or bun.lockb)
├── server.js
├── build/
│ ├── client/ # Static assets
│ └── server/ # Server-side code
Styling
This template comes with Tailwind CSS already configured for a simple default starting experience. You can use whatever CSS framework you prefer.
Built with ❤️ using React Router.