[Radiance-general] Gendaylit- bad sky description (John Ford)

[John Ford]

Wendelin, 

Thanks for your response. I've tried the new gendaylit and am getting the same results, below.

$ gendaylit 2 1 8.5 -a -20.27 -o -148.73 -m -150 -W 1031 44
# gendaylit 2 1 8.5 -a -20.27 -o -148.73 -m -150 -W 1031 44
sky clearness or sky brightness out of range 13.563423	 0.052832

john at relume.com.au
0411 519 738
Relume Consulting



On 02/02/2013, at 2:03 AM, Wendelin.Sprenger at ise.fraunhofer.de wrote:

> Dear John, 
> 
> to my knowledge, the Perez model only works in a limited range for the sky clearness and brightness; at least gendaylit does. In the new version of gendaylit that has been announced yesterday, the sky clearness and brightness values are set to the border values in your case, and the output is still calculated. Therefore, the octree can still be created and used for this time step, without the bash script being aborted ("bad sky description"). The warning messages are still directed to stdout as long as the -w option is not set. 
> 
> My guess is a wrong combination of high direct-normal irradiance values and the defined point of time. Do you apply hourly irradiance values? Does the problem still exist if you change the calculation to 10-minute values? Maybe you can recalculate your weather files with the Skartveit-Olseth method (Meteonorm, for example, provides this option.) 
> 
> Cheers, 
> Wendelin 
> 
> 
> _______________________________________________
> Radiance-general mailing list
> Radiance-general at radiance-online.org
> http://www.radiance-online.org/mailman/listinfo/radiance-general

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.radiance-online.org/pipermail/radiance-general/attachments/20130203/94ac51d4/attachment.html>