For the Fall 2020 semester, you will complete three analyses.
||Wednesday, November 11|
||Wednesday, November 18|
||Wednesday, December 2|
|Analysis Revisit||None needed!||Wednesday, December 9|
The files and documentation needed to get started with each analysis are provided in two formats:
.zipfile that is a mirror of the GitHub repo. Use the link in the Files column above.
Use whichever is easier for you. Whichever you choose, start by reading the
README.md file. Both methods are setup such that you only need to edit the
analysis.Rmd file contained within. To complete your analysis, simply knit this file, re-zip the folder provided, and submit!
In place of Analysis 04, you will revisit one of the three previous analyses. You pick! Now that you’re familiar with the analyses, and have had time to work on your own, revisit an analysis with fresh eyes and more video examples from the instructor.
.zipfile as your did for the original analysis.
analysis_original.htmlthat contain your original work.
You can pick whatever you’d like to focus on in the revision. You don’t not need to completely redo an analysis, it would actually be best to keep your revision focused. It could be as simple as comparing an additional modeling technique, or just cleaning up your R Markdown document and your writing.
|Heart Disease||1.1 - YouTube||1.1 - MediaSpace||Goal, Data, Response, Features|
|Heart Disease||1.2 - YouTube||1.2 - MediaSpace||Data Splitting, Missing Data, EDA|
|Heart Disease||1.3 - YouTube||1.3 - MediaSpace||Baseline Performance, Binary Classification|
|Heart Disease||1.4 - YouTube||1.4 - MediaSpace||ML Pipelines|
Our hope is that the process of completing these analyses will help you see how to put what we have learned this semester into practice. Specifically, after completing these analyses and receiving feedback, we hope that students are able to:
Beyond that, we hope you use these analyses as an opportunity for exploration. Hopefully the foundation we have created throughout the semester will give you the confidence to try some things we only briefly discussed, or did not discuss at all!
For these analyses, you will do the following:
Please review the this IMRAD Cheat Sheet developed by the Carnegie Mellon University Global Communication Center.
Even though it is the first thing to appear in the report, the abstract should be the last thing that you write. Generally the abstract should serve as a summary of the entire report. Reading only the abstract, the reader should have a good idea about what to expect from the rest of the document. Abstracts can be extremely variable in length, but a good heuristic is to use a sentence for each of the main sections of the IMARD:
The introduction should discuss the “why” of your analysis and a brief “what” of your data. Essentially, you need to motivate why the analysis that you are about to do should be done. Why does this analysis need to be done? What is the goal of this analysis? The introduction should also provide enough background on the subject area for a reader to understand your analysis. Do not assume your reader knows anything about the subject area that your data comes from. If the reader does not understand your data, there is no way the reader will understand your motivation. Since data is provided for you, but not a scenario, you can create any reasonable scenario that you would like.
You do not need to provide a complete data dictionary in the introduction, but you should include one in the appendix. Often the data would be introduced in the Methods section, but here the data is very closely linked to the motivation of the analysis. It at least needs to be introduced in the the introduction.
Consider including some exploratory data analysis here, and providing some of it to the reader in the report if you feel it helps present and introduce the data.
The methods section should discuss what you did. The methods that you are using are those learned in class. This section should contain the bulk of your “work.” This section will contain most of the
R code that is used to generate the results. Your
R code is not expected to be perfect idiomatic
R, but it is expected to be understood by a reader without too much effort. The majority of your code should be suppressed from the final report, but consider displaying code that helps illustrate the analysis you performed, for example, training of models.
Consider adding subsections in this section. One potential set of subsections could be data and models. The data section would describe your data in detail. What are the rows? What are the columns? Which columns will be used as the response and the features? What is the source of the data? How will it be used in performing your analysis? What if any preprocessing have you done to it? The models section would describe the modeling methods that you will consider, as well as strategies for comparison and evaluation.
Your goal is not to use as many methods as possible. Your task is to use appropriate methods to accomplish the stated goal of the analysis.
The results section should contain numerical or graphical summaries of your results. What are the results of applying the methods you described? Consider reporting a “final” or “best” model you have chosen. There is not necessarily one, singular correct model, but certainly some methods and models are better than others in certain situations. The results sections is about reporting your results. In addition to tables or graphics, state the result in plain English.
The discussion section should contain discussion of your results. That is, the discussion section is used for commenting on your results. This should also frame your results in the context of the data. What do your results mean? Why would someone care about these results? Results are often just numbers, here you need to explain what they tell you about the analysis you are performing. The results section tells the reader what the results are. The discussion section tells the reader why those results matter. The discussion section is the most important section. It takes numbers on a page and gives them meaning.
The appendix section should contain any additional code, tables, and graphics that are not explicitly referenced in the narrative of the report. The appendix should contain a data dictionary.
.zip file to Compass that contains:
.Rmdfile that is your IMRAD.
.htmlfile that is the result of knitting your
You may simply use the files and template provided. If so, you only need to modify the given
analysis.Rmd file, knit, and zip the folder before submitting.
.zip file to the correct assignment on Compass2g. You are granted an unlimited number of submissions. Your last submission before each of the deadlines will be graded, provided you do not make a late submission. Because we will be releasing solutions, we cannot offer a super flexible late submission policy like with quizzes. You may submit up to 24 hours late with a 3 point reduction. If you make a submission after the initial deadline, this penalty will be applied. No exceptions! When in doubt, it is generally not worth re-submitting after the deadline to fix a small mistake.
For Fall 2020 all grading will be based on completion. Submit a reasonable looking report and you will receive full credit. Feel free to simply follow along with the videos posted above and submit those results as your analysis. We’re more concerned with your engagement than being critical of your work via grading. That said, you should be critical of your own work, as that is how you will learn and become more proficient at analysis.
Beyond here was the “original” plan which no longer applies.
The analyses will be graded out of 20 points. Each of the following criteria will be worth two points. A score of 0, 1, and 2 is possible within each criteria:
0: Criteria is largely ignored or incorrect.
1: Criteria is only partially satisfied.
2: Criteria is met.
The following criteria will be evaluated:
[eye-test]Final rendered document passes the “eye test.”
.Rmdfile. Only make code visible in the final report if it is a short, concise, easy to understand way to communicate what you have done.
[code-style]R code and R Markdown follow suggested STAT 432 style guidelines.
[imrad-style]Document is well written and follows the IMRAD template.
[data-exp]Data is well explained.
[pred-just]There is a clear (context driven) justification for making predictions about the response variable.
[feat-style]There is a clear (context driven) justification for using the features considered.
[train-test]Train and test data are used for appropriate tasks.
[causation]No causal claims are made.
[result-scrutiny]Any “chosen” model is scrutinized beyond a single numeric metric.
[issues]Potential shortcomings of the analysis are made clear to the reader.
The instructor and graders reserve the right to apply additional deductions for submissions that are extremely poor, containing so little content that it cannot be evaluated based on the above criteria. Our hope is that this grading structure allows students to feel confident in their grade, while being able to perform the analysis however they choose.
For Analysis 01, you will be given feedback according the the above criteria, but for Analysis 01 only, grading will actually be based on completion. That is, if you submit anything before the deadline, you will receive full credit. But please, do not abuse this policy! Our hope is that you will still attempt the analysis in order to obtain feedback that you can carry forward to future analyses so that you feel confident in the grading procedure.
How long should the report be?
What if I don’t get a good results?
Do I need to use method X or Y or Z?