This paper focuses on the onboard planner and scheduler CASPER, whose core planning engine is based on the ground system ASPEN. Given the challenges of developing flight software, we discuss several of the issues encountered in preparing the planner for flight, including reducing the code image size, determining what data to place within the engineering telemetry packet, and performing long term planning.
Flight software issues in onboard automated planning: lessons learned on EO-1
International Workshop on Planning and Scheduling for Space ; 2004 ; Darmstadt, Germany
2004-06-01
Conference paper
No indication
English
Onboard Training Program Development: Lessons Learned
NTIS | 1982
|Flight Planning Branch Space Shuttle Lessons Learned
NTRS | 2011
|Lessons Learned Supporting Onboard Solid-State Recorders
British Library Conference Proceedings | 1994
|