DaveC426913 said:
No, I'm considering it as a valid outcome in a hypothetical game. "If it lands on its edge, you win a car!" or some such.
I'm simply pointing out what Dale was after - to prove (to myself) that fixed integer starting options can lead to outcomes that can't be represented as an equal-probability-per-row table.
Unlike the standard probability distribution for a coin toss, which is used as a model for a 50:50 chance, the probability of a coin landing on its edge is inestimable and extremely small. Your reply to
@Dale in response to his saying that not all dice are fair, "Then you might as well include spurious winds and inclement weather in the table!", is equally applicable to your acceptance of an edge landing for a coin toss as a possibility that should be reflected in a table of coin toss outcomes.
A proper table for a single coin toss has 2 cells, one for heads and one for tails, unless there is some other outcome condition that pivotally matters.
Using 2 table rows of 1 cell each, 1 row for left-handed tosses that result in heads, and 1 for right-handed tosses that result in heads, with only 1 table row for a toss, with either hand, that results in tails, when the bet is won or lost depending only on whether the actual outcome is heads or tails, is unnecessarily informative, and could invite the mis-supposition that there are 3 possibilities, and therefore 1/3 chance for each.
I think that saying that there are 3 possibilities, 2 with 1/4 chance each, which should then be summed to 2/4, and 1 possibility that is 1/2, for the 2 'outcomes' that have heads in common, along with the 1 tails outcome, is not the best remedy for the potential of some persons to be misled in the matter, and that a better remedy would be ignoring the superfluous information of which hand was used to perform the toss.
I think that such a scenario of using and explaining 3 table rows for a 2-sided coin toss is functionally similar to, albeit somewhat simpler than, the using and explaining of 4 table rows for 3 car locations scenario that was presented at the inception of this thread.
Including repetitions of the same outcome on the grounds of there being or not being something irrelevant that took place in conjunction with the pivotal event, e.g. music was or wasn't playing during the event, is a different error from including a remote possibility that the conventional procedure as normally stated does not include as a possibility.
Let's please look further at the example of a table of outcomes for a throw of 2 dice -- a pair of two fair cubic dice is thrown -- no edge or vertex landing -- proper 1-face-up landings only, 36 possible pair outcomes, 11 possible sums -- some of the sums will have higher probability than others -- each cell on the outcome table represents a single ordered ##\mathtt {(An, Bn)}## or ##\mathtt {(Bn, An)}## pair:
\begin{array}{|c|c|c|c|c|c|c|c|c|c|}
\hline\ \ \ \ \ &\ \ \mathtt {A1}\ \ &\ \ \ \mathtt {A2}\ \ &\ \ \ \mathtt {A3}\ \ &\ \ \ \mathtt {A4}\ \ &\ \ \ \mathtt {A5}\ \ &\ \ \mathtt {A6}\ \ \\
\hline\ \ \ \mathtt {B1}\ \ &\ \ \mathtt 2\ \ &\ \ \mathtt 3\ &\ \ \mathtt 4\ &\ \ \mathtt 5\ &\ \ \mathtt 6\ &\ \ \mathtt 7\ \ \\
\hline\ \ \ \mathtt {B2}\ \ &\ \ \mathtt 3\ \ &\ \ \mathtt 4\ &\ \ \mathtt 5\ &\ \ \mathtt 6\ &\ \ \mathtt 7\ &\ \ \mathtt 8\ \ \\
\hline\ \ \ \mathtt {B3}\ \ &\ \ \mathtt 4\ \ &\ \ \mathtt 5\ &\ \ \mathtt 6\ &\ \ \mathtt 7\ &\ \ \mathtt 8\ &\ \ \mathtt 9\ \ \\
\hline\ \ \ \mathtt {B4}\ \ &\ \ \mathtt 5\ \ &\ \ \mathtt 6\ &\ \ \mathtt 7\ &\ \ \mathtt 8\ &\ \ \mathtt 9\ &\ \ \mathtt {10}\ \ \\
\hline\ \ \ \mathtt {B5}\ \ &\ \ \mathtt 6\ \ &\ \ \mathtt 7\ &\ \ \mathtt 8\ &\ \ \mathtt 9\ &\ \ \mathtt {10}\ &\ \ \mathtt {11}\ \ \\
\hline\ \ \ \mathtt {B6}\ \ &\ \ \mathtt 7\ \ &\ \ \mathtt 8\ &\ \ \mathtt 9\ &\ \ \mathtt {10}\ &\ \ \mathtt {11}\ &\ \ \mathtt {12}\ \ \\
\hline
\end{array}
The table shows one cell per ordered pair outcome. When each of the 2 dice shows the same number there is only 1 cell for that pair, whereas when the 2 numbers are different, ##\mathtt {(An, Bn)}## is a different outcome from ##\mathtt {(Bn, An)}##, just as on a planar ##(x,y)## graph, when ##x=y##, then only the same point is defined as when ##y=x##, not 2 distinct points, as when ##x \neq y##. The cells contain the sums of the values on the 2 dice.
The number of possibilities for each die is 6, and the number of possible outcomes for the 2 dice is the number of possibilities per die times the number of dice: 6(6)=36. The chance for each outcome is therefore 1/36, but that's not the total chance for any 1 outcome sum; the number of cells for each possible sum is not the same as the number of cells for each other possible sum.
Dale said:
The point is that there is no single procedure or rule for writing tables that will have the following properties for all games: no lines are repeated, each line has equal probability. Therefore, you should augment the table with one or more columns for probability. That way you can choose the rules for writing your rows as you like and always come out with a correct analysis.
Without the probability column, no rule for writing the rows will give correct probabilities for all games. With the probability column, any rule for writing the rows will give correct probabilities for all games.
If the purpose of constructing the table is to learn the total per-throw probability for each of the sums, then it doesn't make sense that the table should have to contain in advance an explicit reference to the probability for each sum.
Instead, we can use the table to help us to sum the number of possibilities for each possible sum, 2-12 inclusive, and thereby determine the total probability per throw for each possible sum.
It can be seen at once that the sums in the cells along each of the ##\mathtt {(An \to Bn)}## diagonals, i.e., those diagonals such that ##\mathtt {(A1 \to B1 \dots A6 \to B6)}##, are the same, and that no equal sums appear elsewhere on the table. That makes the following table, of total probabilities per throw for each sum easy to construct; the number of instances of each sum is the number of instances of it in its diagonal, i.e., the total number of cells in the ##\mathtt {An \to Bn}## diagonal in which exclusively that sum exclusively appears:
\begin{array}{|c|c|c|c|c|c|c|c|c|c|c|}
\hline \mathtt {sum~of~dice} & \mathtt {2} & \mathtt {3} & \mathtt {4} & \mathtt {5} & \mathtt {6} & \mathtt {7} & \mathtt {8} & \mathtt {9} & \mathtt {10} & \mathtt {11} & \mathtt {12}\\
\hline \mathtt {num~of~cells} & \mathtt {1} & \mathtt {2} & \mathtt {3} & \mathtt {4} & \mathtt {5} & \mathtt {6} & \mathtt {5} & \mathtt {4} & \mathtt {3} & \mathtt {2} & \mathtt {1}\\
\hline \mathtt {num/36 (dec)} & \mathtt {.02 \overline 7} & \mathtt {.0 \overline 5} & \mathtt {.08 \overline 3} & \mathtt {. \overline 1} & \mathtt {.13 \overline 8} & \mathtt {.1 \overline 6} & \mathtt {.13 \overline 8} & \mathtt {. \overline 1} & \mathtt {.08 \overline 3} & \mathtt {.0 \overline 5} & \mathtt {.02 \overline 7}\\
\hline
\end{array}
The tables above, and the table that you (
@DaveC426913) posted in post #103, do not over-represent any of the possible actual outcomes, and in not so over-representing, they do not thereby omit any actual outcomes.
Dale said:
Goats are not electrons. They are distinguishable. The two different goats are two distinguishable outcomes and can reasonably be counted as separate rows in a table, just like different faces of a dice are put in separate rows even if for the purposes of a given game they are equivalent.
They're not final outcomes, and they don't affect any of the car location outcomes, including the final outcome that they share in representing.
In the 4-line table presented by
@cmb in post #1, the 2 'outcomes' that are acting as co-aliases for 1 car location outcome, the 1 such that the car is behind the door originally chosen, are listed not as sub-outcomes for 1 car location outcome, but instead are each presented as outcomes at the same level as the 2 other car location outcomes, and consequently they make the 4-line table misleading.
I think that using a second row for that single car location makes the table less readily useful for the above-illustrated purpose of enumerating the relevant probabilities by correctly counting all and only the 3 actually different car location outcomes.
It's true that there are 2 possible pre-revealed-location-sub-outcomes for that 1 behind-the-originally-chosen-door 1/3 probable car location outcome, but the difference between those 2 non-car-location-sub-outcomes in no way affects the car location outcome, so giving procedural cognizance to them, in my view, is at best embracement of a distraction.
I think that even listing them as 2 sub-outcomes with 1/2 each of the 1/3 probability for the 1 possible car location that they share in representing, prescribes too much attention being given to which door is opened when the car is behind the door originally chosen.