Metaculus / Metaculus/forecasting-tools

When there are a lot of MC options, forcing min of 1% makes things error

Open
#211 1 comment 0 reactions 1 assignee View on GitHub

@elisescu is already working on this.

Since Feb 18, 2026.

Medium Priority
Dominant language
Python
Stars
79
Forks
38
Avg merge
20m
Merged PRs (30d)
12

Description

For example here. Keeping a min of 1% makes sense for binaries, and most MC, but we should probably scale the min based on the number of options (or remove the min for MC). The LLM will give a prediction of 0% from time to time.

Example problem question here

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.