Nice job everyone! I have provided some comments for your first milestone. Please address these concerns in your third milestone submission.
Draft a Team work contract: Correctness
Project set-up: Mechanics
Its great that you dockerized the project makes it very easy for others to run it up and execute.
Project proposal: reasoning
Maybe you can explain the reason for choosing f1 score instead of others cores such as AUC or recall. How f1 is better for this specific problem instead of other metrics.
A script that downloads the data: Accuracy
A script that downloads the data: Quality
Exploratory data analysis in a literate code document: QUALITY
Exploratory data analysis in a literate code document: VIZ
Exploratory data analysis in a literate code document: REASONING
In your EDA; a brief explanation after each visualizations would make it easier to follow in terms of your conclusions and what you are trying to achieve with this plot. I know that there are remarks at the end in the EDA, but just a small description after a plot would make it easier for the reader to follow your logic.
Exploratory data analysis in a literate code document: ACCURACY
Nice job everyone! I have provided some comments for your first milestone. Please address these concerns in your third milestone submission.
Draft a Team work contract: Correctness
Project set-up: Mechanics
A script that downloads the data: Accuracy
A script that downloads the data: Quality
Exploratory data analysis in a literate code document: QUALITY
Exploratory data analysis in a literate code document: VIZ
Exploratory data analysis in a literate code document: REASONING
Exploratory data analysis in a literate code document: ACCURACY
Expectations: Mechanics