I have found that there are many discussions on the Internet and social media about data analytics tools, programming languages and predictive modeling algorithms. However, as data analytics practitioners, we spend most of 70% or more our time on data issues like identifying data sources, data gathering, data cleanse, etc., before we even start performing analytics. I have started a forum, http://70pct.com dedicated to these topics, particularly data sources. We can sharing our knowledge and experience about data there.
Saturday, June 11, 2016
I have found an excellent website to learn Oracle PL/SQL Oracle SQL live. From the website, we can run SQL or PL/SQL commands. There are also many scripts in Code Library that we can learn from. Here are screenshots.
Wednesday, May 11, 2016
- ZSales: 70% increase in response rate
- ZClaim: 40% reduction in insurance claim losses
- ZCheck: 70% reduction in charge off
- ZCredit: 50% reduction in delinquency rate
Sunday, March 06, 2016
In the post a Young Data Scientist- Kaggle Competition Top 5% Winner: Yuyu Zhou, Yuyu talks about the important role of feature engineering, i.e, finding good derived variables, and gradient boosting trees in their success. He also tells me a very interesting observations on Kaggle Competition ranking.
"After participating teams finished building their predictive models, they apply their models to two data sets to generate predictions: a smaller set containing target variable and a larger data set where the target variable is removed. Each participating team's model is temporarily ranked based on the result on the smaller data set with the target variable. After the competition's deadline is due, Kaggle will calculate the final ranking of each team based on a model's prediction on the larger data set. "
"It is interesting to see that the rankings of some top 1% models based on the smaller data set drop more than 20% on the larger data set. I figure out what might cause the huge discrepancies in their model performance. Those teams' models fit the smaller data set so well that they lose their capability to generalize. It is a typical overfitting problem."It is important to avoid model overfitting. After all, a predictive model is only useful if it can generalize, i.e., able to handle new data reasonably well.
Saturday, March 05, 2016
Yuyu Zhou is a graduate student in Analytics in University of New Hampshire. His team has achieved the top 3% and 5% in two Kaggle prediction competitions respectively. In an interview, I asked him how their predictive models performed so well. Yuyu said,
"One of the keys to the success is that we spend tremendous amount of time working on building feature variables. Those variables are usually the results of combining several raw variables. For example, the ratio between the body weight and height is a better variable in predicting a patient's health than using body weight or height alone."
"My training in computer science is extremely helpful in these projects. I am able to write Java, Python and SQL scripts to perform tasks such as data cleansing, data merge, and data transform, etc. As we know, more than 80% of time in a project is typically spent on those tasks before we start building predictive models."
"We have tried many type of predictive models and found that gradient boosting trees have consistently perform the best."
The following is a summary of Yuyu's contribution in those two projects.
Kaggle Competition: Rossmann Store Sales Prediction (ranked top 5%) Oct 2015 – Dec 2015
- Built the Predictive Model for daily sales for Rossmann Stores using Python Machine Learning library.
- Conducted data cleaning and feature engineering for increasing data quality.
- Designed final prediction model by combining the multiple gradient boosting trees algorithms
- Prediction accuracy was ranked at 163 out of 3303 teams
Kaggle Competition: Property Risk Level Prediction (ranked top 3%) July 2015 – Aug 2015
- Developed Statistics models to predict risk level of properties which Liberty Mutual Inc is going to protect.
- Led the team and conducted cost and benefit analysis on new ideas.
- Implemented ideas using statistical packages from Python.
- Prediction accuracy was ranked at 71 out of 2236 teams.
Friday, March 04, 2016
We may run the following query from SYS to find the tablespace names for all tables, including IOTs (index organized table) and partitioned tables (replacing 'DMUSER' with your user name).
select u.name owner, o.name table_name,t.name tablspace_name from obj$ o, ts$ t, sys_objects s, user$ u where o.obj#=s.object_id and s.ts_number=t.ts# and o.owner#=u.user# and o.type#=2 and u.name='DMUSER' order by 1,2; OWNER TABLE_NAME TABLSPACE_NAME -------------------------------- -------------------------------- DMUSER AI_EXPLAIN_OUTPUT TBS_1 DMUSER AR_SH_SAMPLE_SETTINGS TBS_1 DMUSER DM$P0AR_SH_SAMPLE TBS_1 DMUSER DM$P0AR_SH_SAMPLE_2COL TBS_1 DMUSER DM$P0EM_SH_CLUS_SAMPLE TBS_1 DMUSER DM$P0NB_SH_CLAS_SAMPLE TBS_1 DMUSER DM$P0OC_SH_CLUS_SAMPLE TBS_1 DMUSER DM$P1EM_SH_CLUS_SAMPLE TBS_1 DMUSER DM$P1NB_SH_CLAS_SAMPLE TBS_1 DMUSER DM$P1OC_SH_CLUS_SAMPLE TBS_1