user: text: Write a concise one-sentence TLDR summary of the scientific paper content below.

Title: Enabling Limited Resource-Bounded Disjunction in Scheduling

Paper content:
We describe three approaches to enabling an extremely computationally limited embedded scheduler to consider a small number of alternative activities based on resource availability.
We consider the case where the scheduler is so computationally limited that it cannot backtrack search.
The first two approaches precompile resource checks (called guards) that only enable selection of a preferred alternative activity if sufficient resources are estimated to be available to schedule the remaining activities.
The final approach mimics backtracking by invoking the scheduler multiple times with the alternative activities.
We present an evaluation of these techniques on mission scenarios (called sol types) from NASA's next planetary rover where these techniques are being evaluated for inclusion in an onboard scheduler.
Embedded schedulers must often operate with very limited computational resources.
Due to such limitations, it is not always feasible to develop a scheduler with a backtracking search algorithm.
This makes it challenging to perform even simple schedule optimization when doing so may use resources needed for yet unscheduled activities.In this paper, we present three algorithms to enable such a scheduler to consider a very limited type of preferred activity while still scheduling all required (hereafter called mandatory) activities.
Preferred activities are grouped into switch groups, sets of activities, where each activity in the set is called a switch case, and exactly one of the activities in the set must be scheduled.
They differ only by how much time, energy, and data volume they consume and the goal is for the scheduler to schedule the most desirable activity (coincidentally the most resource consuming activity) without sacrificing any other mandatory activity.The target scheduler is a non-backtracking scheduler to be onboard the NASA Mars 2020 planetary rover BID9 that schedules in priority first order and never removes or moves an activity after it is placed during a single run of the scheduler.
Because the scheduler does not backtrack, it is challenging to ensure that scheduling a consumptive switch case will not use too many resources Copyright c 2019, California Institute of Technology.
Government Sponsorship Acknowledged.
and therefore prevent a later (in terms of scheduling order, not necessarily time order) mandatory activity from being scheduled.The onboard scheduler is designed to make the rover more robust to run-time variations by rescheduling multiple times during execution BID4 .
If an activity ends earlier or later than expected, then rescheduling will allow the scheduler to consider changes in resource consumption and reschedule accordingly.
Our algorithms to schedule switch groups must also be robust to varying execution durations and rescheduling.We have developed several approaches to handle scheduling switch groups.
The first two, called guards, involve reserving enough sensitive resources (time, energy, data volume) to ensure all later required activities can be scheduled.
The third approach emulates backtracking under certain conditions by reinvoking the scheduler multiple times.
These three techniques are currently being considered for implementation in the Mars 2020 onboard scheduler.
There are many areas for future work.
Currently the time guard heavily limits the placement of activities.
As we saw, using preferred time to address this issue resulted in dropping mandatory activities.
Ideally analysis of start time windows and dependencies could determine where an activity could be placed without blocking other mandatory activities.Additionally, in computing the guard for Minimum SOC using the Sol Wide Guard, instead of increasing the guard value by a predetermined fixed amount which could result in over-conservatism, binary search via Monte Carlo analysis could more precisely determine the guard amount.Currently we consider only a single switch group per plan, the Mars 2020 rover mission desires support for multiple switch groups in the input instead.
Additional work is needed to extend to multiple switch groups.Further exploration of all of the MSI variants is needed.
Study of starting MSI invocations if an activity ends early by at least some amount and the switch case is the next activity is planned.
We would like to analyze the effects of evenly spacing the MSI invocations in order to avoid relying on throttling and we would like to try disabling rescheduling after MSI is complete until the switch case has been committed and understand if this results in major drawbacks.We have studied the effects of time and energy on switch cases, and we would like to extend these approaches and analysis to data volume.
We have presented several algorithms to allow a very computationally limited, non-backtracking scheduler to consider a schedule containing required, or mandatory, activities and sets of activities called switch groups where each activity in such sets differs only by its resource consumption.
These algorithms strive to schedule the most preferred, which happens to be the most consumptive, activity possible in the set without dropping any other mandatory activity.
First, we discuss two guard methods which use different approaches to reserve enough resources to schedule remaining mandatory activities.
We then discuss a third algorithm, MSI, which emulates backtracking by reinvoking the scheduler at most once per level of switch case.
We present empirical analysis using input sets of activities derived from data on expected planetary rover operations to show the effects of using each of these methods.
These implementations and empirical evaluation are currently being evaluated in the context of the Mars 2020 onboard scheduler.

assistant: text: This paper describes three techniques to allow a non-backtracking,  computationally limited scheduler to consider a small number of alternative activities based on resource availability.