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
It seems that, on my end at least, this error only occurs with very specific light curves for some reason. It will not run if the flux's type is a MaskedQuantity. After trying out some different light curves for mu Eridani, it seems that only light curves from SPOC or TESS-SPOC have their fluxes as MaskedQuantities:
I haven't tested this with other stars. Does this happen to anyone else as well?
Note, the original issue was resolved by updating to astropy 5.3. However, I think this is still an issue as I'm not sure whether the MaskedQuantity vs Quantity data type difference is intentional.
In terms of the actual codes, lightkurve does not do anything SPOC / TESS-SPOC specific to return MaskedQuantity. It seems to be a by-product of the a) specific FITS format used by SPOC / TESS-SPOC and b) astropy FITS reader behavior.
If it's decided to use Quantity instead of MaskedQuantity, PR #1281 would provide a fix.
I think using Quantity (instead of MaskedQuantity) will alleviate the various quirks / bugs / API differences with MaskedQuantity.
For users who have specific requirement to use MaskedQuantity, they can still convert the columns to MaskedQuantity.
It seems that, on my end at least, this error only occurs with very specific light curves for some reason. It will not run if the flux's type is a MaskedQuantity. After trying out some different light curves for mu Eridani, it seems that only light curves from SPOC or TESS-SPOC have their fluxes as MaskedQuantities:
I haven't tested this with other stars. Does this happen to anyone else as well?
Originally posted by @Paco-2000 in #1338 (comment)
The text was updated successfully, but these errors were encountered: