Search NASA⌕ Search

SEARCH · Search NASA

Results for “Architecture Development”

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 577 records · Page 32

The NOAA Satellite Observing System Architecture Study

NOAA is beginning a study, the NOAA Satellite Observing System Architecture (NSOSA) study, to plan for the future operational environmental satellite system that will follow GOES and JPSS, beginning about 2030. This is an opportunity to design a modern architecture with no pre-conceived notions regarding instruments, platforms, orbits, etc. The NSOSA study will develop and evaluate architecture alternatives to include partner and commercial alternatives that are likely to become available. The objectives will include both functional needs and strategic characteristics (e.g., flexibility, responsiveness, sustainability). Part of this study is the Space Platform Requirements Working Group (SPRWG), which is being commissioned by NESDIS. The SPRWG is charged to assess new or existing user needs and to provide relative priorities for observational needs in the context of the future architecture. SPRWG results will serve as input to the process for new foundational (Level 0 and Level 1) requirements for the next generation of NOAA satellites that follow the GOES-R, JPSS, DSCOVR, Jason-3, and COSMIC-2 missions.

Value Model↗

Integrating Upper Class E Traffic Management (ETM) Operations into the National Airspace System: Use Cases and Research Questions

As new categories of vehicles are introduced in the National Airspace System, so too are novel concepts for a cooperative approach to traffic management environments. One of these new environments, Upper Class E Traffic Management (ETM), is expected to include a variety of high altitude, long endurance vehicles with a range of performance capabilities and mission profiles that operate in cooperative areas above 60,000 feet. In addition to developing the rules, architecture, and systems for operations within the ETM environment itself, it is also important to consider how ETM vehicles will integrate with traditional Air Traffic Management and interact with Air Traffic Control (ATC) as they traverse ATC-controlled airspace and transition in and out of cooperative ETM operating areas. As a first step toward future ETM demonstrations at the National Aeronautics and Space Administration (NASA) Ames Research Center’s Airspace Operations Laboratory, use cases with step-by-step procedures were developed to identify both nominal and off-nominal scenarios in which ETM operations will interact with ATC. As NASA prepares to develop a simulation platform to demonstrate ETM cooperative practices and ETM-ATC interactions, the procedures, ATC roles and responsibilities, data exchange requirements, and research questions that were identified as part of use case development will inform scenario and system architecture design. The upcoming simulation work will include initial prototype ETM-ATC coordination tools to support ATC controllers’ interactions with ETM operations. This paper will briefly discuss NASA’s upcoming ETM development work and then provide background on ETM-ATC interactions, describe each ETM-ATC interaction use case, and discuss open questions on concept, procedures, and assumptions.

ATC↗

Integrating Upper Class E Traffic Management (ETM) Operations into the National Airspace System: Use Cases and Research Questions

As new categories of vehicles are introduced in the National Airspace System, so too are novel concepts for a cooperative approach to traffic management environments. One of these new environments, Upper Class E Traffic Management (ETM), is expected to include a variety of high altitude, long endurance vehicles with a range of performance capabilities and mission profiles that operate in cooperative areas above 60,000 feet. In addition to developing the rules, architecture, and systems for operations within the ETM environment itself, it is also important to consider how ETM vehicles will integrate with traditional Air Traffic Management and interact with Air Traffic Control (ATC) as they traverse ATC-controlled airspace and transition in and out of cooperative ETM operating areas. As a first step toward future ETM demonstrations at the National Aeronautics and Space Administration (NASA) Ames Research Center’s Airspace Operations Laboratory, use cases with step-by-step procedures were developed to identify both nominal and off-nominal scenarios in which ETM operations will interact with ATC. As NASA prepares to develop a simulation platform to demonstrate ETM cooperative practices and ETM-ATC interactions, the procedures, ATC roles and responsibilities, data exchange requirements, and research questions that were identified as part of use case development will inform scenario and system architecture design. The upcoming simulation work will include initial prototype ETM-ATC coordination tools to support ATC controllers’ interactions with ETM operations. This paper will briefly discuss NASA’s upcoming ETM development work and then provide background on ETM-ATC interactions, describe each ETM-ATC interaction use case, and discuss open questions on concept, procedures, and assumptions.

ATC↗

An MBSE Approach to Space Suit Development

