_Editor’s note: I wrote a book called Elements of Data Analytic Style. Buy it on Leanpub or Amazon! If you buy it on Leanpub, you get all updates (there are likely to be some) for free and you can pay what you want (including zero) but the author would be appreciative if you’d throw a little scratch his way. _
So uh, I was going to soft launch my new book The Elements of Data Analytic Style yesterday. I figured I’d just quietly email my Coursera courses to let them know I created a new reference. It turns out that that wasn’t very quiet. First this happened:
— Andrew Janke (@AndrewJanke) March 2, 2015
and sure enough the website was down:
then overnight it did something like 6,000+ units:
So lesson learned, there is no soft open with Coursera. Here is the post I was going to write though:
### Post I was gonna write
I have been doing data analysis for something like 10 years now (gulp!) and teaching data analysis in person for 6+ years. One of the things we do in my data analysis class at Hopkins is to perform a complete data analysis (from raw data to written report) every couple of weeks. Then I grade each assignment for everything from data cleaning to the written report and reproducibility. I’ve noticed over the course of teaching this class (and classes online) that there are many common elements of data analytic style that I don’t often see in textbooks, or when I do, I see them spread across multiple books.
I’ve posted on some of these issues in some open source guides I’ve posted to Github like:
- 10 things statistics taught us about big data analysis
- The Leek Group Guide to R packages
- How to share data with a statistician
But I decided that it might be useful to have a more complete guide to the “art” part of data analysis. One goal is to summarize in a succinct way the most common difficulties encountered by practicing data analysts. It may be a useful guide for peer reviewers who could refer to section numbers when evaluating manuscripts, for instructors who have to grade data analyses, as a supplementary text for a data analysis class, or just as a useful reference. It is modeled loosely in format and aim on the Elements of Style by William Strunk. Just as with the EoS, both the checklist and my book cover a small fraction of the field of data analysis, but my experience is that once these elements are mastered, data analysts benefit most from hands on experience in their own discipline of application, and that many principles may be non-transferable beyond the basics. But just as with writing, new analysts would do better to follow the rules until they know them well enough to violate them.
The book includes a basic checklist that may be useful as a guide for beginning data analysts or as a rubric for evaluating data analyses. I’m reproducing it here so you can comment/hate/enjoy on it.
The data analysis checklist
This checklist provides a condensed look at the information in this book. It can be used as a guide during the process of a data analysis, as a rubric for grading data analysis projects, or as a way to evaluate the quality of a reported data analysis.
I Answering the question
Did you specify the type of data analytic question (e.g. exploration, assocation causality) before touching the data?
Did you define the metric for success before beginning?
Did you understand the context for the question and the scientific or business application?
Did you record the experimental design?
Did you consider whether the question could be answered with the available data?
II Checking the data
Did you plot univariate and multivariate summaries of the data?
Did you check for outliers?
Did you identify the missing data code?
III Tidying the data
Is each variable one column?
Is each observation one row?
Do different data types appear in each table?
Did you record the recipe for moving from raw to tidy data?
Did you create a code book?
Did you record all parameters, units, and functions applied to the data?
IV Exploratory analysis
Did you identify missing values?
Did you make univariate plots (histograms, density plots, boxplots)?
Did you consider correlations between variables (scatterplots)?
Did you check the units of all data points to make sure they are in the right range?
Did you try to identify any errors or miscoding of variables?
Did you consider plotting on a log scale?
Would a scatterplot be more informative?
Did you identify what large population you are trying to describe?
Did you clearly identify the quantities of interest in your model?
Did you consider potential confounders?
Did you identify and model potential sources of correlation such as measurements over time or space?
Did you calculate a measure of uncertainty for each estimate on the scientific scale?
Did you identify in advance your error measure?
Did you immediately split your data into training and validation?
Did you use cross validation, resampling, or bootstrapping only on the training data?
Did you create features using only the training data?
Did you estimate parameters only on the training data?
Did you fix all features, parameters, and models before applying to the validation data?
Did you apply only one final model to the validation data and report the error rate?
Did you identify whether your study was randomized?
Did you identify potential reasons that causality may not be appropriate such as confounders, missing data, non-ignorable dropout, or unblinded experiments?
If not, did you avoid using language that would imply cause and effect?
VIII Written analyses
Did you describe the question of interest?
Did you describe the data set, experimental design, and question you are answering?
Did you specify the type of data analytic question you are answering?
Did you specify in clear notation the exact model you are fitting?
Did you explain on the scale of interest what each estimate and measure of uncertainty means?
Did you report a measure of uncertainty for each estimate on the scientific scale?
Does each figure communicate an important piece of information or address a question of interest?
Do all your figures include plain language axis labels?
Is the font size large enough to read?
Does every figure have a detailed caption that explains all axes, legends, and trends in the figure?
Did you lead with a brief, understandable to everyone statement of your problem?
Did you explain the data, measurement technology, and experimental design before you explained your model?
Did you explain the features you will use to model data before you explain the model?
Did you make sure all legends and axes were legible from the back of the room?
Did you avoid doing calculations manually?
Did you create a script that reproduces all your analyses?
Did you save the raw and processed versions of your data?
Did you record all versions of the software you used to process the data?
Did you try to have someone else run your analysis code to confirm they got the same answers?
XI R packages
Did you make your package name “Googleable”
Did you write unit tests for your functions?
Did you write help files for all functions?
Did you write a vignette?
Did you try to reduce dependencies to actively maintained packages?
Have you eliminated all errors and warnings from R CMD CHECK?
comments powered by Disqus