Closed JosephKarpinski closed 2 years ago
More examples of missing targets:
'K2-315','K2-316','K2-317','K2-318','K2-319','K2-320', 'K2-321','K2-322','K2-323','K2-324','K2-325','K2-326', 'K2-331','K2-332','K2-333','K2-334','K2-335','K2-336','K2-337','K2-338','K2-339', 'K2-340','K2-341','K2-342','K2-343','K2-344','K2-345','K2-346','K2-347','K2-348','K2-349', 'K2-350','K2-351','K2-352','K2-352','K2-352','K2-353','K2-354','K2-355','K2-356','K2-357','K2-358',
Feels like this is a refresh issue on your part, that lightkurve is not picking up latest target updates.
It uses MAST name resolver, which relies on Simbad and NED to turn names into coordinates. Kepler-1700 doesn't resolve by Simbad, thus it doesn't resolve in MAST, thus it doesn't resolve in lightkurve. If you know the KIC ID, all of those will resolve because "KIC xyz" uses the Kepler Input Catalog at MAST to translate it into a coordinate. The "Kepler-xyz" identifiers are assigned by NExScI and thus aren't maintained by MAST.
@scfleming Do you reckon we ought to open a ticket with Nexsci and/or Simbad?
Based on a few spot checks, I have the impression that each of the planets listed above have a recent discovery publication (published within the past ~year), so they are likely in the queue for Simbad to ingest.
(@JosephKarpinski Thank you for posting the examples!)
Would not be a bad idea to understand their plans on updates for IDs like these!
Ok! I went ahead and submitted an exoplanet archive ticket pointing to this issue.
I'm going to close the issue here because no change to Lightkurve is required, but anyone should feel free to re-open this issue and/or post updates below as needed!
It would be nice to be able to explore all the exoplanets currently listed in the below catalog with lightkurve
http://openexoplanetcatalogue.com/systems/
Thanks,
Joseph Karpinski
Sent from my iPhone
On Nov 8, 2021, at 12:17 PM, Geert Barentsen @.***> wrote:
Closed #1156https://github.com/lightkurve/lightkurve/issues/1156.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/lightkurve/lightkurve/issues/1156#event-5584462823, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI3HMIDKRSHEGC2IQH3BM73ULAA4HANCNFSM5HQ64BMQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Problem description
I'm not sure where lightkurve resolves its targets from but all these Kepler targets don't resolve:
'Kepler-1663','Kepler-1664','Kepler-1665','Kepler-1666','Kepler-1667','Kepler-1668','Kepler-1669', 'Kepler-1670','Kepler-1671','Kepler-1672','Kepler-1673','Kepler-1674','Kepler-1675','Kepler-1676','Kepler-1677','Kepler-1678','Kepler-1679', 'Kepler-1680','Kepler-1681','Kepler-1682','Kepler-1683','Kepler-1684','Kepler-1685','Kepler-1686','Kepler-1687','Kepler-1688','Kepler-1689', 'Kepler-1690','Kepler-1691','Kepler-1692','Kepler-1693','Kepler-1694','Kepler-1695','Kepler-1696','Kepler-1697','Kepler-1698','Kepler-1699', 'Kepler-1700','Kepler-1701','Kepler-1702','Kepler-1704',
There are also other target categories besides "Kepler" that do not resolve. Kepler are the easiest to show the issue with.
Example
Print a list of all target entries
target1 = "Kepler-1700"
print("Target: " + str(target1)) search_result = lk.search_lightcurve(target1) print(search_result) print("\n")