The EVA/Space Suit Development Office (ESSD) Systems Engineering and Integration (SE&I) team has utilized MBSE in multiple programs. After developing operational and architectural models, the MBSE framework was expanded to link the requirements space to the system models through functional analysis and interfaces definitions. By documenting all the connections within the technical baseline, ESSD experienced significant efficiency improvements in analysis and identification of change impacts. One of the biggest challenges presented to the MBSE structure was a program transition and restructuring effort, which was completed successfully in 4 months culminating in the approval of a new EVA Technical Baseline. During this time three requirements sets spanning multiple DRMs were streamlined into one NASA-owned Systems Requirement Document (SRD) that successfully identified requirements relevant to the current hardware development effort while remaining extensible to support future hardware developments. A capability-based hierarchy was established to provide a more flexible framework for future space suit development that can support multiple programs with minimal rework of basic EVA/Space Suit requirements. This MBSE approach was most recently applied for generation of an EMU Demonstrator technical baseline being developed for an ISS DTO. The relatively quick turnaround of operational concepts, architecture definition, and requirements for this new suit development has allowed us to test and evolve the MBSE process and framework in an extremely different setting while still offering extensibility and traceability throughout ESSD projects. The ESSD MBSE framework continues to be evolved in order to support integration of all products associated with the SE&I engine.

Cordova, Lauren↗

Creating Communications, Computing, and Networking Technology Development Road Maps for Future NASA Human and Robotic Missions

For human and robotic exploration missions in the Vision for Exploration, roadmaps are needed for capability development and investments based on advanced technology developments. A roadmap development process was undertaken for the needed communications, and networking capabilities and technologies for the future human and robotics missions. The underlying processes are derived from work carried out during development of the future space communications architecture, an d NASA's Space Architect Office (SAO) defined formats and structures for accumulating data. Interrelationships were established among emerging requirements, the capability analysis and technology status, and performance data. After developing an architectural communications and networking framework structured around the assumed needs for human and robotic exploration, in the vicinity of Earth, Moon, along the path to Mars, and in the vicinity of Mars, information was gathered from expert participants. This information was used to identify the capabilities expected from the new infrastructure and the technological gaps in the way of obtaining them. We define realistic, long-term space communication architectures based on emerging needs and translate the needs into interfaces, functions, and computer processing that will be required. In developing our roadmapping process, we defined requirements for achieving end-to-end activities that will be carried out by future NASA human and robotic missions. This paper describes: 10 the architectural framework developed for analysis; 2) our approach to gathering and analyzing data from NASA, industry, and academia; 3) an outline of the technology research to be done, including milestones for technology research and demonstrations with timelines; and 4) the technology roadmaps themselves.

Bhasin, Kul↗

Modular, Autonomous Command and Data Handling Software with Built-In Simulation and Test

The spacecraft system that plays the greatest role throughout the program lifecycle is the Command and Data Handling System (C&DH), along with the associated algorithms and software. The C&DH takes on this role as cost driver because it is the brains of the spacecraft and is the element of the system that is primarily responsible for the integration and interoperability of all spacecraft subsystems. During design and development, many activities associated with mission design, system engineering, and subsystem development result in products that are directly supported by the C&DH, such as interfaces, algorithms, flight software (FSW), and parameter sets. A modular system architecture has been developed that provides a means for rapid spacecraft assembly, test, and integration. This modular C&DH software architecture, which can be targeted and adapted to a wide variety of spacecraft architectures, payloads, and mission requirements, eliminates the current practice of rewriting the spacecraft software and test environment for every mission. This software allows missionspecific software and algorithms to be rapidly integrated and tested, significantly decreasing time involved in the software development cycle. Additionally, the FSW includes an Onboard Dynamic Simulation System (ODySSy) that allows the C&DH software to support rapid integration and test. With this solution, the C&DH software capabilities will encompass all phases of the spacecraft lifecycle. ODySSy is an on-board simulation capability built directly into the FSW that provides dynamic built-in test capabilities as soon as the FSW image is loaded onto the processor. It includes a six-degrees- of-freedom, high-fidelity simulation that allows complete closed-loop and hardware-in-the-loop testing of a spacecraft in a ground processing environment without any additional external stimuli. ODySSy can intercept and modify sensor inputs using mathematical sensor models, and can intercept and respond to actuator commands. ODySSy integration is unique in that it allows testing of actual mission sequences on the flight vehicle while the spacecraft is in various stages of assembly, test, and launch operations all without any external support equipment or simulators. The ODySSy component of the FSW significantly decreases the time required for integration and test by providing an automated, standardized, and modular approach to integrated avionics and component interface and functional verification. ODySSy further provides the capability for on-orbit support in the form of autonomous mission planning and fault protection.

