~kennylevinsen/wlsunset-devel

5 2

-s/-S/-d options do not work as expected

Details
Message ID
<e52dbe59-07ed-da2e-b4c8-39b73949da88@gmail.com>
DKIM signature
missing
Download raw message
I run wlsunset as `wlsunset -S 6:00 -s 20:00 -d 3600 -t 2800`, I even 
tried changing it to `-S 4:00`, but no matter what I do, in the morning 
the colour temperature change persists until 10:00 and then changes to 
normal suddenly without any transition. Why could it be?
Details
Message ID
<BK09BR.X1HE0DEFRMB22@kl.wtf>
In-Reply-To
<e52dbe59-07ed-da2e-b4c8-39b73949da88@gmail.com> (view parent)
DKIM signature
missing
Download raw message
This could be a timezone issue. Can you try to input the time as UTC?

wlsunset operates entirely in UTC internally to normalize time against 
orbit calculations, but as a side-effect the manual time input is 
currently also UTC. It's a little annoying to fix in a portable way 
(i.e. works both on Linux and FreeBSD), so I haven't looked at it yet.
Details
Message ID
<d721ce70-4ca0-4176-cf06-b2b897f9ad24@gmail.com>
In-Reply-To
<BK09BR.X1HE0DEFRMB22@kl.wtf> (view parent)
DKIM signature
missing
Download raw message
How to input the time as UTC? Is there some kind of format to input a 
timezone with the time?

On 02/05/2022 19.19, Kenny Levinsen wrote:
> This could be a timezone issue. Can you try to input the time as UTC?
>
> wlsunset operates entirely in UTC internally to normalize time against 
> orbit calculations, but as a side-effect the manual time input is 
> currently also UTC. It's a little annoying to fix in a portable way 
> (i.e. works both on Linux and FreeBSD), so I haven't looked at it yet.
>
>
Details
Message ID
<R789BR.8G43F6OODKMS3@kl.wtf>
In-Reply-To
<d721ce70-4ca0-4176-cf06-b2b897f9ad24@gmail.com> (view parent)
DKIM signature
missing
Download raw message
Just specify what the time would be in UTC-land - if you want sunrise 
at 6AM your time, and you're in UTC+4, you say 2AM instead.

It's a little clumsy, but it'll take a bit before I have time to look 
at fixing the manual time input. Automatic calculation using 
latitude/longitude is the primary way to use wlsunset.
Details
Message ID
<b83fcff8-6629-b7be-a74d-ad0220712ce5@gmail.com>
In-Reply-To
<R789BR.8G43F6OODKMS3@kl.wtf> (view parent)
DKIM signature
missing
Download raw message
Nah, this doesn't work. At least sunset time is interpreted as a local 
time, that's for sure.

On 02/05/2022 22.04, Kenny Levinsen wrote:
> Just specify what the time would be in UTC-land - if you want sunrise 
> at 6AM your time, and you're in UTC+4, you say 2AM instead.
>
> It's a little clumsy, but it'll take a bit before I have time to look 
> at fixing the manual time input. Automatic calculation using 
> latitude/longitude is the primary way to use wlsunset.
>
>
Details
Message ID
<e49cdaeb-bdad-99d9-269d-a20790610d13@gmail.com>
In-Reply-To
<R789BR.8G43F6OODKMS3@kl.wtf> (view parent)
DKIM signature
missing
Download raw message
I started wlsunset yesterday with desirable for me -S and -s option 
values (by local time). At the specified time of sunset it started 
gradually decreasing the colour temperature until the calculated time of 
dusk. But at the calculated time of dawn happened as well as at the 
specified time of sunrise. Only at 10:00 it suddenly reverted the colour 
temperature back to normal, without any gradual change. I must say that 
I live in UTC+10 timezone, so my local 10:00 is UTC 0:00.

On 02/05/2022 22.04, Kenny Levinsen wrote:
> Just specify what the time would be in UTC-land - if you want sunrise 
> at 6AM your time, and you're in UTC+4, you say 2AM instead.
>
> It's a little clumsy, but it'll take a bit before I have time to look 
> at fixing the manual time input. Automatic calculation using 
> latitude/longitude is the primary way to use wlsunset.
>
>
Reply to thread Export thread (mbox)