-s option not working properly #2
Comments
|
Yes, you are right. I tried with -s60m, -s6m, -s6y and all of them didn't work. All of them gave days wise result instead. I have reported this problem to Astrodienst. Hope they will respond soon and thank you for reporting this issue. |
|
Hi Mukesh,
Thank you for the quick reply.
Interestingly this options works fine when I try it on the Swiss Ephemeris
test page!
How can that be?
http://www.astro.com/swisseph/swetest.htm
Paul
…On Sun, May 13, 2018 at 11:23 AM Mukesh Chapagain ***@***.***> wrote:
Yes, you are right. I tried with -s60m, -s6m, -s6y and all of them didn't
work. All of them gives days wise result instead. I have reported this
problem to Astrodienst. Hope they will respond soon and thank you for
reporting this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMsKzmjIyOMMBREWZKRhU3d0s2p7FHoWks5tyF4QgaJpZM4T8owY>
.
|
|
*This could be a version issue. Are you using the latest version of
swetest?*
*I found this on the forum:*
Thoma, the issue had already been resolved. Charles had used an older
version of swetest, these options work only since version 2.05.01
…-sN timestep N days, default 1. This option is only meaningful
when combined with option -n.
If an 'y' is appended, the time step is in years instead of days,
for example -s10y for a time step of 10 years.
If an 'mo' is appended, the time step is in months instead of days,
for example -s3mo for a time step of 3 months.
If an 'm' is appended, the time step is in minutes instead of days,
for example -s15m for a time step of 15 minutes.
If an 's' is appended, the time step is in seconds instead of days,
for example -s1s for a time step of 1 second.
On Sun, May 13, 2018 at 11:23 AM Mukesh Chapagain ***@***.***> wrote:
Yes, you are right. I tried with -s60m, -s6m, -s6y and all of them didn't
work. All of them gives days wise result instead. I have reported this
problem to Astrodienst. Hope they will respond soon and thank you for
reporting this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMsKzmjIyOMMBREWZKRhU3d0s2p7FHoWks5tyF4QgaJpZM4T8owY>
.
|
|
I downloaded the "swetest" exectuable file from http://www.astro.com/ftp/swisseph/src/ and updated it with the one present in this repo. But, still the same issue. Can you try at your end as well? |
|
I did the same and it's working fine with the swetest.exe I downloaded
directly from the astro.com site.
…On Tue, May 15, 2018 at 11:39 PM Mukesh Chapagain ***@***.***> wrote:
I downloaded the "swetest" exectuable file from
http://www.astro.com/ftp/swisseph/src/ and updated it with the one
present in this repo. But, still the same issue. Can you try at your end as
well?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMsKzmkZA2D5-WPhj1loPraBJIlx6DKCks5ty62YgaJpZM4T8owY>
.
|
|
Hi Mukesh,
Same here. I tried the one on their site (swetest) and it's not working
either.
So this means that the problem is on their side.
However is does work when I use (locally) the swetest.exe file compiled for
Windows.
Did you get any reply from you communication with them yet?
…On Tue, May 15, 2018 at 11:39 PM Mukesh Chapagain ***@***.***> wrote:
I downloaded the "swetest" exectuable file from
http://www.astro.com/ftp/swisseph/src/ and updated it with the one
present in this repo. But, still the same issue. Can you try at your end as
well?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMsKzmkZA2D5-WPhj1loPraBJIlx6DKCks5ty62YgaJpZM4T8owY>
.
|
|
Hi Paul, I have not received any reply from astro.com of my email to them regarding this issue. Today, I have also submitted a question in their forum: https://forum.astro.com/cgi/forum.cgi?num=1527060442 Hope to get some replies there. |
|
Mukesh,
I just got a response from them.
They claim that we are using a older version because these options were not
in the older version.
I will let you know when I learn more.
…On Wed, May 23, 2018 at 2:29 AM Mukesh Chapagain ***@***.***> wrote:
Hi Paul,
I have not received any reply from astro.com for my email to them
regarding this issue.
Today, I have also submitted a question in their forum:
https://forum.astro.com/cgi/forum.cgi?num=1527060442
Hope to get some reply there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMsKzr5_4fXWLzY3zYs7ha_MfG240wWjks5t1Q_HgaJpZM4T8owY>
.
|
|
It didn't work for me either.
I found one that works here:
https://github.com/cyjoelchen/php-sweph
…On Tue, May 15, 2018 at 11:39 PM Mukesh Chapagain ***@***.***> wrote:
I downloaded the "swetest" exectuable file from
http://www.astro.com/ftp/swisseph/src/ and updated it with the one
present in this repo. But, still the same issue. Can you try at your end as
well?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMsKzmkZA2D5-WPhj1loPraBJIlx6DKCks5ty62YgaJpZM4T8owY>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am not having any success using the -s option with minutes or other time modifiers.
Example: -n10 -s60m
This should generate 10 outputs separated by 60 minutes in time. The "m" modifier has no effect. Instead I get 10 outputs separated by 60 days instead of 60 minutes. The program ignores the m or any of the other letters after the number. The other options like s, mo and y (for seconds, months, years) don't work either.
The text was updated successfully, but these errors were encountered: