We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm working on a port of your great library to Dart https://github.com/shawnlauzon/meeus. While doing that, I noticed that one of my ported tests failed which seems correct. Both implementations generate the same JD: 2447442.3543003574. However, your test thinks that this is 1988 October 7, at 20ʰ30ᵐ TD, but in fact the time is 20:30:12. I have confirmed this with https://www.aavso.org/jd-calculator and it's the same result that my code produces.
My guess is that sexa.FmtTime is truncating the seconds part for this case, but I don't know why that would be.
The text was updated successfully, but these errors were encountered:
@soniakeys died a few years ago.
Sorry, something went wrong.
🥺 Wow, so sorry to hear that
No branches or pull requests
I'm working on a port of your great library to Dart https://github.com/shawnlauzon/meeus. While doing that, I noticed that one of my ported tests failed which seems correct. Both implementations generate the same JD: 2447442.3543003574. However, your test thinks that this is 1988 October 7, at 20ʰ30ᵐ TD, but in fact the time is 20:30:12. I have confirmed this with https://www.aavso.org/jd-calculator and it's the same result that my code produces.
My guess is that sexa.FmtTime is truncating the seconds part for this case, but I don't know why that would be.
The text was updated successfully, but these errors were encountered: