Skip to content

Jeff 551 - #644

Open
Jeff-Stammler wants to merge 3 commits into
mainfrom
Jeff-551
Open

Jeff 551#644
Jeff-Stammler wants to merge 3 commits into
mainfrom
Jeff-551

Conversation

@Jeff-Stammler

Copy link
Copy Markdown
Collaborator

Moved all of the dataFile classes up a level (got them out of the Utility folder) now that ALL of them use this method - no need to put them under utility.

Added .csv files for Accuracy, ClimbPosition and ClimbLevel. Added dataFile classes for all three, and then fixed up any references to them to be consistent with the other dataFile classes. (getAccuracyValue -> getAccuracyId [for example]).

Simplified how we display the Loading... messages using a parameterized string rather than having double strings (loading vs error).

Fixed logic in PostMatch for detecting if all fields are filled in. Before, we logged a few things then did some checks (which leaves partial logged data - which didn't cause an issue, but didn't make sense (and used more memory). Also when checking the ClimbPosition and ClimbLevel, only check IF the components are ENABLED (meaning the robot climbed and we need a choice). Otherwise ignore it. Not sure how that worked correctly before if the robot didn't climb.

fixed some compiler warnings and grammar issues (android studio reports these now!)

fixes #551

Moved all of the dataFile classes up a level (got them out of the Utility folder) now that ALL of them use this method - no need to put them under utility.

Added .csv files for Accuracy, ClimbPosition and ClimbLevel.  Added dataFile classes for all three, and then fixed up any references to them to be consistent with the other dataFile classes.  (getAccuracyValue -> getAccuracyId [for example]).

Simplified how we display the Loading... messages using a parameterized string rather than having double strings (loading vs error).

Fixed logic in PostMatch for detecting if all fields are filled in.  Before, we logged a few things then did some checks (which leaves partial logged data - which didn't cause an issue, but didn't make sense (and used more memory).  Also when checking the ClimbPosition and ClimbLevel, only check IF the components are ENABLED (meaning the robot climbed and we need a choice).  Otherwise ignore it.  Not sure how that worked correctly before if the robot didn't climb.
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.

Read ClimbPositions from a .csv file rather than hard coding into Java.

1 participant