174
edits
Line 53: | Line 53: | ||
* Too many questions marks? | * Too many questions marks? | ||
====Things to investigate==== | ====Things to investigate now==== | ||
* Rosjava - http://code.google.com/p/rosjava/ | * Rosjava - http://code.google.com/p/rosjava/ | ||
*I'm currently trying to figure out how easy/quick it would be to create a 1D depth map from a slice of video from an android phone. For doing mapping/navigation e.g. SLAM for a robot. It could probably do with a LED light as well to illuminate and create areas of contrast. For 2D stuff it seems like people detect features such as corners. For 1D stuff detecting edges and gradients should suffice. And be easy-ish. It might be possible to use orientation from the phone as information on which direction to look. Feature extraction would be parallel, feature comparison would be serial. | |||
====Things to investigate later==== | |||
* Integration with Kinnect? Probably need a rooted tablet | |||
* RenderScript - http://developer.android.com/guide/topics/renderscript/index.html OpenCL alternative available now? Ziilabs has opencl running. Renderscript seems to be nicer in that it allocates jobs to cores at run time (rather than fixing them) so can use multi-core as well as GPU but it can't currently use GPU even in ICS. It depends how long it takes Google to implement renderscript vs opencl. Ziilabs only does opencl for their chips I think.... | * RenderScript - http://developer.android.com/guide/topics/renderscript/index.html OpenCL alternative available now? Ziilabs has opencl running. Renderscript seems to be nicer in that it allocates jobs to cores at run time (rather than fixing them) so can use multi-core as well as GPU but it can't currently use GPU even in ICS. It depends how long it takes Google to implement renderscript vs opencl. Ziilabs only does opencl for their chips I think.... | ||
==Work in progress tutorial on inkscape== | ==Work in progress tutorial on inkscape== |
edits