....be forewarned that you don't just "use FPGAs".  They are a major=20
change from procedural thinking and will have a pretty steep learning=20
curve both in how they are used as well as very complex toolchains.  As=20
other posters have suggested, C++ on a new machine will get you a vast=20
speedup vs. Java.  I personally would suggest running your finished code=20
on multiple PCs (i.e. 'render farm') to get further speedups if needed,=20
or even 'in the cloud' before turning to FPGAs.

The exception would be if you can find a library+sample code for doing=20
image processing similar to what you need for CUDA or a FPGA.  Small=20
customizing steps from a demonstrated working system may not take too=20
long.  Cost-wise I expect one or even several new desktop PCs networked=20
together will be cheaper, and of course usable for things besides=20
highspeed image analysis.

J


> Yeah, for sure I'm going to be using C++ to program this at the very leas=
t.
> Also, if not CUDA, then I will be using FPGAs. Java was chosen by a frien=
d
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.