astropy/astropy#9468 highlighted that there are code snippets in docstrings that are not actually picked up during doctesting. I strongly feel that shouldn't be the case, we should skip any such testing in very rare occasions.
I tag this as a coordinates issue, but they may be other sub packages affected by the same problem.

I am suggesting adding up another feature which will be either a standalone or a part of an advanced search. I suggest adding up a tool which will permit to select a given area. A user can predefine searchable objects by their type (like dwarfs, blue giants and the like) and magnitude (all objects of the apparent/absolute magnitude, for example, 13). When search is done, the search box would list

it should either link to the animator docs or copy the function signature information

I have been playing around with
"Performing Pixel Level Decorrelation with the PLDCorrector in lightkurve" tutorial in colab and have been applying it to TESS data. I have noticed several potential issues - I apologize in advance if these are not issue or bugs, but simple mistakes made on my end.

I first tried to run the task via creating a cut out from FFI data and then passing through to

The python implementation of leapfrog does not make use of the fact that drifts can be combined when not storing output, causing it to be slower than necessary. Comparing to the C implementation, it also appears to not be as precise.