Cuseo, John↗

SIM Configuration Evolution

The Space Interferometry Mission (SIM) is a space-based 10 m baseline Michelson interferometer. Planned for launch in 2005 aboard a Delta III launch vehicle, or equivalent, its primary objective is to measure the positions of stars and other celestial objects with an unprecedented accuracy of 4 micro arc seconds. With such an instrument, tremendous advancement can be expected in our understanding of stellar and galactic dynamics. Using triangulation from opposite sides of the orbit around the sun (i.e. by using parallax) one can measure the distance to any observable object in our galaxy. By directly measuring the orbital wobble of nearby stars, the mass and orbit of planets can be determined over a wide range of parameters. The distribution of velocity within nearby galaxies will be measurable. Observations of these and other objects will improve the calibration of distance estimators by more than an order of magnitude. This will permit a much better determination of the Hubble Constant as well as improving our overall understanding of the evolution of the universe. SIM has undergone several transformations, especially over the past year and a half since the start of Phase A. During this phase of a project, it is desirable to perform system-level trade studies, so the substantial evolution of the design that has occurred is quite appropriate. Part of the trade-off process has addressed two major underlying architectures: SIM Classic; and Son of SIM. The difference between these two architectures is related to the overall arrangement of the optical elements and the associated metrology system. Several different configurations have been developed for each architecture. Each configuration is the result of design choices that are influenced by many competing considerations. Some of the more important aspects will be discussed. The Space Interferometry Mission has some extremely challenging goals: millikelvin thermal stability, nanometer stabilization of optics, picometer measurement of wavefront, and others. In order to meet these goals, a significant amount of technological development is required. Although there has been a program operating for about a decade developing technologies specifically to address the challenges of space-based interferometry, there still remains a tremendous effort to achieve the incredible accuracy required of SIM. The projected viability of some of these areas has influenced design choices during the evolution of the many configurations that have been developed. For instance, the perceived complexity of the IR laser metrology system used to measure and control the positions of key optical elements was the strongest discriminator between the two architectures, and led to a decision to select SOS rather than Classic in early 1998. More recently, an appreciation of the sensitivity to beam-walk within the SOS architecture is forcing a reconsideration of that decision. At the time of submission of this abstract, there is some hope that a full-aperture metrology system may alleviate this issue. In addition to describing the current configuration of SIM, the influence of a few selected areas on the evolution of the configuration will be discussed.

Aaron, Kim M.↗

Re-Engineering Complex Legacy Systems at NASA

The Flight Production Process (FPP) Re-engineering project has established a Model-Based Systems Engineering (MBSE) methodology and the technological infrastructure for the design and development of a reference, product-line architecture as well as an integrated workflow model for the Mission Operations System (MOS) for human space exploration missions at NASA Johnson Space Center. The design and architectural artifacts have been developed based on the expertise and knowledge of numerous Subject Matter Experts (SMEs). The technological infrastructure developed by the FPP Re-engineering project has enabled the structured collection and integration of this knowledge and further provides simulation and analysis capabilities for optimization purposes. A key strength of this strategy has been the judicious combination of COTS products with custom coding. The lean management approach that has led to the success of this project is based on having a strong vision for the whole lifecycle of the project and its progress over time, a goal-based design and development approach, a small team of highly specialized people in areas that are critical to the project, and an interactive approach for infusing new technologies into existing processes. This project, which has had a relatively small amount of funding, is on the cutting edge with respect to the utilization of model-based design and systems engineering. An overarching challenge that was overcome by this project was to convince upper management of the needs and merits of giving up more conventional design methodologies (such as paper-based documents and unwieldy and unstructured flow diagrams and schedules) in favor of advanced model-based systems engineering approaches.

Ruszkowski, James↗

Development of a Subcell Based Modeling Approach for Modeling the Architecturally Dependent Impact Response of Triaxially Braided Polymer Matrix Composites

