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-oss: Agentic RL Environments (MiMo RL release). 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…

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. The thing that keeps tripping me…

Part of XiaomiMiMo/MiMo-V2.6-RL-oss.