question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Search provides two TPFs for Kepler-76

See original GitHub issue

Problem description

Kepler-76b is in two tpfs. When we search for it, we get both back

Example

lk.search_targetpixelfile('kepler-76', quarter=3)

image

Expected behavior

It should only provide one file.

Issue Analytics

  • State:open
  • Created 5 years ago
  • Comments:11

github_iconTop GitHub Comments

1reaction
scflemingcommented, Feb 4, 2019

OK so the cause is that these two targets are so close together in the sky that their footprints (which are 4 or 8 arcsecond squares in the Portal, cant remember which) on the sky overlap each other when searching for the exact position of the one star. See attached screenshot doing a very tight search of 1 arcsecond directly on the coordinate of the other target.

The distance column is the separation between the search coordinate and the closest edge of an observation’s footprint. So, because this coordinate is within the footprints of BOTH Kepler targets, that column is listed as “0.0” for both targets, even though on-sky they are separated by 7+ arcseconds. Note the mouseover description text for Distance in the Portal UI is not correct, I will file a ticket here to fix that.

As an immediate fix, you can further refine the closest target by using the RA and DEC columns of the returned footprints to caculate among those with distance=0 which one is actually closest to your search position (in this case, one should give you 0 and the other several arcseconds).

One possibility to reduce this problem on our side would be to assign footprints on sky that are point sources (no actual dimensions) but there are trade-offs there too (if you don’t have a perfect position or big enough search area you might miss a target entirely). Hope this helps for now at least to understand why this behavior is happening (it is correct based on what the actual definition of distance is as defined in the Portal).

0reactions
scflemingcommented, Feb 4, 2019

Oh sorry, since your screen shot had coordinates I thought you were searching on those. Yeah using the name resolver to get back resolved coordinates should work provided the user is searcing on an identiier it understands. I’ll ask about why that function is private…

Read more comments on GitHub >

github_iconTop Results From Across the Web

kepler light curve: Topics by Science.gov
For KOI-13, HAT-P-7, and Kepler-76 we find that the beaming-based planetary mass estimate is larger than the mass estimated from the ellipsoidal amplitude, ......
Read more >
The Properties of Transiting Exoplanets
From a transit search of K2 M-dwarfs, I compiled a list of so-called ... This has been successful in the discovery of two...
Read more >
Probabilistic Forecasting of the Masses and Radii of Other ...
Mass and radius are two of the most fundamental properties of an astronomical object. Increasingly, new planet discoveries are being ...
Read more >
НАСА - Юнионпедия
ANtarctic Search for METeorites, Поиск метеоритов в Антарктике) — программа ... Kepler-76 b ... TPF) — проект НАСА по созданию космического телескопа, ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found