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.

Sign up for GitHub

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

Move form HTML out into its own file #1

Open
wants to merge 4 commits into
base: website
Choose a base branch
from
Open

Move form HTML out into its own file #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
462fdec
Website: move static form HTML out into its own file
tom-votes Dec 3, 2018
2044b07
Standards-compliant index.html
tom-votes Dec 3, 2018
0ba36a0
Add note about working with HTML and 'autoreloader'
tom-votes Dec 3, 2018
cea2f79
Merge remote-tracking branch 'upstream/website' into website
zperumal Jan 13, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
372 changes: 372 additions & 0 deletions code/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,372 @@
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8" />
<style>
input[type=text], select {
width: 50%;
padding: 12px 20px;
margin: 8px 0;
display: inline-block;
border: 1px solid #ccc;
border-radius: 4px;
box-sizing: border-box;
}
input[type=submit] {
width: 100%;
background-color: #4CAF50;
color: white;
font-size: 14px;
padding: 15px 20px;
margin: 8px 0;
border-radius: 4px;
}

table, th, td {
border: 1px solid black;
}
</style>
<title>Bayesian Ballot Comparison Tool</title>
</head>
<body>
<h1> Bayesian Ballot Comparison Tool </h1>
<p>This module provides support for auditing of a single plurality contest
over multiple jurisdictions using a Bayesian ballot-level
comparison audit.</p>

<p>This module provides routines for computing the winning probabilities
for various choices, given audit sample data. Thus, this program
provides a risk-measuring functionality.</p>

<p>More precisely, the code builds a Bayesian model of the unsampled
ballots, given the sampled ballots. This model is probabilistic,
since there is uncertainty about what the unsampled ballots are.
However, the model is generative: we generate many possible
sets of likely unsampled ballots, and report the probability that
various choices win the contest. (See References below for
more details.)</p>

<p>The main output of the program is a report on the probability
that each choice wins, in these simulations.</p>

<p>The contest may be single-jurisdiction or multi-jurisdiction.
More precisely, we assume that there are a number of "collections"
of ballots that may be sampled. Each relevant jurisdiction may
have one or more such collections. For example, a jurisdiction
may be a county, with one collection for ballots submitted by
mail, and one collection for ballots cast in-person.</p>

<p>This module may be used for ballot-polling audits (where there
no reported choices for ballots) or "hybrid" audits (where some
collections have reported choices for ballots, and some have not).</p>

<h2> References and Code</h2>
<p> Descriptions of Bayesian auditing methods can be found in: </p>
<ul>
<li><a href="http://people.csail.mit.edu/rivest/pubs.html#RS12z">
A Bayesian Method for Auditing Elections</a>
by Ronald L. Rivest and Emily Shen
EVN/WOTE'12 Proceedings
</li>

<li><a href="http://people.csail.mit.edu/rivest/pubs.html#Riv18a">
Bayesian Tabulation Audits: Explained and Extended</a>
by Ronald L. Rivest
2018
</li>

<li><a href="http://people.csail.mit.edu/rivest/pubs.html#Riv18b">
Bayesian Election Audits in One Page</a>
by Ronald L. Rivest
2018
</li>

</ul>

<h2>Implementation Note</h2>
<p> The code for this tool is available on github at
<a href="https://github.com/ron-rivest/2018-bctool">www.github.com/ron-rivest/2018-bctool</a>.
This web form provides exactly the same functionality as the stand-alone
Python tool
<a href=https://github.com/ron-rivest/2018-bctool>www.github.com/ron-rivest/2018-bctool/BCTool.py</a>.
The Python tool
requires an environment set up with Python 3 and Numpy.
This web form was implemented using
<a href="https://github.com/cherrypy/cherrypy">
CherryPy
</a>.
<p>(See <a href="https://github.com/ron-rivest/2018-bptool">www.github.com/ron-rivest/2018-bptool</a>
for similar code for a Bayesian ballot-level polling audit. The code here was based
in part on that code.)
</p>


<form action="ComparisonAudit" method="post" enctype="multipart/form-data">

<h2>Step 1: Upload Collections File</h2>

<p> In the box below, upload a CSV file with the data about collections
in the contest being audited. </p>

<h3>
COLLECTIONS.CSV format:</h3>

<p>Example collections.csv file:</p>

<table style="width:100%">
<tr>
<th style="text-align:center">Collection</th>
<th style="text-align:center">Votes</th>
<th style="text-align:center">Comment</th>
</tr>
<tr>
<td style="text-align:center">Bronx</td>
<td style="text-align:center">11000</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Queens</td>
<td style="text-align:center">120000</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Mail-In</td>
<td style="text-align:center">56000</td>
<td style="text-align:center"></td>
</tr>
</table>

<p>with one header line, as shown, then one data line for
each collection of paper ballots that may be sampled.
Each data line gives the name of the collection and
then the number of cast votes in that collection
(that is, the number of cast paper ballots in the collection).
An additional column for optional comments is provided.</p>


Collections File: <input type="file" name="collections" />

<h2>Step 2: Upload Reported Votes File</h2>

<p> In the box below, upload a CSV file with the data about the reported votes
in the contest being audited. </p>

<h3>
REPORTED.CSV format:</h3>

<p>Example reported.csv file:</p>

