Morning math/Voting systems - Revision history

50.0.83.116: adds model

2012-12-18T18:13:13Z

adds model

← Older revision		Revision as of 11:13, 18 December 2012
Line 1:		Line 1:
	~~A mathematical model can be very simple or very complex. The goal is to represent a system or process using precise definitions and mathematical relationships. One way to create a model~~ is to simply start building it, acknowledging it won't be perfect, but trying to improve the model along the way. Eventually you should arrive at a basic (fairly simple) model, which you can then make more complex (and perhaps more accurate) by elaborating in areas that previously were glossed over.		This project is an example of formulating a '''mathematical model'''. Read more about [[Morning math/Models \| mathematical models]]

	~~For instance, if I want to represent amount of daylight in a single day, one of the simplest models might be:~~

	* For any given day D, some percentage of that day occurs in which there is measurable daylight L.

	~~However, I can improve this model and make it more complicated by:~~

	* Measuring daylight L as hours, minutes, seconds, milliseconds (or similarly as some percentage up to a particular decimal point e.g. 49.255%) of some day.
	* Adding new variables, such as a geolocation--G<sub>1</sub> longitude and G<sub>2</sub> latitude, since daylight is a function of where on the earth measurement is taken. Or, allowing daylight to be more than a percentage, represented by an ~~additional variable for luminosity U (imagine clouds reducing the impact of daylight).~~

	~~However, perhaps some of the complications are not relevant given the context, so one may want to simplify the model to simply be:~~

	* Daylight L for any given day D is a function of ~~location only (G<sub>1</sub> longitude and G<sub>2</sub> latitude). Now, if we construct~~ a ~~look-up table for daylight at any given geolocation, we~~'~~d be able to find~~ ''~~'L(G<sub>1</sub>, G<sub>2</sub>) = some # of seconds per day D~~'''.

	==Voting systems Model==		==Voting systems Model==

50.0.83.116: adds voting model

2012-12-18T18:11:20Z

adds voting model

← Older revision		Revision as of 11:11, 18 December 2012
Line 15:		Line 15:

	==Voting systems Model==		==Voting systems Model==
			There are three sections to this model: variables (our basic definitions), relationships (attempts to represent a more complex understanding of the components of our model), and the side-line (items that will complicate the model further, to be tackled later, as we go).

			Overall questioning the "1 person, 1 vote" assumption in an effort to assess fairness and error in voting systems.

			===Variables===
			* V<sub>a</sub> = a voting event.
			* E = overall error
			* e = error
			* T = a topic to be voted upon
			* b = a single ballot
			* v = a vote (a choice)
			* J = jurisdiction (a geographic boundary)
			* M = a vote counting method
			* t = tabulation time
			===Relationships===
			# For any voting event V<sub>a</sub>, there exists an overall error E<sub>V<sub>a</sub></sub>.
			# For any voting event V<sub>a</sub>, there exists at least one jurisdiction J.
			# For any jurisdiction J, there exists an error e<sub>J</sub>.
			# For any jurisdiction J, there exists at least one vote-counting method M.
			# For any jurisdiction J, there exists n number of ballots b<sub>1</sub>, ..., b<sub>n</sub>.
			# For any jurisdiction J, there exists an average time to tabulate an individual ballot t<sub>M<sub>1</sub></sub>, ..., t<sub>M<sub>n</sub></sub>.
			# For any ballot b, there exists some number m of voting topics, T<sub>1</sub>, ..., T<sub>m</sub>.
			# For any ballot b, there exist v<sub>T<sub>1</sub></sub>, ... v<sub>T<sub>m</sub></sub> votes, each of which can be null (no vote).
			# For any ballot b, there exists a corresponding method M<sub>x</sub>
			# For any ballot b, there exists a ballot type y.
			===Side-line===
			* Rank-choice? -- Other voting styles, multiple votes per voter
			* Anecdotal secrete ballot
			* Some voters may require assistance (potential introduction to error?)
			* Vote-counting is functional
			* What about predictions?
			* Errors on basis of discernable intent of the registered voter.
			** We are not concerned with human intermediaries (e.g. volunteers).

50.0.83.116: creates page, intro

2012-12-18T17:48:52Z

creates page, intro

New page

A mathematical model can be very simple or very complex. The goal is to represent a system or process using precise definitions and mathematical relationships. One way to create a model is to simply start building it, acknowledging it won't be perfect, but trying to improve the model along the way. Eventually you should arrive at a basic (fairly simple) model, which you can then make more complex (and perhaps more accurate) by elaborating in areas that previously were glossed over.

For instance, if I want to represent amount of daylight in a single day, one of the simplest models might be:

* For any given day D, some percentage of that day occurs in which there is measurable daylight L.

However, I can improve this model and make it more complicated by:

* Measuring daylight L as hours, minutes, seconds, milliseconds (or similarly as some percentage up to a particular decimal point e.g. 49.255%) of some day.
* Adding new variables, such as a geolocation--G1 longitude and G2 latitude, since daylight is a function of where on the earth measurement is taken. Or, allowing daylight to be more than a percentage, represented by an additional variable for luminosity U (imagine clouds reducing the impact of daylight).

However, perhaps some of the complications are not relevant given the context, so one may want to simplify the model to simply be:

* Daylight L for any given day D is a function of location only (G1 longitude and G2 latitude). Now, if we construct a look-up table for daylight at any given geolocation, we'd be able to find '''L(G1, G2) = some # of seconds per day D'''.

==Voting systems Model==