How a Data Scientist Built a Web-Based Data Application
I’m an algorithms guy, and what I want more than anything else is to be able to effectively communicate the models I’ve built and get them into the hands of other people to see what they can find. Read on to learn more.
Join the DZone community and get the full member experience.Join For Free
but like i said, i’m an algorithms guy. those machine learning models i’ve tuned are in python and r. and, i don’t want to spend all my time trying to glue them together with web code that i don't understand very well and am not terribly interested in.
here is an interactive data application that was the keystone of a post about building topic models on the presidential state of the union addresses . try it out. you can choose the number of topics, as well as document frequency filters for the maximum and minimum number of documents a word can appear. more topics is like zooming in on the body of text. fewer is like zooming out. a maximum document frequency of 0.75 means that if a word appears in more than 75% of the speeches it is not used since it is “too common”. in the same way, a minimum document frequency of 0.05 means that if a word appears in less than 5% of the speeches, it is “too rare” to contribute to an overall trend. (note: the lda model takes a few seconds to run.)
here is a behind the curtain look at the exaptive elements that make up this xap:
the xap is grouped into those same 3 functional areas: user input (html), algorithm (python), and visualization(d3.js)... plus a fourth to show a progress bar when the app is processing a model and control, a universal color scheme across plots. each section is made up of several components. each component takes inputs on the left and outputs to the right. which outputs are connected to which inputs is governed by a drag and drop wire. inside each component, the best technology to accomplish that task is encapsulated. the platform takes care of communications between components.
clicking on the component in the algorithmic layer shows the python code used to build the latent dirichlet allocation topic model .
this is the part i did not write. in fact, this is far better and more scalable d3 than i can write. all i have to do now is connect the output data of my topic model component to the inputs of the visualization components. not only that, but the output of one visualization can be used as an input into another one to make the plots dynamic and interactive.
i’m an algorithms guy (please stop me if i start repeating myself), and what i want more than anything else is to be able to effectively communicate the models i’ve built and get them into the hands of other people to see what they can find. but somewhere out there is someone who is a great visualization person that would love to have good algorithmic components to wire into their visuals. they built these visualization components i am using. they make my work better, and i hope my algorithms can do the same for them . if i can effectively connect and collaborate with those interested in visualization, design, user experience, subject matter expertise, and even other types of algorithms, then we can amplify the quality of each other’s work.
Published at DZone with permission of Frank Evans, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.