artoonie / rcvis Goto Github PK

Probably use: http://jsfiddle.net/shawnbot/BJLe6/

(if you want any help with this, i can intro you to my friend who's great with d3 etc. & willing to help)

Bug report:

"on my Windows 10 computer with Chrome browser, when I follow any link to a results display, it scrolls down too far and cuts off the top and I have to scroll back up to see the top of the results."

"On Firefox, it is a little closer to the top:"

Probably an easy fix (rotate labels 90deg?), but something George was hung up on.

@davidryal this is already done - do you have examples of where it doesn't work?

As you scroll down, the name alignment will get further and further off from their position.
Fix the name positions as you scroll based on which nodes are currently visible. If nodes are invisible, hide their associated names.

2019-01-25_12-29-39_summary.json.zip
The above JSON has only 9/10 rounds visualized.

As per: https://www.fairvote.org/2018_election

The final round is displaying vote totals prior to the surplus redistribution that occurred in Round 6 in the attached image

Looks like an artifact of removing overflow votes in multi-winner, but needs to get fixed ASAP

e.g.: http://rcvis.arminsamii.com/visualize=2019-08-15_12-17-20_summaryjson-27#tabular-by-candidate -- in my tests, only the bar chart options work correctly; all other options move just below the navbar when clicked

edit: just saw your note "Don't scroll down when switching between different visualizations. Leave the top nav bar there." -- same thing)

As you scrub back and forth between rounds, it seems like the win threshold should adjust based on the selected round (and the ever increasing number of exhausted ballots (or are we calling them "concluded" ballots these days?)) instead of it just showing the final threshold no matter which round is elected. Does that make sense?

For these multi-winner contests, the threshold probably should be displayed in the title

It would look similar to how it is today, except instead of showing the most votes a candidate had, it would show how many votes they had on a certain round (meaning that it would show "0 [Eliminated]" for eliminated candidates, and wouldn't show results higher than Round X when the slider is on X. Thus, by paging through each round, the view can see how the election developed "frame by frame"

2019-01-25_12-29-39_summary.json.zip

Above is a screenshot and the JSON file (zipped)

The vote totals are only displayed to two digits whereas they need to be displayed to four digits (or whatever the local rule calls for).

George's goal is to get at least to the quality/completeness of Minneapolis' display options e.g. http://vote.minneapolismn.gov/results/2017/2017-mayor-tabulation -- we can discuss how best to implement display options

maybe reorganize navbar links? group somehow? the order seems kind of random, but I'm not 100% sure the best way to group/prioritize them in relation to each other.. I trust you to figure it out :)

Using a similar slider to the Bar graph option, create a new Tabular format which shows the results per-round, rather than the results per-candidate-per-round, so that it's similar to the CCD Round-by-Round results but they wouldn't live on their own page

maybe use a border with no fill, or a slight striped fill?

just capturing george's feedback on call

Done for the graphical representations, not the tabular. If we want it for tabular, can we create another story? (In short, the graphs can be done with a shared JS module, the tabular formats need a shared Python module - just the way I happened to architect it)

Delivered.

Old:

Fixed:

Notice that this bug led to several issues:

1. First-round incorrect totals
2. Incorrect totals for rounds after a winner had overvotes transferred away (C is correctly showing 7.25 votes instead of 8)
3. Incorrect total in the second-round caused by a combination of (1) and (2)

This was a bug only visible in multi-winner rounds with overflow votes getting redistributed, as visible here: http://rcvis.arminsamii.com/visualize=2019-02-04_22-51-06_summaryjson

George's goal is to get at least to the quality/completeness of Minneapolis' display options e.g. http://vote.minneapolismn.gov/results/2017/2017-mayor-tabulation -- we can discuss how best to implement display options

See below:

Introduced with TODO here:
6f29564#diff-0a389bec1693f4f3f11fe10c26578d3bR68
sankey.js:67

Requested by Eastpointe.
(is this easy? seems like it might not be)

Definitely a glitch somewhere - not sure if it's the tabulator or the visualizer

Need to figure out:

• Live or static embedding?
• Testing plan
• Should I be using oEmbed?