Skip to content

Adding Data Hub - #2

Open
Aztechs157-Git wants to merge 7 commits into
rebuilt2026from
data-hub
Open

Aztechs157-Git wants to merge 7 commits into
rebuilt2026from
data-hub

Conversation

@Aztechs157-Git

Copy link
Copy Markdown
Contributor

Analysis of the match data has traditionally been done outside of the app using a combination of python code to aggregate the data and excel to view and analyze. In 2025 we also tested out Tableau with minor success. This data hub builds a basic page to start in-app analysis.

Key Additions:

  1. Sandwich menu navigation: The Data Hub, Competition Selection, and Pre-Match scouting pages each display a sandwich menu at the top of the screen to move between the data hub and match scouting. Once the user has gotten past Pre-Match, the sandwich menu is no longer available to avoid distraction from actual match scouting.
  2. Data Hub Page: The Data hub page reads data from the csvs generated by the match scouting to show some simple views: Top Teams (sorted by total score and other options), Individual Team Summary, Individual Team performance trend (line graph of team's scoring for each match), Individual Team's match data lookup (see what the team did each match)
  3. Data Organization: Match scouting data now falls into Internal Storage/Documents instead of the more difficult to access App Data directory it was available at before

No major changes to user input for match scouting pages.

Code for these changes was generated using a combination of Ranier's design and constant feedback and review, and Gemini.


/**
* Converts qualitative accuracy strings to numeric multipliers.
* Note: "More than 95%" is treated as 0.97 to account for occasional misses.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

comment for "Less than 10%" where?

Comment thread docs/PR_DEEP_DIVE.md
3. **Aggregation**: Data is filtered by `Team Number` and aggregated using Java Streams to calculate averages and success rates.

### Visualizations:
* **Team Search**: Implemented a `MaterialAutoCompleteTextView` allowing scouters to jump to any team present in the local database.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

change "scouters" to "scouts"

Comment thread docs/PR_DEEP_DIVE.md
* `passed_fuel`

### Storage & Permissions (SDK 35)
* The app now targets **Android 15 (API 35)**.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment thread docs/PR_DEEP_DIVE.md

## 4. UI/UX Improvements
* **Sidebar Navigation**: Implemented a `NavigationDrawer` (Sidebar) to allow quick switching between the Scouting flow and the Dashboard without hitting "Back" 5 times.
* **Match Details**: Tapping a match in the history list now opens a `MaterialAlertDialog` with a full qualitative breakdown of that specific match, including scouter comments.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

change "scouter" to "scout"

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.

4 participants