|
|
|
 The secret to this whole thing is that it's the robot that builds the team. - JohnBoucher [more] |
 |
|
|||||||
|
||||||||
Mostly complete framework to allow for testing code away from a cRIO.
We set out to create a framework with these goals:
Critical logic can be run without access to a cRIO or Robot
Supports writing and running test cases
Has reusable components for future seasons (and other teams)
The code in question is here: https://github.com/Team488/Shared
(also linked to in the document)
Attached Files
-
Offseason Architecture.pptx
Offseason Architecture.pptx
download file
uploaded: 01-02-2014 11:15 AM
filetype: ptx
filesize: 482.95kb
downloads: 245
Discussion
view entire thread
01-02-2014 11:28 AM
JohnGilb
Re: paper: 488 2013 Offseason Architecture
Github repository for the code
This public repository contains the results of some experiments we conducted in the offseason in Java. Our goal was to create a simple framework where robot code could be developed and tested without a cRIO.
There's still many ways this framework could be improved, but we believe we have made progress worth sharing.
Here's the summary (included in the linked document) of our goals:
Critical logic can be run without access to a cRIO or Robot
- Multiple teams (Electrical, Mechanical, Programming) need access to the robot or a cRIO, so this has often been a bottleneck for us
- Now that our programming team has a large pool of programmers, the odds of making a change that causes a regression has increased
- In addition, we want to be able to write proof-of-concept tests during development
- The progress we make this year should be applicable to future years (assuming no rules changes about shared libraries)
12-30-2014 12:05 PM
JohnGilb
Re: paper: 488 2013 Offseason Architecture
The repository now includes code from 2014 and 2014 off-season as well.
view entire thread
Tags
loading ...