I think that's the best solution for the OpenCL code I'm working on.
However, with the normal code, computing the lat/long as needed may
take less time, RAM, and hard drive space then pre-computing it. So
either situation may be better, depending on how the code is run.
~Seth
On Jun 9, 2010, at 10:16 PM, Yann Chemin wrote:
to make things faster (and maybe more consistent), it may just be
better to have lat and long rasters as input to r.sun, instead of
repeatingly calling for a function to convert them.
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
