Monday, January 28, 2008
let's blogroll
over on the right side of this page now resides a list ("blogroll") of those students' blogs who've sent me their addresses so far; this list will increase as more people get on board. although you can click on the "Read More" link at the bottom to go to a page that pulls together everyone's most recent posts (an "aggregator"), it's still worth visiting particular blogs individually, both to see some of the impressive design jobs that your fellow students have done (very artistic!) as well as to read and participate in the commenting that follows on the various posts.
Thursday, January 24, 2008
*cough* who knew blogs could get so dusty? *wheeze*
well, i'm back. please, no applause. thank you.
hereby i shall resurrect my old blog from last year to serve as a model, inspiration, and touchstone for you, my class, whom i have again tasked with starting and keeping your own blogs, where you will comment on your readings, thinkings, analyses, and general development as statisticians. and probably crack a few corny jokes.
i have kept the links to last year's blogs (over on the right side of the page) for the time being so that -- browsing through them -- you can get a sense of what was attempted by last year's students. some were quite successful.
my goals for this project this time around are twofold: first -- to foster introspection, or, as the educational psychologists call it, metacognition. in short: if you have to think about what you're thinking about, you're likely to get more out of thinking about it. that's the idea, anyways. ymmv.
second -- i want to foster discussion. again, for pedagogical reasons, this has important benefits: it builds a sense of community (which is especially important in a challenging class such as this one), and it gives each of you the opportunity to share what you've figured out. you never really know a subject so well as when you've had to teach it to someone else.
at any rate, even if all that fails, it's still better than quizzes.
and you get to crack jokes. e.g.: "97.3% of all statistics are made up."
hereby i shall resurrect my old blog from last year to serve as a model, inspiration, and touchstone for you, my class, whom i have again tasked with starting and keeping your own blogs, where you will comment on your readings, thinkings, analyses, and general development as statisticians. and probably crack a few corny jokes.
i have kept the links to last year's blogs (over on the right side of the page) for the time being so that -- browsing through them -- you can get a sense of what was attempted by last year's students. some were quite successful.
my goals for this project this time around are twofold: first -- to foster introspection, or, as the educational psychologists call it, metacognition. in short: if you have to think about what you're thinking about, you're likely to get more out of thinking about it. that's the idea, anyways. ymmv.
second -- i want to foster discussion. again, for pedagogical reasons, this has important benefits: it builds a sense of community (which is especially important in a challenging class such as this one), and it gives each of you the opportunity to share what you've figured out. you never really know a subject so well as when you've had to teach it to someone else.
at any rate, even if all that fails, it's still better than quizzes.
and you get to crack jokes. e.g.: "97.3% of all statistics are made up."
Tuesday, April 17, 2007
types i, ii, and iii contingency tables
hereby some examples drawn from Sokal and Rohlf (1995: 724 et seq.), and edited and expanded a bit by me to (hopefully) clarify the distinction among Models I, II, and III contingency tables:
Type I: neither set of column totals set by investigator:
100 plants are examined, and their soil type and leaf texture is recorded:
Type II: one set of column totals set by investigator:
100 moths are exposed to bird predation: 50 light morphs and 50 dark morphs (note that the proportion doesn't have to be 50:50, though); investigator records whether moths are eaten or not:
Type III: both sets of column totals set by investigator:
one hundred beans are placed in a jar: 50 with thick skins and 50 with thin skins (again, doesn't have to be 50:50). seventy hungry weevil larvae -- each of which will burrow in to one unoccupied bean -- are added to the jar, and some time later the investigator records the numbers of each type of bean and whether or not it was attacked:
at first glance, it seems that having both the row totals and the column totals fixed will automatically fix the cell totals; this is not actually true, as the following values of a, b, c, and d will illustrate:
a = 20, b = 30, c = 50, d = 0;
a = 25, b = 25, c = 45, d = 5;
a = 35, b = 15, c = 35, d = 15;
etc.
Sokal and Rohlf indicate that they have "not yet encounted a [non-hypothetical] example of this model."
Type I: neither set of column totals set by investigator:
100 plants are examined, and their soil type and leaf texture is recorded:
| Pubescent Leaves | Smooth Leaves | Total | |
|---|---|---|---|
| Serpentine Soil | 12 | 30 | 42 |
| Non-serpentine Soil | 47 | 11 | 58 |
| Total | 59 | 41 | 100 |
Type II: one set of column totals set by investigator:
100 moths are exposed to bird predation: 50 light morphs and 50 dark morphs (note that the proportion doesn't have to be 50:50, though); investigator records whether moths are eaten or not:
| Prey | Survivor | Total | |
|---|---|---|---|
| Light Morph | 39 | 11 | 50 |
| Dark Morph | 30 | 20 | 50 |
| Total | 69 | 31 | 100 |
Type III: both sets of column totals set by investigator:
one hundred beans are placed in a jar: 50 with thick skins and 50 with thin skins (again, doesn't have to be 50:50). seventy hungry weevil larvae -- each of which will burrow in to one unoccupied bean -- are added to the jar, and some time later the investigator records the numbers of each type of bean and whether or not it was attacked:
| Attacked | Not Attacked | Total | |
|---|---|---|---|
| Thick Skin | a | b | 50 |
| Thin Skin | c | d | 50 |
| Total | 70 | 30 | 100 |
at first glance, it seems that having both the row totals and the column totals fixed will automatically fix the cell totals; this is not actually true, as the following values of a, b, c, and d will illustrate:
a = 20, b = 30, c = 50, d = 0;
a = 25, b = 25, c = 45, d = 5;
a = 35, b = 15, c = 35, d = 15;
etc.
Sokal and Rohlf indicate that they have "not yet encounted a [non-hypothetical] example of this model."
Friday, April 6, 2007
ancova
as a (relatively) uncomplicated published example of ancova, i humbly present for my biostats students' consideration the following: http://www.tulane.edu/~guill/Reprints/Guill_and_Heins_2000.pdf
perhaps most useful to them will be the formats it uses for reporting the results of the analyses (which -- looking back over it, i'm embarrassed to say, aren't perfect: one needs 2 values for the degrees of freedom for an F ratio. my bad.)
also, it may serve as a reasonably useful model for what i'll be looking for in their independent projects -- basically something approximating the 'methods' and 'results' section of this paper in length and depth, supported perhaps by a few well-crafted figures and tables, as appropriate. anything beyond that (e.g. intro or discussion) will be lagniappe.
perhaps most useful to them will be the formats it uses for reporting the results of the analyses (which -- looking back over it, i'm embarrassed to say, aren't perfect: one needs 2 values for the degrees of freedom for an F ratio. my bad.)
also, it may serve as a reasonably useful model for what i'll be looking for in their independent projects -- basically something approximating the 'methods' and 'results' section of this paper in length and depth, supported perhaps by a few well-crafted figures and tables, as appropriate. anything beyond that (e.g. intro or discussion) will be lagniappe.
anova by hand
and here i was thinking i was being all progressive and modern by not making my biostats students work through all the calculations for anova by hand, but -- lo and behold! -- busy tosser has opined that the old-skool approach might actually be helpful. she's probably right;) so, let it never be said that i'm not willing to hand out additional work when it's asked for -- here you go:
a quick google search on "anova by hand" turned up the following worksheet:statisticshell.com/anovabyhand.pdf. the 'parent' site that it comes from -- statisticshell.com -- is a hoot. i've worked through the worksheet and it's actually quite good -- he walks you through one example (response to viagra, no less!) and then gives you a second problem to work on your own, followed by the answers to that one as well. i checked his results in R and get the same answers as he did, so -- if you're so inclined -- have at it!
let me know if it helps.
a quick google search on "anova by hand" turned up the following worksheet:statisticshell.com/anovabyhand.pdf. the 'parent' site that it comes from -- statisticshell.com -- is a hoot. i've worked through the worksheet and it's actually quite good -- he walks you through one example (response to viagra, no less!) and then gives you a second problem to work on your own, followed by the answers to that one as well. i checked his results in R and get the same answers as he did, so -- if you're so inclined -- have at it!
let me know if it helps.
Thursday, March 8, 2007
testing testing
this is just a test to see what kind of HTML formatting blogger will allow you to use such that we can incorporate R code and output while preserving spacing for columns and the like (so it looks like the output on your R terminal).
for instance, compare this:
> head(iris)
Sepal.Length Sepal.Width Petal.Length Petal.Width Species
1 5.1 3.5 1.4 0.2 setosa
2 4.9 3.0 1.4 0.2 setosa
3 4.7 3.2 1.3 0.2 setosa
4 4.6 3.1 1.5 0.2 setosa
5 5.0 3.6 1.4 0.2 setosa
6 5.4 3.9 1.7 0.4 setosa
with this:
the trick is to enclose the cut-and-pasted output from R in between the HTML markup tags <PRE> ... <\PRE>
for instance, compare this:
> head(iris)
Sepal.Length Sepal.Width Petal.Length Petal.Width Species
1 5.1 3.5 1.4 0.2 setosa
2 4.9 3.0 1.4 0.2 setosa
3 4.7 3.2 1.3 0.2 setosa
4 4.6 3.1 1.5 0.2 setosa
5 5.0 3.6 1.4 0.2 setosa
6 5.4 3.9 1.7 0.4 setosa
with this:
> head(iris)
Sepal.Length Sepal.Width Petal.Length Petal.Width Species
1 5.1 3.5 1.4 0.2 setosa
2 4.9 3.0 1.4 0.2 setosa
3 4.7 3.2 1.3 0.2 setosa
4 4.6 3.1 1.5 0.2 setosa
5 5.0 3.6 1.4 0.2 setosa
6 5.4 3.9 1.7 0.4 setosa
>
the trick is to enclose the cut-and-pasted output from R in between the HTML markup tags <PRE> ... <\PRE>
Tuesday, March 6, 2007
g&e ch 6
i realized only this morning that i hadn't blogged my usual preview note for the upcoming chapter. i apologize; theryn will be acting as MC today, leading our class discussion, and i guess i shifted into "participant" mode a little too soon. at any rate, it's probably too late for anyone to benefit from reading my rambling thoughts (i doubt anyone is up reading my blog at 6 AM) but at least this will be here for later review and reflection.
this chapter is straightforward, mostly non-quantitative (only a couple of equations pertaining to what is -- imho -- a largely tangential bit about modelling...), and full of good advice on how to worry about all of the things that might go wrong with your field study. no, not really... but it does lay out and emphasizes well the general principles of replication and randomization, and how necessary they are in order to make the results of your hard work as generalizable (and interesting, and useful, and, therefore, publishable) as possible.
i think the authors may be a bit too sanguine about the about the possibility of controlling for or taking into account all of the potential confounding variables that may affect a field study. my perspective is that, given finite resources and time, there will always be the risk of an unmeasured covariate that presents itself as possibly important after-the-fact, but that a reasonably well replicated and randomized design minimizes (but doesn't eliminate) this risk.
this chapter is straightforward, mostly non-quantitative (only a couple of equations pertaining to what is -- imho -- a largely tangential bit about modelling...), and full of good advice on how to worry about all of the things that might go wrong with your field study. no, not really... but it does lay out and emphasizes well the general principles of replication and randomization, and how necessary they are in order to make the results of your hard work as generalizable (and interesting, and useful, and, therefore, publishable) as possible.
i think the authors may be a bit too sanguine about the about the possibility of controlling for or taking into account all of the potential confounding variables that may affect a field study. my perspective is that, given finite resources and time, there will always be the risk of an unmeasured covariate that presents itself as possibly important after-the-fact, but that a reasonably well replicated and randomized design minimizes (but doesn't eliminate) this risk.
Subscribe to:
Posts (Atom)