Skip to main content

Too much information as bad as no information

I haven't read Kartik's book but it looks like something I'd enjoy. In this interview with Verge, he cited the following experiment: One problem with grading in college courses is that different TAs are more or less lenient. So they used an algorithm to normalize or modify the grade so that the level of leniency was consistent. Then, one group received minimal information about how the algorithm worked, a second group got some high-level data, and the third got all of the information on how the algorithm worked and the raw data and all the changes made. The result was that the level of trust in the third group was back down to the same level as the group that didn’t receive any information. So it goes to show that if you reveal that much information, it’s as if you reveal nothing. This discussion is about transparency when it comes to algorithms. His recommendation is to provide "just enough" information but not "too much". The test group that received details  about the algorithm trusted it less than the group that received high-level information, and about the same as the group that was kept in the dark. Kartik cites this experiment in the context of explaining to end-users how algorithms work. The above commentary is equally valid when explaining algorithms to decision-makers, such as senior managers at an organization. Most people experienced at this quickly realize the futility of explaining minute details of an algorithm. Decision-makers are satisified if they gain an intuitive understanding of how the machine functions, and if they observe that the outputs "make sense." *** One important issue that isn't addressed in the interview is gaming. More transparency is more fodder for those who want to game the system. I discuss this in the chapter about credit scoring in Numbers Rule Your World (link): we can now correct our credit history data, but this will clearly introduce a bias because people will remove incorrect, negative data but not incorrect, positive data.   [PS. After I wrote this, the current controversy around Boeing 737 MAX provides a counter-point. The current theory about what caused the crashes (at least the Lion Air one) is that an automation software misdiagnosed the problem. Apparently, Boeing decided not to inundate pilots with too much information and did not disclose the software prior to the Lion Air crash.]  

from Big Data, Plainly Spoken (aka Numbers Rule Your World) https://ift.tt/2Hx5S0X
via IFTTT

Comments

Popular posts from this blog

Controlling legend appearance in ggplot2 with override.aes

[This article was first published on Very statisticious on Very statisticious , and kindly contributed to R-bloggers ]. (You can report issue about the content on this page here ) Want to share your content on R-bloggers? click here if you have a blog, or here if you don't. In ggplot2 , aesthetics and their scale_*() functions change both the plot appearance and the plot legend appearance simultaneously. The override.aes argument in guide_legend() allows the user to change only the legend appearance without affecting the rest of the plot. This is useful for making the legend more readable or for creating certain types of combined legends. In this post I’ll first introduce override.aes with a basic example and then go through three additional plotting scenarios to how other instances where override.aes comes in handy. Table of Contents R packages Introducing override.aes Adding a guides() layer Using the guide argument in scale_*() Changing multiple aesthetic par...

Zooming in on maps with sf and ggplot2

(This article was first published on r-bloggers – WZB Data Science Blog , and kindly contributed to R-bloggers) When working with geo-spatial data in R, I usually use the sf package for manipulating spatial data as Simple Features objects and ggplot2 with geom_sf for visualizing these data. One thing that comes up regularly is “zooming in” on a certain region of interest, i.e. displaying a certain map detail. There are several ways to do so. Three common options are: selecting only certain areas of interest from the spatial dataset (e.g. only certain countries / continent(s) / etc.) cropping the geometries in the spatial dataset using sf_crop() restricting the display window via coord_sf() I will show the advantages and disadvantages of these options and especially focus on how to zoom in on a certain point of interest at a specific “zoom level”. We will see how to calculate the coordinates of the display window or “bounding box” around this zoom point. Loading t...