I was wondering...
Since the build season is over i would like to know if i was allowed to make my "stupid" little programs to further my knowledge in labview. I understand not to work in imaging or other things we don't require for the robotic programming.

Basically, for programming, the teleop stuff is pretty easy. That shouldn't pose a problem, because there's not much robot-side processing involved -- it's mainly the driver processing what they see.

What's hard is autonomous mode. For that, we need image (and other sensors) processing. So without the robot itself, what you could do is wire up a static image (or have a "choose file" type thing) in LabVIEW and process that. Then use trig and other math functions to figure out what you can about the target information (angle, distance, etc).
Just make sure you time it, so you know how long it takes per frame.

I'm not sure if you can do this, but feel free to try (if you have time): record some video (webcam or any other method), and then process that frame-by-frame. Ideally, the code should finish executing when/before the video is done (time-wise).

Examples of what NOT to do:
- Video/3D output. Absolutely no relation to the robot.
- Sound.
- Network I/O. That's handled by FRC library, and there's no point (maybe against rules) to reinvent the wheel.
I may augment that list later.

thx

plz teach me labveiw i'm dying here

Are you going to switch to working on programming now boy?