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

Unexpected behavior at certain radius values for astroquery.imcce.Skybot.cone_search #3119

Open
emersonwhittaker1 opened this issue Oct 14, 2024 · 3 comments
Labels

Comments

@emersonwhittaker1
Copy link

When I use this set of coordinates at this time I get an empty result for one radius:

from astroquery.imcce import Skybot
from astropy.time import Time
from astropy.coordinates import SkyCoord
import astropy.units as u
epoch = Time('55362.69789455', format='mjd')
field = SkyCoord(180.16294575*u.deg, 0.04415185*u.deg)
Skybot.cone_search(field, 19.789250330604407*u.arcmin, epoch, get_raw_response=True, find_asteroids=True)

result: # Flag: -1\n# Ticket: 181292695259995135\nSkyBoT comet conesearch -> MySQL server (asterws3.imcce.fr): \n

But a non-empty result for the following marginally smaller radius:

Skybot.cone_search(field, 19.78925033060440*u.arcmin, epoch, get_raw_response=True, find_asteroids=True)

result: # Flag: 1\n# Ticket: 181292699247551035\n# Num | Name | RA(h) | DE(deg) | Class | Mv | Err(arcsec) | d(arcsec) | dRA(arcsec/h) | dDEC(arcsec/h) | Dg(ua) | Dh(ua) | Phase(deg) | SunElong(deg) | x(au) | y(au) | z(au) | vx(au/d) | vy(au/d) | vz(au/d) | Ref. Epoch(JD) \n 397879 | 2008 UC100 | 12 00 31.7111 | +00 03 45.841 | MB>Inner | 23.4 | 2.017 | 129.546 | 22.1342 | -9.885 | 2.40648073312 | 2.70744509418 | 21.95 | 95.76 | -2.518461043 | -0.907950204 | -0.388408409 | 0.003630443 | -0.007884952 | -0.003471052 | 2455360 \n ... etc.

There seems to be no correlation with number of decimal places or with the size of the radius value in determining what breaks the code. This may be an issue with SkyBot itself, I am not sure.

@keflavich
Copy link
Contributor

@mommermi, do you have any idea about this one?

@bsipocz
Copy link
Member

bsipocz commented Jan 13, 2025

cc @mkelley

@mkelley
Copy link
Contributor

mkelley commented Jan 13, 2025

@emersonwhittaker1 I just tried this myself by copy-pasting your example and found the two to be identical except for the "Ticket" portion:

>>> a = Skybot.cone_search(field, 19.789250330604407*u.arcmin, epoch, get_raw_response=True, find_asteroids=True)
>>> b = Skybot.cone_search(field, 19.78925033060440*u.arcmin, epoch, get_raw_response=True, find_asteroids=True)
>>> a.splitlines()[2:] == b.splitlines()[2:]
True

Can you clear your cache and try again? Skybot.clear_cache() Are they still different?

Also, if it helps to debug, I think one can get the URL after a running query from the Skybot object via Skybot.uri Then you can see exactly what was sent to the IMCCE to help determine if it is an Skybot-astroquery or Skybot-IMCCE issue.

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

No branches or pull requests

4 participants