Skip to content
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

Decide how to deal with STV CVRs #107

Open
vteague opened this issue Jun 6, 2024 · 1 comment
Open

Decide how to deal with STV CVRs #107

vteague opened this issue Jun 6, 2024 · 1 comment
Labels
Development Documentation Improvements or additions to documentation

Comments

@vteague
Copy link
Member

vteague commented Jun 6, 2024

Although we are not required to audit STV contests (i.e. multi-winner preferential contests), we need to ensure that colorado-rla does not break when they are uploaded. This requires a bit of thought. Probably we want three types of contests: plurality, IRV and STV.
Probably:

  • when parsing, a contest with ranks and multiple winners should be STV,
  • STV contests should be always NOT_AUDITABLE
  • STV contests cannot be targeted for audit
  • STV winners should have a clear placeholder (e.g. UNKNOWN or "") - note that the default contest counter will get the wrong winner, just as it does for IRV.
  • STV estimatedSampleSizes and optimisticSampleSizes should match the values for other NOT_AUDITABLE contests. (I have a vague recollection that this is 0, but we should check.)

Think about whether we could easily get a count of 'other discrepancy' in the event that an STV contest happens to be on an audited ballot.

Consider whether all this is best achieved with an STVComparisonAudit class.

@vteague vteague added Development Documentation Improvements or additions to documentation labels Jun 6, 2024
@vteague vteague assigned vteague and unassigned vteague Jun 6, 2024
@vteague
Copy link
Member Author

vteague commented Jul 14, 2024

This will probably also need to update ReportRows::genSumResultsReport, just to make sure the tallies computed by countContest are not output for STV (where they will be wrong).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development Documentation Improvements or additions to documentation
Projects
Status: Elicit requirements
Development

No branches or pull requests

1 participant