Search NASA⌕ Search

SEARCH · Search NASA

Results for “Analysis 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 217 records · Page 12

Utility of the Virtual Liver Parenchymal Perfusion Area Using a Commercially Available Workstation in Transarterial Chemoembolization for Hepatocellular Carcinoma

Purpose: To evaluate the accuracy of the virtual liver parenchymal perfusion area using a commercially available workstation and liver analysis software in conventional transarterial chemoembolization (cTACE) for hepatocellular carcinoma (HCC). Materials and Methods: This method was retrospectively applied to 29 treated HCCs in 23 patients. The virtual embolic area (VEA) was estimated based on cone beam computed tomography during hepatic arteriography using a commercially available workstation and liver analysis software by two observer groups (group A: experts; group B: semi-experts). The real embolic area (REA) was defined as the area where iodized oil accumulated on computed tomography at 1 week after cTACE. The REA was estimated by each of the two groups, and the mean REA between the groups (mREA) was used as a standard reference. Agreement of volume and cross-sectional area in three orthogonal planes between the VEA and mREA were analyzed using intraclass correlation coefficients (ICCs) and Bland–Altman plots. Results: The ICCs for volume between VEA and mREA were 0.97 and 0.88 for groups A and B, respectively, and those for cross-sectional area were 0.94 and 0.88 for the axial plane, 0.95 and 0.83 for the coronal plane, and 0.87 and 0.74 for the sagittal plane, respectively. Thus, the overall agreement was excellent, except for the sagittal imaging plane in group B. Conclusion: This method using a commercially available workstation and liver analysis software can be useful for estimating the embolic area in cTACE.

62 RADIOLOGY AND NUCLEAR MEDICINE↗

Security Vulnerability Profiles of NASA Mission Software: Empirical Analysis of Security Related Bug Reports

NASA develops, runs, and maintains software systems for which security is of vital importance. Therefore, it is becoming an imperative to develop secure systems and extend the current software assurance capabilities to cover information assurance and cybersecurity concerns of NASA missions. The results presented in this report are based on the information provided in the issue tracking systems of one ground mission and one flight mission. The extracted data were used to create three datasets: Ground mission IVV issues, Flight mission IVV issues, and Flight mission Developers issues. In each dataset, we identified the software bugs that are security related and classified them in specific security classes. This information was then used to create the security vulnerability profiles (i.e., to determine how, why, where, and when the security vulnerabilities were introduced) and explore the existence of common trends. The main findings of our work include:- Code related security issues dominated both the Ground and Flight mission IVV security issues, with 95 and 92, respectively. Therefore, enforcing secure coding practices and verification and validation focused on coding errors would be cost effective ways to improve mission's security. (Flight mission Developers issues dataset did not contain data in the Issue Category.)- In both the Ground and Flight mission IVV issues datasets, the majority of security issues (i.e., 91 and 85, respectively) were introduced in the Implementation phase. In most cases, the phase in which the issues were found was the same as the phase in which they were introduced. The most security related issues of the Flight mission Developers issues dataset were found during Code Implementation, Build Integration, and Build Verification; the data on the phase in which these issues were introduced were not available for this dataset.- The location of security related issues, as the location of software issues in general, followed the Pareto principle. Specifically, for all three datasets, from 86 to 88 the security related issues were located in two to four subsystems.- The severity levels of most security issues were moderate, in all three datasets.- Out of 21 primary security classes, five dominated: Exception Management, Memory Access, Other, Risky Values, and Unused Entities. Together, these classes contributed from around 80 to 90 of all security issues in each dataset. This again proves the Pareto principle of uneven distribution of security issues, in this case across CWE classes, and supports the fact that addressing these dominant security classes provides the most cost efficient way to improve missions' security. The findings presented in this report uncovered the security vulnerability profiles and identified the common trends and dominant classes of security issues, which in turn can be used to select the most efficient secure design and coding best practices compiled by the part of the SARP project team associated with the NASA's Johnson Space Center. In addition, these findings provide valuable input to the NASA IVV initiative aimed at identification of the two 25 CWEs of ground and flight missions.

vulnerability↗

Information Extraction for System-Software Safety Analysis: Calendar Year 2007 Year-End Report

