-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sort by Suspense #119
Sort by Suspense #119
Conversation
(ideally this would incorporate some recency metric, but my python is extremely rusty and the single 30 second attempt at datetime math I made didn't work) |
I'm a 👎 on this change -- I like the idea of a volatility metric, but it should be part of the state header or something, and not a sort order. Using it for sorting means the file could change in between runs/reloads of the webpage, which is super jarring. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See other comment.
Hey! Thanks for the PR! This would cause the states to shuffle around based on the value of suspense. I'm worried that'd cause a lot of shuffling. I'm curious if you have any suggestions on how to avoid that? |
Updated the metric - the goal was to have the most relevant states up at the top of the page, verus the alphabetic sort. Maybe some kind of rolling average to keep things relatively stable? In practice, the tighter the race the higher the 'suspense' so in theory the sort should be relatively stable, or switch between two tight races? |
Hi @blaine! Thanks for the suggestion! We've decided not to change the sort, but are going to be defaulting to the collapsed tables, so everything is easy to access. |
(hurdle - block trend) * precincts reporting