Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “architecture design”

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 667 records · Page 37

NASA/BAE SYSTEMS SpaceWire Effort

This paper discusses the state of the NASA and BAE SYSTEMS developments of SpaceWire. NASA has developed intellectual property that implements SpaceWire in Register Transfer Level (RTL) VHDL for a SpaceWire link and router. This design has been extensively verified using directed tests from the SpaceWire Standard and design specification, as well as being randomly tested to flush out hard to find bugs in the code. The high level features of the design will be discussed, including the support for multiple time code masters, which will be useful for the James Webb Space Telescope electrical architecture. This design is now ready to be targeted to FPGA's and ASICs. Target utilization and performance information will be presented for Spaceflight worthy FPGA's and a discussion of the ASIC implementations will be addressed. In particular, the BAE SYSTEMS ASIC will be highlighted which will be implemented on their .25micron rad-hard line. The chip will implement a 4-port router with the ability to tie chips together to make larger routers without external glue logic. This part will have integrated LVDS drivers/receivers, include a PLL and include skew control logic. It will be targeted to run at greater than 300 MHz and include the implementation for the proposed SpaceWire transport layer. The need to provide a reliable transport mechanism for SpaceWire has been identified by both NASA And ESA, who are attempting to define a transport layer standard that utilizes a low overhead, low latency connection oriented approach that works end-to-end. This layer needs to be implemented in hardware to prevent bottlenecks.

Rakow, Glenn Parker↗

NASA/BAE Systems SpaceWire Efforts

This paper discusses the state of the NASA and BAE SYSTEMS developments using Spacewire. NASA has developed intellectual property that implements Spacewire in Register Transfer Level VHDL for a Spacewire link and router. This design has been extensively verified using directed tests from the Spacewire Standard and design specification, as well as being randomly tested to flush out hard to find bugs in the code. The high level features of the design will be discussed, including the support for multiple time code masters, which will be useful for the James Webb Space Telescope electrical architecture. This design is now ready to be targeted to FPGA's and ASICs. Target utilization and performance information will be presented for some spaceflight qualified FPGA's and a discussion of the ASIC implementations will be addressed. In particular, the BAE SYSTEMS ASIC will be highlighted which will be implemented in their 0.25 micron rad-hard line. The chip will implement a 4-port router with the ability to tie chips together to make larger routers without external glue logic. This part will have integrated LVDS driver/receivers, include a PLL and include skew control logic. It will be targeted to run at greater than 300 MHz and include the implementation for the proposed Spacewire transport layer. The need to provide a reliable transport mechanism for Spacewire has been identified by both NASA and ESA, who are attempting to define a transport layer standard that utilizes a low overhead, low latency connection oriented approach. The Transport layer needs to be implemented in hardware-to prevent bottlenecks.

Rakow, Glenn Parker↗

Configuring the Orion Guidance, Navigation, and Control Flight Software for Automated Sequencing

The Orion Crew Exploration Vehicle is being designed with greater automation capabilities than any other crewed spacecraft in NASA s history. The Guidance, Navigation, and Control (GN&C) flight software architecture is designed to provide a flexible and evolvable framework that accommodates increasing levels of automation over time. Within the GN&C flight software, a data-driven approach is used to configure software. This approach allows data reconfiguration and updates to automated sequences without requiring recompilation of the software. Because of the great dependency of the automation and the flight software on the configuration data, the data management is a vital component of the processes for software certification, mission design, and flight operations. To enable the automated sequencing and data configuration of the GN&C subsystem on Orion, a desktop database configuration tool has been developed. The database tool allows the specification of the GN&C activity sequences, the automated transitions in the software, and the corresponding parameter reconfigurations. These aspects of the GN&C automation on Orion are all coordinated via data management, and the database tool provides the ability to test the automation capabilities during the development of the GN&C software. In addition to providing the infrastructure to manage the GN&C automation, the database tool has been designed with capabilities to import and export artifacts for simulation analysis and documentation purposes. Furthermore, the database configuration tool, currently used to manage simulation data, is envisioned to evolve into a mission planning tool for generating and testing GN&C software sequences and configurations. A key enabler of the GN&C automation design, the database tool allows both the creation and maintenance of the data artifacts, as well as serving the critical role of helping to manage, visualize, and understand the data-driven parameters both during software development and throughout the life of the Orion project.

Odegard, Ryan G.↗

Modular Growth NTR Space Transportation System for Future NASA Human Lunar, NEA and Mars Exploration Missions

The nuclear thermal rocket (NTR) is a proven, high thrust propulsion technology that has twice the specific impulse (I(sub sp) approx.900 s) of today's best chemical rockets. During the Rover and NERVA (Nuclear Engine for Rocket Vehicle Applications) programs, twenty rocket reactors were designed, built and ground tested. These tests demonstrated: (1) a wide range of thrust; (2) high temperature carbide-based nuclear fuel; (3) sustained engine operation; (4) accumulated lifetime; and (5) restart capability - everything required for affordable human missions beyond LEO. In NASA's recent Mars Design Reference Architecture (DRA) 5.0 study, the NTR was selected as the preferred propulsion option because of its proven technology, higher performance, lower IMLEO, versatile vehicle design, and growth potential. Furthermore, the NTR requires no large technology scale-ups since the smallest engine tested during the Rover program - the 25 klb(sub f) "Pewee" engine is sufficient for human Mars missions when used in a clustered engine configuration. The "Copernicus" crewed Mars transfer vehicle developed for DRA 5.0 was an expendable design sized for fast-conjunction, long surface stay Mars missions. It therefore has significant propellant capacity allowing a reusable "1-year" round trip human mission to a large, high energy near Earth asteroid (NEA) like Apophis in 2028. Using a "split mission" approach, Copernicus and its two key elements - a common propulsion stage and integrated "saddle truss" and LH2 drop tank assembly - configured as an Earth Return Vehicle / propellant tanker, can also support a short round trip (approx.18 month) / short orbital stay (60 days) Mars reconnaissance mission in the early 2030's before a landing is attempted. The same short stay orbital mission can be performed with an "all-up" vehicle by adding an "in-line" LH2 tank to Copernicus to supply the extra propellant needed for this higher energy, opposition-class mission. To transition to a reusable Mars architecture, Copernicus' saddle truss / drop tank assembly is replaced by an in-line tank and "star truss" assembly with paired modular drop tanks to further increase the vehicle's propellant capacity. Shorter "1-way" transit time fast-conjunction Mars missions are another possibility using this vehicle configuration but, as with reusability, increased launch mass is required. "Scaled down" versions of Copernicus (sized to a SLS lift capability of approx.70 t - 100 t) can be developed initially allowing reusable lunar cargo delivery and crewed landing missions, easy NEA missions (e.g., 2000 SG344 also in 2028) or an expendable mission to Apophis. Mission scenario descriptions, key vehicle features and operational characteristics are provided along with a brief discussion of NASA's current activities and its "pre-decisional" plans for future NTR development.

Borowski, Stanley K.↗

The Planning Execution Monitoring Architecture

The Planning Execution Monitoring (PEM) architecture is a design concept for developing autonomous cockpit command and control software. The PEM architecture is designed to reduce the operations costs in the space transportation system through the use of automation while improving safety and operability of the system. Specifically, the PEM autonomous framework enables automatic performance of many vehicle operations that would typically be performed by a human. Also, this framework supports varying levels of autonomous control, ranging from fully automatic to fully manual control. The PEM autonomous framework interfaces with the core flight software to perform flight procedures. It can either assist human operators in performing procedures or autonomously execute routine cockpit procedures based on the operational context. Most importantly, the PEM autonomous framework promotes and simplifies the capture, verification, and validation of the flight operations knowledge. Through a hierarchical decomposition of the domain knowledge, the vehicle command and control capabilities are divided into manageable functional "chunks" that can be captured and verified separately. These functional units, each of which has the responsibility to manage part of the vehicle command and control, are modular, re-usable, and extensible. Also, the functional units are self-contained and have the ability to plan and execute the necessary steps for accomplishing a task based upon the current mission state and available resources. The PEM architecture has potential for application outside the realm of spaceflight, including management of complex industrial processes, nuclear control, and control of complex vehicles such as submarines or unmanned air vehicles.

Wang, Lui↗

A Standard Platform for Testing and Comparison of MDAO Architectures

The Multidisciplinary Design Analysis and Optimization (MDAO) community has developed a multitude of algorithms and techniques, called architectures, for performing optimizations on complex engineering systems which involve coupling between multiple discipline analyses. These architectures seek to efficiently handle optimizations with computationally expensive analyses including multiple disciplines. We propose a new testing procedure that can provide a quantitative and qualitative means of comparison among architectures. The proposed test procedure is implemented within the open source framework, OpenMDAO, and comparative results are presented for five well-known architectures: MDF, IDF, CO, BLISS, and BLISS-2000. We also demonstrate how using open source soft- ware development methods can allow the MDAO community to submit new problems and architectures to keep the test suite relevant.

Gray, Justin S.↗

Controller of the Laser Interferometer Space Antenna

The Laser Interferometer Space Antenna mission is a planned gravitational wave detector consisting of three spacecraft in heliocentric orbit. Laser interferometry is used to measure distance fluctuations between test masses aboard each spacecraft to the picometer level over a 5 million kilometer separation. The Disturbance Reduction System comprises the pointing and positioning control of the spacecraft, electrostatic suspension control of the test masses, and point-ahead and acquisition control. This paper presents a control architecture and design for the Disturbance Reduction System to meet the stringent pointing and positioning requirements. Simulations are performed to demonstrate the feasibility of the proposed architecture.

Hyde, T. T.↗

Medical Data Architecture (MDA) Project Status

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products supported by current prototype development will directly inform exploration medical system requirements.In fiscal year 2018, the MDA project developed Test Bed 2, the second iteration in a series of prototypes with functionality focused on data security through role-based access control and encryption, integration with One Portal exercise software and ingestion of an ultrasound Digital Imaging and Communications in Medicine (DICOM) file and image display. Test Bed 2 advances the medical data system architecture framework by providing these functionalities in a scalable system that maintained a layered, modular design. The architecture framework uses a data services approach with role-based access to data in a customized medical record system suitable for space exploration. These functionalities were demonstrated as part of the Next Space Technologies for Exploration Partnerships (NextSTEP) ground test demonstrated at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Interfacing to a Core Flight Software (CFS) system, the MDA system, using Consultative Committee for Space Data Systems (CCSDS) protocol, transferred an exercise file from the simulated flight MDA system to a mirrored MDA system on the ground through the CFS system. The selection of data sources and demonstrations enabled the team to address stakeholder concerns throughout the development process. In the next iteration, the MDA team will work with stakeholders to identify additional relevant functionalities to further advance system data models, standards and principles that will inform the medical system requirements development.

medical data architecture↗

Methods for evaluating integrated airframe/propulsion control system architectures

Methodology, analysis, and detailed design of integrated control system architectures suitable for high-performance aircraft of the 1990s are presented. A methodology, with supporting analytical tools, has been developed to provide system designers with the capability to specify candidate architectures and accurately predict their reliability and performance in the early stages of design development. The authors address the methodology and supporting tools.

Gerald C Cohen↗

The Readout Electronics of the Mu2e Electromagnetic Calorimeter

The Mu2e electromagnetic calorimeter has been designed to measure ~100 MeV electrons with energy resolution σE/E <10%, time resolution σt < 500ps and position resolution σx < 1cm. The detector is composed of 1348 un-doped CsI crystals coupled to two large area Silicon Photomultipliers (SiPMs). Each SiPM is connected to a Front End Electronics (FEE) chip which hosts the shaping amplifier and the high voltage linear regulator. A group of 20 FEE is controlled by one Mezzanine Board (MB) which transmits the amplified signals to one Digitizer ReAdout Controller board (DiRAC). The DiRAC samples the waveforms at 200 MHz with 12-bit ADCs, packs the data according to the Mu2e custom format and transmits them to the event builder through an optical transceiver. To limit the number of pass-through connectors and the length of the cables, the readout and digitization electronics is located inside the detector cryostat and close to the interaction target. The boards will have to sustain a neutron fluence of about 5x10 10 n/cm 2 @ 1 MeVeq (Si)/y and a Total Ionizing Dose of about 12 krad, while working into a 1T magnetic field and a vacuum of 10 (-4) Torr. This harsh operational environment has made the electronics design challenging and required an extended campaign of tests to select and qualify the employed electronic components. In this paper we report on the board architecture and design, on the qualification of the prototypes, as well as on the results of the first vertical slice test of the Mu2e calorimeter.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

An Architecture for Real-Time Interpretation and Visualization of Structural Sensor Data in a Laboratory Environment

A visualization system is being developed out of the need to monitor, interpret, and make decisions based on the information from several thousand sensors during experimental testing to facilitate development and validation of structural health monitoring algorithms. As an added benefit the system will enable complete real-time sensor assessment of complex test specimens. Complex structural specimens are routinely tested that have hundreds or thousands of sensors. During a test, it is impossible for a single researcher to effectively monitor all the sensors and subsequently interesting phenomena occur that are not recognized until post-test analysis. The ability to detect and alert the researcher to these unexpected phenomena as the test progresses will significantly enhance the understanding and utilization of complex test articles. Utilization is increased by the ability to halt a test when the health monitoring algorithm response is not satisfactory or when an unexpected phenomenon occurs, enabling focused investigation potentially through the installation of additional sensors. Often if the test continues, structural changes make it impossible to reproduce the conditions that exhibited the phenomena. The prohibitive time and costs associated with fabrication, sensoring, and subsequent testing of additional test articles generally makes it impossible to further investigate the phenomena. A scalable architecture is described to address the complex computational demands of structural health monitoring algorithm development and laboratory experimental test monitoring. The researcher monitors the test using a photographic quality 3D graphical model with actual sensor locations identified. In addition, researchers can quickly activate plots displaying time or load versus selected sensor response along with the expected values and predefined limits. The architecture has several key features. First, distributed dissimilar computers may be seamlessly integrated into the information flow. Second, virtual sensors may be defined that are complex functions of existing sensors or other virtual sensors. Virtual sensors represent a calculated value not directly measured by particular physical instrument. They can be used, for example, to represent the maximum difference in a range of sensors or the calculated buckling load based on the current strains. Third, the architecture enables autonomous response to preconceived events, where by the system can be configured to suspend or abort a test if a failure is detected in the load introduction system. Fourth, the architecture is designed to allow cooperative monitoring and control of the test progression from multiple stations both remote and local to the test system. To illustrate the architecture, a preliminary implementation is described monitoring the Stitched Composite Wing recently tested at LaRC.

Doggett, William↗

Nuclear Thermal Propulsion (NTP): A Proven Growth Technology for Human NEO/Mars Exploration Missions

The nuclear thermal rocket (NTR) represents the next "evolutionary step" in high performance rocket propulsion. Unlike conventional chemical rockets that produce their energy through combustion, the NTR derives its energy from fission of Uranium-235 atoms contained within fuel elements that comprise the engine s reactor core. Using an "expander" cycle for turbopump drive power, hydrogen propellant is raised to a high pressure and pumped through coolant channels in the fuel elements where it is superheated then expanded out a supersonic nozzle to generate high thrust. By using hydrogen for both the reactor coolant and propellant, the NTR can achieve specific impulse (Isp) values of ~900 seconds (s) or more - twice that of today s best chemical rockets. From 1955 - 1972, twenty rocket reactors were designed, built and ground tested in the Rover and NERVA (Nuclear Engine for Rocket Vehicle Applications) programs. These programs demonstrated: (1) high temperature carbide-based nuclear fuels; (2) a wide range of thrust levels; (3) sustained engine operation; (4) accumulated lifetime at full power; and (5) restart capability - all the requirements needed for a human Mars mission. Ceramic metal "cermet" fuel was pursued as well, as a backup option. The NTR also has significant "evolution and growth" capability. Configured as a "bimodal" system, it can generate its own electrical power to support spacecraft operational needs. Adding an oxygen "afterburner" nozzle introduces a variable thrust and Isp capability and allows bipropellant operation. In NASA s recent Mars Design Reference Architecture (DRA) 5.0 study, the NTR was selected as the preferred propulsion option because of its proven technology, higher performance, lower launch mass, versatile vehicle design, simple assembly, and growth potential. In contrast to other advanced propulsion options, no large technology scale-ups are required for NTP either. In fact, the smallest engine tested during the Rover program - the 25,000 lbf (25 klbf) "Pewee" engine is sufficient when used in a clustered engine arrangement. The "Copernicus" crewed spacecraft design developed in DRA 5.0 has significant capability and a human exploration strategy is outlined here that uses Copernicus and its key components for precursor near Earth object (NEO) and Mars orbital missions prior to a Mars landing mission. The paper also discusses NASA s current activities and future plans for NTP development that include system-level Technology Demonstrations - specifically ground testing a small, scalable NTR by 2020, with a flight test shortly thereafter.

