MisterHouse: Home Automation with Perl

Hi Max,

Max Lock wrote:
>  Hi Folks,
>
>  Bit of a weird one this. I live in the uk and have set the following 
> variables in mh.ini
>
> latitude  =  51.40
> longitude =  -1.26
> time_zone =  0
>   
For what it's worth, here's my settings from mh.private.ini:
# Category = Location
latitude=55.097
longitude=-1.586
time_zone=0
@ For $Time_Sunrise_Twilight and $Time_Sunset_Twilight.
@ In order of increasing brightness:  astronomical, nautical, or civil
twilight = civil

On my system (Fedora 9,  mh 2.104) these give:
Time Sunrise Twilight:  7:19 Time Sunrise:  8:02 Time Sunset:  15:46 
Time Sunset Twilight:  16:29
>  Now this gives me some odd sun times:
>
> Latitude: 51.40,  Longitude: -1.26,  Time Zone: 0
> sunrise=9:50 PM sunset=5:40 AM
> sunrise twilight=9:10 PM sunset twilight=6:20 AM
>
>  The TZ environment variable isn't set, and /etc/timezone is correct.
>
> root@...:~# cat /etc/timezone
> Europe/London
> root@...:~# env |grep TZ
> root@...:~#
>   
Neither are set on my Fedora system either.
>  Can anyone give me a pointer as to what to look at?
>   
Have you tried setting 'twilight = civil' in case a sane default value 
is not being set?

TTFN,

James
-- 
James Derrick    
    lists@..., Cramlington, England
    Beyond the Horizon of the place we lived when we were young,
    In a World of Magnets and Miracles. Pink Floyd.

Hi James,

 Yes, I've got twilight set to civil as well? I'm stumped.

 -Max

James Derrick wrote:
> Hi Max,
>
> Max Lock wrote:
>   
>>  Hi Folks,
>>
>>  Bit of a weird one this. I live in the uk and have set the following 
>> variables in mh.ini
>>
>> latitude  =  51.40
>> longitude =  -1.26
>> time_zone =  0
>>   
>>     
> For what it's worth, here's my settings from mh.private.ini:
> # Category = Location
> latitude=55.097
> longitude=-1.586
> time_zone=0
> @ For $Time_Sunrise_Twilight and $Time_Sunset_Twilight.
> @ In order of increasing brightness:  astronomical, nautical, or civil
> twilight = civil
>
> On my system (Fedora 9,  mh 2.104) these give:
> Time Sunrise Twilight:  7:19 Time Sunrise:  8:02 Time Sunset:  15:46 
> Time Sunset Twilight:  16:29
>   
>>  Now this gives me some odd sun times:
>>
>> Latitude: 51.40,  Longitude: -1.26,  Time Zone: 0
>> sunrise=9:50 PM sunset=5:40 AM
>> sunrise twilight=9:10 PM sunset twilight=6:20 AM
>>
>>  The TZ environment variable isn't set, and /etc/timezone is correct.
>>
>> root@...:~# cat /etc/timezone
>> Europe/London
>> root@...:~# env |grep TZ
>> root@...:~#
>>   
>>     
> Neither are set on my Fedora system either.
>   
>>  Can anyone give me a pointer as to what to look at?
>>   
>>     
> Have you tried setting 'twilight = civil' in case a sane default value 
> is not being set?
>
> TTFN,
>
> James
>

Hi Folks,

 OK so it seems the sine and cosine functions may be giving different 
results on different cpu architectures. I added a debug line to 
sun_time.pl at line 115 to dump all the variables. The problem seems to 
stem from the $P variable not being set correctly by these functions.

X86 - P 1.28772467070848
ARM - P -1.57038638775843

 I can't find anything via google about cpu specifics? any perl gurus 
here :)

 -Cheers Max.

On 2008/12/06 15:26, Max Lock wrote:
> Hi Folks,
> 
>  OK so it seems the sine and cosine functions may be giving different 
> results on different cpu architectures. I added a debug line to 
> sun_time.pl at line 115 to dump all the variables. The problem seems to 
> stem from the $P variable not being set correctly by these functions.
> 
> X86 - P 1.28772467070848
> ARM - P -1.57038638775843
> 
>  I can't find anything via google about cpu specifics? any perl gurus 
> here :)
> 
>  -Cheers Max.

This is (probably) not directly a Perl problem.  AFAICT, Perl gets its math
functions by linking against libm.  If so, you should see the same
misbehavior in any language that uses libm.  Try a simple test program in C
or Python or ... , and see what you get on your two machines.

You may need a patched libm for ARM and your version on Linux.

Mark