`df_sso=lc.query_solar_system_objects(cadence_mask='all')` Query Fail about lightkurve HOT 5 CLOSED

@RandomNewz Skybot service is functioning again. So the issue is resolved.

from lightkurve.

Hi there! 👋 Thank you for opening your first Lightkurve issue! 🙏 One of our maintainers will get back to you as soon as possible. 👩‍🚀 You can expect a response within 7 days. 📅 If you haven’t heard anything by then, feel free to ping this thread. 🛎️ We love that you are using Lightkurve and appreciate your feedback. 👍

from lightkurve.

There seems to some issue in the underlying Skybot service. I started experience it in late December 2023. E.g., if I use Skybot's web UI:
https://vo.imcce.fr/webservices/skybot/?forms

I cannot get any meaningful results either.

from lightkurve.

So, nothing can be done until the Skybot service gets fixed?

from lightkurve.

If the goal is to identify specific asteroids around the target of the lightcurve, I'm afraid I don't have any suggestion.

If the goal is to see if there are asteroids (or any type of background events) that contaminate a lightcurve, there are ways without using Skybot (identifying specific asteroids).

1. one can inspect the background, in SAP_BKG for TESS SPOC lightcurves, to identify dips in lightcurves due to spikes in the background (often due to asteroids passing through).

lc = lc.truncate(3256.1, 3256.4)  # zoom-in to the relevant time
lc.scatter();
lc.select_flux("sap_bkg").scatter(label="sap_bkg");

2. If TargetPixelFile is available, one can inspect the lightcurve at per-pixel level with tpf.plot_pixels() function. The trajectory of an asteroid can often be seen visually:

from lightkurve.