Baselight

Titanic

For Binary logistic regression

@kaggle.azeembootwala_titanic

Loading...
Loading...

About this Dataset

Titanic

Context

This Data was originally taken from Titanic: Machine Learning from Disaster .But its better refined and cleaned & some features have been self engineered typically for logistic regression . If you use this data for other models and benefit from it , I would be happy to receive your comments and improvements.

Content

There are two files namely:-
train_data.csv :- Typically a data set of 792x16 . The survived column is your target variable (The output you want to predict).The parch & sibsb columns from the original data set has been replaced with a single column called Family size.

All Categorical data like Embarked , pclass have been re-encoded using the one hot encoding method .

Additionally, 4 more columns have been added , re-engineered from the Name column to Title_1 to Title_4 signifying males & females depending on whether they were married or not .(Mr , Mrs ,Master,Miss). An additional analysis to see if Married or in other words people with social responsibilities had more survival instincts/or not & is the trend similar for both genders.

All missing values have been filled with a median of the column values . All real valued data columns have been normalized.

test_data.csv :- A data of 100x16 , for testing your model , The arrangement of test_data exactly matches the train_data

I am open to feedbacks & suggesstions

Tables

Test Data

@kaggle.azeembootwala_titanic.test_data
  • 13.77 KB
  • 100 rows
  • 17 columns
Loading...

CREATE TABLE test_data (
  "unnamed_0" BIGINT,
  "passengerid" BIGINT,
  "survived" BIGINT,
  "sex" BIGINT,
  "age" DOUBLE,
  "fare" DOUBLE,
  "pclass_1" BIGINT,
  "pclass_2" BIGINT,
  "pclass_3" BIGINT,
  "family_size" DOUBLE,
  "title_1" BIGINT,
  "title_2" BIGINT,
  "title_3" BIGINT,
  "title_4" BIGINT,
  "emb_1" BIGINT,
  "emb_2" BIGINT,
  "emb_3" BIGINT
);

Train Data

@kaggle.azeembootwala_titanic.train_data
  • 25.2 KB
  • 792 rows
  • 17 columns
Loading...

CREATE TABLE train_data (
  "unnamed_0" BIGINT,
  "passengerid" BIGINT,
  "survived" BIGINT,
  "sex" BIGINT,
  "age" DOUBLE,
  "fare" DOUBLE,
  "pclass_1" BIGINT,
  "pclass_2" BIGINT,
  "pclass_3" BIGINT,
  "family_size" DOUBLE,
  "title_1" BIGINT,
  "title_2" BIGINT,
  "title_3" BIGINT,
  "title_4" BIGINT,
  "emb_1" BIGINT,
  "emb_2" BIGINT,
  "emb_3" BIGINT
);

Share link

Anyone who has the link will be able to view this.