This annual report describes work to integrate a set of tools to support early model-based analysis of failures and hazards due to system-software interactions. The tools perform and assist analysts in the following tasks: 1) extract model parts from text for architecture and safety/hazard models; 2) combine the parts with library information to develop the models for visualization and analysis; 3) perform graph analysis on the models to identify possible paths from hazard sources to vulnerable entities and functions, in nominal and anomalous system-software configurations; 4) perform discrete-time-based simulation on the models to investigate scenarios where these paths may play a role in failures and mishaps; and 5) identify resulting candidate scenarios for software integration testing. This paper describes new challenges in a NASA abort system case, and enhancements made to develop the integrated tool set.

Malin, Jane T.↗

Information Extraction for System-Software Safety Analysis: Calendar Year 2008 Year-End Report

This annual report describes work to integrate a set of tools to support early model-based analysis of failures and hazards due to system-software interactions. The tools perform and assist analysts in the following tasks: 1) extract model parts from text for architecture and safety/hazard models; 2) combine the parts with library information to develop the models for visualization and analysis; 3) perform graph analysis and simulation to identify and evaluate possible paths from hazard sources to vulnerable entities and functions, in nominal and anomalous system-software configurations and scenarios; and 4) identify resulting candidate scenarios for software integration testing. There has been significant technical progress in model extraction from Orion program text sources, architecture model derivation (components and connections) and documentation of extraction sources. Models have been derived from Internal Interface Requirements Documents (IIRDs) and FMEA documents. Linguistic text processing is used to extract model parts and relationships, and the Aerospace Ontology also aids automated model development from the extracted information. Visualizations of these models assist analysts in requirements overview and in checking consistency and completeness.

Malin, Jane T.↗

Recent Advancements in Tomographic Gamma Scanning for Non- Destructive Assay - 17321

Canberra Industries has recently designed and built a Tomographic Gamma Scanning (TGS) system for the deployment in a nuclear facility. The TGS technique combines high-resolution gamma spectroscopy with low spatial resolution 3- dimensional image reconstruction to provide increased accuracy over traditional approaches for the assay of non-uniform source distributions in low-to medium-density containers. The TGS system has been optimized to measure 120 liter drums and has the capability to measure containers of various sizes. Canberra has incorporated numerous enhancements and improvements to the latest system in both its hardware and software components. The signal processing chain and data analysis software have been configured to use either an electronic pulser or digital signal processing (DSP) electronics for dead time corrections. In the case of using the DSP electronics, the need to calibrate and maintain a pulser can be eliminated without sacrificing any performance. For the 120 liter container, the TGS system has been calibrated and validated with three different spatial resolutions, using two collimator aperture sizes, measuring 2.54 and 1.27 cm in width. The system has also been supplied and calibrated with a wide, rectangular collimator (25.4 cm W x 10.2 cm H) for scanning containers solely in the vertical axis. The TGS system also has an automated attenuator assembly, which has the capability to use a combination of attenuators to reduce the count rate for high activity samples. An extensive measurement campaign was performed in addition to the calibration verification to evaluate the accuracy of the system using rod sources, point sources, and a variety of matrices and source distributions. Improvements to the evaluation of the total measurement uncertainty based upon these studies have been incorporated into the analysis software package. Finally, the performance of this new TGS system will be demonstrated in the context of Canberra's previous TGS systems, including several 208 liter-based systems and a smaller, 20 liter container TGS system. (authors)

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

Raster-scanning serial protein crystallography using micro- and nano-focused synchrotron beams

A raster scanning serial protein crystallography approach is presented, that consumes as low ∼200–700 nl of sedimented crystals. New serial data pre-analysis software, NanoPeakCell, is introduced. High-resolution structural information was obtained from lysozyme microcrystals (20 µm in the largest dimension) using raster-scanning serial protein crystallography on micro- and nano-focused beamlines at the ESRF. Data were collected at room temperature (RT) from crystals sandwiched between two silicon nitride wafers, thereby preventing their drying, while limiting background scattering and sample consumption. In order to identify crystal hits, new multi-processing and GUI-driven Python-based pre-analysis software was developed, named NanoPeakCell, that was able to read data from a variety of crystallographic image formats. Further data processing was carried out using CrystFEL, and the resultant structures were refined to 1.7 Å resolution. The data demonstrate the feasibility of RT raster-scanning serial micro- and nano-protein crystallography at synchrotrons and validate it as an alternative approach for the collection of high-resolution structural data from micro-sized crystals. Advantages of the proposed approach are its thriftiness, its handling-free nature, the reduced amount of sample required, the adjustable hit rate, the high indexing rate and the minimization of background scattering.

75 CONDENSED MATTER PHYSICS, SUPERCONDUCTIVITY AND↗

Geodetic Strain Analysis Tool

A geodetic software analysis tool enables the user to analyze 2D crustal strain from geodetic ground motion, and create models of crustal deformation using a graphical interface. Users can use any geodetic measurements of ground motion and derive the 2D crustal strain interactively. This software also provides a forward-modeling tool that calculates a geodetic velocity and strain field for a given fault model, and lets the user compare the modeled strain field with the strain field obtained from the user s data. Users may change parameters on-the-fly and obtain a real-time recalculation of the resulting strain field. Four data products are computed: maximum shear, dilatation, shear angle, and principal components. The current view and data dependencies are processed first. The remaining data products and views are then computed in a round-robin fashion to anticipate view changes. When an analysis or display parameter is changed, the affected data products and views are invalidated and progressively re-displayed as available. This software is designed to facilitate the derivation of the strain fields from the GPS and strain meter data that sample it to facilitate the understanding of the strengths and weaknesses of the strain field derivation from continuous GPS (CGPS) and other geodetic data from a variety of tectonic settings, to converge on the "best practices" strain derivation strategy for the Solid Earth Science ESDR System (SESES) project given the CGPS station distribution in the western U.S., and to provide SESES users with a scientific and educational tool to explore the strain field on their own with user-defined parameters.

Kedar, Sharon↗

User-Centered Design Guidelines for Collaborative Software for Intelligence Analysis

In this position paper we discuss the necessity of using User-Centered Design (UCD) methods in order to design collaborative software for the intelligence community. We present some standing issues in collaborative software based on existing work within the intelligence community. Based on this information we present opportunities to address some of these challenges.

collaboration↗

SoK: A Framework for and Analysis of Software Bill of Materials Tools

Modern software development has gradually become more complex, leveraging available open-source software and third party components. This practice has raised questions about the provenance, licensing, versioning and compliance of reused code and its dependencies. Furthermore, it is par ticularly important to review such code fragments and third party components for known-vulnerabilities before they are included in a software product. A Software Bill of Materials (SBoM) is a mechanism to achieve such an analysis, provid ing transparency and visibility into a software product to both the software developer and its respective consumer. An SBoM lists information and details about all the elements constituting a piece of software and can, therefore, be used to evaluate associated security risk. While the concept of SBoMs is growing in popularity, it is still fairly new to many organizations, causing them to potentially struggle with pro ducing and processing SBoMs and limiting their widespread adoption. In this work, we delve into the area of SBoMs and present the state-of-the-art SBoM tools, creating a framework for analysis and categorizing them based on a diverse set of features and functionalities. We are the first to provide a detailed analysis of 83 open-source SBoM tools along with a perspective on how a potential SBoM user can select a tool based on their specific requirements. Our work aims to help promote understanding of this domain, thereby encouraging and furthering its overall adoption. We additionally seek to pave a path for future work in this area by providing recommendations to tool developers and users, researchers, and standardizing organizations.

99 GENERAL AND MISCELLANEOUS↗

REPRESENTING COMMON-CAUSE FAILURES IN THE SAPHIRE SOFTWARE

Currently, the risk analysis software SAPHIRE has implemented a common-cause failure (CCF) module to represent standard CCF methods such as alpha-factor and multiple Greek letter approaches. However, changes to SAPHIRE are required to support the Nuclear Regulatory Commission’s 2007 “Risk Assessment Standardization Project” CCF analysis guidance for events assessment. This guidance provides an outline of how both the nominal CCF probabilities and conditional (e.g., after a redundant component has failed) CCF probabilities should be calculated. Based upon user-provided input and extending the limitations in the current version of SAPHIRE, the CCF module calculations will be made consistent with the new guidance. The CCF modifications will involve changes to (1) the SAPHIRE graphical user interface directing how end-users and modelers interface with PRA models and (2) algorithmic changes as required. Included in the modifications will be the possibility to treat CCF probability adjustments based upon failure types (e.g., independent versus dependent) and failure modes (e.g., failure-to-run versus failure-to-start). In general, SAPHIRE is being modified to allow the risk analyst to define a CCF object. This object is defined in terms of a basic event. For the CCF object, the analyst would need to specify a minimal set of information, including: - The number of redundant components - The failure criteria (how many component have to fail) - The CCF model type (alpha-factor, MGL, or beta-factor) - The parameters (e.g., the alpha-factors) associated with the model - Staggered or non-staggered testing assumption - Default level of detail (expanded, showing all of the specific failure combinations, or not) This paper will outline both the theory behind the probabilistic calculations and the resulting implementation in the SAPHIRE software.

97 MATHEMATICS AND COMPUTING↗

Preliminary calibration results for the BATSE instrument on CGRO

Preliminary results pertaining to spectral reconstruction using Burst and Transient Source (BATSE) Large Area Detector measurements of solar flares are presented. The solar flare measurements are currently being used to fine tune the calibration of our data analysis software. The current status of the stability of spectral analysis, given the systematic errors present in burst location, are given. A brief description is given of enhancements to the input data for the atmospheric scattering algorithm that will be implemented in the data analysis software.

Pendleton, G. N.↗

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.↗

Simulating response versus scan angle characterization on OCI for the upcoming PACE mission

The Plankton, Aerosol, Cloud ocean Ecosystem (PACE) mission Ocean Color Instrument (OCI) is the next generation ocean color sensor following on from the SeaWiFS and VIIRS designs, to be launched into low Earth orbit in 2022. Like those heritage sensors, OCI has cross track scanning fore-optics, the reflectivity of which (referred to here as the response versus scan angle or RVS) must be characterized prior to launch. The expected test setup, component reflectivity measurements, instrument model, and heritage sensor testing were used to generate simulated RVS data. This simulated data set was then used to verify the functionality of the analysis software in preparation for the upcoming ground test campaign. The analysis software is designed to characterize the RVS for all OCI bands over the full range of scan angles to be measured on orbit as well as verify compliance with the sensor design requirements in near real-time.

PACE↗

New developments and prospects on COSI, the simulation software for fuel cycle analysis

COSI, software developed by the Nuclear Energy Direction of the CEA, is a code simulating a pool of nuclear power plants with its associated fuel cycle facilities. This code has been designed to study various short, medium and long term options for the introduction of various types of nuclear reactors and for the use of associated nuclear materials. In the frame of the French Act for waste management, scenario studies are carried out with COSI, to compare different options of evolution of the French reactor fleet and options of partitioning and transmutation of plutonium and minor actinides. Those studies aim in particular at evaluating the sustainability of Sodium cooled Fast Reactors (SFR) deployment and the possibility to transmute minor actinides. The COSI6 version is a completely renewed software released in 2006. COSI6 is now coupled with the last version of CESAR (CESAR5.3 based on JEFF3.1.1 nuclear data) allowing the calculations on irradiated fuel with 200 fission products and 100 heavy nuclides. A new release is planned in 2013, including in particular the coupling with a recommended database of reactors. An exercise of validation of COSI6, carried out on the French PWR historic nuclear fleet, has been performed. During this exercise quantities like cumulative natural uranium consumption, or cumulative depleted uranium, or UOX/MOX spent fuel storage, or stocks of reprocessed uranium, or plutonium content in fresh MOX fuel, or the annual production of high level waste, have been computed by COSI6 and compared to industrial data. The results have allowed us to validate the essential phases of the fuel cycle computation, and reinforces the credibility of the results provided by the code.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

Data Analyst - A Device for Continuous Repeating Real-Time Assay of HPGe, CZT, or Scintillation Gamma Spectra - 18574

There are many situations where a continuous repeating series of quantitative gamma spectral assays is desirable. These include measurements of fluid going through a pipe, of items on a conveyor passing under a detector, a detector aimed at the ground on a moving platform, or a detector in free air as a plume of radioactivity drifts by. While Canberra and many others have built and deployed many of these devices, they have all been custom built for that particular application, and rather expensive. The Data Analyst [DA] is a general purpose device that is designed to fulfill many of these applications without modification, but can be fairly-easily modified if needed. The DA is a small [12 x 18 x 5 cm], low-power [3 W] box that accepts the input from external MCAs, controls the acquisition cycle, analyzes the results, and transmits them to the outside world when needed. The detector-MCAs supported are HPGe with Lynx MCA, NaI or CeBr or LaBr with Osprey MCA, and CZT or CsI with internal MCAs. The DA internal software used for analysis is the full standard Genie analysis software, which is very widely used and well accepted in the industry. This allows exported spectral files to be reviewed and confirmed by Experts, and reanalyzed if needed. The DA hardware is totally autonomous. As soon as power is applied, it starts the pre-programmed sequences of acquisition and analysis. Multiple analysis sequences [called Workflows] can be in operation simultaneously, e.g. with different count times and different nuclide libraries. Only the detector with MCA, and the DA are required in the field. A PC can be connected to the DA locally or remotely via WiFi, USB, or Ethernet. The PC is needed to setup the DA, and to readout the results. The DA also supports [with application-specific programming] external Inputs/Outputs either for recording with the analysis results or for use in the computation of the result, e.g. temperature, flow rate, pressure, ... ]. The DA also has an internal GPS receiver with external antenna. Applications of the DA that are discussed include stack gas effluent activity where a portion of the effluent stream was extracted to flow through a shield with a HPGe detector and Lynx MCA, and measurement of reactor coolant activity where a shielded CZT detector and MCA were aimed at various sections of reactor primary coolant during a maintenance outage. Potential other applications are also described. (author)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Detection of faults and software reliability analysis

Multiversion or N-version programming was proposed as a method of providing fault tolerance in software. The approach requires the separate, independent preparation of multiple versions of a piece of software for some application. Specific topics addressed are: failure probabilities in N-version systems, consistent comparison in N-version systems, descriptions of the faults found in the Knight and Leveson experiment, analytic models of comparison testing, characteristics of the input regions that trigger faults, fault tolerance through data diversity, and the relationship between failures caused by automatically seeded faults.

Knight, J. C.↗

High-Rate Delay Tolerant Networking (HDTN) Software Requirements Analysis

This document serves as a detailed analysis of the main networking protocols implemented by HDTN. Sources of the protocol specifications include Internet Engineering Task Force (IETF) Request for Comments (RFC) and Consultative Committee for Space Data Systems (CCSDS) standards. The focus of this report is to derive software requirements suitable for NASA Procedural Requirements 7150.2D Class B compliance, including requirements traceability and software verification and validation, from the source specifications. This analysis will be incorporated into the finalized HDTN Software Requirements Specification (SRS) but does not encompass the full scope of the HDTN SRS. Requirements in this document are considered draft. The complete requirements will include bundle application requirements, interface requirements, computer resource requirements, software quality factors, and additional requirements as determined by the project. This document is publicly released to the greater community to receive feedback and foster collaboration opportunities.

Rachel Dudukovich↗

Sample problems for Section III, Division 5 design by inelastic analysis of Grade 91 components

This report works through two sample design analyses of representative Grade 91 components using the ASME Boiler & Pressure Vessel Code Section III, Division 5, Appendix HBB-T rules for the strain and deformation and creep-fatigue design criteria using a design by inelastic analysis approach. The component geometries and loadings were selected to span a wide variety of potential applications. The sample components are an endplate geometry, which is fairly representative of typical pressure vessel construction, and a core block, representing a critical component in a heat pipe microreactor, which has a complicated geometry and complex thermal stress history. These sample problems serve several functions. First, they are complete worked examples of how to apply the current design by inelastic analysis rules. Second, they serve as test cases to evaluate the current rules and provide feedback on how they could be optimized to deal with complicated component geometries or to be better automated in modern finite element analysis software. Finally, the analysis here uses an inelastic constitutive model for Grade 91 developed by Argonne National Laboratory and proposed for inclusion in the ASME Boiler & Pressure Vessel Code Section III, Division 5 rules as a reference constitutive model. Using this constitutive model in the sample problem analyses tests the model in the context of the ASME Code rules. The final conclusions of this report are that the material model and the current Code rules are satisfactory, but that the Code rules could be optimized to simplify automation and reduce over conservatism. Future work should address the specific optimization topics discussed in this report.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