Not logged in
Talk
Contributions
Create account
Log in
Navigation
Main page
About
People
Publications
Teaching
Resources
Research Blog
Wiki Functions
Recent changes
Help
Licensing
Page
Discussion
Edit
View history
Editing
Statistics and Statistical Programming (Winter 2017)
(section)
From CommunityData
Jump to:
navigation
,
search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Weekly Problem Sets and Participation === Each week I will post a problem set with a list of questions. Some of these will be drawn from the textbooks and some will be ones I design or write. The questions will cover: * '''Statistics questions''' β These will be questions about statistics from the OpenIntro sections as well as any empirical papers that are listed as required for that that day. * '''Programming challenges''' β These will be R programming problems that cover material from the Verzani text that was listed as required from the previous session. I won't be grading these assignment and I won't be asking you to turn in anything for the ''statistics questions'' portion of the weekly assignment. That said, we will spend a good chunk of class each day going through the answers to the questions due on that day. Because randomness is an extremely important concept in statistics, I will use a small R program to '''randomly cold call''' on students in the class to walk through your "answer" to each question and explain your reasoning to the class. We'll then have an opportunity to discuss the different approaches as a group. I don't promise to ask all of these questions in class (especially if it's clear that folks get the point). Although I might ask them, I won't cold call for questions that are not on the list. For the programming challenges, I will ask that everybody shares code for any solutions to programming problems before class so we can walk through in class. If you get completely stuck on a problem and cannot "solve" it, that's OK, but share the code that you do have so that you can walk us through what you did and what you were thinking. Although the problem sets are not going to be graded, it is critical that you be at class and that you be able to discuss your answers to each of the questions. Your ability to do these latter two things will be reflected in your participation grade for the course which makes a full 40% of your grade. I can't emphasize enough how important it will be to be in class. I'm not going to form groups for you but it's totally fine with me if you want to work on these problem sets in small groups. The "Participation Rubric" section of [https://mako.cc/teaching/assessment.html my page on assessment] gives the details on how I evaluate participation in my classes. If you sense a conflict between material in this section and material on that page, you can safely assume that the syllabus takes precedence.
Summary:
Please note that all contributions to CommunityData are considered to be released under the Attribution-Share Alike 3.0 Unported (see
CommunityData:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:
Cancel
Editing help
(opens in new window)
Tools
What links here
Related changes
Special pages
Page information