Search NASA⌕ Search

SEARCH · Search NASA

Results for “Planning software”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 127 records · Page 7

SPRINT: Scheduling Planning Routing Intersatellite Network Tool

The Scheduling Planning Routing Intersatellite Network Tool (SPRINT) software system plans and schedules the operations (observations, inter-satellite crosslink communications, and ground communications) of Earth observation (EO) constellations of hundreds of resource-constrained small satellites to enable global, near real-time science. Historically, most CubeSats have flown radios only for direct-to-ground downlink of data; as a result, data availability is delayed by as long as it takes for the capturing satellite to pass over a ground station, typically hours. Current Planning and Scheduling (P&S) systems for constellations cannot handle data routing through a large, dynamic network topology, and all planning is handled on the ground without .the ability to autonomously prioritize important observations, or respond to unexpected changes in communication window or bandwidth. SPRINT directly handles both data routing for low latency bulk observation data downlink and replanning onboard to deal with dynamic priorities and fault response, maximizing the utility of downlinked data.

Kerri Cahoy↗

Dynamic IT Security Database and Analytics for Launch Control Systems Software

During the Summer 2020 session, I worked with intern Destani S. Van Arsdalen of EGS Software. Together, we co-created a tool to aid the dynamic investigation, updated over time,of the security compliance of LCS COTS and open source software. We originally planned touse spreadsheet software for management and analysis, but through this exploratoryproject, chose to use Python and JSON after receiving feedback on our project’s current anddesired capabilities at that time.At first, the project was solely designed to help on-board new COTS software, based on aquestionnaire that could be filled out for each software package. This, combined with usingthe spreadsheet application’s web-query capabilities to fetch information from the NVD,allowed presentation and analytics cells to automatically populate as elements of themanually-filled questionnaire changed. While this system was promising, we decided tochange technologies for a few reasons. In the spreadsheet, single cells could not hold complexdata like arrays and objects. The automatic population of cells and dynamic updates made itdifficult to manage and add new features. And finally, it had limited extensibility sinceadding new software required significant understanding of how both the spreadsheet wasconstructed, and the more obscure, proprietary scripting languages packaged with it.The pivot to a standard computer science database language of JSON, aided by thescripting capabilities of Python, greatly helped to improve the project’s functionality. First,and most importantly, the script’s import and analysis of database data is easilyreproducible. Additional data analysis can be modularly added without requiringmodification of the script and is capable of routine scheduling. The revised process can besplit into three parts. First, the conversion of LCS asset and software documentation into theJSON hierarchical database format. Second, the merging of this database with the NVD,forming a new data structure, using CPEs of the CVE object as a linking element betweenthem. And third, the automatically performed analytics and analysis of the combined data,in a modular and extensible format, to produce better informed business decisions. The outputted graphs, for example, are automatically generated by the Python script inconnection with the combined database. This allows updated graphs and any analytics to be re-rendered automatically following updates to the LCS’s initial asset documentation. Afinal report can then be programmatically and easily constructed from these sources to allow fully reproducible metrics for heavily evidenced risk management decisions.

it↗

SEQ-POINTER: Next generation, planetary spacecraft remote sensing science observation design tool

Since Mariner, NASA-JPL planetary missions have been supported by ground software to plan and design remote sensing science observations. The software used by the science and sequence designers to plan and design observations has evolved with mission and technological advances. The original program, PEGASIS (Mariners 4, 6, and 7), was re-engineered as POGASIS (Mariner 9, Viking, and Mariner 10), and again later as POINTER (Voyager and Galileo). Each of these programs were developed under technological, political, and fiscal constraints which limited their adaptability to other missions and spacecraft designs. Implementation of a multi-mission tool, SEQ POINTER, under the auspices of the JPL Multimission Operations Systems Office (MOSO) is in progress. This version has been designed to address the limitations experienced on previous versions as they were being adapted to a new mission and spacecraft. The tool has been modularly designed with subroutine interface structures to support interchangeable celestial body and spacecraft definition models. The computational and graphics modules have also been designed to interface with data collected from previous spacecraft, or on-going observations, which describe the surface of each target body. These enhancements make SEQ POINTER a candidate for low-cost mission usage, when a remote sensing science observation design capability is required. The current and planned capabilities of the tool will be discussed. The presentation will also include a 5-10 minute video presentation demonstrating the capabilities of a proto-Cassini Project version that was adapted to test the tool. The work described in this abstract was performed by the Jet Propulsion Laboratory, California Institute of Technology, under contract to the National Aeronautics and Space Administration.

Boyer, Jeffrey S.↗

Redefining Tactical Operations for MER Using Cloud Computing

The Mars Exploration Rover Mission (MER) includes the twin rovers, Spirit and Opportunity, which have been performing geological research and surface exploration since early 2004. The rovers' durability well beyond their original prime mission (90 sols or Martian days) has allowed them to be a valuable platform for scientific research for well over 2000 sols, but as a by-product it has produced new challenges in providing efficient and cost-effective tactical operational planning. An early stage process adaptation was the move to distributed operations as mission scientists returned to their places of work in the summer of 2004, but they would still came together via teleconference and connected software to plan rover activities a few times a week. This distributed model has worked well since, but it requires the purchase, operation, and maintenance of a dedicated infrastructure at the Jet Propulsion Laboratory. This server infrastructure is costly to operate and the periodic nature of its usage (typically heavy usage for 8 hours every 2 days) has made moving to a cloud based tactical infrastructure an extremely tempting proposition. In this paper we will review both past and current implementations of the tactical planning application focusing on remote plan saving and discuss the unique challenges present with long-latency, distributed operations. We then detail the motivations behind our move to cloud based computing services and as well as our system design and implementation. We will discuss security and reliability concerns and how they were addressed

Mars↗

Certification Considerations for Adaptive Stress Testing of Airborne Software

eduAdaptive Stress Testing (AST) has shown promise in identifying errant corner cases in complex software used in aerospace applications including Flight Management Systems (FMS). The strength of AST is performing test-based verification of complex aerospace software intensive systems at scale in simulated operational environments.Simulating and capturing the realistic operational complexities in integrated verification environments may exposeflaws in the softwareprior to field deployment, whereas the software may perform just fine to traditional requirements-basedunit and component level testing.AST can be used to test the whole system.Individual components may behave safely, but together can result in complex interactions and emergent failures, so it is important to test at the integrated system level.Motivated by the observed benefitsat the prototype proof of concept scale, this paper considers how AST may be integrated into a production workflow and used to generate objective evidence in a processthat delivers certified aerospace software.The research includes evaluation of alignment with both DO-178C and Overarching Properties(OP). The paper addresses questions such as “where should AST fit in the Plan for Software Aspects of Certification (PSAC) and Software Verification Plan (SVP), what aspects of AST do not fit, and what objectives does it satisfy?” The paper concludes that AST is in fact useful at locating errors in complex airborne application software and in doing so provides benefits to suppliers and end users. Furthermore, AST appears appropriate to add value in both DO-178Cbased and Overarching Properties based certification approaches.

certification↗

Numerical arc segmentation algorithm for a radio conference - A software tool for communication satellite systems planning

A detailed description of a Numerical Arc Segmentation Algorithm for a Radio Conference (NASARC) software package for communication satellite systems planning is presented. This software provides a method of generating predetermined arc segments for use in the development of an allotment planning procedure to be carried out at the 1988 World Administrative Radio Conference (WARC - 88) on the use of the GEO and the planning of space services utilizing GEO. The features of the NASARC software package are described, and detailed information is given about the function of each of the four NASARC program modules. The results of a sample world scenario are presented and discussed.

Whyte, W. A.↗

An Extensible, User- Modifiable Framework for Planning Activities

This software provides a development framework that allows planning activities for the Mars Science Laboratory rover to be altered at any time, based on changes of the Activity Dictionary. The Activity Dictionary contains the definition of all activities that can be carried out by a particular asset (robotic or human). These definitions (and combinations of these definitions) are used by mission planners to give a daily plan of what a mission should do. During the development and course of the mission, the Activity Dictionary and actions that are going to be carried out will often be changed. Previously, such changes would require a change to the software and redeployment. Now, the Activity Dictionary authors are able to customize activity definitions, parameters, and resource usage without requiring redeployment. This software provides developers and end users the ability to modify the behavior of automatically generated activities using a script. This allows changes to the software behavior without incurring the burden of redeployment. This software is currently being used for the Mars Science Laboratory, and is in the process of being integrated into the LADEE (Lunar Atmosphere and Dust Environment Explorer) mission, as well as the International Space Station.

Joshing, Joseph C.↗

Maximization of orbiter altitude at ALT interface airspeed, mission planning, mission analysis and software

The determination of the separation initial conditions (i.e. incidence angle) that maximize orbiter altitude at the ALT interface airspeed is considered. Optimum altitude airspeed profiles are generated for each orbiter incidence angle and tailcone configuration. Results show that the highest separation altitude does not result in the highest altitude at ALT interface airspeed. The altitude attainable at ALT interface airspeed should therefore be considered in the selection of the initial conditions (i.e. incidence angle). Without violating any known constraints, the incidence angles that maximize orbiter altitude at the ALT interface airspeeds are 7.0 deg for ALT free flight 1 and 5.5 deg for ALT free flight 6.

Glenn, G. M.↗

Proposed powered explicit guidance thrust integrals derivation/implementation. Mission planning, mission analysis and software formulation

A new exoatmospheric, powered explicit guidance (PEG) thrust integral formulation and a simple method of implementation are presented. The new thrust integral formulation is significantly simpler than that currently used in PEG. Preliminary estimates indicate a computer storage savings of 220 words, which is approximately 10 percent of the current PEG ascent program. Alternate methods of implementation that could produce even more savings are noted.

Jaggers, R. F.↗

Orbiter/carrier separation for the ALT free flight no. 1 reference trajectories. Mission planning, mission analysis and software formulation

Details of the generation of the separation trajectories are discussed. The analysis culminated in definition of separation trajectories between physical separation and orbiter/carrier vortex clearance. Specifications, assumptions and analytical approach used to generate the separation trajectories are presented. Results of the analytical approach are evaluated. Conclusions and recommendations are summarized. Supporting references are listed.

Glenn, G. M.↗

Orbiter altitude at ALT interface based on ALSES (Approach and Landing Shuttle Engineering Simulation) analyses. Mission planning, mission analysis and software formulation

The details of the orbiter altitude attainable at the approach and landing tests (ALT) interface determined by the approach and landing shuttle engineering simulation (manned) were documented. The analysis culminated in the verification of the trends observed in a similar analysis performed previously on the space vehicle dynamics simulation (unmanned). Altitude variations attributable to pilot steering variability ranged between 492 ft higher to 383 ft lower. The requirement for this parametric analysis is first elaborated. The specifications, assumptions, and analytical approach used to determine the orbiter altitude at the ALT interface are then presented, followed by the results of the analytical approach and the conclusions and recommendations.

Colwell, C. L.↗

Star tracker constraint violations digital capability description and analysis results. Mission planning, mission analysis, and software formulation

Results of star tracker constraint violation analyses performed with the digital computer program Shuttle Attitude and Pointing Time Line Processor (SAPT) are presented. Results are typical of those utilized to provide the information required to update Baseline Reference Mission Attitude and Pointing Time Lines. Descriptions of SAPT modifications implemented to perform these analyses are also presented.

Poston, P. L.↗

Mission planning, mission analysis and software formulation. Level C requirements for the shuttle mission control center orbital guidance software

The formulation of Level C requirements for guidance software was reported. Requirements for a PEG supervisor which controls all input/output interfaces with other processors and determines which PEG mode is to be utilized were studied in detail. A description of the two guidance modes for which Level C requirements have been formulated was presented. Functions required for proper execution of the guidance software were defined. The requirements for a navigation function that is used in the prediction logic of PEG mode 4 were discussed. It is concluded that this function is extracted from the current navigation FSSR.

Langston, L. J.↗

Error Analysis of the Shuttle Orbital Maneuvering System P-V-T Propellant Gaging Module. Mission Planning, Mission Analysis and Software Formulation

An investigation of the shuttle orbital maneuvering system (OMS) pressure-volume-temperature (P-V-T) propellant gaging module has revealed that the gaging errors due to the combined effects of random instrumentation measurement errors, propellant loading uncertainties, and simplifying assumptions in the software are non-linear over the range of the usable propellant quantity gage (0-100%), with the largest error being at the zero point. When the OMS propellant tanks in the orbiter vehicle pods are filled to contain 100% of the maximum usable propellant, the gaging error at the zero point was determined to be 9.5% for the fuel and 9.5% for the oxidizer. When the OMS propellant tanks initially contain 50% of the maximum usable propellant, the largest gaging error is still 9.5% for the fuel and 9.5% for the oxidizer.

Duhon, D. D.↗

Space shuttle engineering and operations support. ALT separation reference trajectories for tailcone on orbiter forward and aft CG configurations. Mission planning, mission analysis and software formulation

A preflight analysis of the ALT separation reference trajectories for the tailcone on, forward, and aft cg orbiter configurations is documented. The ALT separation reference trajectories encompass the time from physical separation of the orbiter from the carrier to orbiter attainment of the maximum ALT interface airspeed. The trajectories include post separation roll maneuvers by both vehicles and are generated using the final preflight data base. The trajectories so generated satisfy all known separation design criteria and violate no known constraints. The requirement for this analysis is given along with the specifications, assumptions, and analytical approach used to generate the separation trajectories. The results of the analytical approach are evaluated, and conclusions and recommendations are summarized.

Glenn, G. M.↗