inconsistency in search_targetpixelfile (some cases)

Problem description

Given coordinates, the result of search_targetpixelfile will be reported including TIC ID matches. When one of TIC ID reported is supplied in the search_targetpixelfile, the tpf cannot be searched instead.

Example

import lightkurve as lk
from astropy.coordinates import SkyCoord

ra, dec = 47.0935, -60.1725
c = SkyCoord(ra=ra,dec=dec,unit='deg')
res = lk.search_targetpixelfile(c, mission='TESS')

SearchResult containing 2 data products.

target_name                     productFilename                        description     distance
----------- ------------------------------------------------------- ------------------ --------
  220571983 tess2018234235059-s0002-0000000220571983-0121-s_tp.fits Target pixel files      0.0
  220571983 tess2018263035959-s0003-0000000220571983-0123-s_tp.fits Target pixel files      0.0

Then if the reported TIC ID is supplied instead:

res = lk.search_targetpixelfile(220571983, mission='TESS')

No data found for target “220571983”.

It appears this only happens for some targets only, e.g. [ra,dec=(80.0694 -51.9997), tic id=219423302] also. Other queries with matching TIC ID and coordinate should generally work, but this may be a hint of some inherent bug in search_targetpixelfile or data source.

Expected behavior

Environment:

• platform (e.g. Linux, OSX, Windows): Linux
• lightkurve version (e.g. 1.0b6): 1.0.1
• installation method (e.g. pip, conda, source): pip

[scfleming]

Or, automatically append an appropriate string based on the specific mission, if you still would like users to supplay a numerical ID only…

[gully]

The core issue here is closed by #558, and the issue of TRAPPIST-1’s custom aperture getting missed is a duplicate of #499.