Skip to content

Closed lower bound questions are misleading in UI vs API, and possibly unnecessary?? #1646

Description

@jkraybill

Current behavior

Consider post 28845, "How many Metaculus users that ranked in the top 16 in the Q3 2024 Quarterly Cup will remain in the top 16 at the end of Q4 2024 Quarterly Cup?". The answer UI makes it look like you can enter guesses from 1 to 16. So does the API, where scaling.range_min=1 and scaling.range_max=16.

image

I'm not certain what happens in the database when you try to place a significant weight on the "1" in the above, but in the API, it's not allowed; cdf[0] must equal 0. The UI implies that you are able to weight that 0-index value (or close to it) -- as you can see above, many users have non-zero values for what I assume must be cdf[1].

In my uninformed opinion, cdf[0] should be an allowably non-zero value for both open and closed lower bound questions, and I further contest that there is no difference between the two in the Metaculus paradigm. cdf[0] should never be required to be zero, and should be always treated as the P(x<=min). cdf[max] being required to be 1 makes sense, but the constraints around cdf[0] to me make no sense. In the above example, does anyone get points if the answer resolves to 1? Clearly a number of people think so, but the API implies no.

Expected/desired behavior

Someone needs to rework the numeric question framework, it has many problems that are especially palpable for quantizable (N(A) < 200) questions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions