Big Data and Cloud Computing

Technology is advancing so rapidly that we will experience radical changes in society not only in our lifetimes but in the coming years. We have already begun to see ways in which computing, sensors, artificial intelligence and genomics are reshaping entire industries and our daily lives. As we undergo this rapid change, many of the old assumptions that we have relied will no longer apply. Technology is creating a new set of rules that will change our very existence. Here are six: 1. Anything that can be digitized will be. Digitization began with words and numbers. Then we moved into games and later into rich media, such as movies, images and music. We also moved complex business functions, medical tools, industrial processes and transportation systems into the digital realm. Now, we are digitizing everything about our daily lives: our actions, words and thoughts. Inexpensive DNA sequencing and machine learning are unlocking the keys to the systems of life. Cheap,...

In my experience, there are two types of companies when it comes to big data: those who don’t want anything to do with it (because they think it’s for somebody else) and those who desperately want to implement, but don’t know where to start.   Regardless of where your company falls on that spectrum, there are several attitudes I encounter regularly that can kill a big data project faster than anything else.  Identifying and neutralizing these attitudes is key to getting a project off the ground and into implementation. We are not a data company. Every company is now a data company, and you’d better wake up to that fact. Data is everywhere and a part of everything, and I cannot think of a single industry or business that couldn’t benefit from understanding more about their customers, their sales cycles, demand for their product or service or their production inefficiencies. Just because you don’t  yet  know how big data could benefit your company, doesn’t mean...

var punycode = new function Punycode() { // This object converts to and from puny-code used in IDN // // punycode.ToASCII ( domain ) // // Returns a puny coded representation of "domain". // It only converts the part of the domain name that // has non ASCII characters. I.e. it dosent matter if // you call it with a domain that already is in ASCII. // // punycode.ToUnicode (domain) // // Converts a puny-coded domain name to unicode. // It only converts the puny-coded parts of the domain name. // I.e. it dosent matter if you call it on a string // that already has been converted to unicode. // // this.utf16 = { // The utf16-class is necessary to convert from javascripts  internal character representation to unicode and back. decode:function(input){ var output = [], i=0, len=input.length,value,extra; while (i < len) { value = input.charCodeAt(i++)...

The following is a simple example of a much larger simulation that I want to run Define some processes norTheta [ mu_ , sigma_ ] := Random [ NormalDistribution [ mu , sigma ]] ; norPi [ mu_ , sigma_ ] := Random [ NormalDistribution [ mu , sigma ]] ; thetaNext [ thetaNow_ ] := thetaNow + ( - lambdaTheta * ( thetaNow - thetaBar ) * deltaT + sigmaTheta * norTheta [ 0 , 1 ] * Sqrt [ deltaT ]) ; piNext [ piNow_ , thetaNow_ ] := piNow + ( - lambdaPi * ( piNow - thetaNow ) * deltaT + sigmaPi * norPi [ 0 , 1 ] * Sqrt [ deltaT ]) ;   Then define some parameters   lambdaTheta = 0.07 ; thetaBar = 0.02 ; sigmaTheta = 0.012 ; lambdaPi = 1.0 ; sigmaPi = 0.0125 ;     Then simulate the system   steps = 252 ; T = 50 ; deltaT = 1 / steps ; // N Maturity = T * steps ; process = Transpose [ NestList [{ piNext [ # [[ 1 ]] , # [[ 2 ]]] , thetaNext [ # [[ 2 ]]]} &, { 0.02 , 0.02 } , Maturity ]] ...