Understanding the high velocity impact response of polymer matrix composites with complex architectures is critical to many aerospace applications, including engine fan blade containment systems where the structure must be able to completely contain fan blades in the event of a blade-out. Despite the benefits offered by these materials, the complex nature of textile composites presents a significant challenge for the prediction of deformation and damage under both quasi-static and impact loading conditions. The relatively large mesoscale repeating unit cell (in comparison to the size of structural components) causes the material to behave like a structure rather than a homogeneous material. Impact experiments conducted at NASA Glenn Research Center have shown the damage patterns to be a function of the underlying material architecture. Traditional computational techniques that involve modeling these materials using smeared homogeneous, orthotropic material properties at the macroscale result in simulated damage patterns that are a function of the structural geometry, but not the material architecture. In order to preserve heterogeneity at the highest length scale in a robust yet computationally efficient manner, and capture the architecturally dependent damage patterns, a previously-developed subcell modeling approach where the braided composite unit cell is approximated as a series of four adjacent laminated composites is utilized. This work discusses the implementation of the subcell methodology into the commercial transient dynamic finite element code LS-DYNA (Livermore Software Technology Corp.). Verification and validation studies are also presented, including simulation of the tensile response of straight-sided and notched quasi-static coupons composed of a T700/PR520 triaxially braided [0deg/60deg/-60deg] composite. Based on the results of the verification and validation studies, advantages and limitations of the methodology as well as plans for future work are discussed.

finite element method↗

Medical System Concept of Operations for Mars Exploration Mission-11: Exploration Medical Capability (ExMC) Element - Human Research Program

NASA’s exploration missions to Mars will have durations of 2-3 years and will take humans farther away from Earth than ever before. This will result in a paradigm shift for mission planning, spacecraft design, human systems integration, and in-flight medical care. Constraints on real-time communication, resupply, and medical evacuation are major architectural drivers. These constraints require medical system development to be tightly integrated with mission and vehicle design to provide crew autonomy and enable mission success. This concept of operations provides a common vision of medical care for developing a medical system for Mars exploration missions. It documents an overview of the stakeholder needs and goals of a medical system and provides examples of the types of activities the system will be used for during the mission. Development of the concept of operations considers mission variables such as distance from Earth, duration of mission, time to definitive medical care, communication protocols between crewmembers and ground support, personnel capabilities and skill sets, medical hardware and software, and medical data management. The information provided in this document informs the ExMC Systems Engineering effort to define the functions to be provided by the medical system. In addition, this concept of operations will inform the subsequent systems engineering process of developing technical requirements, system architectures, interfaces, and verification and validation approaches for the medical system. This document supports the closure of ExMC Gap Med01: We do not have a concept of operations for medical care during exploration missions, corresponding to the ExMC-managed human system risk: Risk of Adverse Health Outcomes & Decrements in Performance due to Inflight Medical Conditions. This document is applicable to the ExMC Element Systems Engineering process and may be used for collaboration within the Human Research Program.

Urbina, Michelle↗

Programming model for distributed intelligent systems

A programming model and architecture which was developed for the design and implementation of complex, heterogeneous measurement and control systems is described. The Multigraph Architecture integrates artificial intelligence techniques with conventional software technologies, offers a unified framework for distributed and shared memory based parallel computational models and supports multiple programming paradigms. The system can be implemented on different hardware architectures and can be adapted to strongly different applications.

Sztipanovits, J.↗

Space Network IP Services (SNIS): An Architecture for Supporting Low Earth Orbiting IP Satellite Missions

The NASA Space Network (SN) supports a variety of missions using the Tracking and Data Relay Satellite System (TDRSS), which includes ground stations in White Sands, New Mexico and Guam. A Space Network IP Services (SNIS) architecture is being developed to support future users with requirements for end-to-end Internet Protocol (IP) communications. This architecture will support all IP protocols, including Mobile IP, over TDRSS Single Access, Multiple Access, and Demand Access Radio Frequency (RF) links. This paper will describe this architecture and how it can enable Low Earth Orbiting IP satellite missions.

Israel, David J.↗

An Open Specification for Space Project Mission Operations Control Architectures

An 'open specification' for Space Project Mission Operations Control Architectures is under development in the Spacecraft Control Working Group of the American Institute for Aeronautics and Astro- nautics. This architecture identifies 5 basic elements incorporated in the design of similar operations systems: Data, System Management, Control Interface, Decision Support Engine, & Space Messaging Service.

