You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Thanks for the bug report.
Just so I understand: you only encounter this by calling into the solver code via those Python bindings, is that right? Ie, you have not hit this problem using solve-field?
(I'm trying to do the right thing and produce a failing test case or at least a demo before fixing the bug!)
thanks!
For very large fields (N > 1000), Astrometry.net runs into an out-of-bounds issue. This appears to be caused by the hard-coded capping of
numxy
inastrometry.net/solver/solver.c
Line 793 in 7fff04d
The limit is only applied to
numxy
, which means thatstartobj
orendobj
can become larger thannumxy
and trigger segfaults, for instance inastrometry.net/solver/solver.c
Line 879 in 7fff04d
I am happy to draft a PR, but I think that there are a few possible fixes:
startobj
andendobj
(The issue was first reported by @kevinss5, see neuromorphicsystems/astrometry#5).
The text was updated successfully, but these errors were encountered: