TravisPe

The green line represents the number of tweets that were marked as being anxious and the blue lines represents tweets marked as calm.

You can see that after the tsunami hit there was a general spike in the overall traffic, but a much larger spike for tweets where the user described being anxious.

We also analyzed the tweets for emotions flagging each to either be "happy" or "sad". Don't have the data able to be displayed in any consumable format at the moment though.

These are some logs for the day (totals)

                   Calm   Anxious Happy   Sad
  2011-03-08       2034   8730    77032   94119
  2011-03-09       1349   5129    47708   59406
  2011-03-10       1614   6020    51623   72214
  2011-03-11       4126   20427   87763   126688
  2011-03-12       3251   13009   104434  136389

A friend and I started playing around with twitter data back in early 2010. We currently have something close to over 587 million tweets collected (We stopped collecting earlier this year). We only pulled English tweets and those that described what someone was feeling (Im, I am, I feel, I am feeling, etc. along with the negatives I don't feel, I do not feel, etc).

We were able to see some interesting events happen during the time though. This is a graph of the anxiety levels of twitter on March 11th, the bottom axis is the hour of the day EST. The earthquake hit Japan @ 1:46 EST.

http://i.imgur.com/BeBwa.jpg

There is a strange dip around noon that we are unsure of how to account for as our servers did not report any failures.

It was a fun project to play around with.

I've recently been jumping around in my naming conventions. I'm a student and haven't quite settled in one one particular convention. For the current project I'm working on (C++) I've been using function overloading. So for example, I have a class called BankAccount. I have a private and a public method that will set the balance or return the balance (set is private, get is public) of the account, I've overloaded this so that if no parameter is passed it returns the balance, and if a parameter is passed it will set the balance accordingly. I use this in my deposit and withdrawal methods. I do the same thing for other setters/getters. I picked up this convention from seeing it used in other languages like Ruby and Javascript.

Is this a bad practice? It seems logical to me, but I'm wonder what other peoples thoughts are and if it may be confusing to someone else.