You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could you add a feature to have a timer in the background of scouting which starts when the scouter selects anything, logs all the selections they make, and ends when they select something such as finished climbing, this log would not be visible to the scouter but would be accessible in the exported spreadsheet.
The text was updated successfully, but these errors were encountered:
This is a tough one. I feel like it would over complicate the application to some degree. If someone you know has the time to work on this, by all means go for it, but I barely have much time on my schedule to work on it.
I'm curious as to what the use-case is here. Could you tell us more about why you want to log all scout interactions and what value that adds to your scouting system?
I was thinking that the person analyzing the scouting info could get data for cycle times without having to rely on scouters filling out times in addition to what the robots are doing which we've found to be unreliable. However, this could prove ineffective since the scouters still have to fill out the sheet at the time the things are done. Overall, in my opinion, it's significantly less important than the rest of the features I've mentioned.
Could you add a feature to have a timer in the background of scouting which starts when the scouter selects anything, logs all the selections they make, and ends when they select something such as finished climbing, this log would not be visible to the scouter but would be accessible in the exported spreadsheet.
The text was updated successfully, but these errors were encountered: