Open jorgemarpa opened 2 months ago
Some other ideas to be discussed:
self.ephem
and self.ephemeris
, the first one has the original DF that the user input to initialize the object, the second one seems to be only the track positions in the frames that fall inside the science portion of the CCD and also match the observing time (by interp). It could be a good idea have a one-to-one mapping between those two, because the new tracks will come with flags per time that tell the quality (interpolation or projection or fitted) of the position. Something to change in a future PR:
_create_threshold_mask()
function, we should add an option to use the predicted asteroid ephemeris as the reference_pixel
. This should probably be the default value, instead of center, seeing as the asteroid is not often directly centered.Something to add in a future PR:
I found some code recommendations/issues while using the first version of
tess-asteroids
. Some of these are not urgent and can be done later, I add them here to keep track.self.shape
I was expecting to get the cube shape when calling this. I would also recommend setting shape as an object property https://github.com/altuson/tess-asteroids/blob/770f46a70a1ed02d2065d4225ec041daa3fde0b9/src/tess_asteroids/tpf.py#L122target_id
or something more explicit than justtarget
https://github.com/altuson/tess-asteroids/blob/770f46a70a1ed02d2065d4225ec041daa3fde0b9/src/tess_asteroids/tpf.py#L36I'll keep reviewing and using the code and add things as they come out in