Injury Prediction For Competitive Runners
With Machine Learning Identify Injuries for Runners
@kaggle.shashwatwork_injury_prediction_for_competitive_runners
With Machine Learning Identify Injuries for Runners
@kaggle.shashwatwork_injury_prediction_for_competitive_runners
CREATE TABLE day_approach_maskedid_timeseries (
"nr_sessions" DOUBLE,
"total_km" DOUBLE,
"km_z3_4" DOUBLE,
"km_z5_t1_t2" DOUBLE,
"km_sprinting" DOUBLE,
"strength_training" DOUBLE,
"hours_alternative" DOUBLE,
"perceived_exertion" DOUBLE,
"perceived_trainingsuccess" DOUBLE,
"perceived_recovery" DOUBLE,
"nr_sessions_1" DOUBLE,
"total_km_1" DOUBLE,
"km_z3_4_1" DOUBLE,
"km_z5_t1_t2_1" DOUBLE,
"km_sprinting_1" DOUBLE,
"strength_training_1" DOUBLE,
"hours_alternative_1" DOUBLE,
"perceived_exertion_1" DOUBLE,
"perceived_trainingsuccess_1" DOUBLE,
"perceived_recovery_1" DOUBLE,
"nr_sessions_2" DOUBLE,
"total_km_2" DOUBLE,
"km_z3_4_2" DOUBLE,
"km_z5_t1_t2_2" DOUBLE,
"km_sprinting_2" DOUBLE,
"strength_training_2" DOUBLE,
"hours_alternative_2" DOUBLE,
"perceived_exertion_2" DOUBLE,
"perceived_trainingsuccess_2" DOUBLE,
"perceived_recovery_2" DOUBLE,
"nr_sessions_3" DOUBLE,
"total_km_3" DOUBLE,
"km_z3_4_3" DOUBLE,
"km_z5_t1_t2_3" DOUBLE,
"km_sprinting_3" DOUBLE,
"strength_training_3" DOUBLE,
"hours_alternative_3" DOUBLE,
"perceived_exertion_3" DOUBLE,
"perceived_trainingsuccess_3" DOUBLE,
"perceived_recovery_3" DOUBLE,
"nr_sessions_4" DOUBLE,
"total_km_4" DOUBLE,
"km_z3_4_4" DOUBLE,
"km_z5_t1_t2_4" DOUBLE,
"km_sprinting_4" DOUBLE,
"strength_training_4" DOUBLE,
"hours_alternative_4" DOUBLE,
"perceived_exertion_4" DOUBLE,
"perceived_trainingsuccess_4" DOUBLE,
"perceived_recovery_4" DOUBLE,
"nr_sessions_5" DOUBLE,
"total_km_5" DOUBLE,
"km_z3_4_5" DOUBLE,
"km_z5_t1_t2_5" DOUBLE,
"km_sprinting_5" DOUBLE,
"strength_training_5" DOUBLE,
"hours_alternative_5" DOUBLE,
"perceived_exertion_5" DOUBLE,
"perceived_trainingsuccess_5" DOUBLE,
"perceived_recovery_5" DOUBLE,
"nr_sessions_6" DOUBLE,
"total_km_6" DOUBLE,
"km_z3_4_6" DOUBLE,
"km_z5_t1_t2_6" DOUBLE,
"km_sprinting_6" DOUBLE,
"strength_training_6" DOUBLE,
"hours_alternative_6" DOUBLE,
"perceived_exertion_6" DOUBLE,
"perceived_trainingsuccess_6" DOUBLE,
"perceived_recovery_6" DOUBLE,
"athlete_id" BIGINT,
"injury" BIGINT,
"date" BIGINT
);
CREATE TABLE week_approach_maskedid_timeseries (
"nr_sessions" DOUBLE,
"nr_rest_days" DOUBLE,
"total_kms" DOUBLE,
"max_km_one_day" DOUBLE,
"total_km_z3_z4_z5_t1_t2" DOUBLE,
"nr_tough_sessions_effort_in_z5_t1_or_t2" DOUBLE,
"nr_days_with_interval_session" DOUBLE,
"total_km_z3_4" DOUBLE,
"max_km_z3_4_one_day" DOUBLE,
"total_km_z5_t1_t2" DOUBLE,
"max_km_z5_t1_t2_one_day" DOUBLE,
"total_hours_alternative_training" DOUBLE,
"nr_strength_trainings" DOUBLE,
"avg_exertion" DOUBLE,
"min_exertion" DOUBLE,
"max_exertion" DOUBLE,
"avg_training_success" DOUBLE,
"min_training_success" DOUBLE,
"max_training_success" DOUBLE,
"avg_recovery" DOUBLE,
"min_recovery" DOUBLE,
"max_recovery" DOUBLE,
"nr_sessions_1" DOUBLE,
"nr_rest_days_1" DOUBLE,
"total_kms_1" DOUBLE,
"max_km_one_day_1" DOUBLE,
"total_km_z3_z4_z5_t1_t2_1" DOUBLE,
"nr_tough_sessions_effort_in_z5_t1_or_t2_1" DOUBLE,
"nr_days_with_interval_session_1" DOUBLE,
"total_km_z3_4_1" DOUBLE,
"max_km_z3_4_one_day_1" DOUBLE,
"total_km_z5_t1_t2_1" DOUBLE,
"max_km_z5_t1_t2_one_day_1" DOUBLE,
"total_hours_alternative_training_1" DOUBLE,
"nr_strength_trainings_1" DOUBLE,
"avg_exertion_1" DOUBLE,
"min_exertion_1" DOUBLE,
"max_exertion_1" DOUBLE,
"avg_training_success_1" DOUBLE,
"min_training_success_1" DOUBLE,
"max_training_success_1" DOUBLE,
"avg_recovery_1" DOUBLE,
"min_recovery_1" DOUBLE,
"max_recovery_1" DOUBLE,
"nr_sessions_2" DOUBLE,
"nr_rest_days_2" DOUBLE,
"total_kms_2" DOUBLE,
"max_km_one_day_2" DOUBLE,
"total_km_z3_z4_z5_t1_t2_2" DOUBLE,
"nr_tough_sessions_effort_in_z5_t1_or_t2_2" DOUBLE,
"nr_days_with_interval_session_2" DOUBLE,
"total_km_z3_4_2" DOUBLE,
"max_km_z3_4_one_day_2" DOUBLE,
"total_km_z5_t1_t2_2" DOUBLE,
"max_km_z5_t1_t2_one_day_2" DOUBLE,
"total_hours_alternative_training_2" DOUBLE,
"nr_strength_trainings_2" DOUBLE,
"avg_exertion_2" DOUBLE,
"min_exertion_2" DOUBLE,
"max_exertion_2" DOUBLE,
"avg_training_success_2" DOUBLE,
"min_training_success_2" DOUBLE,
"max_training_success_2" DOUBLE,
"avg_recovery_2" DOUBLE,
"min_recovery_2" DOUBLE,
"max_recovery_2" DOUBLE,
"athlete_id" BIGINT,
"injury" BIGINT,
"rel_total_kms_week_0_1" DOUBLE,
"rel_total_kms_week_0_2" DOUBLE,
"rel_total_kms_week_1_2" DOUBLE,
"date" BIGINT
);
Anyone who has the link will be able to view this.