Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Programming (http://www.chiefdelphi.com/forums/forumdisplay.php?f=51)
-   -   Is the crio powerful enough? (http://www.chiefdelphi.com/forums/showthread.php?t=86470)

JamesBrown 04-08-2010 08:29

Re: Is the crio powerful enough?
 
Quote:

Originally Posted by PAR_WIG1350 (Post 970842)
I love trig:D

team 1350 used binocular vision in 2006 somewhat successfully, I wasn't there to get the specifics, but it used 2 CMUcams and trig, and that was with the old IFI rc, assuming there is a target that can be easily picked up at a low resolution, and the servos controlling the cameras are accurate enough (the closer the object, the less acurate they need to be), it should be *relatively simple. Streamlining the rest of the code to free up memory should also help.

Hint, research "boids", it could help with programing how to react to other robots.

If memory serves, you guys also used a Gumstix as a Co-Processor to handle the stereo vision. I dont think the old controller could handle two CMU cams very well.

Nadav Zingerman 04-08-2010 10:44

Re: Is the crio powerful enough?
 
The cRIO is powerful enough so that a few trig functions make absolutely no difference. We used a couple dozen of them for our drive routine with no noticeable slow-down at all. Using them in the vision routine should be no different. The main thing that will be slow is image processing, which is mostly affected by the camera resolution.

In addition, I imagine that the existing trig functions are already highly optimized for real-time applications, as that's what the cRIO is for. The cRIO has a floating point processor, so that should work pretty well.

Also, in my experience, one camera is good enough for range finding, provided you know the physical dimensions of the target, which has been the case in the last few games.

EricVanWyk 04-08-2010 12:37

Re: Is the crio powerful enough?
 
This conversation is focusing way too much on the cost of the trig functions, compared to the cost of the vision functions. Trig is a lot more expensive than addition and subtraction, but trivial compared to vision.

kamocat 04-08-2010 15:47

Re: Is the crio powerful enough?
 
In summary:
Yes, the cRIO is powerful enough for trig functions.
No, the cRIO is not powerful enough for stereo image processing at 60hz, without reprogramming the FPGA.

Ether 04-08-2010 19:51

Re: Is the crio powerful enough?
 
On a 3.4GHz Pentium D, the sin() function is about 3 times slower than a 3rd degree polynomial approximation.

But since we're only talking 0.3 microseconds for the sin() function, it's not to worry. Anybody have numbers for the cRIO, just curious?

biojae 04-08-2010 20:07

Re: Is the crio powerful enough?
 
Which vision target are you designing for?
Green light (2005 - 2007) / Pink and green (2009)
Concentric ellipses

If it is the first one then the cRio might be able to process it.
The thresholding operations take much less processing power.

Are you trying to use stereoscopic vision techniques, or just triangulation?

EricVanWyk 04-08-2010 20:14

Re: Is the crio powerful enough?
 
Quote:

Originally Posted by Ether (Post 970905)
On a 3.4GHz Pentium D, the sin() function is about 3 times slower than a 3rd degree polynomial approximation.

But since we're only talking 0.3 microseconds for the sin() function, it's not to worry. Anybody have numbers for the cRIO, just curious?

Ether -

How did you measure 0.3 microseconds?

I recently wrote a sin function that runs in ~0.7 microseconds on an 80MHz Arm Cortex-M3, with comparable accuracy.

davidthefat 04-08-2010 20:20

Re: Is the crio powerful enough?
 
Quote:

Originally Posted by biojae (Post 970906)
Which vision target are you designing for?
Green light (2005 - 2007) / Pink and green (2009)
Concentric ellipses

If it is the first one then the cRio might be able to process it.
The thresholding operations take much less processing power.

Are you trying to use stereoscopic vision techniques, or just triangulation?

The target is any target really, its not specific targets, but just an object that has similar colors. I will go further and do object identification, but I am not thinking that far ahead, Its just alot easier to use an IR Rangefinder and probably more accurate, but I want it to be actually useful. Also 3d mapping is one idea I have in my head

PAR_WIG1350 05-08-2010 00:22

Re: Is the crio powerful enough?
 
Quote:

Originally Posted by EricVanWyk (Post 970907)
Ether -
How did you measure 0.3 microseconds?

you don't, you just perform the same operation a few million times and divide.:)

kamocat 05-08-2010 01:31

Re: Is the crio powerful enough?
 
Quote:

Originally Posted by PAR_WIG1350 (Post 970922)
you don't, you just perform the same operation a few million times and divide.:)

I don't suppose there's any reason to perform it with changing input values, is there? Computers take just as long to multiply 0x0 as they do 57x291, correct?

Just in case, I used a random-number generator. (This prevents LabVIEW from compiling the results as constants in the program)


It took about 0.000492ms per iteration of the sine function, measured over a million iterations. To put it on the same scale as Ether's measurement, that's 0.5 microseconds.

biojae 05-08-2010 02:05

Re: Is the crio powerful enough?
 
Like what was said previously, the trig is not going to be a problem instead its the vision proc.

The triangulation tracking won't take much more processing then 2 *(current load for 1 camera + pointing).

However, a 3d disparity map for stereo optics will take the load of the previous as well as the load of the calculations to make the map and then find a target and distance.

Here is a whitepaper on stereo optics
http://www.cse.unr.edu/~bebis/CS791E...ereoCamera.pdf

EricVanWyk 05-08-2010 08:54

Re: Is the crio powerful enough?
 
Quote:

Originally Posted by kamocat (Post 970926)
I don't suppose there's any reason to perform it with changing input values, is there? Computers take just as long to multiply 0x0 as they do 57x291, correct?

Actually, that isn't always true. For example, the Cortex-M3 multiply timing follows:
32 bits x 32 bits = 32 bits is always one cycle
32b x 32b = 64b takes 3 cycles if the result is small
32b x 32b = 64b takes 5 cycles if the result is big

Also, it is relatively common for functions to bail early for special values, such as 0. For example, my sine function bails in less than half of the usual execution time if the input is a multiple of 45 degrees.

Quote:

Originally Posted by kamocat (Post 970926)

Just in case, I used a random-number generator. (This prevents LabVIEW from compiling the results as constants in the program)


It took about 0.000492ms per iteration of the sine function, measured over a million iterations. To put it on the same scale as Ether's measurement, that's 0.5 microseconds.

Thanks!

davidthefat 05-08-2010 18:55

Re: Is the crio powerful enough?
 
I was not very aware of FPGAs, so I read up on them; essentially FPGAs are processors that are highly customizable to fit specific functions? So do FPGAs need to be configured hardwarely before it can be programmed? Is the cRio a type of FPGA? If not, which FPGA is a suitable FPGA for the purpose of image processing? Also would the FPGAs be used primarily to capture the images or process the images? Regarding cameras, would they need to be directly communicating with the FPGA, like the middle man, or would the cameras be communicating with the cRio? If the cameras were to be communicating with the cRio, would a Ethernet network cable splitter suffice? Would the cameras show up as two separate cameras or would the set up just fail?

kamocat 05-08-2010 19:59

Re: Is the crio powerful enough?
 
An FPGA is not a processor. It does not have to work with only four bytes at a time. It doesn't have to grab data from a register, manipulate it, and then put it somewhere else in memory; it can just process the data continuously. It runs in parallel, like analog hardware. Think of it as a million operational amplifiers you can connect in whatever pattern you like, but instead of having to remanufacture it each time, you can reconfigure it electronically. In truth, it actually loads its configuration from non-volatile memory each time it is turned on, as opposed to it being burned in like a CD.

On the cRIO, there is a processor and an FPGA. I'm not sure about the ethernet or RS232, but I know that every one of the eight modules goes through the FPGA to get to the processor. For example, a small part of our FPGA is programmed as an accumulator for the gyro, to integrate degrees/second into absolute degrees. The FPGA is also used to improve the performance of the processor by acquiring data so that interrupts are rarely necessary; when the processor requests an input, the data is right there.

Now, as to how to get access to the FPGA: We aren't given the LabVIEW FPGA module in FRC. That's because
  1. It's believed to be too difficult for highschoolers in 6 weeks.
  2. It contains the system watchdog, and FIRST would be worried about safety hazards if it is disabled.
  3. It is a very valuble product of National Instruments, and it's a lot of what prevents loss of profit through piracy of the software we get for free. If we were to buy this software and a cRIO, it would be around $8,000 (single license).
Now, with that said, if you download a trial of LabVIEW, you have 30 days to play with it. LabVIEW 2010 just came out yesterday. It is common to have multiple versions of LabVIEW on a single computer without conflict, but if you like, feel free to back it up. After the 30 days, you license will expire, but your code will still be functional if it is deployed. If you'd like to use your code in LabVIEW 8.6, make sure to back-save it so that you can open it with the earlier version of LabVIEW.
When you'd like to use the cRIO for FIRST again, you will have to re-image.

Ether 05-08-2010 20:02

Re: Is the crio powerful enough?
 
Quote:

Originally Posted by EricVanWyk (Post 970907)
Ether -
How did you measure 0.3 microseconds?

First thing I did was to make a FreeDOS boot disk and boot that so I could access the hardware directly. Then I programmed the 8254 PIT to time 100 calcs of each (plus an empty loop so I could subtract out overhead).

~


All times are GMT -5. The time now is 23:12.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi