AutoGen Version 5.0

Version 5.0 of the AutoGen software has been released. Previous versions, variously denoted Autogen and autogen, were reported in two articles: Automated Sequence Generation Process and Software (NPO-30746), Software Tech Briefs (Special Supplement to NASA Tech Briefs), September 2007, page 30, and Autogen Version 2.0 (NPO- 41501), NASA Tech Briefs, Vol. 31, No. 10 (October 2007), page 58. To recapitulate: AutoGen (now signifying automatic sequence generation ) automates the generation of sequences of commands in a standard format for uplink to spacecraft. AutoGen requires fewer workers than are needed for older manual sequence-generation processes, and greatly reduces sequence-generation times. The sequences are embodied in spacecraft activity sequence files (SASFs). AutoGen automates generation of SASFs by use of another previously reported program called APGEN. AutoGen encodes knowledge of different mission phases and of how the resultant commands must differ among the phases. AutoGen also provides means for customizing sequences through use of configuration files. The approach followed in developing AutoGen has involved encoding the behaviors of a system into a model and encoding algorithms for context-sensitive customizations of the modeled behaviors. This version of AutoGen addressed the MRO (Mars Reconnaissance Orbiter) primary science phase (PSP) mission phase. On previous Mars missions this phase has more commonly been referred to as mapping phase. This version addressed the unique aspects of sequencing orbital operations and specifically the mission specific adaptation of orbital operations for MRO. This version also includes capabilities for MRO s role in Mars relay support for UHF relay communications with the MER rovers and the Phoenix lander

Reporting Differences Between Spacecraft Sequence Files

A suite of computer programs, called seq diff suite, reports differences between the products of other computer programs involved in the generation of sequences of commands for spacecraft. These products consist of files of several types: replacement sequence of events (RSOE), DSN keyword file [DKF (wherein DSN signifies Deep Space Network)], spacecraft activities sequence file (SASF), spacecraft sequence file (SSF), and station allocation file (SAF). These products can include line numbers, request identifications, and other pieces of information that are not relevant when generating command sequence products, though these fields can result in the appearance of many changes to the files, particularly when using the UNIX diff command to inspect file differences. The outputs of prior software tools for reporting differences between such products include differences in these non-relevant pieces of information. In contrast, seq diff suite removes the fields containing the irrelevant pieces of information before processing to extract differences, so that only relevant differences are reported. Thus, seq diff suite is especially useful for reporting changes between successive versions of the various products and in particular flagging difference in fields relevant to the sequence command generation and review process

MPST Software: grl_pef_check