spacecraft ground systems↗

Reducing the Risk of Human Missions to Mars Through Testing

During the summer of 2002 the NASA Deputy Administrator charted an internal NASA planning group to develop the rationale for exploration beyond low-Earth orbit. This team, termed the Exploration Blueprint, performed architecture analyses to develop roadmaps for how to accomplish the first steps beyond Low-Earth Orbit through the human exploration of Mars. The previous NASA Exploration Team (NEXT) activities laid the foundation and framework for development of NASA s Integrated Space Plan. The reference missions resulting from the analysis performed by the Exploration Blueprint team formed the basis for requirement definition, systems development, technology roadmapping, and risk assessments for future human exploration beyond low-Earth orbit. Emphasis was placed on developing recommendations on what could be done now to effect future exploration activities. The Exploration Blueprint team embraced the Stepping Stone approach to exploration where human and robotic activities are conducted through progressive expansion outward beyond low- Earth orbit. Results from this study produced a long-term strategy for exploration with near-term implementation plans, program recommendations, and technology investments. Specific results included the development of a common exploration crew vehicle concept, a unified space nuclear strategy, focused bioastronautics research objectives, and an integrated human and robotic exploration strategy. Recommendations from the Exploration Blueprint included the endorsement of the Nuclear Systems Initiative, augmentation of the bioastronautics research, a focused space transportation program including heavy-lift launch and a common exploration vehicle design for ISS and exploration missions, as well as an integrated human and robotic exploration strategy for Mars. Following the results of the Exploration Blueprint study, the NASA Administrator has asked for a recommendation by June, 2003 on the next steps in human and robotic exploration in order to put into context an updated Integrated Space Transportation Plan (post- Columbia) and guide Agency planning. NASA was on the verge of committing significant funding in programs that would be better served if longer term goals were better known including the Orbital Space Plane, research on the ISS, National Aerospace Initiative, Shuttle Life Extension Program, Project Prometheus, as well as a wide range of technology development throughout the Agency. Much of the focus during this period was on integrating the results from the previous studies into more concrete implementation strategies in order to understand the relationship between NASA programs, timing, and resulting budgetary implications. This resulted in an integrated approach including lunar surface operations to retire risk of human Mars missions, maximum use of common and modular systems including what was termed the exploration transfer vehicle, Earth orbit and lunar surface demonstrations of long-life systems, collaboration of human and robotic missions to vastly increase mission return, and high-efficiency transportation systems (nuclear) for deep-space transportation and power. The data provided in this summary viewgraph presentation was developed to begin to address one of the key elements of the emerging implementation strategy, namely how lunar missions help retire risk of human missions to Mars. During this process the scope of the activity broadened into the issue of how testing in general, in various venues including the Moon, can help reduce the risk for Mars missions.

Drake, Bret G.↗

Microservice Architecture for Cognitive Networks

This develops the concept of a cognitive network and describes a microservice based architecture which could be used to implement such a system. Delay tolerant networking (DTN) influences the design of the architecture as well as the networking scenarios that the system attempts to address. A cognitive storage and fragmentation service is developed based on existing artificial intelligence techniques such as Advantage Actor Critic (A2C) and Deep Q-Networks. The system is simulated using OpenAI Gym in a custom developed DTN environment.

cognitive networks↗

Digital optical computers at the optoelectronic computing systems center

The Digital Optical Computing Program within the National Science Foundation Engineering Research Center for Opto-electronic Computing Systems has as its specific goal research on optical computing architectures suitable for use at the highest possible speeds. The program can be targeted toward exploiting the time domain because other programs in the Center are pursuing research on parallel optical systems, exploiting optical interconnection and optical devices and materials. Using a general purpose computing architecture as the focus, we are developing design techniques, tools and architecture for operation at the speed of light limit. Experimental work is being done with the somewhat low speed components currently available but with architectures which will scale up in speed as faster devices are developed. The design algorithms and tools developed for a general purpose, stored program computer are being applied to other systems such as optimally controlled optical communication networks.

Jordan, Harry F.↗

SMEX-Lite Modular Solar Array Architecture

