gauntlet ocgv1

ℹ️ Gauntlet Special Rules

• 🤝 Community Driven This is a community made initiative, reach out to the player who created it on Discord!
• 📈 Incremental Gauntlet Each week's stage builds on the previous one. Performance and efficiency compound for better or worse.
• 🥇 Weekly Best Revealed The best stage from each week will be revealed at the start of the following week. You can use it... or try to beat it.
• 🤖 Prime Process Unlockable If the Prime Process is still the best at the end of a week, its solution will be revealed.

🎮 Quick Tips

• 🏆 Focus on speed first Ticks are weighted at 40%
• ⚖️ Balance matters Don't ignore the other 60%!
• 🤖 Process Prime is the official reference design. Beating it is a significant milestone.
• 📅 Participate every week Missing a week means losing points!
• 🔬 Experiment Different designs can excel at different metrics
• 📏 Check the ranges See what's possible and where you can improve
• 🎯 One score per week Only your best submission counts
• 🛑 No backfill No points can be earned after a week closes.

🎯 How Scoring Works

The Four Metrics

Every submission is measured on four key performance metrics (lower is better):

• Ticks How fast your design runs (execution time)
• Blocks How many logic blocks you use (design complexity)
• Volume The physical volume of your design (space efficiency)
• MOS Total transistor count (nMOS + pMOS)

Weighted Scoring

• Ticks: 40% Speed is the top priority!
• Blocks: 20% Design simplicity matters
• Volume: 20% Space efficiency counts
• MOS: 20% Transistor efficiency is valuable

Reference Baseline

Scoring uses Sub Process (Ref Naïve) as the worst-case baseline and Process Prime (Ref Best) as the starting best-case reference. Beating Process Prime is a significant achievement.

📊 Understanding the Leaderboards

Weekly Leaderboard (0–100 pts)

• Your best submission is scored against all players
• Metric scores total = 40% Tick + 20% Block + 20% Volume + 20% MOS
• Tie-breaker: Earlier submission wins
• Maximum: 100 points per week

Gauntlet Leaderboard (rank-based points)

• Each week you earn points based on your finishing rank
• 1st place earns 10 pts, 2nd earns 10 x ((Players-rank)/(Players-1)) ^ y, … last place earns 0 pt (where y = 1.5)
• Points accumulate across all completed non-warmup weeks
• Participate every week to maximize your total missing a week means 0 pts for that week
• Ranked by total accumulated rank-points (highest wins)

🔍 Metric Range Leaderboards

What These Show

Each metric tab displays specialized rankings sorted by that metric:

• Ticks Range: Best tick-count submissions
• Blocks Range: Best block-count submissions
• Volume Range: Best volume submissions
• MOS Range: Best transistor-count submissions

Key Points

• Your best submission per metric may differ
• These ranges determine min/max for normalization
• Optimize for different goals with different designs

📐 Normalization Formula

How Scores Are Calculated

Each metric is converted to a 0–100 scale:

Score = 100 − ((Your − Best) / (Worst − Best)) × 100

• 100 pts = You achieved the best value
• 0 pts = You matched the worst value (Sub Process)
• Clamped between 0 and 100, then weighted

Dynamic vs Fixed Ranges

• Best Value: 📊 Dynamic improves as players improve
• Worst Value: 🤖 Fixed based on "Sub Process (Ref Naïve)"

❓ Common Questions

Q: Can I submit multiple times?

A: Yes! Only your best overall score per week counts.

Q: What if I miss a week?

A: You can still compete in future weeks, but you'll miss that week's points.

Q: Why do metric ranges show different submissions?

A: Your best tick-optimized design may use more blocks. The system tracks your best per category.

Q: How do I maximize my score?

A: Create balanced designs with extra emphasis on tick count. Check metric ranges to improve.

🎥 Week 1 - Kick-start guide

🎥 Week 2 - Same but different Xor Not Multi Gate

🎥 Week 3 - A tiny bit bigger AndOrXorNot Multigate

🎥 Week 4 - The Honest 4Bit AndOrXorNot