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

Student Stress Level Detection #681

Closed
kom-senapati opened this issue Jun 26, 2024 · 4 comments · Fixed by #682
Closed

Student Stress Level Detection #681

kom-senapati opened this issue Jun 26, 2024 · 4 comments · Fixed by #682
Assignees
Labels
Assigned 💻 Issue has been assigned to a contributor Intermediate Points 30 - SSOC 2024 SSOC

Comments

@kom-senapati
Copy link
Contributor

ML-Crate Repository (Proposing new issue)

🔴 Project Title : Student Stress Level Detection
🔴 Aim : This project aims to predict student stress levels based on study load, academic performance and other stuff.
🔴 Dataset : https://www.kaggle.com/datasets/samyakb/student-stress-factors/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. 😎

@kom-senapati kom-senapati added the Up-for-Grabs ✋ Issues are open to the contributors to be assigned label Jun 26, 2024
Copy link

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

@kom-senapati
Copy link
Contributor Author

kom-senapati commented Jun 26, 2024

Hi @abhisheks008 👋🏻, It's my first time here and I wanna start contributing, please assign it to me under SSOC

Full name : K Om Senapati

GitHub Profile Link : K Om Senapati

Participant ID (If not, then put NA): NA

Approach for this Project: I will do EDA first then data cleaning and data transformation if needed. After that, I will split data sets into training and testing sets. Then will use scaling and test with models like SVR, Decision Tree, Random Forest, and Gradient Boost and find a good model with high R2 and less MAE.

What is your participant role?: SSOC

@abhisheks008
Copy link
Owner

Hi @kom-senapati implement 6-7 models for this project/problem statement.

Assigned to you.

@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 Jun 26, 2024
Copy link

Hello @kom-senapati! Your issue #681 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
Assigned 💻 Issue has been assigned to a contributor Intermediate Points 30 - SSOC 2024 SSOC
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants