Posted in Uncategorized

Nice Video on getting Started with Apache Spark

Posted in Bioinformatics, Data Science, Neurology, R Language

Installing and Using R lanuage in Ubuntu

The World of Tomorrow
We are surrounded by data and tools that collects it. Every time you perform a web search on bing or use Google map to find a location; you are generating data. Those able to analyze data and extract knowledge that enables informed decision-making will be at a advantage. It is reminiscent of when software usage and basic computer skills went from a “convenience” to an “mandatory.”

Before we start changing the world with Data analysis/Data Science; first things first, lets get a basic tool for analyzing data up and running. Let’s pretend Microsoft Excel never came your mind. R language is the tool I will focus on in this blog. It is both a programming language and platform for data science.

Install on non-Linux Platforms
This blog will focus only on Linux and the command line installation (I am a Microsoft guy fighting hard to get away from GUI-addiction.) If you like an alternative means, check out this URL, select a country in it and follow the instructions:

For example, for United States, an image from Berkeley, select:

Installation on Ubuntu

  1. Open a command line
  2. Run command to update Linux (optional but recommended):
    sudo apt-get update
  3. Run command to install R Language:
    sudo apt-get install r-base

Running R Language
In command line, run this (its case sensitive):

Hello, World test
Here is a Hello, world test:

  1. To save a variable with a value, type:
    x <- "Hello, world"
  2. To print out the saved variable’s value, type:

To Close R Language Command Prompt
In command line, run this command (ts case sensitive):

Installing R Studio
The command line version is suitable for basic R language operations. However, for more real-world analysis, it would be better to use an IDE like R Studio

To begin installing R Studio, go to:

Search for the word “Ubuntu” on the page above and make sure you select the appropriate version that matches the bit (32 or 64) of your machine. Clicking on this will download a file for installation. Double click on the downloaded file and the Ubuntu Software Center will come up (if not, bring it up.) Follow the instructions.

You should be ready to use it, if you followed the steps in the blog loyally. Have fun.

Posted in Uncategorized

ChicagoVeg’s restaurant application updated (January 23rd 2015)

ChicagoVeg is a non-profit organization in Chicago, whose goal is to promote veganism, vegetarians and raw veganism in Chicagoland. The organization has updated its restaurant application ( The primary goal of the update was to improve users’ mobile experience. Some changes made were:

– Fixed issue with map getting out of bounds on mobile and tablet
– Added warning message for users using IE 8 and lower (Google only supports IE 9 and above so the restaurant app is forced to too)
– Corrected issue in mobile where direction overflowed
– Added ability for users to post information about the site on social media
– Enlarged filtering options (e.g. Name | Distance in Restaurant list) to improve visibility and click-ability in mobile
– Fixed issue with mobile where address boxes was getting misaligned

Posted in Uncategorized

Reminder on how to Perform Basic Git operations on Github-code (using command lines)

This blog is a summary of a way of setting up an environment to use git and checking in code. It assumes you have used a form of source control. If you are a total newbie to programming, try this first –
This blog uses an application called restaurant listing application ( for demonstration purposes. Change references to this to suit your needs.


  1. Download git:
  2. Create a repository in github. Go to your github page and click on the Repository-button.

Steps Up Environment

        1. Create a directory on your local drive, where you want the code.
        2. Go to PowerShell or Command Prompt or some other command line application that supports git; and go to the directory from Step #1
        3. In the prompt, type in (to set up directory to be a local git repo):
          git init
        4. Get the code (you will find the URL in the github page, under “HTTPS clone URL”, on the right-hand-side):
          git remote add origin
        5. Create a master branch
          git checkout -t -b master origin/master
        6. Track changes
          git branch --set-upstream-to=origin/master


        • If you get an issue where a path name is too long, run this command:
          git config --system core.longpaths true
        • If you get an error where there is no tracking information (means you skipped this step above), run this:
          git branch --set-upstream master origin/master

Checking in Code

      1. Get the code onto your local repo. Reminder, git is about each user having their local repo (for your own changes) and everyone sharing a group-repo (cumulative code one or more people shared)
        git pull
      2. Tracking untracked files (Adding new files to your local repo)
        To untracked files (files not already in github) to the commit package, use this:
        git add .
        Note: This add all untracked files. If you want to add specific files, adjust ths. See this for more more information:
      3. Here is a way of committing changes to your local repo:
        git commit -am "This is some comment Fixed #4"Note: (1)This will NOT check in the code to the main repository for others to use. It commits it to your local, which you can later check in for others to use. The push command does the check in and that will be discusses later. (2)This is unnecessary if you have no newly added files. (3)In “-am”, the ‘a’ stands adds all changes while the ‘m’ is for commenting. This is not appropriate if you do not want to add all recent changes to your local repository. Use a different option for commit as suites your needs. (4)The “#4” in the commit associated the check-in to an issue number. It can be left out the comment if you are not associating the commit to an issue. Although I advise to always associate check-ins to something.
      4. To submit code from your local repo to the shared repo, use this command:
        git push
        Note: This pulls from your local repository and pushed it to github.

A tutorial with less verbose than this can be found here:

Posted in JavaScript

Reminder on how to get up and going with bower.js

This is a reminder of how to get up and running with Bower.js. It is intended for people have used it before but just need a quick refresher.

Installing Bower
Step 1: Download node.js (you may likely have it installed already)

Step 2: Install it (globally preferred, locally if you must)
npm install bower -g

Step 3: Create bower.json file using bower itself:
bower init

Step 4 (Optional): Change where bower is stored from bower_component to anything you want. For example, to use js/lib:

1st: creat file called: “.bowerrc”
2nd: The file above should have content like:

"directory": "js/lib"

The only thing you change is “js/lib” if that is not where you want to store your packages

Maintaining packages
Updating a package and update the bower config file(e.g. lodash)
bower install lodash --save

Uninstall a package
bower uninstall lodash

To get specific version
bower install lodash#2.2.1

check for available versions
bower info lodash

update all packages
bower update

Posted in Uncategorized

Here is a quick reminder on how to use LESS, one of the many CSS precompliers:

Variables: As they are in porgramming languages

@greenColor: #00FF00;
@font-family: Georgia

.makeItGreen {

background-color: @greenColor;
font-family: @font-family;

Mixin: For style sheet/rules reuse

@greenColor: #00FF00;
@font-family: Georgia

.makeItGreen {
background-color: @greenColor;
font-family: @font-family;
.greatGreenStyle {
.makeItGreen; // here is the reuse

Reusing rules from a different file

@import “element.less”


Note: This has to be in the same location as the less file in question


nav {
width: 200px;
height: 100px;
li {                                                      /* nested */
width: 100px;
background-color: green;
a {                                              /* second nested-level: nav li a */
color: lime;

Nesting with pseudo class

a {
font-family: Georgia;
&.hover {
color: green;

Note: & refers to the current rule

@height: 200px

div {
height: @height * 2;

Note: Similar principle applies to other arithmetic operations