Inconsistent target ID attribute makes mission-agnostic code awkward
Inconsistent target ID attribute makes mission-agnostic code awkward: a task in MiMo-V2.6-RL-harbor-code: MiMo-V2.6-RL Code (Harbor) (Harbor dataset). I'm writing a few small helper scripts that work with light curves and pixel files from different missions (Kepler, K2, TESS) interchangeably —…
The task
I'm writing a few small helper scripts that work with light curves and pixel files from different missions (Kepler, K2, TESS) interchangeably — things like logging, summarising a batch run, or just printing which object I'm currently processing.
Part of FineEnvs/MiMo-V2.6-RL-harbor-code.