{'fraction_non_alphanumeric': 0.02323503127792672, 'fraction_numerical': 0.0, 'mean_word_length': 5.829268292682927, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
QoS tradeoffs for guidance, navigation, and control

Future space missions will require onboard autonomy to reduce data, plan activities, and react appropriately to complex dynamic events. Software to support such behaviors is computationally-intensive but must execute with sufficient speed to accomplish mission goals. The limited processing resources onboard spacecraft must be split between the new software and required guidance, navigation, control, and communication tasks. To-date, control-related processes have been scheduled with fixed execution period, then autonomy processes are fit into remaining slack time slots. We propose the use of quality-of-service (QoS) negotiation to explicitly trade off the performance of all processing tasks, including those related to spacecraft control. We characterize controller performance based on exhaustive search and a Lyapunov optimization technique and present results that analytically predict worst-case performance degradation characteristics. The results are illustrated by application to a second-order linear system with a linear state feedback control law.