12:22 AM
@Matt I wouldn't categorize things nearly so harshly. There can be perfectly legitimate reasons to treat something as linear even if it might not be (we do it every time we fit a linear model, for goodness sake). George Box's maxim (in Box and Draper as "Remember that all models are wrong; the practical question is how wrong do they have to be to not be useful") applies here as much as anywhere else. Such assumptions have their place!
They're not especially common, I think, but it can be a reasonable approach with ordered categories.
R has the nice feature of by default coding up the model matrix for ordered categories as orthogonal polynomials, so if you're really after a simpler model (or at least, one containing an additional assumption), like a linear one, you can do that, or if you want to fit a "full" model but see whether it's close to linear, you can do that.
Or if you want to investigate smooth deviations from linearity (eg imagine 6 ordered categories but where you think the means for the categories should progress nonlinearly but smoothly) you can do that (by, for example, only fitting the linear to cubic terms, say)
As an alternative of course, one could consider "nonparametric" smooths instead (and that may be better in many situations, though the orthogonal-polynomial route has some interesting/useful features)
One thing to keep in mind is that for many areas, data is hard to obtain, and power to pick up an effect (in particular, the impact of variance) may be more important that a bit of bias in a model. If you had a hundred times as many subjects, bias would rule and it would make no sense to consider anything but a full model. In very small samples, variance rules.
1:49 AM
@MatthewDrury "Suppose we have an eigenspace, but also a vector outside of the eigenspace that the matrix sends inside of the eigenspace. When that happens, the matrix cannot be diagonalizable." I might be missing something from the context, but diag(0,1) is obviously diagonalizable, being diagonal already. (1,1)^t is not in the eigenspace as it's mapped to (0,1)^t, but that is in the eigenspace (being mapped to itself, lambda=1).
Is this not a vector outside an eigenspace sent inside an eigenspace by a diagonalizable matrix? I think I've missed something.
On an unrelated note... I see it took just two minutes for me to go from 665 helpful flags to 667, hence almost entirely avoiding the dreaded sextuple Nelson. I envision a moderator hopping on one leg for the duration.
2
1 hour later…
3:05 AM
1 hour later…
8 hours later…
12:17 PM
221
What is Stack Overflow's long-term solution for the Help Vampire problem? Quote from article follows: Identifying Help Vampires can be tricky, because they look like any ordinary person (or Internet user, whichever is lesser). But by closely observing an individual's behavior using this hand...
52
Here are some further symptoms of a help vampire, viz a poster who treats the SO community as they would an online product support chat helpline, viz, a user who: Will continue to extend the original question with continued questions, even after the original question has been well answered. Pro...
2 hours later…
2:48 PM
3:43 PM
It is funny that in the voting about When re-tagging old threads, how many should one do at once? the leading answer is up to 5 and the second leading is no limit at all. I invite more people to contribute there, because this is kind of important.
6 hours later…
9:56 PM
@general I saw your vote -- I was letting you know I agreed with that judgement. It's closed, the OP needs to improve the question now. You've gone above and beyond already in comments, so you needn't worry.
@amoeba It is. I voted as soon as I saw it. Personally I'd have thought the split "should we have a limit or not" would be a first vote and then worry about how big it should be. Otherwise you could end up with a majority of people voting for a limit -- and even regarding no limit as the worst of all possible choices -- yet no limit might get up because enough limit options were available.
It's one of the big problems with first past the post voting -- if you offer similar options you dilute their vote.
None of this is intended as criticism of your actions. It's an observation on the nature of voting on issues.
Preference voting sometimes tends to leave you with the least hated rather than the most liked choice (which may actually be a good outcome in many cases, in that overall dissatisfaction with the choice is reduced)
10:16 PM
One real blind spot for me, which I am realizing more and more lately, is the use of stats for explanation instead (or along with) prediction.
@Glen_b That's a really good point about voting, perhaps I did not think about it long enough before posting my question. However, I should also say that we have only very limited resources in how we can set up a voting on Meta
10:41 PM
But we may be talking slightly at cross-purposes there. You shouldn't read my bit as anything but a comment on Kodiologist's response
... I'll consider whether I answer. I don't mind you knowing so much as I worry about influencing anyone else too much.
While first past the post can have the obvious effect of spoiler candidates (e.g. if the opposite side looks like winning, getting an even more extreme candidate from your position to run as well can hand you the election), but even with STV elections you can get a spoiler-like outcome, if the first choice can influence subsequent choices (influence the order you list your later preferences), you can get something like that happen.
E.g. in a national election, if Greens start to pick up a lot of votes a conservative party may induce people to set up some other "environmental" party that has more middle-of-the-road position on other social issues, who then encourage voters to put their later preferences toward the conservative side. That party is not there to be elected, but to drain preferences of people who might otherwise vote green away from the less conservative opponents.
@MatthewDrury I reached the counterexample by reasoning about an eigenbasis (and immediately kicked myself for not seeing such a simple counterexample sooner, as one always does) but I didn't think carefully enough to see whether there would be another type of counterexample. It's an interesting Q actually.
« first day (2205 days earlier) ← previous day next day → last day (2821 days later) »