Search NASA⌕ Search

SEARCH · Search NASA

Results for “Software Release”

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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRS2019

New Features in the SPOC Pipeline Release 4.0

The Science Processing Operations Center is in the process of testing and deploying Release 4.0 of the codebase in the March 2019 timeframe. This paper describes the new features of the software and their likely impact on the quality of the TESS science data products. The major goals of Release 4.0 are to improve the extraction of photometry from the pixels in light of the non-uniform pointing performance and the identification of instrumental signatures from the light curves. We also describe modifications to the FFI pipeline to allow the generation of FFI light curves, correction of the instrumental systematics therein, and planet searches, primarily for the purpose of validating the 2-min pipeline against the FFI pipeline, but also to be able to provide cotrending basis vectors (CBVs) derived directly from the FFIs to the public to aid them in their extraction and correction of photometry. We also discuss the improvements in photometric performance of the pipeline and its various components.The lapse in funding experienced between 22 December 2018 and 27 January 2019 significantly delayed our ability to conduct integration testing as planned for late December/early January, delaying the start of V&V by one month to the end of February 2019.The TESS Mission is funded by NASA's Science Mission Directorate as an Astrophysics Explorer Mission.The Science Processing Operations Center is in the process of testing and deplo!"ing Release 4.0 of thecodebase In the March 2019 tlmeframe. This paper describes the new features or the software and theirlikely impact on the quality of the TESS science data products. The major goals or Release 4.0 are to Imtheidentification of instrumental signatures from the light cuNes. We also describe modifications tothe FFI pipeline to allow the generation of FFI light curves, correction of the instrumental systematicstherein, and planet searches, primarily for the purpose of validating the 2-min pipelineagainst the FFI pipeline, but also to be able to provide cotrending basis vectors (C3Vs) ,,.~,.;.derived directly from the FFls to the public to aid them in their extractbn and correction , :-; ~'-'\'.'.of photometry. We also discuss the Improvements In photometric performance• of ~~\":;:•the pipeline and its various components. :,;.-.;The lapse In funding experienced between 22 December 2018 and 27January 2019 significantly delayed our ability to conduct Integrationtesting as planned for late December/early January, delaying thestart of V&V by one month to the end of February 2019.The TESS Mission is funded by NASA's Science Mission Directorateas an Astrophysics Explorer Mission.o.iu.c...,.....~~New Features in SPOC 4.01. Use of quatemions In photometry and centroiding.2. Use of quaternions to Identify high-motion cadences and exclude same.3. Use of the TPS detections to deemphasize pathological cadences ("skyline flattenlng"I.4. Improved CAL calculations for black and smear correction.5. PA brightness metric calculation improvements (induo'e crowding in calrulation)./ • 6. Improved POC spike goodness metric.•~• 7. Improved handling of gaps and momentum duni:>S in POC.8. Improved tuning of POC., 9. Improved attitude tweak correction in PDC.10. Improvements in PDC introduced noise and correlation goodness metrics11. Using the improved spike goodness metric to minimize overlitting in the spikeremover ' • :,''l./ 12. Enable FFI processing through planet search.,,. ,• • "« ,;,,,•.~'A , 13.1 D4.V S mtreinaim-relipnoinrgts d aartcah irveetrdie tvoa Ml aAnSdT p ersistence to database 15. Improved management of jobs on the NAS Pleiadss supercomputer

Jenkins, Jon M.↗
NASA NTRS1993

Space Station Freedom (SSF) Data Management System (DMS) performance model data base

The purpose of this document was originally to be a working document summarizing Space Station Freedom (SSF) Data Management System (DMS) hardware and software design, configuration, performance and estimated loading data from a myriad of source documents such that the parameters provided could be used to build a dynamic performance model of the DMS. The document is published at this time as a close-out of the DMS performance modeling effort resulting from the Clinton Administration mandated Space Station Redesign. The DMS as documented in this report is no longer a part of the redesigned Space Station. The performance modeling effort was a joint undertaking between the National Aeronautics and Space Administration (NASA) Johnson Space Center (JSC) Flight Data Systems Division (FDSD) and the NASA Ames Research Center (ARC) Spacecraft Data Systems Research Branch. The scope of this document is limited to the DMS core network through the Man Tended Configuration (MTC) as it existed prior to the 1993 Clinton Administration mandated Space Station Redesign. Data is provided for the Standard Data Processors (SDP's), Multiplexer/Demultiplexers (MDM's) and Mass Storage Units (MSU's). Planned future releases would have added the additional hardware and software descriptions needed to describe the complete DMS. Performance and loading data through the Permanent Manned Configuration (PMC) was to have been included as it became available. No future releases of this document are presently planned pending completion of the present Space Station Redesign activities and task reassessment.

Stovall, John R.↗
NASA NTRS2004

Evaluation of Open-Source Hard Real Time Software Packages

Reliable software is, at times, hard to find. No piece of software can be guaranteed to work in every situation that may arise during its use here at Glenn Research Center or in space. The job of the Software Assurance (SA) group in the Risk Management Office is to rigorously test the software in an effort to ensure it matches the contract specifications. In some cases the SA team also researches new alternatives for selected software packages. This testing and research is an integral part of the department of Safety and Mission Assurance. Real Time operation in reference to a computer system is a particular style of handing the timing and manner with which inputs and outputs are handled. A real time system executes these commands and appropriate processing within a defined timing constraint. Within this definition there are two other classifications of real time systems: hard and soft. A soft real time system is one in which if the particular timing constraints are not rigidly met there will be no critical results. On the other hand, a hard real time system is one in which if the timing constraints are not met the results could be catastrophic. An example of a soft real time system is a DVD decoder. If the particular piece of data from the input is not decoded and displayed to the screen at exactly the correct moment nothing critical will become of it, the user may not even notice it. However, a hard real time system is needed to control the timing of fuel injections or steering on the Space Shuttle; a delay of even a fraction of a second could be catastrophic in such a complex system. The current real time system employed by most NASA projects is Wind River's VxWorks operating system. This is a proprietary operating system that can be configured to work with many of NASA s needs and it provides very accurate and reliable hard real time performance. The down side is that since it is a proprietary operating system it is also costly to implement. The prospect of replacing this somewhat costly implementation is the focus of one of the SA group s current research projects. The explosion of open source software in the last ten years has led to the development of a multitude of software solutions which were once only produced by major corporations. The benefits of these open projects include faster release and bug patching cycles as well as inexpensive if not free software solutions. The main packages for hard real time solutions under Linux are Real Time Application Interface (RTAI) and two varieties of Real Time Linux (RTL), RTLFree and RTLPro. During my time here at NASA I have been testing various hard real time solutions operating as layers on the Linux Operating System. All testing is being run on an Intel SBC 2590 which is a common embedded hardware platform. The test plan was provided to me by the Software Assurance group at the start of my internship and my job has been to test the systems by developing and executing the test cases on the hardware. These tests are constructed so that the Software Assurance group can get hard test data for a comparison between the open source and proprietary implementations of hard real time solutions.

Mattei, Nicholas S.↗
NASA NTRSDate not supplied

NASA CARA Tools

The NASA Conjunction Assessment Risk Analysis (CARA) team has created and posted to GitHub a set of MATLAB software tools for collision assessment (CA) analysis. The software is provided to the public under a NASA Open-Source Software Agreement and is maintained/updated by the CARA Analysis team. Capabilities provided within the toolset include algorithms in assessing probability of collision (Pc), collision consequence, covariance realism, Orbit Determination (OD) quality assessment, and single covariance max Pc. Additionally, a set of utilities are provided for astrodynamics topics closely related to CA, such as: Conjunction Data Message (CDM) parsing, covariance transformations, coordinate system transformations, etc. The repository is regularly updated on a monthly basis and new functionality will be added as algorithms are approved for public release. This presentation will provide a brief introduction to the toolset, highlight some of the key components which can be used in operations, and will present information on algorithms that are in the release pipeline and can be expected soon. This software will enable operators to independently perform CA calculations using the same core algorithms that CARA uses in operations.

L. Baars↗
NASA NTRSDate not supplied

NASA CARA Tools

The NASA Conjunction Assessment Risk Analysis (CARA) team has created and posted to GitHub a set of MATLAB software tools for collision assessment (CA) analysis. The software is provided to the public under a NASA Open-Source Software Agreement and is maintained/updated by the CARA Analysis team. Capabilities provided within the toolset include algorithms in assessing probability of collision (Pc), collision consequence, covariance realism, Orbit Determination (OD) quality assessment, and single covariance max Pc. Additionally, a set of utilities are provided for astrodynamics topics closely related to CA, such as: Conjunction Data Message (CDM) parsing, covariance transformations, coordinate system transformations, etc. The repository is regularly updated on a monthly basis and new functionality will be added as algorithms are approved for public release. This presentation will provide a brief introduction to the toolset, highlight some of the key components which can be used in operations, and will present information on algorithms that are in the release pipeline and can be expected soon. This software will enable operators to independently perform CA calculations using the same core algorithms that CARA uses in operations.

Luis Baars↗
NASA NTRS1993

Development and operations of the Astrophysics Data System

The main effort in October 1992 was for the development and of the Astrophysics Data System (ADS) 3.1 graphical interface (GUI) and the preparation for its release. The beta-release for the GUI was made available to the nodes for testing. Development of the Abstract Server progressed satisfactorily. A test version was prepared for the ADASS meeting. Another major effort was the preparation for the user and nodes meetings on 5 and 6 November and for the ADASS conference on 2-4 November. February 1993 was highlighted by the preparation for the update release and its associated problems. We have the okay from the Commerce Department to export ADS. Foreign users can now sign on and receive the software. The main event during June was the AAS meeting. In the summer, the project decided on a new release schedule. The next major release is scheduled for January 1994 and will include major architectural improvements. In late spring 1994, a major release will include the new networking software.

Murray, S. S.↗
NASA NTRSDate not supplied

NASA Class A Certification of Core Flight Software (cFS)

NASA Gateway program has named cFS as the software architecture for the vehicle. The core CFS team (GSFC+JSC) is tasked to develop a certifiable release of the cFS bundle, by components, as class A, safety-critical flight software. It is to be available to all Gateway software developers, including our element vendors and international partners. Its availability & usage will be as stated by the Gateway User Agreement license. In this presentation, we will describe our general certification process, and more importantly, our certification artifacts that can be re-run to certify cFS on different platforms. Our goal is to also make available these certifiable packages to the open source community, specifically for cFE, OSAL and certain cFS applications and libraries that are currently hosted on NASA github (https://github.com/nasa).

Tam M Ngo↗
NASA NTRSDate not supplied

NASA Class A Certification of Core Flight Software (cFS)

NASA Gateway program has named cFS as the software architecture for the vehicle. The core CFS team (GSFC+JSC) is tasked to develop a certifiable release of the cFS bundle, by components, as class A, safety-critical flight software. It is to be available to all Gateway software developers, including our element vendors and international partners. Its availability & usage will be as stated by the Gateway User Agreement license. In this presentation, we will describe our general certification process, and more importantly, our certification artifacts that can be re-run to certify cFS on different platforms. Our goal is to also make available these certifiable packages to the open source community, specifically for cFE, OSAL and certain cFS applications and libraries that are currently hosted on NASA github (https://github.com/nasa).

Tam M Ngo↗
NASA NTRS2001

[Low Fidelity Simulation of a Zero-Y Robot]

The item to be cleared is a low-fidelity software simulation model of a hypothetical freeflying robot designed for use in zero gravity environments. This simulation model works with the HCC simulation system that was developed by Xerox PARC and NASA Ames Research Center. HCC has been previously cleared for distribution. When used with the HCC software, the model computes the location and orientation of the simulated robot over time. Failures (such as a broken motor) can be injected into the simulation to produce simulated behavior corresponding to the failure. Release of this simulation will allow researchers to test their software diagnosis systems by attempting to diagnose the simulated failure from the simulated behavior. This model does not contain any encryption software nor can it perform any control tasks that might be export controlled.

Sweet, Adam↗
NASA NTRS1991

The Land Analysis System (LAS)

The Land Analysis System (LAS) is an interactive software system, available in the public domain, for the analysis, display, and management of multispectral and other digital image data. The system was developed to support earth sciences research and development activities. LAS provides over 240 applications functions and utilities, a flexible user interface, complete on-line and hardcopy documentation, extensive image data file management, reformatting, and conversion utilities, and high level device independent access to image display hardware. The capabilities are summarized of the latest release of the system (version 5). Emphasis is given to the system portability and the isolation of hardware and software dependencies in this release.

Lu, Yun-Chi↗
NASA NTRS2000

Level 1 Processing of MODIS Direct Broadcast Data From Terra

In February 2000, an effort was begun to adapt the Moderate Resolution Imaging Spectroradiometer (MODIS) Level 1 production software to process direct broadcast data. Three Level 1 algorithms have been adapted and packaged for release: Level 1A converts raw (level 0) data into Hierarchical Data Format (HDF), unpacking packets into scans; Geolocation computes geographic information for the data points in the Level 1A; and the Level 1B computes geolocated, calibrated radiances from the Level 1A and Geolocation products. One useful aspect of adapting the production software is the ability to incorporate enhancements contributed by the MODIS Science Team. We have therefore tried to limit changes to the software. However, in order to process the data immediately on receipt, we have taken advantage of a branch in the geolocation software that reads orbit and altitude information from the packets themselves, rather than external ancillary files used in standard production. We have also verified that the algorithms can be run with smaller time increments (2.5 minutes) than the five-minute increments used in production. To make the code easier to build and run, we have simplified directories and build scripts. Also, dependencies on a commercial numerics library have been replaced by public domain software. A version of the adapted code has been released for Silicon Graphics machines running lrix. Perhaps owing to its origin in production, the software is rather CPU-intensive. Consequently, a port to Linux is underway, followed by a version to run on PC clusters, with an eventual goal of running in near-real-time (i.e., process a ten-minute pass in ten minutes).

Lynnes, Christopher↗
NASA NTRS2002

Large 0/12 GMT Differences of US Vaisala RS80 Observations

Large differences been observations taken at 0 and 12 GMT have been revealed during routine monitoring of observations at the Data Assimilation Office (DAO) at NASA's Goddard Space Flight Center (GSFC). As a result, an investigation has been conducted to confirm the large differences and isolate its source. The data clearly shows that 0/12 GMT differences are largely artificial especially over the central US and that the differences largely originate in the post processing software at the observing stations. In particular, the release time of the rawinsonde balloon may be misspecified to be the synoptic time which would lead to the miscalculation of the bias correction that accounts for solar radiation effects on the thermistor.

Atlas, Robert↗
NASA NTRS2001

Medium Fidelity Simulation of Oxygen Tank Venting

The item to he cleared is a medium-fidelity software simulation model of a vented cryogenic tank. Such tanks are commonly used to transport cryogenic liquids such as liquid oxygen via truck, and have appeared on liquid-fueled rockets for decades. This simulation model works with the HCC simulation system that was developed by Xerox PARC and NASA Ames Research Center. HCC has been previously cleared for distribution. When used with the HCC software, the model generates simulated readings for the tank pressure and temperature as the simulated cryogenic liquid boils off and is vented. Failures (such as a broken vent valve) can be injected into the simulation to produce readings corresponding to the failure. Release of this simulation will allow researchers to test their software diagnosis systems by attempting to diagnose the simulated failure from the simulated readings. This model does not contain any encryption software nor can it perform any control tasks that might be export controlled.

Sweet, Adam↗
NASA NTRS2008

User's Manual for LEWICE Version 3.2

A research project is underway at NASA Glenn to produce a computer code which can accurately predict ice growth under a wide range of meteorological conditions for any aircraft surface. This report will present a description of the code inputs and outputs from version 3.2 of this software, which is called LEWICE. This version differs from release 2.0 due to the addition of advanced thermal analysis capabilities for de-icing and anti-icing applications using electrothermal heaters or bleed air applications, the addition of automated Navier-Stokes analysis, an empirical model for supercooled large droplets (SLD) and a pneumatic boot option. An extensive effort was also undertaken to compare the results against the database of electrothermal results which have been generated in the NASA Glenn Icing Research Tunnel (IRT) as was performed for the validation effort for version 2.0. This report will primarily describe the features of the software related to the use of the program. Appendix A has been included to list some of the inner workings of the software or the physical models used. This information is also available in the form of several unpublished documents internal to NASA. This report is intended as a replacement for all previous user manuals of LEWICE. In addition to describing the changes and improvements made for this version, information from previous manuals may be duplicated so that the user will not need to consult previous manuals to use this software.

Wright, William↗
NASA NTRS2018

VCCT with Progressive Nodal Release for Simulating Mixed-Mode Delamination: Formulation, Algorithmic Improvements and Implications

To simulate the propagation of cracks using the Virtual Crack Closure Technique (VCCT), intermediate crack positions between existing node pairs can be modeled by progressively releasing the nodes using fracture mechanics principles. This approach has been implemented in commercial software and can be applied to simulate delamination growth. Recent research has provided insight into the synchronized mixed mode nodal release, extending and formalizing the methodology for delamination growth. This paper documents the development of the Jacobians associated with delamination propagation under quasi-static mixed-mode conditions, leading to improvements in convergence of the implicit nonlinear solvers used.

Mabson, G. E.↗
NASA NTRS2018

VCCT with Progressive Nodal Release for Simulating Mixed-Mode Delamination: Formulation, Algorithmic Improvements and Implications

To simulate the propagation of cracks using the Virtual Crack Closure Technique (VCCT), intermediate crack positions between existing node pairs can be modeled by progressively releasing the nodes using fracture mechanics principles. This approach has been implemented in commercial software and can be applied to simulate delamination growth. Recent research has provided insight into the synchronized mixed mode nodal release, extending and formalizing the methodology for delamination growth. This paper documents the development of the Jacobians associated with delamination propagation under quasi-static mixed-mode conditions, leading to improvements in convergence of the implicit nonlinear solvers used.

G E Mabson↗
NASA NTRS2012

pyam: Python Implementation of YaM

pyam is a software development framework with tools for facilitating the rapid development of software in a concurrent software development environment. pyam provides solutions for development challenges associated with software reuse, managing multiple software configurations, developing software product lines, and multiple platform development and build management. pyam uses release-early, release-often development cycles to allow developers to integrate their changes incrementally into the system on a continual basis. It facilitates the creation and merging of branches to support the isolated development of immature software to avoid impacting the stability of the development effort. It uses modules and packages to organize and share software across multiple software products, and uses the concepts of link and work modules to reduce sandbox setup times even when the code-base is large. One sidebenefit is the enforcement of a strong module-level encapsulation of a module s functionality and interface. This increases design transparency, system stability, and software reuse. pyam is written in Python and is organized as a set of utilities on top of the open source SVN software version control package. All development software is organized into a collection of modules. pyam packages are defined as sub-collections of the available modules. Developers can set up private sandboxes for module/package development. All module/package development takes place on private SVN branches. High-level pyam commands support the setup, update, and release of modules and packages. Released and pre-built versions of modules are available to developers. Developers can tailor the source/link module mix for their sandboxes so that new sandboxes (even large ones) can be built up easily and quickly by pointing to pre-existing module releases. All inter-module interfaces are publicly exported via links. A minimal, but uniform, convention is used for building modules.

Myint, Steven↗
NASA NTRS2008

Space Telecommunications Radio Systems (STRS) Hardware Architecture Standard: Release 1.0 Hardware Section

This report defines a hardware architecture approach for software-defined radios to enable commonality among NASA space missions. The architecture accommodates a range of reconfigurable processing technologies including general-purpose processors, digital signal processors, field programmable gate arrays, and application-specific integrated circuits (ASICs) in addition to flexible and tunable radiofrequency front ends to satisfy varying mission requirements. The hardware architecture consists of modules, radio functions, and interfaces. The modules are a logical division of common radio functions that compose a typical communication radio. This report describes the architecture details, the module definitions, the typical functions on each module, and the module interfaces. Tradeoffs between component-based, custom architecture and a functional-based, open architecture are described. The architecture does not specify a physical implementation internally on each module, nor does the architecture mandate the standards or ratings of the hardware used to construct the radios.

Reinhart, Richard C.↗