I have a notebook with T7200 Intel CPU and r.sun completes
one day's calculation between 3-4 mins(with linke turbidity raster
and shadowing, step = 1). I want to run r.sun with step=0.5 in a
large scale and detailed area.
So, I need to reduce the calculation time for calculating 365 day data.
Could you give me advices about hardware for reducing
calculation time?
24 hours to complete isn't so bad
suggestion: to take advantage of dual processor split up operations and
(if running linux) run two concurrent mapsets for day 0-180 and 181-365.
then when done use g.mapsets to add second mapset to first's search path.
buraq wrote:
> I have a notebook with T7200 Intel CPU and r.sun completes
> one day's calculation between 3-4 mins(with linke turbidity raster
> and shadowing, step = 1). I want to run r.sun with step=0.5 in a
> large scale and detailed area.
> So, I need to reduce the calculation time for calculating 365 day data.
> Could you give me advices about hardware for reducing
> calculation time?
24 hours to complete isn't so bad
suggestion: to take advantage of dual processor split up operations and
(if running linux) run two concurrent mapsets for day 0-180 and 181-365.
then when done use g.mapsets to add second mapset to first's search path.
in the past I (and colleagues) have used r.sun(2) to get the job done
(estimations of global rad over a "small" study area in central greece). Now
we are re-doing this for another (smaller) study area but for a larger period
of time.
If you have no objections, we would like to have that ".pdf"
Cheers, Nikos
