Skip to content

Feature/algorithm visualization#72

Open
keshavgoel787 wants to merge 36 commits intomainfrom
feature/algorithm_visualization
Open

Feature/algorithm visualization#72
keshavgoel787 wants to merge 36 commits intomainfrom
feature/algorithm_visualization

Conversation

@keshavgoel787
Copy link
Copy Markdown
Collaborator

Description

Added Visualizations and way for users to visually understand what correlations exist between the foods the eat and symptoms that occur based on our algorithm. Also added a small python script to allow for a way for the generated data to be added into our backend.

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • [ x] New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactoring (code improvement without changing functionality)
  • Documentation update
  • Configuration/infrastructure change
  • Performance improvement
  • Test coverage improvement

What Changed?

  • New visualizations
  • a python script for adding seed data to backend so frontend can access it

Testing & Validation

How this was tested

Screenshots/Recordings

Screenshot 2026-04-01 at 3 34 29 PM Screenshot 2026-04-01 at 3 34 41 PM

Unfinished Work & Known Issues

I had a slight issue with creating a user, filling in data, and seeing the new correlations based on new data, so that's why I just hardcoded the seed data and autodefaulted to user_001

  • None, this PR is complete and production-ready
  • The following items are intentionally deferred:



Notes & Nuances



Pre-Merge Checklist

Code Quality

  • Code follows the project's style guidelines and conventions
  • Self-review completed (I've reviewed my own code for obvious issues)
  • No debugging code, console logs, or commented-out code left behind
  • No merge conflicts with the base branch
  • Meaningful commit messages that explain the "why"

Testing & CI

  • All CI checks are passing
  • All new and existing tests pass locally
  • Test coverage hasn't decreased (or decrease is justified)
  • Linting passes without errors

Documentation

  • Code is self-documenting or includes helpful comments for complex logic
  • API documentation updated (if backend endpoints changed)
  • Type definitions are accurate and up-to-date

Reviewer Notes

  • Areas needing extra attention: ...
  • Questions for reviewers: ...

Base automatically changed from feature/algorithm to main April 4, 2026 16:18
keshavgoel787 and others added 22 commits April 7, 2026 13:28
…1 for testing purposes, since was having issues with login
…1 for testing purposes, since was having issues with login
…1 for testing purposes, since was having issues with login
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants