📃: Pokémon Data Analysis and Legendary Prediction #304
Assignees
Labels
Contributor
Denotes issues or PRs submitted by contributors to acknowledge their participation.
gssoc-ext
hacktoberfest
level2
Status: Assigned
Indicates an issue has been assigned to a contributor.
Comments
|
🙌 Thank you for bringing this issue to our attention! We appreciate your input and will investigate it as soon as possible. Feel free to join our community on Discord to discuss more! |
UTSAVS26
added
Contributor
This was referenced Oct 8, 2024
UTSAVS26
added a commit
that referenced
this issue
Oct 10, 2024
# Pull Request for PyVerse 💡 ## Issue Title : <!-- Enter the issue title here -->📃: Pokémon Data Analysis and Legendary Prediction #304 - **Info about the related issue (Aim of the project)** : <!-- What's the goal of the project --> This project aims to analyze Pokémon data to predict whether a Pokémon is legendary or not using advanced machine learning models. The dataset includes various attributes such as base stats, type, and generation, which will be used to train and evaluate different models. - **Name:** <!--Mention Your name--> Jatin Gupta - **GitHub ID:** <!-- Mention your GitHub ID --> thejatingupta7 - **Email ID:** <!--Mention your email ID for further communication. --> [email protected] - **Idenitfy yourself: (Mention in which program you are contributing in. Eg. For a WoB 2024 participant it's, `WoB Participant`)** <!-- Mention in which program you are contributing --> GSSOC Hacktoberfest <!-- Mention the following details and these are mandatory --> Closes: #issue number that will be closed through this PR #304 ### Describe the add-ons or changes you've made 📃 This project aims to analyze Pokémon data to predict whether a Pokémon is legendary or not using advanced machine learning models. The dataset includes various attributes such as base stats, type, and generation, which will be used to train and evaluate different models. ## Type of change ☑️ What sort of change have you made: <!-- Example how to mark a checkbox:- - [x] My code follows the code style of this project. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Code style update (formatting, local variables) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update ## How Has This Been Tested? ⚙️ Various data analysis tools, various preprocessing techniques (such as Imputation by K Nearest Neighbours, Normalization, etc), and various machine learning models, from logistic regression to Neural Nets (MLP), ## Checklist: ☑️ <!-- Example how to mark a checkbox: - [x] My code follows the code style of this project. --> - [x] My code follows the guidelines of this project. - [x] I have performed a self-review of my own code. - [x] I have commented on my code, particularly wherever it was hard to understand. - [x] I have made corresponding changes to the documentation. - [x] My changes generate no new warnings. - [x] I have added things that prove my fix is effective or that my feature works. - [x] Any dependent changes have been merged and published in downstream modules.
|
✅ This issue has been closed. Thank you for your contribution! If you have any further questions or issues, feel free to join our community on Discord to discuss more! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🔴 Title : Pokémon Data Analysis and Legendary Prediction
🔴 Aim : To add an in-depth analysis and prediction on legendary pokemon dataset
🔴 Brief Explanation: Uses various data analysis tools, various preprocessing techniques (such as Imputation by K Nearest Neighbours, Normalisation, etc), and various machine learning models, from logistic regression to Neural Nets (MLP),
Screenshots 📷
NA
✅ To be Mentioned while taking the issue :
GSSOC, hacktoberfest
Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎
The text was updated successfully, but these errors were encountered: