Ooh, that looks cool. You could possibly use composite strategies https://hypothesis.readthedocs.org/en/master/data.html#composite-strategies for testing dataframes.
From: Joe A. Wagner
Sent: Thursday, February 25, 2016 11:03 AM
To: Abraham D. Flaxman
Subject: property based testing
Have you seen hypothesis? It looks really useful. I’ve been meaning to incorporate it into my code, but I’m having a hard time defining properties of data frames (which is usually the input of most of my functions).
This long-read from vox.com would be 13 pages if I printed it, but it is for a general audience, so it’s not like a 13 page research paper.
Linked from the link is this amazing video:
I’ve been gifted a steady stream of math clocks over the years, including a really transcendental one that has been in my dining room for quite a while. I didn’t realize how often I used it to check the time until my four-year-old broke the hands off one recent day. (“I wanted to see what happens when you bend them back and forth,” he explained, but I digress.)
The purpose of this blog is to document the *fix* for this failure that we developed together:
“What time is it?”, I inattentively asked myself as a kid came down the stairs this morning. Perfect answer!
This crossed my inbox recently:
The e-book is available now from https://www.manning.com/books/practical-probabilistic-programming. The print version will be available on Friday.
>From the cover:
Practical Probabilistic Programming introduces the working programmer to probabilistic programming. In it, you’ll learn how to use the PP paradigm to model application domains and then express those probabilistic models in code. Although PP can seem abstract, in this book you’ll immediately work on practical examples, like using the Figaro language to build a spam filter and applying Bayesian and Markov networks, to diagnose computer system data problems and recover digital images.
Short article from the kick-off of a new IHME journal club, with a focus on diversity and health disparities: [link]
Topics that bubbled up in discussion: composition of search committees, pipeline issues and other barriers to attracting diverse candidates, the scale of the problem with systemic racism.
Second edition of the Diversity Lunch Discussion journal club, with a focus on the Implicit Association Test. Many participants also *took* an IAT—Rose suggests you try taking the Race IAT before our discussion tomorrow: https://implicit.harvard.edu/implicit/takeatest.html
So much knowledge and expertise in this group.
Pairs well with pseudocode exercise, despite irrelevance: https://docs.google.com/document/d/1Qouj-ZxcPVmYehvIvLGnNV0X_4E_9YNyjXEeCOmmBaI/edit
Is there some GH relevant *thing* that they can build, instead of messing around with legos? Maybe I can get some tech device that requires assembly, like those solar water filtration things.
Pseudocode Guide: https://docs.google.com/document/d/14x2S42cQ4J20uKRc_2LxrM-u39LE6j3M5FVCdQx5Jg8/edit
Suggests 3 examples are are not particularly relevant to health science. Alternative example: prescriptions, with examples (and a formal language, as well) from POP-PL work http://users.eecs.northwestern.edu/~sfq833/resources/papers/GPCE_POP-PL_2015.pdf
I had to put an icon on a chart in Python last week, and I couldn’t find a good brief blog about how to do it. Here is what I cobbled together:
1. Find a free, appropriate image from The Noun Project.
2. Load it into Python with
3. Draw it in the proper place on a figure with
plt.imshow and some cryptic, hacky options.
Looks good, right?
See this all in action here: https://gist.github.com/aflaxman/c171050384471636e8f23f322ba7e9c5