Borowski, Stanley K.↗

Near Earth Asteroid Human Mission Possibilities Using Nuclear Thermal Rocket (NTR) Propulsion

The NTR is a proven technology that generates high thrust and has a specific impulse (Isp (is) approximately 900 s) twice that of today's best chemical rockets. During the Rover and NERVA (Nuclear Engine for Rocket Vehicle Applications) programs, twenty rocket reactors were designed, built and ground tested. These tests demonstrated: (1) a wide range of thrust; (2) high temperature carbide-based nuclear fuel; (3) sustained engine operation; (4) accumulated lifetime; and (5) restart capability - all the requirements needed for a human mission to Mars. Ceramic metal fuel was also evaluated as a backup option. In NASA's recent Mars Design reference Architecture (DRA) 5.0 study, the NTR was selected as the preferred propulsion option because of its proven technology, higher performance, lower launch mass, versatile vehicle design, simple assembly, and growth potential. In contrast to other advanced propulsion options, NTP requires no large technology scale-ups. In fact, the smallest engine tested during the Rover program - the 25 klbf 'Pewee' engine is sufficient for a human Mars mission when used in a clustered engine configuration. The 'Copernicus crewed NTR Mars transfer vehicle design developed for DRA 5.0 has significant capability that can enable reusable '1-year' round trip human missions to candidate near Earth asteroids (NEAs) like 1991 JW in 2027, or 2000 SG344 and Apophis in 2028. A robotic precursor mission to 2000 SG344 in late 2023 could provide an attractive Flight Technology Demonstration of a small NTR engine that is scalable to the 25 klbf-class engine used for human missions 5 years later. In addition to the detailed scientific data gathered from on-site inspection, human NEA missions would also provide a valuable 'check out' function for key elements of the NTR transfer vehicle (its propulsion module, TransHab and life support systems, etc.) in a 'deep space' environment prior to undertaking the longer duration Mars orbital and landing missions that would follow. The initial mass in low Earth orbit required for a mission to Apophis is approximately 323 t consisting of the NTR propulsion module ((is) approximately 138 t), the integrated saddle truss and LH2 drop tank assembly ((is) approximately 123 t), and the 6-crew payload element ((is) approximately 62 t). The later includes a multi-mission Space Excursion Vehicle (MMSEV) used for close-up examination and sample gathering. The total burn time and required restarts on the three 25 klbf 'Pewee-class' engines operating at Isp (is) approximately 906 s, are approximately 76.2 minutes and 4, respectively, well below the 2 hours and 27 restarts demonstrated on the NERVA eXperimental Engine, the NRX-XE. The paper examines the benefits, requirements and characteristics of using NTP for the above NEA missions. The impacts on vehicle design of HLV payload volume and lift capability, crew size, and reusability are also quantified.

Borowski, Stanley↗

Mission Options for an Electric Propulsion Demonstration Flight Test

Several mission options are discussed for an electric propulsion space test which provides operational and performance data for ion and arcjet propulsion systems and testing of APSA arrays and a super power system. The results of these top-level studies are considered preliminary. Ion propulsion system design and architecture for the purposes of performing orbit raising missions for payloads in the range of 2400 to 2700 kg are described. Focus was placed on a design which can be characterized by simplicity, reliability, and performance. Systems of this design are suitable for an electric propulsion precursor flight which would provide proof of principle data necessary for more ambitious and complex missions.

Garner, Charles↗

GFEChutes Lo-Fi

