meaning - How high is “probability” in terms of likelihood as compared with “possibility”?

There is the following famous line in the book, “Life Lessons” co-authored by Elisabeth Kuble-Ross, an expert on death and dying and her colleague, David Kessler,

“We all live with the possibility of death, but the dying live with the probability.”

From this text, it seems “probability” has a larger chance of incidence happening than “possibility.”

Can we translate the level of likelihood of “possibility” and “probability” roughly into percentage of certainty? We say high / low possibility (likelihood). Can’t we say low probability?

P.S.

In Japan, we express possibility (可能性 -kanohsei in Japanese) by percentage, like “There will be 100 (80, 50, 20, 2-3) % possibility of earthquake taking place in Tokyo area in next 30 years,” and we seldom use the word, “蓋然性- gaizensei,” which is a counterpart to English “probability.” “蓋然性- gaizensei,” is a big word, and its usage is limited to academic or scientific writings.

Answer

This is a question Statistics professors ask within the first hour of Statistics 101. Possibility vs Probability vs Likelihood. Then the professor would give an interesting story and then he would leave it at a cliff-hanger and say that the rest of story will follow over the course of the next couple of semesters.

In Mathematics, we have the situation of qualitative vs quantitative.

Probability is measurable. It is quantitative.

Possibility is not measurable. Like beautiful, it is a qualitative term.

Likelihood, is the expectation of a probability. Perhaps, if you could understand the concept of acceleration of acceleration, you should be able to visualize the idea of expectation of chances, the probabilities of a probability.

what is the probability that the probability is 60%, measured two months prior to election day, of Hillary becoming President?

What is the likelihood that the poll figures in May, being the same as those in August? What is the likelihood that the probabilities due to the poll taken in May, accurately reflects Hillary's chances in October?

What is the likelihood that the probability due to the 1000 person sample accurately reflects the probable tendencies of this city of 100K?

What is the likelihood that when a tree falls in the forest, and only 2% chance that someone would notice it, and then what is the likelihood of that 2% probability being sufficiently insignificant that would allow us to say that there would be no sound observed?

When you ask

"What are the possibilities of the space shuttle having a stratospheric accident?" you are asking for the various ways the accident could occur.

"What is the probability of the space shuttle having a stratospheric accident?" you are asking for a signature number calculated to tell us how likely such an accident would occur. Such that out of 1000 flights, how many of them would explode in the stratosphere.

"Is there possibility of the space shuttle having a stratospheric accident?" you are asking if it is possible, yes/no.

"What is the possibility of the space shuttle having a stratospheric accident?" you are asking for that one descriptive possibility.

"What are the probabilities of the space shuttle having a stratospheric accident?" you are asking for the various methodologies of calculating the probability to tell us how likely such an accident would occur. Such that out of 1000 flights, how many of them would explode in the stratosphere, comparing various means of analyses.

And please refer to the statistics stack for Likelihood vs Probability.

And the wikipedia explanation.

Is there a word/phrase for "unperformant"?

As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...

What warning does Chuchundra issue to Rikki?

Chuchundra, the sniveling, fearful muskrat who creeps around walls because he is too terrified to go into the center of a room, meets Rikki in the middle of the night. He insults Rikki by begging him not to kill him. He then insults him by suggesting that Nag might mistake Chuchundra for Rikki. He says, "Those who kill snakes get killed by snakes." He issues this warning to Rikki not to help keep Rikki safe but as a way of explaining why Rikki's presence gives him, Chuchundra, more reason to fear. Chuchundra starts to tell Rikki what Chua the rat told him--but breaks it off when he realizes he might be overheard by Nag. He says, "Nag is everywhere, Rikki-Tikki." Rikki threatens to bite Chuchundra to get him to talk. Even then, Chuchundra won't overtly reveal any information. But he does say, "Can't you hear, Rikki-Tikki?" This is enough of a clue for the clever mongoose. He listens carefully and can just make out the "faintest scratch-s...

Notes

Search This Blog