Difference between revisions of "Stronghold Meeting - 18-Jan-2016"

From DEW Robotics
Jump to: navigation, search
(Programming)
(Programming)
Line 16: Line 16:
 
==Programming==
 
==Programming==
  
- We developed a new system for selecting the drive type.  
+
- We started with investigating the memory problem of GRIP.  
  
:-This year, arcade/tank, gyro correction, auto aim, and (if necessary) anti-tip will all be supported.
+
:-Fist, we watched to see if there was a memory leak. It did not appear to be so. If there was one, it was unnoticeable.  
  
:-At any time, all of these may be turned on. We needed a way to allow for different features to be prioritized. For example, anti tip takes priority over the vision auto aim.  
+
:-We deployed the GRIP program, watching the RAM before and after. The GRIP program used almost 50 mb of RAM.  
  
:-We decided to store the priority in an integer. Each bit of the integer would be if each feature was on / off. The highest bit would be the highest priority. This code became much more streamlined and robust than simply using if statements for every feature. Adding a feature becomes very easy.  
+
:-For now, it seems that GRIP only causes memory issues occasionally during deploys.
  
- We also worked on having our code start GRIP instead of manually. This way the drivers would not have to start it before each match.
+
:-Since this did not cause a serious problem, we decided to wait for a GRIP update to address this issue.
 
 
:-After trying many different things, we were finally able to get the program to run GRIP. However, we then noticed that GRIP was eating up quite a bit of RAM.
 
  
 
==Strategy==
 
==Strategy==

Revision as of 08:02, 24 January 2016

Competition Season Meeting

Meeting Date Meeting Time Location Attendees
TCHS Brandywine

CAD & Design

Mechanical

Programming

- We started with investigating the memory problem of GRIP.

-Fist, we watched to see if there was a memory leak. It did not appear to be so. If there was one, it was unnoticeable.
-We deployed the GRIP program, watching the RAM before and after. The GRIP program used almost 50 mb of RAM.
-For now, it seems that GRIP only causes memory issues occasionally during deploys.
-Since this did not cause a serious problem, we decided to wait for a GRIP update to address this issue.

Strategy

Field Elements

Other



Recorded by: Date: Journal Editor: Date: