# Difference between revisions of "R.sun"

From GRASS-Wiki

(use r.horizon) |
HamishBowman (talk | contribs) (→Tips: example link) |
||

Line 5: | Line 5: | ||

== Tips == | == Tips == | ||

− | The speed of r.sun is much higher if {{cmd|r.horizon}} is used first and the resulting maps are given as input to r.sun. Background: the horizon needs to be computed only one time before, not in every step within r.sun. | + | The speed of r.sun is much higher if {{cmd|r.horizon}} is used first and the resulting maps are given as input to r.sun. Background: the horizon needs to be computed only one time before, not in every step within r.sun. See the example at the end of the {{cmd|r.sun}} help page. |

=== Testing === | === Testing === |

## Revision as of 03:25, 20 May 2009

## Contents

## Help page

- r.sun manual page

## Tips

The speed of r.sun is much higher if r.horizon is used first and the resulting maps are given as input to r.sun. Background: the horizon needs to be computed only one time before, not in every step within r.sun. See the example at the end of the r.sun help page.

### Testing

Create an artificial surface containing a Gaussian mound:

```
r.surf.volcano out=gauss method=gaussian kurtosis=1
```

### Time step

The following three images demonstrate the effects of using different time **step** parameters.

r.sun -s elevin="gauss" glob_rad="rad.global.30minT" day=180 step=0.5

r.sun -s elevin="gauss" glob_rad="rad.global.15minT" day=180 step=0.25

r.sun -s elevin="gauss" glob_rad="rad.global.03minT" day=180 step=0.05

The 3 minute time step takes roughly ten times as long to run as the 30 minute timestep.