For the most part, Goddard solar arrays have been custom designs that are unique to each mission. The solar panel design has been frozen prior to issuing an RFP for their procurement. There has typically been 6-9 months between RFP release and contract award, followed by an additional 24 months for performance of the contract. For Small Explorer (SMEX) missions, with three years between mission definition and launch, this has been a significant problem. The SMEX solar panels have been sufficiently small that the contract performance period has been reduced to 12-15 months. The bulk of this time is used up in the final design definition and fabrication of flight solar cell assemblies. Even so, it has been virtually impossible to have the spacecraft design at a level of maturity sufficient to freeze the solar panel geometry and release the RFP in time to avoid schedule problems with integrating the solar panels to the spacecraft. With that in mind, the SMEX-Lite project team developed a modular architecture for the assembly of solar arrays to greatly reduce the cost and schedule associated with the development of a mission- specific solar array. In the modular architecture, solar cells are fabricated onto small substrate panels. This modular panel (approximately 8.5" x 17" in this case) becomes the building block for constructing solar arrays for multiple missions with varying power requirements and geometrical arrangements. The mechanical framework that holds these modules together as a solar array is the only mission-unique design, changing in size and shape as required for each mission. There are several advantages to this approach. First, the typical solar array development cycle requires a mission unique design, procurement, and qualification including a custom qualification panel. With the modular architecture, a single qualification of the SMEX-Lite modules and the associated mechanical framework in a typical configuration provided a qualification by similarity to multiple missions. It then becomes possible to procure solar array modules in advance of mission definition and respond quickly and inexpensively to a selected mission's unique requirements. The solar array modular architecture allows the procurement of solar array modules before the array geometry has been frozen. This reduces the effect of procurement lead-time on the mission integration and test flow by as much as 50%. Second, by spreading the non-recurring costs over multiple missions, the cost per unit area is also reduced. In the case of the SMEX-Lite procurement, this reduction was by about one third of the cost per unit area compared to previous SMEX mission-unique procurements. Third, the modular architecture greatly facilitates the infusion of new solar cell technologies into flight programs as these technologies become available. New solar cell technologies need only be fabricated onto a standard-sized module to be incorporated into the next available mission. The modular solar array can be flown in a mixed configuration with some new and some standard cell technologies. Since each module has its own wiring terminals, the array can be arranged as desired electrically with little impact to cost and schedule. The solar array modular architecture does impose some additional constraints on systems and subsystem engineers. First, they must work with discrete solar array modules rather than size the array to fit exactly within an available envelope. The array area is constrained to an integer multiple of the module area. Second, the modular design is optimized for space radiation and thermal environments not greatly different from a typical SMEX LEO environment. For example, a mission with a highly elliptical orbit (e.g., Polar, SMEX/FAST) would require thicker coverglasses to protect the solar cells from the more intense radiation environment.

Lyons, John↗

What Multilevel Parallel Programs do when you are not Watching: A Performance Analysis Case Study Comparing MPI/OpenMP, MLP, and Nested OpenMP

With the current trend in parallel computer architectures towards clusters of shared memory symmetric multi-processors, parallel programming techniques have evolved that support parallelism beyond a single level. When comparing the performance of applications based on different programming paradigms, it is important to differentiate between the influence of the programming model itself and other factors, such as implementation specific behavior of the operating system (OS) or architectural issues. Rewriting-a large scientific application in order to employ a new programming paradigms is usually a time consuming and error prone task. Before embarking on such an endeavor it is important to determine that there is really a gain that would not be possible with the current implementation. A detailed performance analysis is crucial to clarify these issues. The multilevel programming paradigms considered in this study are hybrid MPI/OpenMP, MLP, and nested OpenMP. The hybrid MPI/OpenMP approach is based on using MPI [7] for the coarse grained parallelization and OpenMP [9] for fine grained loop level parallelism. The MPI programming paradigm assumes a private address space for each process. Data is transferred by explicitly exchanging messages via calls to the MPI library. This model was originally designed for distributed memory architectures but is also suitable for shared memory systems. The second paradigm under consideration is MLP which was developed by Taft. The approach is similar to MPi/OpenMP, using a mix of coarse grain process level parallelization and loop level OpenMP parallelization. As it is the case with MPI, a private address space is assumed for each process. The MLP approach was developed for ccNUMA architectures and explicitly takes advantage of the availability of shared memory. A shared memory arena which is accessible by all processes is required. Communication is done by reading from and writing to the shared memory.

Jost, Gabriele↗