Christina Hedges

Hi @bbrady-vassar, I'm sorry that this has taken us so long to take a look at. I can confirm this behavior is still happening, and it's something we'd like to...

Hi @Kenz19, thanks for submitting an issue, sorry that we haven't gotten back to you until now! Since you raised this issue there have been several updates to `Lightkurve`, and...

@0J3lack0 and @ZRupp thank you for opening this issue and discussing this. We're aware that the `bin` function is very slow and we're going put some work into addressing that...

@eivshina thanks for your comment! I believe @orionlee has answered your question above so I'm going to close this, if you have any more questions please feel free to reach...

Hi @bmorris3, it seems like this issue has been open for a while now, and I can't easily reproduce this failure. I'm going to close this issue for now, but...

Hi @decaelus that's a great catch. I think this is actually expected, the `PLDCorrector` relies on a PCA algorithm from `fbpca`. I believe determining the PCA components is a somewhat...

@vvilhelmus re ChatGPT: the TESS GI office is now taking over maintenance and expansion of `Lightkurve` and so there is a flurry of activity as we have more hands on...

@aminpdsh I'm closing this, it looks like your target (`"EPIC 201092669"`) was never observed by K2, that's why the code above is failing. If you think this is an error,...

It looks like this issue is no longer the case in v2.3.0 so I am going to close this issue ```python-traceback time : flux : flux_err : cadenceno : sap_flux...

@pmaxted I think this might be an issue arising from working with a large amount of data. As has been said above, PLD wasn't necessarily tested on the short cadence...