Team 103 Beta Code

[BrianBT103]

Attached is our Labview Beta code. Please post any questions if you have any. For those of you who are going to BE 7 and Ramp Riot, we look forward to seeing you there.

[Charles Harris]

Thank you for trying to share your work, but the "rest of us" who do not have the dependent libraries cannot load any of the VI's. How about the html view????

[Kevin Sevcik]

I kind of prefer having both available. It's much easier to trace the flow and organization of the code as an actual VI, even if you don't have the requisite libraries. The HTML version gives you actual icons for the VIs if you really need them, but I think just hovering over the blank icons to get the VI names is pretty helpful.

Also, a question for Brian:

Is there a reason you're building up arrays of clusters of arrays by adding one item at a time to them in your autonomous loop? Doing things that way is frightfully inefficient, as the cRIO has to keep changing the size of the arrays and reserving more memory as they get larger. Plus, unbundling them just to rebundle them back up seconds later wastes more time and memory. And finally, if you keep your robot in autonomous mode for too long, those arrays are going to keep growing and growing until your cRIO crashes or shudders to a halt. There's several more efficient ways of doing that if you spend some time looking into it.

[norm365]

Are you prevented from sharing the WPI library VIs? It makes loading the VIs still possible but cumbersome and leaves us to look at wires to have an idea of what the data flow is since those VIs show up as big ?. I know you can't help with the fact that we do not have the cRIO plugin. When posting HTML, in the past I have not seed all the possible cases of case statements printed. Keep that in mind.

[jross]

Are you prevented from sharing the WPI library VIs? It makes loading the VIs still possible but cumbersome and leaves us to look at wires to have an idea of what the data flow is since those VIs show up as big ?. I know you can't help with the fact that we do not have the cRIO plugin. When posting HTML, in the past I have not seed all the possible cases of case statements printed. Keep that in mind.

You are correct, we are prohibited from providing the libraries. FIRST will post them when they are ready.

It is possible to display all the cases when generating the html, but it can be confusing if you have a lot of case statements, because it isn't always clear which one goes with which.

[BrianBT103]

Also, a question for Brian:

Is there a reason you're building up arrays of clusters of arrays by adding one item at a time to them in your autonomous loop? Doing things that way is frightfully inefficient, as the cRIO has to keep changing the size of the arrays and reserving more memory as they get larger. Plus, unbundling them just to rebundle them back up seconds later wastes more time and memory. And finally, if you keep your robot in autonomous mode for too long, those arrays are going to keep growing and growing until your cRIO crashes or shudders to a halt. There's several more efficient ways of doing that if you spend some time looking into it.

Your completely right in what you are saying, except we are not "building up" arrays of clusters so to speak. I mean, it may be a little inefficient but I don't believe that it has such a huge impact as what your are saying it does.

[willson.thomas]

Could you please post the code in HTML form please? It is a lot nicer to view the code with the FIRST "blocks" in place.