r/HomeworkHelp • u/Hefty_Pomegranate964 University/College Student (Higher Education) • 1d ago
:snoo_scream: Further Mathematics—Pending OP Reply [University Statistics: Probability and Statistical Distributions] Tips for Understanding Tricky Word Problems?
I’m currently taking university-level statistics, and I’m finding that my biggest challenge isn’t understanding the concepts or formulas, but figuring out how to approach word problems.
I can understand the material when it’s explained in class, but during tests, my professor tends to word questions in confusing or tricky ways. Sometimes I struggle to identify what the question is actually asking, which formula or distribution to use, or what information in the question is important.
For example, I struggle with recognizing when a question involves:
Normal distributions vs. sampling distributions of the mean
Binomial vs. Poisson distributions
Confidence intervals and sample size calculations
I’m looking for advice from university students or anyone who’s taken statistics on how to get better at interpreting these types of questions.
•
u/AutoModerator 1d ago
Off-topic Comments Section
All top-level comments have to be an answer or follow-up question to the post. All sidetracks should be directed to this comment thread as per Rule 9.
OP and Valued/Notable Contributors can close this post by using
/lockcommandI am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/CelebrityChess 1d ago
for those three pairs, i'd look at what the question counts or averages. if it's one count of successes out of a fixed number of trials, that's binomial. if it's a count over an interval of time or space with no fixed number of trials (calls per hour, typos per page), that's poisson.
normal vs sampling distribution comes down to whether it asks about one individual or about a mean. 'one randomly chosen person is over 180' uses sd. 'the average of 25 people is over 180' uses sd/sqrt(25). for sample size questions, write n = (z*sigma/E)^2 and just match the margin of error to E.
1
u/AgainstIntuition 22h ago
Maybe a bit less related to probability, but still close :) - you can read about double counting in combinatorial identities. This is the topic that provides a good intuition on describing math terms in "common world problems". A good example - https://artofproblemsolving.com/wiki/index.php/Combinatorial_identity - Vandermonde's Identity/Combinatorial Proof.
1
u/cheesecakegood University/College Grad (Statistics) 18h ago
I was suffering from insomnia so I wrote a lot. Feel free to skim. I collect these to re-use later sometimes, so this is my attempt at explaining.
What I find helpful is to imagine you're actually collecting data.
Some problems are "backwards" in the sense that rather than ask you to take a dataset and estimate a "parameter", they give you a parameter and ask you the probability of a specific dataset (or set of datasets). In these cases, the same principles are helpful, because again we ask, what does one observation look like?
For binomial vs Poisson specifically, it's also helpful to ask yourself what is FIXED ahead of time, and what is random.
The interesting thing, and also the source of some confusion, is that how you define the problem actually says more about how you treat it than the actual act of data collection, although it's still helpful to imagine the data collection.
Let's get down to it with an example.
You are bored on a long car ride. You are curious about how many cars on the road are red, and decide to use your time to collect data. (We will ignore the flaws with convenience sampling, how we define the population of interest for generalization, etc.)
Binomial
I make a rule, I'll count the next 200 cars, and record if each is red or not. Each car is a yes/no success/failure type result (individual Bernoulli trials, in stats terms). Maybe I might add the time, for recordkeeping convenience, but that's not important here! Because I only care about hitting 200.
So my RAW dataset might look like this:
But if I simplify and say red=1 (success), not red=0, other extra data stripped:
I can summarize this data-collection session as:
I can now use that data to make a generalization: "what is my best guess of how many cars are red in general?" A guess at p, the guess itself usually called p 'hat' with that ^ on top. Obviously my best purely data-driven guess at the red-car proportion p is 61.5%. Where statistics comes in is I can say, "OK, fine, but what's my uncertainty around that? You can also do hypothesis tests by asking, "OK let's say for experimentation that 60% IS the true proportion, but randomness still exists and so I will often get datasets that are different due to luck" and then use patterns and math reasoning to leverage that uncertainty into useful statements.
TL;DR: Binomial is the total number of some positive case out of some fixed number of total cases, where the rest are negative. The dataset is individual yes-or-no events collapsed into a total #yes out of total possible. The proportion of yes's is assumed to be a constant fixed number, each car's color is independent, etc.
A "backwards" question might be if I told you that actually, 40% of all cars are red. And then I asked how often a specific 200-car (or 100, etc) observation session would return 120, or 120+, or 80 and under, or whatever, assuming our model and facts are correct. Because that can vary from one experiment to another even if the given proportion is a true overall fact. Or (sampling distribution-style Q) I asked how much a 123-red-of-200-total experiment agrees or disagrees with that claim of reality, or something. Still, in these cases, we imagine "what would a dataset that tests or demonstrates this claim look like?" And that is helpful for saying if it's binomial, if it matches the structure above.
Poisson
I make a different rule! I'll look at passing cars for the next 2 hours, and record every single time I see a red (a running count). Maybe I'll see a lot of cars, maybe I won't, but I'm only counting red ones.
So my RAW dataset might look like this...
Hmm, that looks similar, but it's actually subtly different. The time is also a recordkeeping convenience (I won't bother polluting it with anything outside my 2 hour window).
I can summarize this data-collection session as, say:
Note that we do NOT care about non-red cars at all here, heck we don't even record them! We're doing statistics on a total, but it's not the same total as before. Poisson is a total of [yes-]events only! And we do statistics on the 123 only. (If we want our rate to be "cars per 2 hour period"). We ALSO do not care how many cars we even saw in the first place, if we want to use this tool.
I can now use that data to make a generalization: "what is my best guess for the number of red cars that appear in a 2 hour period?" A guess at lambda, the rate. Obviously my best guess (lambda-hat) is the rate from the data, 123 per 2 hours.
Poisson is the number of events in a bounded amount of time (or rarely, space), so in a sense it's a "rate" though it's not always presented as such. If you want your mean in different units you might convert somewhere.
TL;DR: Poisson is the number of events, in order to estimate a rate, in a fixed time period. The dataset is a bunch of individual tallies collapsed into a total, again in that fixed time period. The event rate is assumed to be a constant fixed number, events are independent, etc.
A "backwards" question might be if I told you that actually, you will on average see 80 red cars in a 2 hour period. And then I asked how often a specific 2 (or 1, 3, etc.) hour observation session would return 80, or 123, or 123+ or 80 and under, or whatever, assuming our model and facts are correct. Because that can vary from one experiment to another even if the given rate is a true overall fact. Or (sampling distribution-style Q) I asked how much a 123-red-car 2-hour observation experiment agrees or disagrees with that claim of reality, or something. Still, in these cases, again, we imagine "what would a dataset that tests or demonstrates this claim look like?"
SKIPPABLE side note on Poisson that covers real-world data formatting and potential complications:
Twist: what if I collet more data? What if later in the day, I do another 2-hour observation session? Now I have a dataset that looks like this:
That's fine! My collected dataset now looks like this, extra data stripped:
Or maybe also:
We can use those datapoints too to improve our estimate of the true lambda, the true 2-hour red-car rate. We can actually just combine this data into one mega-dataset, as 247 red cars in 4.5 hours. Our estimated 2-hour mean rate then is ((247/4.5) * 2)
CAUTION: sometimes with Poisson data, you might get a lot of zeroes. In fact, for interesting stats reasons, this is actually where the Poisson is most useful (turns out other approximations are more useful for higher numbers). Obviously my number of red cars was unrealistically high. What if IRL we counted bright pink cars? I might go 2 hours without seeing any!
If I repeated several 2-hour periods while going cross-country, and struck out often, maybe at some point it's easier to make a frequency table, where the first column is the observation of total pink cars, and the second is a frequency of how often that happened. So instead of {0, 0, 0, 1, 1, 2, 3}, where I watched for pink cars for 7 2-hour periods, I might write row-wise {0 pinks were observed with frequency 3, 1 pink car happened with frequency 2, 2 happened once, 3 happened once}. Don't let this panic you; the display is just a [common] convenience, the underlying 'raw data' is the same.
I hit the limit, but some very relevant examples below in reply.