![]() |
Re: 2015 Lessons Learned: The Negative
Quote:
|
Re: 2015 Lessons Learned: The Negative
Quote:
|
Re: 2015 Lessons Learned: The Negative
Quote:
Professional curiosity requires me to ask about your hardware setup. Do you stream HD or standard Def? How many cameras, lockoff, tripod or handheld? Do you take the interface from the scoring system? How big does your car/truck need to be to haul all of this gear around? What switch/SEG? Do you carry lighting as well? Sorry for all the questions, I'm preparing for a local group request that goes " Hey, you do video stuff at work, what can you do for us???" |
Re: 2015 Lessons Learned: The Negative
Quote:
The stream is HD. I believe we have 3 Cameras though sometimes some of the students supplement that with their own gear. Typically 2 are on tripods and one is available for handheld use. Yes they connect to the FMS to get the score overlays. We haul it around in a 53' trailer, but the bulk of the video equipment is in a road case aprox 2'w x 6'l x 5'h, there is a second one of the same size that is for the Audio equipment. Projectors fit in another case that has space and the screens ride on top of the Video and Audio cases. We also have a 2'w x 8'l x 3'h road case that holds the tripods for the speakers and projectors. I know that the IN district has a similar set up and I believe they haul it around in cars since the AndyMark truck that is used to haul the fields does not have room to add another road case. No additional lighting is used. Kevin does have a list with all of the equipment that is used which he is supposed to dig up and forward to me for the areas that are joining, or thinking about joining, the district system for the 2016 or 2017 season. When I get that I can post it. |
Re: 2015 Lessons Learned: The Negative
Quote:
|
Re: 2015 Lessons Learned: The Negative
Quote:
Van Buren was wrong on one account, we rarely have a mobile camera. Usually the third camera is a full field shot. Kevin sometimes brings in his mobile cam, but not to all events. Getting usable footage from it is another problem. Students need a lot more training with it that isn't just verbal commands from the switcher. |
Re: 2015 Lessons Learned: The Negative
Quote:
|
Re: 2015 Lessons Learned: The Negative
Quote:
I sent you an email about the equipment that we use. Yes it just goes in the trailer with the rest of the equipment used to produce the event. I should be able to get a picture of the cases in the next couple of days that I'll forward to you. |
Re: 2015 Lessons Learned: The Negative
Mr V, do you mind sending me that list as well. That would be great!
|
Re: 2015 Lessons Learned: The Negative
Quote:
My team didn't get a programming mentor until our 6th year as a team. And yet we had placed second place at multiple competitions beforehand - many factors were involved in us ending second place rather than first, and while programming was one of them, it was never the predominant factor as to why. We taught ourselves everything we could about control systems, and we actually never got PID fully functional until a programming mentor joined the team - even with 3-4 programmers, one of which is now at an Ivy for CS, so it isn't like we're struggling to build the code. When kids aren't taught Calculus until junior (2 years ahead of schedule) or senior year (1 year ahead), it's kinda difficult to introduce advanced control systems in addition to learning the ins and outs of coding a robot. Coding a robot is far different than your standard software programming, which is what we are taught in our CS classes offered here. Sure, it may seem simple to write driveTrain.drivePID.setXDistance(4.0), but it isn't that simple when you're just starting out. In addition to a plethora of other factors going on within the team - for example, we spent a very long time on design this year - it's not really simple to just magically develop a brand new, state of the art, never-before-seen control system. |
Re: 2015 Lessons Learned: The Negative
Quote:
In college you can likely expect to have to create the internals of the PID classes used in WPIlib (by which I mean programatically [or in some form of hardware] creating the feedback loop and designing the plant) necessitating full understanding of the system. WPILib makes it so that all you have to do for a basic loop is to just tweak k, i, and d values. |
Re: 2015 Lessons Learned: The Negative
Quote:
A year later, when a programming mentor joined, we hand wrote them, and never used WPI at all. And suddenly something clicked and I realized how simple it was. Just error, change in current value since last iteration, and a Riemann sum for the current and last value vs time. Plus the constants that you have to adjust. Maybe we just didn't look in the obvious places, but even adjusting the three constants is relatively time consuming and frustrating if you don't know which value you should be adjusting for which behavior - because in reality, they aren't completely independent of each other. |
| All times are GMT -5. The time now is 06:18. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi