<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Twit on sixman.guru</title><link>http://sixman.guru/tags/twit/</link><description>Recent content in Twit on sixman.guru</description><generator>Hugo -- 0.155.3</generator><language>en-us</language><lastBuildDate>Thu, 09 Jan 2014 14:57:00 +0000</lastBuildDate><atom:link href="http://sixman.guru/tags/twit/index.xml" rel="self" type="application/rss+xml"/><item><title>Creating a simple command line streaming twitter search engine using node.js</title><link>http://sixman.guru/posts/creating-a-simple-command-line-streaming-twitter-search-engine-using-node-js/</link><pubDate>Thu, 09 Jan 2014 14:57:00 +0000</pubDate><guid>http://sixman.guru/posts/creating-a-simple-command-line-streaming-twitter-search-engine-using-node-js/</guid><description>&lt;p&gt;&lt;span style="line-height: 1.5;"&gt;About two weeks ago I published an article on &lt;a href="http://www.sixmanguru.com/texas-football-fan-sentiment-analysis-during-valero-alamo-bowl/"&gt;Texas fan sentiment analysis&lt;/a&gt;, based on over 50,000 tweets I collected the day of the Valero Alamo Bowl.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;This was fairly straightforward, as I utilized the &lt;a href="https://github.com/tgsmith61591/Twitter-and-UT-Football/commit/5f4a13ed6d54f9fb81d37f501bae07cf7f73f0b5"&gt;code my colleague Taylor Smith created&lt;/a&gt; and modified it for my purposes. My biggest changes came with how I analyzed the data.&lt;/p&gt;
&lt;p&gt;The problem I had was that the process of obtaining the tweets tied up my R console. This was problematic because I could neither use R, nor start looking at the data. Another problem was I had to determine up front how long I wanted to run the search. I could kill the process, but if the game ran past the time I had set, I would have to rush and restart it again.&lt;/p&gt;</description></item></channel></rss>