CSA Sprint #1 Checkpoint #2 Feature Ready

[Pitsco]

Requirements:

Team review contains ...

• runtime demo, of key features created in sprint
• planning demo, list of key features that correspond to demo
• requirements demo, a list of key teacher requirement and progress to those requirements

Individual review contains ...

• a review of your TEAM code commits and deltas, preparation of key commits on features is desired
• a review of your JWT/Individual code commits and deltas, preparation of key commits on JWT is desired
• a review of your GitHub commits, work style and work frequency
• other assets, no code, that you created during the sprint

Team review:

Frontend Runtime

Backend Runtime, Deployed

Key Features

Individual:

Vardaan:

Frontend Visualization of Past Stats Creating Draft Page Monte Carlo Simulator Creating Linear Regressor

Vishnu:

Key Commits:

	Branch Commits	Key Commits
Frontend Commits	Main Branch Commits,	Fetching by ID Feature, Specific Game Search, Fetching all Players
Backend Commits	Statistic Branch Commits, Main Branch Commits	Pulling API Data for Both Players and Team, Searching by ID Feature, Specific Game Finder, Fetching All Players

Derrick:

Key Commits:

	Branch Commits	Key Commits
Frontend Commits	Main Branch Commits, Statistic Branch Commits	Fetching by ID Feature, Specific Game Search, Fetching all Players
Backend Commits	Statistic Branch Commits, Main Branch Commits	Pulling API Data for Both Players and Team, Searching by ID Feature, Specific Game Finder, Fetching All Players

Collaboration:

Kaiden: Worked in person and on call with Kaiden, attempted to connect stats page with search feature on Wednesday with Kaiden

Jishnu: Collaborated with him by him helping me pull data from the frontend from backend. Want to further this collaboration with JScharting in the future.

Workstyle and Work frequency

Future Plans:

• Work on creating an individual page (main feature) and use jscharting to create a chart that pulls data from api
• Pull all players CURRENTLY in the NBA, not overall players
  • May be hard because data is only sorted by year
• Incorporate more JWT into the project on my end
  • Do something more advanced with log in and how it stores fantasy data for a specific account?

Jishnu:

Kaiden:

Key Commits:

• Frontend Commits: Making the suggested search & Getting the ID of the player & using linear regression to predict the next game's stats along with graph
• I worked on the individual stats page with Derrick, I got the id of the player after they searched it to retrieve their stats, which me and Derrick did. We worked together because my CORS wasn't working but it worked for Derrick so we called over discord to work on displaying the stats of each player when they search it.
• My future plans are to work on the drafting system to store each person's player to their account. Also I will continue to work on the frontend to style and make everything look better.

Nikhil:

Key Commits:

• Backend Deployment
• Linear Regression Model Development:

Achievements:

• Backend Server Deployment
• Predictive Model Integration: Integrated a linear regressor model into the backend, providing users with predictions of NBA game outcomes.

Future Plans:

• Model Refinement: Plan to enhance the linear regression model by incorporating more complex statistical methods and machine learning algorithms. The goal is to improve prediction accuracy and offer users more reliable insights.
• Frontend Optimization: Plan to add a lot more detail into backend and a lot of styling and different things for money line.

[VishnuAravind12]

Vishnu:

Key Commits:

	Branch Commits	Key Commits
Frontend Commits	Main Branch Commits	Integrated FantasyDraft page with backend, Detailed Stats Page
Backend Commits	Fantasy Branch Commits	Custom Data Objects for both Regression and draft, Logistic Regression Logic Coded, Encapsulated Approach for Regression, Parser for JSON