NASA needed to provide a software model of a parachute system for a manned re-entry vehicle. NASA has parachute codes, e.g., the Descent Simulation System (DSS), that date back to the Apollo Program. Since the space shuttle did not rely on parachutes as its primary descent control mechanism, DSS has not been maintained or incorporated into modern simulation architectures such as Osiris and Antares, which are used for new mission simulations. GFEChutes Lo-Fi is an object-oriented implementation of conventional parachute codes designed for use in modern simulation environments. The GFE (Government Furnished Equipment), low-fidelity (Lo-Fi) parachute model (GFEChutes Lo-Fi) is a software package capable of modeling the effects of multiple parachutes, deployed concurrently and/or sequentially, on a vehicle during the subsonic phase of reentry into planetary atmosphere. The term "low-fidelity" distinguishes models that represent the parachutes as simple forces acting on the vehicle, as opposed to independent aerodynamic bodies. GFEChutes Lo-Fi was created from these existing models to be clean, modular, certified as NASA Class C software, and portable, or "plug and play." The GFE Lo-Fi Chutes Model provides basic modeling capability of a sequential series of parachute activities. Actions include deploying the parachute, changing the reefing on the parachute, and cutting away the parachute. Multiple chutes can be deployed at any given time, but all chutes in that case are assumed to behave as individually isolated chutes; there is no modeling of any interactions between deployed chutes. Drag characteristics of a deployed chute are based on a coefficient of drag, the face area of the chute, and the local dynamic pressure only. The orientation of the chute is approximately modeled for purposes of obtaining torques on the vehicle, but the dynamic state of the chute as a separate entity is not integrated - the treatment is simply an approximation. The innovation in GFEChutes Lo-Fi is to use an object design that closely followed the mechanical characteristics and structure of a physical system of parachutes and their deployment mechanisms. Software objects represent the components of the system, and use of an object hierarchy allows a progression from general component outlines to specific implementations. These extra chutes were not part of the baseline deceleration sequence of drogues and mains, but still had to be simulated. The major innovation in GFEChutes Lo-Fi is the software design and architecture.

Gist, Emily↗

Mars-GRAM Support for the Mars Ascent Vehicle

Mars sample return is a bold concept, which entails gathering a varied, scientifically-relevant collection of Martian rock core samples and bringing them to Earth for analysis. To support this endeavor, the Marshall Space Flight Center (MSFC) is developing the Mars Ascent Vehicle (MAV), which is responsible for getting the collected samples off the planet. The MAV Preliminary Architecture Assessment (PAA) study is designing two vehicle architectures based on different propulsion configurations: a two-stage solid-solid concept, and a hybrid concept. Given different thrust profiles for the two configurations, each concept uses a unique trajectory to reach the same orbit. In support of the PAA, The MSFC Natural Environments Branch (EV44) was asked to produce tables of atmospheric parameters along each of the two trajectories. The Mars Global Reference Atmospheric Model (Mars-GRAM) is an EV44 tool that is ideally suited for this analysis. Mars-GRAM will continue supporting MAV development in future design cycles.

Burns, K. L.↗

VLSI processors for signal detection in SETI

The objective of the Search for Extraterrestrial Intelligence (SETI) is to locate an artificially created signal coming from a distant star. This is done in two steps: (1) spectral analysis of an incoming radio frequency band, and (2) pattern detection for narrow-band signals. Both steps are computationally expensive and require the development of specially designed computer architectures. To reduce the size and cost of the SETI signal detection machine, two custom VLSI chips are under development. The first chip, the SETI DSP Engine, is used in the spectrum analyzer and is specially designed to compute Discrete Fourier Transforms (DFTs). It is a high-speed arithmetic processor that has two adders, one multiplier-accumulator, and three four-port memories. The second chip is a new type of Content-Addressable Memory. It is the heart of an associative processor that is used for pattern detection. Both chips incorporate many innovative circuits and architectural features.

NASA Program Exobiology↗

Optimizing spacecraft design - optimization engine development : progress and plans

At JPL and NASA, a process has been developed to perform life cycle risk management. This process requires users to identify: goals and objectives to be achieved (and their relative priorities), the various risks to achieving those goals and objectives, and options for risk mitigation (prevention, detection ahead of time, and alleviation). Risks are broadly defined to include the risk of failing to design a system with adequate performance, compatibility and robustness in addition to more traditional implementation and operational risks. The options for mitigating these different kinds of risks can include architectural and design choices, technology plans and technology back-up options, test-bed and simulation options, engineering models and hardware/software development techniques and other more traditional risk reduction techniques.

risk↗