This innovation is a tool used to verify and validate spacecraft sequences at the predicted events file (PEF) level for the GRAIL (Gravity Recovery and Interior Laboratory, see http://www.nasa. gov/mission_pages/grail/main/index. html) mission as part of the Multi-Mission Planning and Sequencing Team (MPST) operations process to reduce the possibility for errors. This tool is used to catch any sequence related errors or issues immediately after the seqgen modeling to streamline downstream processes. This script verifies and validates the seqgen modeling for the GRAIL MPST process. A PEF is provided as input, and dozens of checks are performed on it to verify and validate the command products including command content, command ordering, flight-rule violations, modeling boundary consistency, resource limits, and ground commanding consistency. By performing as many checks as early in the process as possible, grl_pef_check streamlines the MPST task of generating GRAIL command and modeled products on an aggressive schedule. By enumerating each check being performed, and clearly stating the criteria and assumptions made at each step, grl_pef_check can be used as a manual checklist as well as an automated tool. This helper script was written with a focus on enabling the user with the information they need in order to evaluate a sequence quickly and efficiently, while still keeping them informed and active in the overall sequencing process. grl_pef_check verifies and validates the modeling and sequence content prior to investing any more effort into the build. There are dozens of various items in the modeling run that need to be checked, which is a time-consuming and errorprone task. Currently, no software exists that provides this functionality. Compared to a manual process, this script reduces human error and saves considerable man-hours by automating and streamlining the mission planning and sequencing task for the GRAIL mission

Documenting AUTOGEN and APGEN Model Files

A computer program called "autogen hypertext map generator" satisfies a need for documenting and assisting in visualization of, and navigation through, model files used in the AUTOGEN and APGEN software mentioned in the two immediately preceding articles. This program parses autogen script files, autogen model files, PERL scripts, and apgen activity-definition files and produces a hypertext map of the files to aid in the navigation of the model. This program also provides a facility for adding notes and descriptions, beyond what is in the source model represented by the hypertext map. Further, this program provides access to a summary of the model through variable, function, sub routine, activity and resource declarations as well as providing full access to the source model and source code. The use of the tool enables easy access to the declarations and the ability to traverse routines and calls while analyzing the model

A preliminary investigation into the prevalence and prediction of problematic cell phone use

Abstract Background and aims Likening mobile phone use dependency to the classification of excessive behaviors may be necessarily equivalent in seriousness to previously established addictions such as problematic computing or excessive gambling. The aim of the study explores into the behavior of excessive use of mobile phones as a pathological behavior. Methods Two studies investigated criteria for problematic mobile phone usage by examining student (Study 1, N = 301) and nonstudent (Study 2, N = 362) responses to a set of adapted mobile phone addiction inventories. Study 1 investigated cell phone addiction inventories as constructs designed to measure problematic cell phone use. Additionally, Study 2 sought to predict age, depression, extraversion, emotional stability, impulse control, and self-esteem as independent variables that augment respondents' perceptions of problematic use. Results The results from Study 1 and Study 2 indicate that 10 to 25% of the participants tested exhibited problematic cell phone usage. Additionally, age, depression, extraversion, and low impulse control are the most suitable predictors for problematic use. Conclusions The results of the two studies indicate that problematic mobile phone use does occur and ought to be taken seriously by the psychological community. Presently, there is limited data providing conclusive evidence for a comprehensible categorization of cell phone addiction, as well as a unified explanatory model specific to problematic mobile phone use. Studies such as this one may contribute substantial findings, adding scientific significance, and offering a valuable submission for the ongoing progress of creating intervention frameworks relative to “virtual addictions”

CLEaR: Closed Loop Execution and Recovery High-Level Onboard Autonomy for Rover Operations

This viewgraph presentation covers the following topics: Coupled Layer Architecture for Robotic Autonomy CLARAty system at the functional layer and the decision layer; and CLEaR - AI Planning and Schedule - Task Based Control, A demonstration is of the operation of the system is given, with viewgraphs of the rover movement control

An Approach to Autonomous Operations for Remote Mobile Robotic Exploration

This viewgraph presentation addresses the use of autonomy for remote mobile robotic exploration. The contents include; 1) Why Use Autonomy?; 2) What Are Some Options? JPL (Reasoning); 3) More Options.. . (Modeling); 4) The CLEaR Control System (Closed Loop Execution and Recovery); 5) Method of Response; 6) Overall Goal; 7) CLEaR in Action; 8) Initial Scenario; 9) Initial Scenario - Planned; 10) Unforeseen Events; and 11) Ongoing Research

Using Planning, Scheduling and Execution for Autonomous Mars Rover Operations

With each new rover mission to Mars, rovers are traveling significantly longer distances. This distance increase raises not only the opportunities for science data collection, but also amplifies the amount of environment and rover state uncertainty that must be handled in rover operations. This paper describes how planning, scheduling and execution techniques can be used onboard a rover to autonomously generate and execute rover activities and in particular to handle new science opportunities that have been identified dynamically. We also discuss some of the particular challenges we face in supporting autonomous rover decision-making. These include interaction with rover navigation and path-planning software and handling large amounts of uncertainty in state and resource estimations. Finally, we describe our experiences in testing this work using several Mars rover prototypes in a realistic environment