Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Health Insurance Cross Sell Prediction #706

Closed
tanuj437 opened this issue Jul 10, 2024 · 6 comments · Fixed by #709
Closed

Health Insurance Cross Sell Prediction #706

tanuj437 opened this issue Jul 10, 2024 · 6 comments · Fixed by #709
Assignees
Labels
Advanced Points 40 - SSOC 2024 Assigned 💻 Issue has been assigned to a contributor SSOC

Comments

@tanuj437
Copy link
Contributor

ML-Crate Repository (Proposing new issue)

🔴 Project Title : Health Insurance Cross Sell Prediction
🔴 Aim : To Successfully Predict the Response
🔴 Dataset : https://www.kaggle.com/competitions/playground-series-s4e7/data
🔴 Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.


📍 Follow the Guidelines to Contribute in the Project :

  • You need to create a separate folder named as the Project Title.
  • Inside that folder, there will be four main components.
    • Images - To store the required images.
    • Dataset - To store the dataset or, information/source about the dataset.
    • Model - To store the machine learning model you've created using the dataset.
    • requirements.txt - This file will contain the required packages/libraries to run the project in other machines.
  • Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

🔴🟡 Points to Note :

  • The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
  • "Issue Title" and "PR Title should be the same. Include issue number along with it.
  • Follow Contributing Guidelines & Code of Conduct before start Contributing.

To be Mentioned while taking the issue :

  • Full name :
  • GitHub Profile Link :
  • Participant ID (If not, then put NA) :
  • Approach for this Project :
  • What is your participant role? (Mention the Open Source Program name. Eg. HRSoC, GSSoC, GSOC etc.)

Happy Contributing 🚀

All the best. Enjoy your open source journey ahead. 😎

@tanuj437 tanuj437 added the Up-for-Grabs ✋ Issues are open to the contributors to be assigned label Jul 10, 2024
Copy link

Thank you for creating this issue! We'll look into it as soon as possible. Your contributions are highly appreciated! 😊

@tanuj437
Copy link
Contributor Author

Full name : Tanuj Saxena
GitHub Profile Link : https://github.com/tanuj437
Participant ID (If not, then put NA) : NA
Approach for this Project : Firstly, Proper EDA removing duplicates, filling empty columns if any, then Using different model for prediction since its having binary response so starting with Logistic, random forest,gradient, XGBoost,SVM etc
What is your participant role? (Mention the Open Source Program name. Eg. HRSoC, GSSoC, GSOC etc.) SSOC'24

@abhisheks008
Copy link
Owner

Let the assigned issue finish first.

@tanuj437
Copy link
Contributor Author

@abhisheks008 now you may assign

@abhisheks008
Copy link
Owner

Assigned @tanuj437

@abhisheks008 abhisheks008 added Assigned 💻 Issue has been assigned to a contributor Intermediate Points 30 - SSOC 2024 SSOC and removed Up-for-Grabs ✋ Issues are open to the contributors to be assigned labels Jul 13, 2024
@abhisheks008 abhisheks008 added Advanced Points 40 - SSOC 2024 and removed Intermediate Points 30 - SSOC 2024 labels Jul 20, 2024
Copy link

Hello @tanuj437! Your issue #706 has been closed. Thank you for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Advanced Points 40 - SSOC 2024 Assigned 💻 Issue has been assigned to a contributor SSOC
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants