You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a problem of abundance: often lightkurve search queries to MAST result in more than one result--- different data reduction authors, different sectors, and different exposure times (aka "cadence"). While it would be nice to handle all of these in a systematic way, it becomes a "big data" challenge and/or heterogeneous data problem.
I propose we solve this problem in two steps.
For now: simply pick whatever lightcurve comes first in the search result: lc = sr[0] This choice will help use move forward with building our analysis tools.
But eventually, I think we should adopt the ELEANOR-LITE standard (#11). These are not available yet (see the referenced issue). But when they are we can simply flip the switch to exclusively use those.
The text was updated successfully, but these errors were encountered:
We have a problem of abundance: often lightkurve search queries to MAST result in more than one result--- different data reduction authors, different sectors, and different exposure times (aka "cadence"). While it would be nice to handle all of these in a systematic way, it becomes a "big data" challenge and/or heterogeneous data problem.
I propose we solve this problem in two steps.
For now: simply pick whatever lightcurve comes first in the search result:
lc = sr[0]
This choice will help use move forward with building our analysis tools.But eventually, I think we should adopt the ELEANOR-LITE standard (#11). These are not available yet (see the referenced issue). But when they are we can simply flip the switch to exclusively use those.
The text was updated successfully, but these errors were encountered: