-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Scouting Information Schema #7
Comments
No assignees, but everyone should be working on this ideally. |
Do you have an example of the types of data we collected in previous years? |
maybe just add functionality to the app that makes it easy to just add new data collection type, similar to a google form? That way we don’t need to actually change any of the code: to add a new data point we can just add a new type of data from a drop-down menu, add some description whatever, and allow for weight changing in however the data points will be weighted depending on that year’s game. |
*repost from teams
Only if we've made a previous scouting app.
https://github.com/Team3256/infinite-recharge-scouting-app/blob/main/my_wb_server/main.py @memori034 can help you as well with this, since we used Google Forms during CalGames. |
yeah in the interest of robot game
|
@realjoshuau do you think we can quantify qualitative data? or even have chatgpt rank/sort qualitative data? or did you plan on manually reading every qualitative comment as that sounds somewhat tedious and subjective. |
we can do ratings on scales |
we probably can, qualitative data isn't just notes and long-form data (even though it is useful during picklist/match strat), but also relative ratings on scales (which is why we assign people experienced with scouting on qual scouting) using AI to rank/sort qual data is interesting and I think we should 100% look into it. we need to train/make the model understand how frc works tho |
@Saamstep lmao |
fire |
Brainstorm ways that we could create a "scouting schema", i.e a way that we should specify what data could be collected, what transforms we could apply to the data, and how that data feeds into other functionality
Since we plan to reuse the app in the seasons coming, a "scouting schema" could be a way that we reuse the app by just re-specifying what data we want to collect.
The text was updated successfully, but these errors were encountered: