[Radiance-general] Strange gendaylit behavior

[David Appelfeld]

Hi Rob,
by using your command I am getting error to, but slightly different.

David$ gendaylit 7 19 19:00:00 -a 39.740000000000002 -o -105.18000000000001
-m -105.0 -L 0.0 1926.55187439894
# gendaylit 7 19 19:00:00 -a 39.740000000000002 -o -105.18000000000001 -m
-105.0 -L 0.0 1926.55187439894
Illegal instruction: 4

Is there any reason by using 0.0 as direct normal illuminance after -l
option. By using 0.00000000001 daylight works. I am not sure if this is what
you are looking for.


I am also getting same error "Illegal instruction: 4" when calling gendaylit
by full path.

# gendaylit 7 19 19:00:00 -a 39.740000000000002 -o -105.18000000000001 -m
-105.0 -L 0.00000000000001 1926.55187439894
# Ground ambient level: 4.7

void light solar
0
0
3 8.220e-13 8.220e-13 8.220e-13

solar source sun
0
0
4 -0.907109 0.416674 0.059465 0.533000

void brightfunc skyfunc
2 skybright perezlum.cal
0
10 1.164e+01 9.485e-01 -0.836705 -0.013368 15.728716 -4.116213 1.003109
-0.907109 0.416674 0.059465



David




On 7 October 2011 15:42, Rob Guglielmetti <rob.guglielmetti at gmail.com>wrote:

> I probably have an odd configuration on my machine, but I'm having trouble
> diagnosing this problem.
>
> If I call gendaylit with these parameters, I get junk in the output sky
> description:
>
> rgugliel$ gendaylit 7 19 19:00:00 -a 39.740000000000002 -o
> -105.18000000000001 -m -105.0 -L 0.0 1926.55187439894
> # gendaylit 7 19 19:00:00 -a 39.740000000000002 -o -105.18000000000001 -m
> -105.0 -L 0.0 1926.55187439894
> # Ground ambient level: nan
>
> void brightfunc skyfunc
> 2 skybright perezlum.cal
> 0
> 10 nan nan nan nan nan nan nan -0.907109 0.416674 0.059465
>
> OK, so where is my gendaylit?
>
> which gendaylit
> /usr/local/bin/gendaylit
>
> OK, so if I call that specific executable, I get this:
>
> rgugliel$ /usr/local/bin/gendaylit 7 19 19:00:00 -a 39.740000000000002 -o
> -105.18000000000001 -m -105.0 -L 0.0 1926.55187439894
> # /usr/local/bin/gendaylit 7 19 19:00:00 -a 39.740000000000002 -o
> -105.18000000000001 -m -105.0 -L 0.0 1926.55187439894
> Warning : skyclearness or skybrightness out of range ;
>  Check your input parameters
> Warning : skyclearness or skybrightness out of range ;
>  Check your input parameters
> Warning : skyclearness or skybrightness out of range ;
>  Check your input parameters
> Warning : skyclearness or skybrightness out of range ;
>  Check your input parameters
> sky clearness or sky brightness out of range 1.000000
>  74434650220083800562091791272162503847257343566676277805826026351882917179884747180439543170910077023728890544527980267722524523537281630301534426272391252609311406925055899551665934885241866457242010167443382973430564036426324486211258871034413056.000000
>
> which is much more useful, because those STERR warnings I can check for and
> use an alternative sky generation method for that timestep, or double check
> input parameters. The former method slips past my gendaylit STERR checks and
> then oconv barfs on that bogus sky description.
>
> I don't THINK I have any other copies of gendaylit lying around, certainly
> not in my path, but it appears that either gendaylit behaves differently
> when called with a full path (unlikely) or I have something else going on. I
> have lost many hairs today grinding on this. This is stupid. Please help.
>
> - Rob
>
> _______________________________________________
> 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/20111007/a4ace39b/attachment.html>