|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
pic: 1706 Aerial Assist Vision Solution Sample
|
|
#2
|
||||
|
||||
|
Re: pic: 1706 Aerial Assist Vision Solution Sample
Are you using RotatedRects? It seems as though your bounding rectangles are turned, not just boxed!
|
|
#3
|
||||
|
||||
|
Re: pic: 1706 Aerial Assist Vision Solution Sample
yes, I am
|
|
#4
|
||||
|
||||
|
Re: pic: 1706 Aerial Assist Vision Solution Sample
How did you use this information during and after autonomous?
|
|
#5
|
||||
|
||||
|
Re: pic: 1706 Aerial Assist Vision Solution Sample
we only used hot goal detection. the rest is still a work in progress. Our team has 3 programmers, we have plans to program for all the data we have, but again, it is only a plan. We have had game piece detection for 3 seasons now and have not used it on the machine control side. We're dwelling in making the switch to c++, which should attract more students than labview, but who knows. We are also interested in doing path planning and autonomously transversing across the field, but that may not happen. Matlab has given us licenses though....so we could port code over to c.
|
|
#6
|
||||
|
||||
|
Re: pic: 1706 Aerial Assist Vision Solution Sample
In May I plan to release a white paper about FRC Tele-Operated HMI that you may be interested in.
It seems we have the opposite problem you have - we know how to acquire & use the vision data in tele-operated, and we have plenty of it - but getting a simple message back to the robot seems to be our Achilles heel . The programmers worked out the issues on the test platform before we packed everything up last weekend, but we'll see what happens at Champs on the real robot. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|