-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fix for FindSpan #24
base: main
Are you sure you want to change the base?
Fix for FindSpan #24
Conversation
FindSpan would fail when the first altitude was less than the target altitude. Fix by starting the loop at altitude index 1 instead of 0.
Hey - do you have a testcase that can reproduce the problem? Thanks - |
Yeah, I think if you select M 31 as the target, let the coordinates populate, set the date to 3/5/2023, and the number of days to 7, and click on the button for the daily report, you should see the exception in the log, and no output on the plug-in page. (sorry if the terminology is inaccurate, I’m not at my computer right now) I believe I also tried the date 12/15/2022 with the same M 31 target and got the same results. Oh, and latitude and longitude were somewhere in the northern hemisphere. I’ll have to check what it was exactly this evening. I just got the coordinates from the ASCOM telescope simulator. |
M31 on March 5 is working for me. Please send me your lat/long (you can
fudge the least significant digits for privacy) as well as a screenshot of
the Target Planning options that are set. Also send the exception - thanks.
- Tom
…On Mon, Mar 6, 2023 at 4:49 PM Carl Svensson ***@***.***> wrote:
Yeah, I think if you select M 31 as the target, let the coordinates
populate, set the date to 3/5/2023, and the number of days to 7, and click
on the button for the daily report, you should see the exception in the
log, and no output on the plug-in page. (sorry if the terminology is
inaccurate, I’m not at my computer right now)
I believe I also tried the date 12/15/2022 with the same M 31 target and
got the same results. Oh, and latitude and longitude were somewhere in the
northern hemisphere. I’ll have to check what it was exactly this evening. I
just got the coordinates from the ASCOM telescope simulator.
—
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACBBCI7F5CRAOFJT36SXBZLW2ZLWNANCNFSM6AAAAAAVQLARWQ>
.
You are receiving this because you commented.Message ID: <tcpalmer/nina.
***@***.***>
|
Here's some more details: lat: 51.079 Here's the text of the exception:
Attached is a screenshot of my other TargetPlanning settings: Click 'Daily Details' to reproduce. This was on NINA 3.0.0.1015-nightly |
FindSpan would fail when the first altitude was less than the target altitude. Fix by starting the loop at altitude index 1 instead of 0.