Skip to content

More basic facts on solves for constructors (post-solve) #489

@revuluri

Description

@revuluri

The overall (number of total completions, number without helpers, and each average completion time) are informative, and the “grid difficulty heat map” is also very insightful.

I’d love to be able to see a distribution (histogram) of solve times, or perhaps a scatterplot of solve times vs. solver rating/score, or at least a few more solve time statistics (quartiles, 5/95 percentile, standard deviation).

I know there are some design decisions about keeping puzzle difficulty scores/ratings less prominent (only auto-tagging by broad ranges) but I have wondered about the difficulty levels of my puzzles (a) at a slightly more granular level and (b) how they might align to “NYT benchmarks”.

I have sometimes wondered about the absolute number of edits (was the most yellow cell really hard, or just the least easy?) as well as the relative as displayed by the heatmap. Maybe a percentage of squares that were edited or a total number of edits? (Probably becomes most informative when it is put in context across other puzzles of similar size and/or rating.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions