Comments (1)
QLP changes for extended mission 2 (sector 56+), from Glen Petitpas (with minor edits):
- Now using “DET_FLUX” and “DET_FLUX_ERR” instead of “KSPSAP_FLUX” and “KSPSAP_FLUX_ERR” for the detrended flux and detrended flux error, respectively.
- Now using “DET_FLUX_SML” and “DET_FLUX_LAG” instead of “KSPSAP_FLUX_SML” and “KSPSAP_FLUX_LAG”.
- Introduced a new “SYS_RM_FLUX” which contains the systematics-removed flux light curve (intermediate data product between raw and systematics-corrected+detrended).
- Introduced a new header variable called “DETMET” which provides the name of the detrending method for reference (QSP vs KSP).
- We have moved the QLP flags from bit 13 to bit 31 to prevent any clashes with possible changes to POC flags. Bits 16-29 are unused.
- bit 13 / 31: Low precision points. The cadence was excluded because low precision
data occurred in a large fraction of the stars . See QLP data product descriptions
- bit 13 / 31: Low precision points. The cadence was excluded because low precision
Lightkurve changes needed would be minor:
- Update docstring on the list of possible columns.
- depending on whether it's from sector 56+ or the older one:
- for the default
flux_err_column
, use ``det_flux_err, or
kspsap_flux_err` or - when users choose
quality_bitmask="hardest"
, include bit 31, or bit 13
- for the default
An existing issue: for quality_bitmasak="hard"
,
- the current implementation inadvertently includes bit 13 (treating it as the Scattered Light Exclude from SPOC) for QLP.
- For QLP, bit 13 probably either be removed from
"hard"
, or include bit 31 in"hard"
as well .
Nuisance in stitching QLP detrended lightcurves across multiple sectors
An user is used to be able to stitch detrended QLP lightcurves across multiple sectors easily:
# lc_coll : a collection of QLP lightcurves
lc = lc_coll.stitch(corrector_func=lambda lc: lc.select_flux("kspsap_flux"))
With the new det_flux
replacing kspsap_flux
in sector 56+, an user would need to handle both cases.
It's unclear whether lightkurve
should provide some convenience helper to handle such cases. Possibilities include:
- creating an alias for
det_flux
askspsap_flux
for new QLP lightcurves (sector 56+). It might shield too much from the users, however. - Make
Lightcurve.select_flux()
accept an ordered list of column names. So users can still stitching detrended lightcurves
# lc_coll : a collection of QLP lightcurves
# use det_flux column, and if it's not present (for sector 55 and ealier), use kspsap_flux
lc = lc_coll.stitch(corrector_func=lambda lc: lc.select_flux(["det_flux", "kspsap_flux"]))
from lightkurve.
Related Issues (20)
- New feature request with pull request coming: lc.remove_data(start=start,end=end,col='str') HOT 3
- search_lightcurve unexpectedly can't find data HOT 9
- Issue with lk.search_lightcurve(TIC, author = 'SPOC') with AttributeError: module 'lightkurve' has no attribute 'search_lightcurve' HOT 7
- issue with tutorial line returning The truth value of an array with more than one element is ambiguous. Use a.any() or a.all() HOT 11
- Can't access hdu from tesscut without saving file HOT 1
- Light curve does not search multiple cadences correctly HOT 3
- Error calling .to_periodogram HOT 10
- Typo in "Searching & downloading Kepler, K2, and TESS data" tutorial HOT 5
- LightCurve.to_fits extra_data keyword not working? HOT 2
- lc.to_fits() + lk.io.read() does not preserve correct FLUX_ORIGIN meta data for SAP_FLUX data HOT 1
- Type error on stitch() HOT 4
- Attempts to download from lightkurve results in a KeyError: 'dataURL' HOT 14
- branch v2.4.x and main is of of sync that could cause merge headache
- Unable to download a lightcurve HOT 1
- showing key error "data URL" while trying to download a targetpixelfile HOT 3
- SearchResult no longer ordered chronologically, it could break user expectation HOT 4
- Having Trouble with lc.download for various stars trying to download TESS-SPOC data HOT 3
- Enhance `TargetPixelFile.interact()` to let user access the selected pixels mask directly in Jupyter notebooks
- Potential memory leak using `lightkurve.read` HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lightkurve.