<table style="width:100%">
<tr>
<th style="text-align:center">Collection</th>
<th style="text-align:center">Reported</th>
<th style="text-align:center">Votes</th>
<th style="text-align:center">Comment</th>
</tr>
<tr>
<td style="text-align:center">Bronx</td>
<td style="text-align:center">Yes</td>
<td style="text-align:center">8500</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Bronx</td>
<td style="text-align:center">No</td>
<td style="text-align:center">2500</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Queens</td>
<td style="text-align:center">Yes</td>
<td style="text-align:center">100000</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Queens</td>
<td style="text-align:center">No</td>
<td style="text-align:center">20000</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Mail-In</td>
<td style="text-align:center">Yes</td>
<td style="text-align:center">5990</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Mail-In</td>
<td style="text-align:center">No</td>
<td style="text-align:center">50000</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Mail-In</td>
<td style="text-align:center">Overvote</td>
<td style="text-align:center">10</td>
<td style="text-align:center"></td>
</tr>
</table>

<p>with one header line, as shown, then one data line for each
collection and each reported choice in that collection,
giving the number of times such reported choice is reported
to have appeared. An additional column for optional comments is
provided.</p>

<p>A reported choice need not be listed, if it occurred zero times,
although every possible choice (except write-ins) should be listed
at least once for some contest, so that this program knows what the
possible votes are for this contest.</p>

<p>For each collection, the sum, over reported choices, of the Votes given
should equal the Votes value given in the corresponding line in
the collections.csv file.</p>

<p>Write-ins may be specified as desired, perhaps with a string
such as "Write-in:Alice Jones".</p>

<p>For ballot-polling audits, use a reported choice of "-MISSING"
or "-noCVR" or any identifier starting with a "-". (Tagging
the identifier with an initial "-" prevents it from becoming
elegible for winning the contest.)</p>

Reported Votes File: <input type="file" name="reported_votes" />

<h2>Step 3: Upload Sampled Votes File</h2>

<p> In the box below, upload a CSV file with the data about the samples
from the contest being audited. </p>

<h3>
SAMPLE.CSV format:</h3>

<p>Example sample.csv file:</p>

<table style="width:100%">
<tr>
<th style="text-align:center">Collection</th>
<th style="text-align:center">Reported</th>
<th style="text-align:center">Actual</th>
<th style="text-align:center">Votes</th>
<th style="text-align:center">Comment</th>
</tr>
<tr>
<td style="text-align:center">Bronx</td>
<td style="text-align:center">Yes</td>
<td style="text-align:center">Yes</td>
<td style="text-align:center">62</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Bronx</td>
<td style="text-align:center">No</td>
<td style="text-align:center">No</td>
<td style="text-align:center">21</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Bronx</td>
<td style="text-align:center">No</td>
<td style="text-align:center">Overvote</td>
<td style="text-align:center">1</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Queens</td>
<td style="text-align:center">Yes</td>
<td style="text-align:center">Yes</td>
<td style="text-align:center">504</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Queens</td>
<td style="text-align:center">No</td>
<td style="text-align:center">No</td>
<td style="text-align:center">99</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Mail-In</td>
<td style="text-align:center">Yes</td>
<td style="text-align:center">Yes</td>
<td style="text-align:center">17</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Mail-In</td>
<td style="text-align:center">No</td>
<td style="text-align:center">No</td>
<td style="text-align:center">73</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Mail-In</td>
<td style="text-align:center">No</td>
<td style="text-align:center">Lizard People</td>
<td style="text-align:center">2</td>
<td style="text-align:center"></td>
</tr>
<tr>
<td style="text-align:center">Mail-In</td>
<td style="text-align:center">No</td>
<td style="text-align:center">Lizard People</td>
<td style="text-align:center">1</td>
<td style="text-align:center"></td>
</tr>
</table>

<p>with one header line, as shown then at least one data line for
each collection for each reported/actual choice pair that was seen
in the audit sample at least once, giving the number of times it
was seen in the sample. An additional column for comments is
provided.</p>

<p>There is no need to give a data line for a reported/actual pair
that wasn't seen in the sample.</p>

<p>If you give more than one data line for a given collection,
reported choice, and actual choice combination, then the votes
are summed. (So the mail-in collection has three ballots the scanner said
showed "No", but that the auditors said actually showed "Lizard
People".) For example, you may give one line per audited ballot,
if you wish.</p>

<p>The lines of this file do not need to be in any particular order.
You can just add more lines to the end of this file as the audit
progresses, if you like.</p>

Sample Votes File: <input type="file" name="sample" />

<h2>(Optional) Specify random number seed</h2>
<p>
The computation uses a random number seed, which defaults to 1.
You may if you wish enter a different seed here.
(Using the same seed with the same data always returns the same results.)
This is an optional parameter; there should be no reason to change it.
</p>

Seed: <input type="text" name="seed" />

<h2>(Optional) Specify number of trials</h2>
<p>Bayesian audits work by simulating the data which hasn't been sampled to
estimate the chance that each candidate would win a full hand recount.
You may specify in the box below the number of
trials used to compute these estimates.
This is an optional parameter, defaulting to 10000. Making it smaller
will decrease accuracy and improve running time; making it larger will
improve accuracy and increase running time.
</p>

Number of trials:<input type="text" name="num_trials" />

<h2>Compute results</h2>
Click on the "Submit" button below to compute the desired answers,
which will be shown on a separate page.
<input type="submit" />

Note: The Bayesian prior is represented by a pseudocount of one vote for
each choice. This may become an optional input parameter later.
</form>
</body>
</html>

Loading