Sam Lee

@barbierimauro In this case, you could `stitch` multiple `lc` objects together as one, each loaded from the FITS file of the underlying TIC - sector. ```python import lightkurve as lk...

@barentsen API doc for `LightCurveCollection`, etc. is missing on http://docs.lightkurve.org/ . It was fixed and merged a while back, but the changes have not yet been uploaded to docs.lightkurve.org.

@benjaminpope For your use case of running CBVCorrector on an HPC system without access to the internet, even if the CBVs can be loaded locally, wouldn't there be a problem...

I don't know enough about wcs to comment on the specifics. But so far it looks like either the underlying data representing wcs is incorrect, or there are issues with...

@vvilhelmus Among the targets you've tried, are there any that show correct coordinates in the projection? Also, I tried doing a projection plot on Kelper-89 using Ken's tool: https://github.com/KenMighell/mkpy3 They...

I looked into it a bit more. It seems like projection and `tpf.plot()` does not play well together for some reason. In Ken's tool, the pixels are plotted using matplotlib's...

The issue does not appear to be specific to Kepler planet system. I tried a couple random TICs. They all have the same issue. As stated in earlier https://github.com/lightkurve/lightkurve/issues/1095#issuecomment-873156405, the...

For the behavior change: I presume @pllim is talking about `.Unit(unit_str, format='vounit', parse_strict='silent')` would return an instance of `UnrecognizedUnit` with this PR. If that's the case, it seems to me...

It sounds like the desired behavior needs to be first clarified. The following is the current behavior for parsing Unit with `vounit` format for various combinations of unit string and...

Concerns so far. If someone is better equipped to push forward, feel free to takeover. 1. The fix is done by passing plain array to `np` functions with `.value` instead...