How to Read MeteorHound Scores Without Overtrusting Them
Turn score tiers into disciplined go/no-go decisions without treating them as certainty.
Who this is for
Users relying on MeteorHound to prioritize hunts near their location.
Why it matters
Scoring helps you move faster, but speed without judgment can still produce poor field outcomes. The score is a triage tool, not a guarantee.
What you'll learn
- What the model is optimizing for.
- How to combine score tier with confidence checks.
- How to build a reliable go/no-go routine.
What the score really represents
MeteorHound score tiers represent comparative likelihood of meteorite recovery based on available signals. They are intended to prioritize your attention, not to replace your final decision process.
A high tier means the event looks promising relative to others in the same stream. It does not mean the strewn field is solved or that a recovery is guaranteed.
Signals behind the tier
Some signals are stronger than others. Terminal behavior and entry speed often matter more than softer context like witness narrative richness.
Source agreement and freshness can improve confidence in interpretation. Weak or partial data can still produce useful ranking, but it should increase your caution.
Using Possible, Unlikely, and Ignore
Possible events merit active planning: map work, permissions, and a timeboxed field session. Unlikely events are best for low-cost local checks or skills training.
Ignore events still have value for learning. They let you practice triage without spending travel time, which improves performance on future strong candidates.
Confidence, uncertainty, and stop rules
Confidence increases when multiple sources agree and measurements are internally consistent. Uncertainty remains in local terrain effects and imperfect impact-zone approximation.
Set stop rules before leaving: maximum travel time, minimum evidence threshold, and a hard field cutoff. This protects your schedule from decision drift.
Common mistakes
- Treating threshold values as certainty.
- Ignoring confidence quality behind the score.
- Skipping manual map checks because a tier is high.
Field checklist
- Verify top signals and source agreement before travel.
- Define stop rules and fallback options.
- Log the reason for your final go/no-go call.