mako: statistics (169)

Sort by: Date / Title / URL

  1. "Project Bamboo is currently piloting a directory of tools, services, and collections that can facilitate digital research. This evolution of Lisa Spiro's DiRT wiki includes new ways of browsing and commenting on the entries. Please send us feedback on how to improve the site!"
  2. Includes a pretty interesting discussion of dealing with overdispersion in mixed-effects models (e.g., count models) by using individual-level fixed effects. It also includes a whole series of citations.
  3. Incredible answer to this question that really makes it clear. If I teach stats, I'm going to use whuber's example.
  4. *Sigh*. Another opt-in survey. This one from the Ada Initiative.
  5. Take Blackduck's results with a giant fist full of salt, but do look at these trends.
  6. Great writeup by Gelman.
  7. It turns out, Google has data on enough search terms that something is always quite highly correlated with your curve! This is a crackpot conspiracy theorists dream!
  8. Correlation.
  9. A bunch of R code to fit your power law distributions.
  10. updated: 2012-04-04, original: 2011-10-16 to , , , , , , - Archived Link
  11. Another cool looking tool from The King.
  12. I've heard great things about this podcast, but haven't yet got a chance to listen to it.
  13. Andrew Gelman comments on every research dataset I have. Without knowing it.
  14. Interesting story. The truth here seems to be something between "court throws out bayes law" and "judge realizes that garbage in means garbage out."
  15. I could easily loose a big chunk of my life to this site.
  16. Presentation on how to use MapR.
  17. I'm a huge fan of data.table and I've used it a ton in my own work in the last year.
  18. There should be a better way of finding your R package than searching though a page of short descriptions of all 2800 package.s But there isn't.
  19. Answer: When considering which class to use, always choose the least complex class that will support the application. That is, use Date if possible, otherwise use chron and otherwise use the POSIX classes.
  20. OK. That's pretty cool.
  21. It's exactly what it sounds like. Good? Slightly horrifying?
  22. Awesome (and very short) section of debugging: 1. Be liberal with the use of print (or cat()) statements in your functions when debugging them! 2. traceback() # can see the sequence of function calls 3. options(error = dump.frames) debugger() # permits you to see the values of objects in the various nested environments of the function calls
  23. A new R module that lets you keep your data on disk.

First / Previous / Next / Last / Page 2 of 5