The Brazilian government often misclassifies the goods it buys. That makes it hard to audit government expenditures. We cannot know whether the price paid for a ballpoint pen (code #7510) was reasonable if the pen was misclassified as a technical drawing pen (code #6675) or as any other good. This paper shows how we can use machine learning to reduce misclassification. I trained a support vector machine (SVM) classifier that takes a product description as input and returns the most likely category codes as output. I trained the classifier using 20 million goods purchased by the Brazilian government between 1999-04-01 and 2015-04-02. In 83.3% of the cases the correct category code was one of the three most likely category codes identified by the classifier. I used the trained classifier to develop a web app that might help the government reduce misclassification. I open sourced the code on GitHub; anyone can use and modify it.
As promised, here’s how to save a trained instance of scikit-learn’s TfidfVectorizer without using pickles - in other words, how to save it as human-readable, shareable data.
The general idea is in my previous post: a model is a set of coefficients so you just extract them and save them as you would save any other data (like the very data you used to train the model). That way you avoid the security and maintainability problems of using pickles. You extract the coefficients, save them as data, then later you load them and plug them back in.
Now, that’s easier to do with some models than with others. With scikit-learn’s SGDClassifier, for instance, that’s a breeze. But with TfidfVectorizer that’s a bit tricky. I had to do it anyway so I thought I should write a how-to of sorts.
Once we’ve trained the vectorizer it will contain two important attributes: idf_, a numpy array that contains the inverse document frequencies (IDFs); and vocabulary_, a dictionary that maps each unique token to its column number on the TF-IDF matrix.
To extract the IDF array you can just print it to the screen and then copy and paste it to a .py file. The file will look like this:
To extract the vocabulary you can do the same, but depending on how many tokens you have this may not be practical. An alternative is to use JSON. Like this:
The vocabulary is now saved in the vocabulary.json file.
That’s it, we’ve disassembled our vectorizer. So far so good.
Now, it’s when we try to put everything back together that things get tricky.
We start by importing the TfidfVectorizer class. But we can’t instantiate the class right away. Here’s the problem: we are not allowed to assign arbitrary values to the idf_ attribute. If you instantiate the class and then try something like vectorizer.idf_ = idfs you get an AttributeError exception.
fromidfsimportidfs# numpy array with our pre-computed idfs
fromsklearn.feature_extraction.textimportTfidfVectorizervectorizer=TfidfVectorizer(lowercase=False,min_df=2,norm='l2',smooth_idf=True)vectorizer.idf_=idfsAttributeError:can't set attribute
The problem is that the idf_ attribute is kind of “read-only”. I say “kind of” because that’s not exactly true: if you train the vectorizer then idf_ will change (it’ll have the IDFs). But idf_ behaves as read-only if you try to plug the IDFs directly, without training the vectorizer.
That happens because idf_ is defined with a @property decorator and has no corresponding setter method - check TfidfVectorizer’s source code.
I can’t imagine why the scikit-learn folks made that choice. That’s a bunch of smart people with a lot of programming experience, so I imagine they had good reasons. But that choice is getting in the way of proper model persistence, so here’s how we get around it:
So, what’s happening here? We are creating a new class - MyVectorizer -, which inherits all attributes (and everything else) that TfidfVectorizer has. And we are plugging our IDFs into the MyVectorizer class. When we instantiate MyVectorizer our pre-computed IDFs are already there, in the idf_ attribute. Problem solved.
But we’re not done yet. If you try to use the vectorizer now you’ll get an error:
So, we’re being told that our vectorizer hasn’t been trained, even though we’ve plugged our pre-computed IDFs. What’s going on?
When we try to use our vectorizer there is a function check_is_fitted that checks, well, whether we have fitted the vectorizer. You’d think it checks the idf_ attribute but it doen’t. Instead it checks the attribute of an attribute: ._tfidf._idf_diag, which is a sparse matrix made from the IDFs. So we need to plug that matrix into the vectorizer.
We can extract ._tfidf._idf_diag from the trained vectorizer, save it as data, then load and plug it - just like we did with the other attributes. But an easier alternative is to simply compute ._tfidf._idf_diag from our IDFs, using scipy.
So, I trained this SVM classifier and I wanted to use it in a web app I built. I used Python for everything, so it seemed straightforward at first: just use the pickle module to save the classifier to disk, then have the app load the pickle. But things got complicated. In the end I found a better way to achieve model persistence, so I thought I should share the experience.
The fundamental problem is that the classifier turned out huge. Not surprising: it was trained with 20 million documents and intended to pick one of 560 possible document categories. The resulting coefficient matrix has dimensions 560 (categories) by 505,938 (unique tokens). That’s a matrix with 283,325,280 cells. When pickled to a file it takes up 8GB of disk space.
I didn’t mind that at first. I thought “fine, so the app will take a few seconds to be ready after I deploy it, no problem”. But the app can’t load an 8GB pickle if there is only, say, 1GB of RAM. I did some tests and realized that I would need a server with at least 16GB of RAM to (barely!) host the app. I looked up server prices on Amazon Web Services and on Google Compute Engine. It would cost me some US$ 200 a month to keep the app alive. Not happening. (Have I mentioned that I live in Brazil and that our currency was massive devalued this year?)
So I gave up on hosting the app. I decided to open source the code instead and let users download and host the app themselves. But that turned my 8GB pickle into a problem. It’s ok to consume your own pickles (well, not really) but it’s not ok to expect other people to consume your pickles. Pickles can have malicious code. And pickles are not guaranteed to work across different versions of the same Python packages.
Now, a model is basically a bunch of coefficients - so why not store it as data? We shouldn’t have to store a model in a pickle or in any format that is not human readable. We can store a model as we store the very data that we used to estimate the model. And that’s what I propose we do.
I used scikit-learn’s stochastic gradient descent class to train my SVM classifier, which I instantiated with the following paramters:
Once the model is trained the coefficients are stored in the clf.coef_ attribute as a numpy array of dimensions 560 (classes) by 505,938 (unique tokens).
As you can see, extracting the coefficients is trivial: just get clf.coef_. But how do we store them as data? I toyed with a couple of ideas and in the end I chose HDF5. If you haven’t used it before, an HDF5 file is a “container” inside which you can store arrays. I had used HDF5 before and it’s great for fast retrieval of large amounts of data. To use it from Python you must have pytables installed. You don’t need to call pytables though - pandas has a nice interface to it. Here’s how I did it:
importpandasaspdstore=pd.HDFStore('coefficients.h5')counter=0forrowinclf.coef_:# annoyingly I couldn't store each row of the
# numpy array directly, I had to convert each
# row into a pandas DataFrame, as you see here,
# or else I got an error message
store['row'+str(counter)]=pd.DataFrame(row)counter+=1store.close()
That’s it - we have extracted our coefficients and stored them in an HDF5 file. Here I had 560 categories and 505,938 unique tokens, so my HDF5 file contains 560 pandas DataFrames, each of length 505,938.
We are not done though. Each of the 560 classes has not only 505,938 coefficients but also one intercept. These are stored in the clf.intercept_ attribute. You can store them with HDF5 as well but with only 560 intercepts I didn’t bother doing that. I just printed clf.intercept_ to the screen and then copied and pasted it into a .py file. Dirty, I know, but quick and easy. The file looks like this:
Finally we need to extract our class labels. They are in clf.classes_. Same as with the intercepts: I just printed the array to the screen and then copied and pasted it into a .py file.
Now we have our model nicely stored as data. People can inspect the HDF5 and .py files without (much) risk of executing arbitrary code. Our model is human readable and shareable. Now my app is indeed open source.
Ok, so much for disassembling the model. How do we put it back together?
Quick and easy. Instantiate the model, load the class labels, the coefficients and the intercepts, and plug everything in:
importnumpyasnpimportpandasaspdfromsklearnimportlinear_model# load class labels
fromclass_labelsimportclass_labels# or however you named the file and array
# load intercepts
frominterceptsimportintercepts# or however you named the file and array
# instantiate model
clf=linear_model.SGDClassifier(loss='modified_huber',penalty='l2',alpha=0.0001,fit_intercept=True,n_iter=60,shuffle=True,random_state=None,n_jobs=4,learning_rate='optimal',eta0=0.0,power_t=0.5,class_weight=None,warm_start=False)# load coefficients
store=pd.HDFStore('coefficients.h5')# convert from pandas DataFrame back to numpy array
coefs=np.array([np.array(store['row'+str(i)]).T[0]foriinrange(len(class_labels)]))# close HDF5 file
store.close()# plug class labels
clf.classes_=class_labels# plug intercepts
clf.intercept_=intercepts# plug coefficients
clf.coef_=coefs
And voilà, we have reconstructed our model. The labels, intercepts and coefficients are in their proper places (i.e., assigned to the proper clf attributes) and the model is ready to use. And everything runs a lot faster than if we were loading pickles.
Some models are more easily “datafied” than others. “Datafying” an instance of scikit-learn’s TfidfVectorizer’s class, for instance, is a bit tricky. I’ll cover that in another post.
Today it’s been a year since I started working as a data scientist. Before that I was doing my Ph.D., in political science. I wonder what other people who’ve made this sort of transition - from some social science to data science - have learned. Here’s what I’ve found out (so far). Maybe this will encourage others to share their own experiences.
Causality doesn’t matter
Political scientists want to know what causes what. Does democracy increase GDP per capita? Does oil make a country more authoritarian? Can trade prevent war? And so on. But causality is hard to establish. You need to run controlled experiments or convince the reviewers that you chose the right instruments or that you matched on the right confounders. And Gary King is always around the corner waiting to stab you in the heart.
So I was overwhelmed with joy when I found out that causality is not a big deal in the world of data science. Take text classification, for instance. You’re mapping word counts to categories. Yes, in a way, the categories do cause the word counts - “let me be clear” appears a lot in Obama’s speeches because they are Obama’s. But we just don’t care about the effect of Obama on the frequency of “let me be clear”. We only care about classifying the text correctly.
That’s liberating. Think of the time and effort that political scientists spend defending their causal claims. Or debunking others’ causal claims. Or trying to accurately measure causal effects. When you remove causality from the equation you suddenly have a lot more time to work on other, potentially more interesting aspects of data analysis.
Debates have clear winners
Most political scientists have no notion of test set or validation set. They take a bunch of data and use 100% of it as a training set. They run their regressions and interpret the equations that map dependent variables to independent variables. And that’s it. Pages and pages of articles and books and blog posts dedicated to training sets.
Which is of course ok - political scientists are trying to understand how the world works - but is also frustrating: debates never end. When you limit yourself to the training data you just don’t have a clear metric of success. It’s largely about how convincingly you can defend your theoretical and methodological choices. That leaves ample room for subjectivity, so it’s never entirely clear who are the winners and losers.
In the world of data science, however, the training data is just the beginning. Once you’ve trained your model you use it on data it hasn’t seen before and you observe how well it performs. And there are clear metrics for that: accuracy, recall, F-measure, etc. You can compare different models and immediately spot the winners and losers. You can argue all you want that your model is inherently “sounder” because of XYZ but that doesn’t matter. What matters is whether your model misclassifies dogs as cats less often than other models do.
There is less ideological bias
Hopefully I don’t need to convince you that social scientists are overwhemingly on the left of the ideology spectrum. To give you but one number, the Democratic:Republican ratio is 5.6:1 among political scientists. The ideological distribution is so skewed that there are survival guides for non-leftists who want to thrive in academia.
Reviewers being humans, sometimes they dislike your instruments or matching or sample because they dislike your paper’s conclusions. If you are in political science you probably lean left, so you’re unlikely to have seen this happen to one of your papers. But try to argue that Latin America’s left turn in the 2000s has eroded democracy in the region. Boy, brace yourself for some angry reviews. It’s not that the methodological criticisms will be unfounded. It’s just that they would likely not exist if your conclusions were reversed.
In data science, on the other hand, you have Kaggle competitions. Winners and losers are not decided on the basis of subjective evaluations of your methods or sample or theory. Winners and losers are decided on the basis of who gets the higher F-measure. It’s a fair fight. So, it’s not just that debates don’t linger forever (see above), but also that they resolved in a much more rigorous way. Sometimes debates do end in political science - but not always as they should.
You want more error, not less
Political scientists want a good model fit. But as I mentioned before all they have is a training set. They have no notion of prediction or out-of-sample testing, so they end up overfitting. The fit is too good - the model doesn’t generalize.
It’s not that political scientists don’t know about overfitting. They do. But if all your data are training data then how the heck can you assess overfitting?
Political scientists believe that you can avoid overfitting by avoiding kitchen-sink regression. If I include only theoretically relevant regressors then everything should be ok, right?
Except we can always twist theory to accomodate whatever variables we need in order to get what we want. Maybe if I square this variable then I’ll get the proper p-values. And then I come up with some creative explanation of why its effect is not linear. Reviewers (ideally) assess theory consistency, of course, but then we’re back to the subjectivity and bias problems I discussed before.
This was perhaps my biggest methodological shock when I started doing data science. At first I struggled with the idea of a regularization term. What? So you want me to bias my coefficients toward zero? Then Andrew Ng’s machine learning course taught me that there is data you use to train your model and data you use to test it. And then regularization made sense. A bit more error is good.
Programming matters
Political scientists’ code is rigid: each script is meant to produce a pre-determined set of estimates, using a pre-determined dataset. The code always takes the same input and always return the same output. It does one thing and one thing alone. It doesn’t matter much if the code could be faster or prettier: as long as it replicates what you did in your paper you have fulfilled your duty.
Data scientists’ code is flexible: your code needs to accept a variety of inputs and return a variety of outputs. That’s because you’re not writing code for yourself, but for others. For instance: you have data in MySQL and other people in your organization want insights from those data. You then write a web app where people can, say, fit a regression line through some subset of the data. You don’t know what subsets people will choose. And you don’t know what the regression lines will look like. So your code needs to handle many different scenarios. What if the user chooses a non-valid subset? Say, years 2012-2014 when the data end in 2010? What if the user chooses all the data and that overloads the server? What if the regression tool you’re using under the hood (say, R’s lm() function) returns an error because the chosen subset is too small? In short: data scientists’ code has a lot more IF/THEN/ELSE statements than political scientists’ code.
So, programming matters in data science. It’s about both depth and breadth: you need a firmer grasp of basic programming concepts, like conditionals and functions (that’s the depth) and you need to learn web development, SQL, NoSQL, database administration, messaging, server maintenance, security, testing (that’s the breadth).
Some of my political scientist friends would rather poke their own eyes out than endure that sort of technical work. Some even consider technical work to be beneath them. I suppose I understand. You survived Social Origins of Dictatorship and Democracy’s 592-page discussion of regime change, class, and modernization - surely you’re destined to higher purposes. You are here to understand the world, not center HTML tables.
But if you don’t mind getting your hands dirty then programming can be a lot of fun - and at least as intelectually rewarding than political science. With programming there is no “arguing your way out” of anything: either your code works or it doesn’t. And when it doesn’t you have to figure out why and that requires a lot of sinapses. As in political science, it’s largely about hypothesis testing - if the code isn’t working because of XYZ then if I try ABC I should get this result, otherwise I should get that other result. Except that there is a finish line: you’ll never really know what makes democracy work but you’ll eventually figure out which regex matches the string you’re looking for. And you will get to the finish line or die trying - you can’t just declare regex to be a meaningless social construct and move on. You can’t get away with vague wording or selective omissions. The machine is not a journal editor - you can’t bullshit your way through it.
You lose freedom
Wait, don’t quit grad school just yet - there’s a lot to miss about academia. First and foremost, I miss the freedom to work on whatever I wanted to.
Don’t get the wrong idea: I thoroughly enjoy what I’m doing right now (I help automate cartel detection; you know, when companies that should compete against each other decide to shake hands instead). I’m learning a lot and it’s by far the most rewarding job I’ve ever had. But I can’t just wake up tomorrow and decide to work on face recognition for the next six months. I can do whatever I want to do in my spare time, but I still need to show up Mon-Fri and work on cartel detection. Sure, I could find another job. But in academia you don’t need to find another job just because you’ve got a new research interest. You stay in the same job, you just start doing something else. And that is awesome. I’m ok with foregoing that freedom, but I imagine not everyone is.
This is it. If you too are in data science as a refugee from the social sciences I would love to hear from you. How did you get here? How is the new life playing out for you? Do you intend to go back some day?
We all know that academic writing stinks, but exactly how bad is it? And in what disciplines does academic writing stink the most? To answer these questions I scraped 174,527 academic articles, came up with a few indicators of “academese” and compared these indicators across disciplines.
our data source
I scraped those articles from SciELO. In case you’ve never heard of SciELO, it’s like JSTOR, but focused on Latin American journals. I would rather have scraped JSTOR, but it’s gated. I could scrape it using my OSU credentials, but the Aaron Swartz brouhaha is not an encouraging precedent. Also, JSTOR articles are usually in PDF, which sucks for text mining (especially when the PDF is the scan of a document, which is often the case in JSTOR). SciELO, by contrast, is ungated (it doesn’t even have a “terms of use” page, so I can’t possibly be breaking any rules) and its articles are in HTML, which is much easier to parse than PDF.
Most articles on SciELO are in Portuguese or Spanish but that’s not a problem here. The flaws of academic writing - cluttered sentences, meaningless words, plenty of jargon - are not language-specific. And thanks to the Normands the mumbo jumbo barely changes from one language to another: in English you problematize the discursive paradigm and in Portuguese você problematiza o paradigma discursivo.
summary statistics
The 174,527 articles I scraped are all the articles in Portuguese from all the 281 active journals on SciELO. Here’s how they are distributed:
We’ll look into specific disciplines in a minute.
(SciELO doesn’t categorize its journals, so the categorizations above are my own, partly based on Latindex’s. In case you are curious, here are the journal ISSN codes and respective areas.)
academese and how to measure it
…the secret of good writing is to strip every sentence to its cleanest components. Every word that serves no function, every long word that could be a short word, every adverb that carries the same meaning that’s already in the verb, every passive construction that leaves the reader unsure of who is doing what - these are the thousand and one adulterants that weaken the strength of a sentence. And they usually occur in proportion to education and rank. (William Zinsser, On Writing Well.)
As we see, academese is not a particular type of bad writing. The same set of flaws that we’ve been calling academese could very well be called journalese or bureaucratese. The specific jargon may change (academics critique, bureaucrats impact) but the underlying sins are the same: clutter and vagueness.
Now that we know what bad writing is we can measure it. Here are my indicators:
Word length.
Sentence length.
Adverbs/total number of words. To identify adverbs I use the 1,000 most frequent adverbs in the Portuguese Corpus.
Gerunds/total number of words. I count as a gerund any word that ends in ‘ndo’, which is how gerunds end in Portuguese - as in fazendo (doing), escrevendo (writing), etc.
Inane words/total number of words. I don’t have an exhaustive list of inane words. Instead I selected any words that match one of the following regular expressions:
'^problematiz.*': problematizar (to problematize), problematização (problematization), etc.
'^paradigma.*': paradigma (paradigme), paradigmático (paradigmatic), etc.
'^discursiv.*': discursivo (discursive), discursividade (discursivity), etc.
'^dial\u00E9tic.*': dialética, dialético (both mean dialectic), etc.
'^critic.*' and '^cr\u00EDtic.*': criticar (to criticize), crítico (critical, critic), criticado (criticized), etc. You may have qualms about this but think: are people supposed to do anything a-critically in academia? If not then critical is inane unless we’re talking about a specific disagreement (as in “Hayek criticized Keynes’ monetary theory”). Elsewhere - “critical theory”, “a critical look at”, etc - critical is pointless.
I picked these words because they are not specific to any disciplines. Sociologists and physicists alike can talk about paradigmes, problematize phenomena, or take a critical look at theories and experiments. Sociologists and physicists may differ in how often they use such inane words (that’s what I want to measure) but they both have the same opportunities to use them.
I considered enriching my list of inane words with words from Sokal’s hoax and from the Bad Writing Contest. But that might stack the deck against the humanities. Physicists probably don’t have many chances to write entelechy, otherness, or essentiality.
I’d rather use a machine learning approach but I couldn’t find a corpora of academic articles pre-labeled as academese/not academese (let alone one such corpora that happens to be in Portuguese). Hence what’s left is this sort of “dictionary” approach, which is much weaker - I’m certainly missing A LOT of relevant features (and possibly using some irrelevant ones). But it’ll have to do for now.
so, who stinks the most?
Here’s the ratio inane words / total number of words:
Adverbs / total number of words:
Gerunds / total number of words:
Average sentence length:
Average word length:
Clearly it’s in the humanities and social sciences that academese really thrives. Not exactly a shocking finding, but it’s nice to finally have some numbers. I didn’t expect the difference in inane words usage to be so large. Conversely, I expected word length to vary a lot more (maybe scientific names are inflating word size in the hard sciences?).
zooming in
Let’s zoom in on some of the humanities and social sciences. Here’s our articles:
Now let’s see how these different disciplines compare. Here’s the ratio inane words / total number of words:
Adverbs / total number of words:
Gerunds / total number of words:
Average sentence length:
Average word length:
Well, these are some disappointing data. I expected big differences - especially between pairs like economics and anthropology, or business and history. Turns out I was wrong. Sadly, there isn’t a clear “worst offender” for us to shame. Philosophy wins (well, loses) when it comes to poor word choices, but not by much, and philosophers don’t use longer sentences or words than the other social scientists.
what’s next
This analysis is not language-specific - what makes bad writing bad is the same set of flaws in English and in Portuguese. But perhaps this analysis is culture-specific? For instance, what passes for economics in Brazil is much different than what we find on the American Economic Review - there is a lot more “problematization of paradigms” in the tropics, so to speak. So I wonder how things would change if I used American articles instead. I’m not going to scrape any gated databases, lest I get in legal trouble. But maybe Google Scholar searches might contain enough ungated results? Or maybe there is some (large enough) ungated database that I don’t know of?
the gory details
Here’s the code I used to scrape SciELO, in case it may be useful to you. (Please, be considerate. SciELO is super nice to us scrapers: it’s ungated, there are no captchas, everything is in plain HTML, and - crucially - they don’t prohibit scraping. So don’t overparallelize or otherwise disrupt their servers.)
importosimportreimportrequestsfrombs4importBeautifulSoup# get URL of each journal (active journals only)
startURL='http://www.scielo.br/scielo.php?script=sci_subject&lng=pt&nrm=iso'session=requests.Session()startHTML=session.get(startURL).textsoup=BeautifulSoup(startHTML)regex=re.compile(soup.find_all('p')[4].text)# regex to filter out non-active journals
sections=soup.find_all(text=regex)journalURLs=[]foriinrange(len(sections)):newSection=sections[i].next_element.find_all('a')newJournalURLs=[URL.get('href')forURLinnewSection]journalURLs+=newJournalURLsbasepath='/Users/thiagomarzagao/Desktop/articles/'# change as needed
# go to each journal
fori,journalURLinenumerate(journalURLs):print'journal num:',i+1,'de',len(journalURLs)k=1IDstart=journalURL.index('pid=')IDend=journalURL.index('&lng')journalID=journalURL[IDstart+4:IDend]print'journal id:',journalIDjournalPath=basepath+journalID+'/'ifos.path.exists(journalPath):continueelse:os.makedirs(journalPath)journalStartHTML=session.get(journalURL.replace('serial','issues')).textjournalSoup=BeautifulSoup(journalStartHTML)# go to each issue
issuesURLs=[URL.get('href')forURLinjournalSoup.find_all('a')[10:-3]][:-2]forn,issueURLinenumerate(issuesURLs):print'issue num:',n+1,'de',len(issuesURLs)ifissueURL:if'pid='inissueURL:issueStartHTML=session.get(issueURL).textissueSoup=BeautifulSoup(issueStartHTML)articlesURLs=[URL.get('href')forURLinissueSoup.find_all('a',text=u'texto em Portugu\u00EAs')]iflen(articlesURLs)>0:# go to each article and scrape it
forarticleURLinarticlesURLs:articleHTML=session.get(articleURL).textarticleSoup=BeautifulSoup(articleHTML)articleTextList=[p.textforpinarticleSoup.find_all('p')]articleText=''forpieceinarticleTextList:articleText+=piece# save article to disk
withopen(journalPath+str(k)+'.txt',mode='wb')asfbuffer:fbuffer.write(articleText.encode('utf8'))k+=1
The code above will yield a little garbage: a few articles not in Portuguese and some texts that are not articles (copyright notices mostly). Not enough garbage to be worth fixing though.
To parse the sentences I used the following regular expression, which I stole from here.
To make the pie charts I used d3pie, which is amazing tool: you make the charts interactively and d3pie generates the code for you. (That sort of defeats the purpose of these posts, which is to help me practice D3, but it was just so quick and easy that I couldn’t resist.) To make the bar charts I just used plain D3. Here’s the code for the first bar chart (the code is almost the same for the others):
<!DOCTYPE html><metacharset="utf-8"><style>.axispath,.axisline{fill:none;stroke:black;}.axistext{font-family:sans-serif;font-size:16px;}#tooltip{position:absolute;width:auto;height:auto;padding:10px;background-color:white;-webkit-box-shadow:4px4px10pxrgba(0,0,0,0.4);-moz-box-shadow:4px4px10pxrgba(0,0,0,0.4);box-shadow:4px4px10pxrgba(0,0,0,0.4);pointer-events:none;}#tooltip.hidden{display:none;}#tooltipp{margin:0;font-family:sans-serif;font-size:16px;line-height:20px;}</style><body><divid="tooltip"class="hidden"><p><spanid="value">100</span></p></div><script src="d3/d3.min.js"></script><script>varmargins={top:12,left:150,right:24,bottom:24},legendPanel={width:0},width=500-margins.left-margins.right-legendPanel.width+150,height=136-margins.top-margins.bottom,dataset=[{data:[{month:'humanities & social',count:0.00080},{month:'biological & earth',count:0.00012},{month:'exact',count:0.00017}],name:''}],series=dataset.map(function(d){returnd.name;}),dataset=dataset.map(function(d){returnd.data.map(function(o,i){// Structure it so that your numeric// axis (the stacked amount) is yreturn{y:o.count,x:o.month};});}),stack=d3.layout.stack();stack(dataset);vardataset=dataset.map(function(group){returngroup.map(function(d){// Invert the x and y values, and y0 becomes x0return{x:d.y,y:d.x,x0:d.y0};});}),svg=d3.select('body').append('svg').attr('width',width+margins.left+margins.right+legendPanel.width).attr('height',height+margins.top+margins.bottom).append('g').attr('transform','translate('+margins.left+','+margins.top+')'),xMax=d3.max(dataset,function(group){returnd3.max(group,function(d){returnd.x+d.x0;});}),xScale=d3.scale.linear().domain([0,xMax]).range([0,width]),months=dataset[0].map(function(d){returnd.y;}),yScale=d3.scale.ordinal().domain(months).rangeRoundBands([0,100],.1),xAxis=d3.svg.axis().ticks(5).scale(xScale).orient('bottom'),yAxis=d3.svg.axis().scale(yScale).orient('left'),colours=d3.scale.category10(),groups=svg.selectAll('g').data(dataset).enter().append('g').style('fill',function(d,i){returncolours(i);}),rects=groups.selectAll('rect').data(function(d){returnd;}).enter().append('rect').attr('x',function(d){returnxScale(d.x0);}).attr('y',function(d,i){returnyScale(d.y);}).attr('height',function(d){returnyScale.rangeBand();}).attr('width',function(d){returnxScale(d.x);}).on('mouseover',function(d){varxPos=parseFloat(d3.select(this).attr('x'))/2+width/2;varyPos=parseFloat(d3.select(this).attr('y'))+yScale.rangeBand()/2;d3.select('#tooltip').style('left',xPos+'px').style('top',yPos+'px').select('#value').text(d.x);d3.select('#tooltip').classed('hidden',false);}).on('mouseout',function(){d3.select('#tooltip').classed('hidden',true);})svg.append('g').attr('class','axis').attr('transform','translate(0,'+height+')').call(xAxis);svg.append('g').attr('class','axis').call(yAxis);series.forEach(function(s,i){svg.append('text').attr('fill','white').attr('x',width+margins.left+8).attr('y',i*24+24).text(s);svg.append('rect').attr('fill',colours(i)).attr('width',60).attr('height',20).attr('x',width+margins.left+90).attr('y',i*24+6);});</script></body>