- 20
- -2
What is this place?
This website is a place for people who want to move past shady thinking and test their ideas in a
court of people who don't all share the same biases. Our goal is to
optimize for light, not heat; this is a group effort, and all commentators are asked to do their part.
The weekly Culture War threads host the most
controversial topics and are the most visible aspect of The Motte. However, many other topics are
appropriate here. We encourage people to post anything related to science, politics, or philosophy;
if in doubt, post!
Check out The Vault for an archive of old quality posts.
You are encouraged to crosspost these elsewhere.
Why are you called The Motte?
A motte is a stone keep on a raised earthwork common in early medieval fortifications. More pertinently,
it's an element in a rhetorical move called a "Motte-and-Bailey",
originally identified by
philosopher Nicholas Shackel. It describes the tendency in discourse for people to move from a controversial
but high value claim to a defensible but less exciting one upon any resistance to the former. He likens
this to the medieval fortification, where a desirable land (the bailey) is abandoned when in danger for
the more easily defended motte. In Shackel's words, "The Motte represents the defensible but undesired
propositions to which one retreats when hard pressed."
On The Motte, always attempt to remain inside your defensible territory, even if you are not being pressed.
New post guidelines
If you're posting something that isn't related to the culture war, we encourage you to post a thread for it.
A submission statement is highly appreciated, but isn't necessary for text posts or links to largely-text posts
such as blogs or news articles; if we're unsure of the value of your post, we might remove it until you add a
submission statement. A submission statement is required for non-text sources (videos, podcasts, images).
Culture war posts go in the culture war thread; all links must either include a submission statement or
significant commentary. Bare links without those will be removed.
If in doubt, please post it!
Rules
- Courtesy
- Content
- Engagement
- When disagreeing with someone, state your objections explicitly.
- Proactively provide evidence in proportion to how partisan and inflammatory your claim might be.
- Accept temporary bans as a time-out, and don't attempt to rejoin the conversation until it's lifted.
- Don't attempt to build consensus or enforce ideological conformity.
- Write like everyone is reading and you want them to be included in the discussion.
- The Wildcard Rule
- The Metarule
Jump in the discussion.
No email address required.
Notes -
I have no idea what you're trying to say here. If you have a distribution for the probability of heads, you can calculate the probability of getting heads. For any symmetrical distribution, it will be 50%, reflecting the fact that you have no reason to favor heads over tails.
Think about it this way: Suppose that you have a much simpler distribution over p, the probability of heads, where it's 0.4 with probability 0.3, otherwise 0.7 Then by the law of total probability, the probability of heads is (probability of heads given p=0.4)*(probability p = 0.4) + (probability of heads given p = 0.7) * (probability p = 0.7) which is clearly 0.12 + 0.49 = 0.61. You might note this is also the expected value of p; in the continuous case, we would use the formula integral_0^1 xf(x) dx where f is the PDF. For your solution, Beta(9, 3), this is just 9/12 = 0.75. This is basically the same example as at the top of https://en.wikipedia.org/wiki/Law_of_total_expectation#Example
I never said it was? It was just another example where you can compute a specific property of the underlying random variable, given a distribution on one of its parameters.
Actually you can't. I don't think you quite understand the point. I can program a
f()
function that return headsp
percent of the time. How many results do you need to accurately "calculate the probability of getting heads"?OK.
Yes, but the "expected value" is not "the answer".
I programmed your example of
0.3*0.4/0.7*0.7
asg(0.3)
, let's say that the thresholdt
in this case is 0.3, but I choose a different threshold for comparison and I run the function 10 times. Can you guess which results are which?[0.7, 0.4, 0.7, 0.7, 0.7, 0.7, 0.4, 0.7, 0.7, 0.4]
[0.7, 0.7, 0.7, 0.7, 0.4, 0.7, 0.7, 0.4, 0.7, 0.7]
Which is
g(0.3)
, which isg(t)
, and what do you guess is the value oft
I choose?What is "accurately"? The method I described will give the correct probability given all of the information available. As you gather more information, the probability changes. Are you getting confused between probability and statistics?
Yes, you can. I just gave you a complete worked example.
In this case, it is. In fact, in any case where you have binary outcome and independent events, the expected number of successes is equal to the p*the number of trials. In the special case of n=1 coin flip, we have E(number of heads) = p. See https://en.wikipedia.org/wiki/Binomial_distribution
It won't.
It's not.
Yes, but it is not. You got it wrong.
But it is not 0.2.
This is the whole point of the article: to raise doubt. But you are not even considering the possibility that you might be wrong, I bet even when I'm telling you the values of
t
in those examples are not the ones you guessed, you will still not consider the possibility that you are wrong, even when the answers are objectively incorrect.It will.
It is.
It seems like you don't know enough probability to really have this discussion. "The expected number of heads from 1 flip is equal to the probability of heads" is a trivial calculation.
That's not how probability works. I said it was more likely and that statement is correct. Just like how in your original coin flip example, it is more likely that p is 0.8 than 0.3, but if it really was 0.3 and you just got unlucky your answer would not have been "wrong" because that's not how probabilistic statements are judged.
Do you know not what an estimate is?
This blatant strawmanning isn't helping your case. The statements I made above about probability are correct, they are fairly basic mathematical ideas that get used all the time. If you think they're wrong, provide an actual argument. I have never said anything like "t is definitely 0.2" nor do I care what its value is, because it's an irrelevant exercise. Have you considered that you might be wrong?
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link