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

Vulnerable Cancer Patients Analysis and Prediction #498

Closed
abhisheks008 opened this issue Jan 13, 2024 · 4 comments · Fixed by #536
Closed

Vulnerable Cancer Patients Analysis and Prediction #498

abhisheks008 opened this issue Jan 13, 2024 · 4 comments · Fixed by #536
Assignees
Labels
Assigned 💻 Issue has been assigned to a contributor Intermediate Points 30 - SSOC 2024 JWOC This issue/pull request will be considered for JWOC 2k22.

Comments

@abhisheks008
Copy link
Owner

ML-Crate Repository (Proposing new issue)

🔴 Project Title : Vulnerable Cancer Patients Analysis and Prediction
🔴 Aim : The aim of this project to find out the cancer patients and predict them.
🔴 Dataset : https://www.kaggle.com/datasets/irinhoque/mental-health-insights-vulnerable-cancer-patients
🔴 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. 😎

@abhisheks008 abhisheks008 added the Up-for-Grabs ✋ Issues are open to the contributors to be assigned label Jan 13, 2024
@Yuvika-14
Copy link

hi abhisekh
Full name: Yuvika Singh
git hub profile link:https://github.com/Yuvika-14/Yuvikademo.git
approch: ensemble methods, gradient boosting, neural networks.
Take care of the missing data if there are any categorical values then will use one hot encoder or label encoder depending upon the issue.

@abhisheks008
Copy link
Owner Author

One issue at a time @Yuvika-14

@CoderOMaster
Copy link
Contributor

CoderOMaster commented Jan 17, 2024

Hi
@abhisheks008
Name: Keshav Arora
GitHub: www.github.com/CoderOMaster
Approach:EDA,use of NLP wrt rnn and it's versions,BERT,etc
JWOC

@abhisheks008
Copy link
Owner Author

Issue assigned to you @CoderOMaster

@abhisheks008 abhisheks008 added Assigned 💻 Issue has been assigned to a contributor Intermediate Points 30 - SSOC 2024 JWOC This issue/pull request will be considered for JWOC 2k22. and removed Up-for-Grabs ✋ Issues are open to the contributors to be assigned labels Jan 17, 2024
@abhisheks008 abhisheks008 linked a pull request Jan 18, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Assigned 💻 Issue has been assigned to a contributor Intermediate Points 30 - SSOC 2024 JWOC This issue/pull request will be considered for JWOC 2k22.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants