Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong Set #19

Open
bobybobybob opened this issue Feb 20, 2018 · 1 comment
Open

Wrong Set #19

bobybobybob opened this issue Feb 20, 2018 · 1 comment

Comments

@bobybobybob
Copy link

bobybobybob commented Feb 20, 2018

root@computer:/home/test# hwclock
2018-02-20 01:02:24.197261+0100

root@computer:/home/test# date
Tue Feb 20 01:02:25 CET 2018

root@computer:/home/test# calcelestial -m rise -p sun -q Frankfurt -H civil
06:53 20.02.2018

root@computer:/home/test# calcelestial -m transit -p sun -q Frankfurt -H civil
12:38 20.02.2018

root@computer:/home/test# calcelestial -m set -p sun -q Frankfurt -H civil
18:21 **19**.02.2018

Later Time

root@computer:~# hwclock
2018-02-20 15:35:31.606800+0100

root@computer:~# date
Tue Feb 20 15:35:31 CET 2018

root@computer:~# calcelestial -m rise -p sun -q Frankfurt -H civil
06:53 20.02.2018

root@computer:~# calcelestial -m transit -p sun -q Frankfurt -H civil
12:38 20.02.2018

root@computer:~# calcelestial -m set -p sun -q Frankfurt -H civil
18:23 20.02.2018

it is OK

@stv0g
Copy link
Owner

stv0g commented Jan 24, 2019

Probably the --next option is useful here?

  -n, --next		use rise, set, transit time of tomorrow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants