Search NASA⌕ Search

SEARCH · Search NASA

Results for “program architectures”

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 1,747 records · Page 97

Fifth NASA Goddard Conference on Mass Storage Systems and Technologies

This document contains copies of those technical papers received in time for publication prior to the Fifth Goddard Conference on Mass Storage Systems and Technologies held September 17 - 19, 1996, at the University of Maryland, University Conference Center in College Park, Maryland. As one of an ongoing series, this conference continues to serve as a unique medium for the exchange of information on topics relating to the ingestion and management of substantial amounts of data and the attendant problems involved. This year's discussion topics include storage architecture, database management, data distribution, file system performance and modeling, and optical recording technology. There will also be a paper on Application Programming Interfaces (API) for a Physical Volume Repository (PVR) defined in Version 5 of the Institute of Electrical and Electronics Engineers (IEEE) Reference Model (RM). In addition, there are papers on specific archives and storage products.

Kobler, Benjamin↗

Structures IVHM for 3rd Generation RLVs

The primary goal of a Structures Integrated Vehicle Health Management (IVHM) system for 3rd generation Reusable Launch Vehicles (RLV) is to provide near 100% structural sensing coverage and thus eliminate both routine, and especially unplanned, inspections which are costly and time consuming. To meet this goal, significant advances in sensing and measurement system technology, data systems architectures, and structures based analysis methodology will be required to enable the needed large numbers of sensors with little weight penalty. This program will leverage X-33, 2nd Gen RLV, Shuttle, and Aviation Safety SIVHM system development experience to address this goal.

Rogowski, Robert S.↗

In-situ Resource Utilization (ISRU) to Support the Lunar Outpost and the Rationale for Precursor Missions

One of the ways that the Constellation Program can differ from Apollo is to employ a live-off-the-land or In-Situ Resource Utilization (ISRU) supported architecture. The options considered over the past decades for using indigenous materials have varied considerably in terms of what resources to attempt to acquire, how much to acquire, and what the motivations are to acquiring these resources. The latest NASA concepts for supporting the lunar outpost have considered many of these plans and compared these options to customers requirements and desires. Depending on the architecture employed, ISRU technologies can make a significant contribution towards a sustainable and affordable lunar outpost. While extensive ground testing will reduce some mission risk, one or more flight demonstrations prior to the first crew's arrival will build confidence and increase the chance that outpost architects will include ISRU as part of the early outpost architecture. This presentation includes some of the options for using ISRU that are under consideration for the lunar outpost, the precursor missions that would support these applications, and a notional timeline to allow the lessons learned from the precursor missions to support outpost hardware designs.

Simon, Thomas M.↗

Recent Progress at NASA in LlSA Formulation and Technology Development

Over the last year, the NASA portion of the LISA team has been focused its effort on advancing the formulation of the mission and responding to a major National Academy review. This talk will describe advances in, and the current state of: the baseline mission architecture, the performance requirements, the technology development and plans for final integration and test. Interesting results stimulated by the NASINRC Beyond Einstein Program Assessment Review will also be described.

Stebbins, Robin↗

Ensemble: an Architecture for Mission-Operations Software

Ensemble is the name of an open architecture for, and a methodology for the development of, spacecraft mission operations software. Ensemble is also potentially applicable to the development of non-spacecraft mission-operations- type software. Ensemble capitalizes on the strengths of the open-source Eclipse software and its architecture to address several issues that have arisen repeatedly in the development of mission-operations software: Heretofore, mission-operations application programs have been developed in disparate programming environments and integrated during the final stages of development of missions. The programs have been poorly integrated, and it has been costly to develop, test, and deploy them. Users of each program have been forced to interact with several different graphical user interfaces (GUIs). Also, the strategy typically used in integrating the programs has yielded serial chains of operational software tools of such a nature that during use of a given tool, it has not been possible to gain access to the capabilities afforded by other tools. In contrast, the Ensemble approach offers a low-risk path towards tighter integration of mission-operations software tools.

Norris, Jeffrey↗

Modification of the International Space Station USOS to Support Installation and Activation of the Node 3 Element

The International Space Station (ISS) program is nearing an assembly complete configuration with the addition of the final resource node module in early 2010. The Node 3 module will provide critical functionality in support of permanent long duration crews aboard ISS. The new module will permanently house the regenerative Environment Control and Life Support Systems (ECLSS) and will also provide important habitability functions such as waste management and exercise facilities. The ISS program has selected the Port side of the Node 1 "Unity" module as the permanent location for Node 3 which will necessitate architecture changes to provide the required interfaces. The USOS ECLSS fluid and ventilation systems, Internal Thermal Control Systems, and Avionics Systems require significant modifications in order to support Node 3 interfaces at the Node 1 Port location since it was not initially designed for that configuration. This paper outlines the design, development, certification, and implementation of these changes in support of ISS assembly complete.

Link, Dwight E., Jr.↗

Lightning Tracking Tool for Assessment of Total Cloud Lightning within AWIPS II

Total lightning (intra‐cloud and cloud‐to‐ground) has been widely researched and shown to be a valuable tool to aid real‐time warning forecasters in the assessment of severe weather potential of convective storms. The trend of total lightning has been related to the strength of a storm's updraft. Therefore a rapid increase in total lightning signifies the strengthening of the parent thunderstorm. The assessment of severe weather potential occurs in a time limited environment and therefore constrains the use of total lightning. A tool has been developed at NASA's Short‐term Prediction Research and Transition (SPoRT) Center to assist in quickly analyzing the total lightning signature of multiple storms. The development of this tool comes as a direct result of forecaster feedback from numerous assessments requesting a real‐time display of the time series of total lightning. This tool also takes advantage of the new architecture available within the AWIPS II environment. SPoRT's lightning tracking tool has been tested in the Hazardous Weather Testbed (HWT) Spring Program and significant changes have been made based on the feedback. In addition to the updates in response to the HWT assessment, the lightning tracking tool may also be extended to incorporate other requested displays, such as the intra‐cloud to cloud‐to‐ground ratio as well as incorporate the lightning jump algorithm.

Burks, Jason E.↗

Integrating MBSE into Ongoing Projects: Requirements Validation and Test Planning for the ISS SAFER

The International Space Station (ISS) Simplified Aid for Extra Vehicular Activity (EVA) Rescue (SAFER) is the spacewalking astronaut's final safety measure against separating from the ISS and being unable to return safely. Since the late 1990s, the SAFER has been a standard element of the spacewalking astronaut's equipment. The ISS SAFER project was chartered to develop a new block of SAFER units using a highly similar design to the legacy SAFER (known as the USA SAFER). An on-orbit test module was also included in the project to enable periodic maintenance/propulsion system checkout on the ISS SAFER. On the ISS SAFER project, model-based systems engineering (MBSE) was not the initial systems engineering (SE) approach, given the volume of heritage systems engineering and integration (SE&I) products. The initial emphasis was ensuring traceability to ISS program standards as well as to legacy USA SAFER requirements. The requirements management capabilities of the Cradle systems engineering tool were to be utilized to that end. During development, however, MBSE approaches were applied selectively to address specific challenges in requirements validation and test and verification (T&V) planning, which provided measurable efficiencies to the project. From an MBSE perspective, ISS SAFER development presented a challenge and an opportunity. Addressing the challenge first, the project was tasked to use the original USA SAFER operational and design requirements baseline, with a number of additional ISS program requirements to address evolving certification expectations for systems operating on the ISS. Additionally, a need to redesign the ISS SAFER avionics architecture resulted in a set of changes to the design requirements baseline. Finally, the project added an entirely new functionality for on-orbit maintenance. After initial requirements integration, the system requirements count was approaching 1000, which represented a growth of 4x over the original USA SAFER system. This presented the challenge - How to confirm that this new set of requirements set would result in the creation of the desired capability.

Anderson, Herbert A.↗

Revealing the Mysteries of Venus: The DAVINCI Mission

The Deep Atmosphere Venus Investigation of Noble gases, Chemistry, and Imaging (DAVINCI) mission described herein has been selected for flight to Venus as part of the NASA Discovery Program. DAVINCI will be the first mission to Venus to incorporate science driven flybys and an instrumented descent sphere into a unified architecture. The anticipated scientific outcome will be a new understanding of the atmosphere, surface, and evolutionary path of Venus as a possibly once-habitable planet and analog to hot terrestrial exoplanets. The primary mission design for DAVINCI as selected features a preferred launch in summer/fall 2029, two flybys in 2030, and descent sphere atmospheric entry by the end of 2031. The in situ atmospheric descent phase subsequently delivers definitive chemical and isotopic composition of the Venus atmosphere during an atmospheric transect above Alpha Regio. These in situ investigations of the atmosphere and near infrared descent imaging of the surface will complement remote flyby observations of the dynamic atmosphere, cloud deck, and surface near infrared emissivity. The overall mission yield will be at least 60 Gbits (compressed) new data about the atmosphere and near surface, as well as the first unique characterization of the deep atmosphere environment and chemistry, including trace gases, key stable isotopes, oxygen fugacity, constraints on local rock compositions, and topography of a tessera.

James B Garvin↗

NASA's Deep Space Network (DSN) Lunar Exploration Upgrades (DLEU)

In the near future, the National Aeronautics and Space Administration (NASA) will return to the moon beginning the next era of human exploration. NASA’s Space Communications and Navigation (SCaN) program will play a vital role in establishing communications and navigation support to realize the ambitious goals of the Artemis program. SCaN’s overall lunar communications support plan will be covered in a separate 2023 SpaceOps paper: “NASA’s Communications and Navigation Architecture Plans to Support the Return to the Moon and a Sustainable Lunar Presence”. The plan as it currently stands, includes a three-fold approach of lunar relay services, a dedicated set of new ground stations and support through the Deep Space Network (DSN). This paper will have a more granular focus on the DSN and NASA’s plans to upgrade and expand the network to be better suited for human spaceflight on and around the lunar surface. NASA’s Deep Space Network (DSN) will be a critical communications component for the upcoming lunar activities. There will be multiple spacecraft, using different bands, and some of those spacecraft will be transmitting and receiving using multiple bands, requiring DSN support of S-band (2 GHz), X-band (7 GHz up, 8 GHz down), and K-band (22.5 GHz up, 26 GHz down). Since there may be more than one spacecraft in the beamwidth of the DSN antennas, the DSN support will require an extension of the DSN’s capability to support multiple spacecraft using one antenna, expanding it to provide two simultaneous uplinks in the different bands at each antenna. Achieving this requires using new techniques for manufacturing the frequency selective surfaces, called dichroics, which steer the different frequency beams from and to the appropriate transmitting and receiving equipment, along with the addition of a new K-band uplink system. Additionally, due to the relative closeness of the moon from Earth (as opposed to the planetary missions the DSN supports daily), significantly higher data rates on both uplink and downlink are required, specifically up to 20 Mbps on the uplink and 150 Mbps on the downlink, both using Low Density Parity Check (LDPC) error correcting codes. And, again due to the relative closeness of the moon, there is a need for low latency data delivery of the high rate downlink telemetry which requires a change in the current DSN paradigm of delivering higher rate data with higher latency.

deep space network↗

NASA’s Deep Space Network (DSN) Lunar Exploration Upgrades (DLEU)

In the near future, the National Aeronautics and Space Administration (NASA) will returnhumansto the moon beginning the next era of human exploration. NASA’s Space Communications and Navigation (SCaN) program will play a vital role in establishing communications and navigation support to realize the ambitious goals of the Artemis program. SCaN’s overall lunar communications support plan will be covered in a separate 2023 SpaceOps paper: “NASA’s Communications and Navigation Architecture Plans to Support the Return to the Moon and a Sustainable Lunar Presence.” The four-point plan,as it currently stands, includes lunar relay services, a dedicated set of new ground stations, international partner contributions,and supportthrough the Deep Space Network (DSN)and associated upgrades. This paper will have a more granular focus on the DSN and NASA’s plans to upgrade and expand the network to be better suited for human spaceflight on and around the lunar surface. NASA’s Deep Space Network (DSN) will be a critical communications component for the upcoming lunar activities. There will be multiple spacecraft, using different bands, and some of those spacecraft will be transmitting and receiving using multiple bands, requiring DSN support of S-band (2 GHz), X-band (7 GHz up, 8 GHz down), and K-band (22.5 GHz up, 26 GHz down). Since there may be more than one spacecraft in the beamwidth of the DSN antennas, the DSN support will require an extension of the DSN’s capability to support multiple spacecraft using one antenna, expanding it to provide two simultaneous uplinks in the different bands at each antenna. Achieving this requires using new techniques for manufacturing the frequency selective surfaces, called dichroics, which steer the different frequency beams from and to the appropriate transmitting and receiving equipment, along with the addition of a new K-band uplink system. Additionally, due to the relative closeness of the moon from Earth (as opposed to the planetary missionsthe DSN supports daily), significantly higher data rates on both uplink and downlinkare requiredare possible and desirable by the lunar missions, specifically up to 20 Mbps on the uplink and 150 Mbps on the downlink, both using Low Density Parity Check (LDPC) error correcting codes. And, again due to the relative closeness of the moon, there is a need for low latency data delivery of the high rate downlink telemetry which requires a change in the current DSN paradigm of delivering higher rate data with higher latency.

Moon↗

NASA's Efforts to Pursue Commercial Communications Services for Missions in Near Space

The National Aeronautics and Space Administration (NASA) Space Communications and Navigation (SCaN) Program enables high speed, robust, secure and cost-effective space communications and navigation services to current and future science and exploration missions. Consistent with National Space Policy, NASA is seeking commercial services for all its future near Earth requirements by incorporating additional direct to Earth (DTE) providers and introducing commercial satellite communications (SATCOM) vendors as NASA’s Tracking and Data Relay Satellites (TDRS) begin to decline. Through the progression of these efforts, SCaN is also integrating commercial services in the cislunar domain. The overarching objective is to satisfy the demands from the mission community – both in terms of capacity and capability – in a robust and cost-effective way, leveraging the strong and growing commercial space sector. For near earth space relay, six SATCOM vendors were awarded Funded Space Act Agreements in June of 2022 to demonstrate the ability to serve near-Earth missions, and are working through their committed milestones. The failure of TDRS Flight-9 (F9) in late 2022 prompted an increased tempo of mission engagement to identify driving user needs that commercial SATCOM can meet in the near-term. NASA has set a course to accelerate a decision to terminate commitments for TDRS services to new missions and has developed a plan to execute validation and risk reduction efforts with early adopter “pathfinder” missions to pave the way to earlier operational services. As the Artemis Program matures and builds on the successful Artemis I flight in November/December of 2022, the definition of the supporting communications and navigation architecture has further been refined. Although NASA government assets will continue to play a key role in provision of services, such as through the Deep Space Network, SCaN is pursuing commercial services offerings to expand ground network capability and implement lunar relay services. In February of 2023, SCaN released solicitation for services that include DTE services to missions near-Earth and in cislunar space, as well as lunar relay services. Further, SCaN is seeking opportunities to integrate commercial capability into lunar surface communications infrastructure. NASA is also advocating for standards that promote interoperability and strategic technology investments in the commercial sector. This paper addresses the recent progress and future plans in the near-Earth space and lunar regimes, discusses the unified approach for industry engagement, and highlights both the common and unique challenges of commercialization efforts in the two regimes.

commercialization↗

Orion's Powered Flight Guidance Performance During Artemis I

Artemis is NASA’s campaign to explore the Moon and beyond. Artemis I, the un-crewed exo-LEO test flight, was completed in 2022. The Artemis I mission provided the means to prove-out both vehicle and systems as a pre-cursor to more advanced missions. The Orion capsule and service module had to be capable of accurately executing all major orbital burns and numerous correction burns to successfully execute the mission profile. In support of this needed translation maneuver capability, a powered flight guidance algorithm has been designed that provides a number of guided burn options depending on the burn objective. Some of these guidance options are based on classic orbit transfer problems, such as Lambert's time-of-flight problem. Some are based on proven NASA heritage manned space programs like Apollo and Shuttle. Some are new concepts that fill unique niche requirements. All of these options are integrated into an architecture based on a proven Shuttle heritage design, with a simple closed-loop guidance strategy, that provides both modularity, simplicity and adaptability to future, as yet to be defined, mission profiles. This paper will summarize the performance of Orion’s orbital powered flight guidance during the mission.

space guidance↗

Characterization of in-Space Propulsion Trade Space to Support Initial Human Mars Segment

The National Aeronautics and Space Administration’s Exploration Systems Development Mission Directorate has been developing architecture concepts for human missions to Mars in alignment with the agency’s Moon to Mars blueprint objectives. The focus of the Architecture Development Office has been to decompose the blueprint objectives into the characteristics and needs for both lunar and Mars missions and develop functional needs to enable an integrated end-to-end mission architecture. One of the key components of a human Mars mission is the in-space transportation system that delivers crew and cargo to Mars vicinity and return crew safely back to Earth. The Mars Architecture Team has been evaluating four in-space transportation options to satisfy this functional need: 1) Hybrid Nuclear Electric/ Chemical Propulsion, 2) Nuclear Thermal Propulsion, 3) Hybrid Solar Electric/ Chemical Propulsion, and 4) All-Chemical propulsion. To answer the question “which transportation option is best?” decision makers will need to understand the performance characteristics—and limitations—for each architecture in the context of their preferred metric. Each option could be considered “better” than the others, depending on whether the primary selection criteria is fast, cheap, maximum cross-government applicability, maximizes commercial capabilities, and/or any other desired metrics. The Mars Architecture Team has completed considerable analysis on the Hybrid Nuclear Electric/Chemical Propulsion concept over the past three years. The Space Nuclear Propulsion program has also conducted significant work on the Nuclear Thermal Propulsion concept. The Hybrid Solar Electric/Chemical Propulsion concept, derived from technology planned for the Gateway program, was originally configurated for minimum vehicle stack mass (and, hence, minimum Earth-launched mass/cost), leveraging a highly efficient propulsion system on a minimum energy Conjunction Class trajectory. Historically, All-Chemical concepts were considered impractical due to the enormous propellant mass required, even for minimum energy Conjunction Class/long stay mission opportunities. However, considering the emerging commercial heavy-lift capabilities, the concept must be reevaluated across a range of concepts that leverage reusable launch vehicle capabilities to reduce the cost of launching large quantities of transportation elements needed for missions of various duration. This paper aims to provide an overview of the in-space transportation assessment work that is on-going within NASA.

Mars↗

Characterization of in-Space Propulsion Trade Space to Support Initial Human Mars Segment

The National Aeronautics and Space Administration’s Exploration Systems Development Mission Directorate has been developing architecture concepts for human missions to Mars in alignment with the agency’s Moon to Mars blueprint objectives. The focus of the Architecture Development Office has been to decompose the blueprint objectives into the characteristics and needs for both lunar and Mars missions and develop functional needs to enable an integrated end-to-end mission architecture. One of the key components of a human Mars mission is the in-space transportation system that delivers crew and cargo to Mars vicinity and return crew safely back to Earth. The Mars Architecture Team has been evaluating four in-space transportation options to satisfy this functional need: 1) Hybrid Nuclear Electric/ Chemical Propulsion, 2) Nuclear Thermal Propulsion, 3) Hybrid Solar Electric/ Chemical Propulsion, and 4) All-Chemical propulsion. To answer the question “which transportation option is best?” decision makers will need to understand the performance characteristics—and limitations—for each architecture in the context of their preferred metric. Each option could be considered “better” than the others, depending on whether the primary selection criteria is fast, cheap, maximum cross-government applicability, maximizes commercial capabilities, and/or any other desired metrics. The Mars Architecture Team has completed considerable analysis on the Hybrid Nuclear Electric/Chemical Propulsion concept over the past three years. The Space Nuclear Propulsion program has also conducted significant work on the Nuclear Thermal Propulsion concept. The Hybrid Solar Electric/Chemical Propulsion concept, derived from technology planned for the Gateway program, was originally configurated for minimum vehicle stack mass (and, hence, minimum Earth-launched mass/cost), leveraging a highly efficient propulsion system on a minimum energy Conjunction Class trajectory. Historically, All-Chemical concepts were considered impractical due to the enormous propellant mass required, even for minimum energy Conjunction Class/long stay mission opportunities. However, considering the emerging commercial heavy-lift capabilities, the concept must be reevaluated across a range of concepts that leverage reusable launch vehicle capabilities to reduce the cost of launching large quantities of transportation elements needed for missions of various duration. This paper aims to provide an overview of the in-space transportation assessment work that is on-going within NASA.

Mars↗

Quicksilver

Quicksilver is proxy application for the Monte Carlo Transport code, Mercury. The purpose of the Quicksilver mini-app is to create a freely distributable code base that represents the key elements of the Mercury workload by solving a simplified time-dependent neutron transport problem. As an open source code, Quicksilver will be hosted on the CZ git/stash repo alongside other mini-apps in the ACS so-design suite. It will be used by vendors and other partners for co-design activities such as identifying root causes of Mercury performance bottlenecks on future architectures (i.e., memory bandwidth, memory latency, flop intensity) and developing Quicksilver will be used within LLNL as a nimble platform to evaluate programming models, algorithms, etc. that might be useful in Mercury. Quicksilver may also become a replacement for MCB in future procurement benchmarks, as well as a way to engage vendors in the Trinity and Sierra Centers of Excellence as well as other co-design efforts.

Richards, David↗

Studying Performance Portability of LAMMPS across Diverse GPU-based Platforms

The molecular dynamics simulation software, LAMMPS, utilizes the Kokkos acceleration library to port computation to a diverse set of architectures including those based on GPU accelerators. In addition to Kokkos, LAMMPS contains a vast code base that leverages the CUDA application programming interface using library functions such as cuFFT, CUDA’s fast-fourier transform (FFT) library, and, more recently, also support for AMD’s Heterogeneous Interface for Portability (HIP) that is rapidly growing. While preparing LAMMPS tests for the AMD GPU-based test system precursors to Frontier, we investigated several strategies for accelerating LAMMPS on AMD GPUs, using the AMD Instinct MI100 and MI250X. In this work, we integrated the HIP FFT library, hipFFT, into the particle-particle particle-mesh (PPPM) long-range solver, which allowed the porting of PPPM calculations to the GPUs. Kokkos behavior on the MI100 and MI250X was also investigated through the package kokkos command of LAMMPS, targeting com- munication, memory usage, and particle grid decomposition. The Tersoff, Reax, Lennard-Jones (LJ), EAM, Granular, and PPPM potentials were investigated in this effort, and results from these experiments are provided. The selected potentials were run on Spock (AMD Instinct MI100), Crusher (AMD Instinct MI250X), AFW HPC11 (NVIDIA A100) and Summit (NVIDIA V100), for comparison. Operational roofline models were constructed and analyzed for the Tersoff, Reax, and Lennard-Jones potentials on Crusher and Summit.

Hagerty, Nick↗

Developing CORBA-Based Distributed Scientific Applications from Legacy Fortran Programs

Recent progress in distributed object technology has enabled software applications to be developed and deployed easily such that objects or components can work together across the boundaries of the network, different operating systems, and different languages. A distributed object is not necessarily a complete application but rather a reusable, self-contained piece of software that co-operates with other objects in a plug-and-play fashion via a well-defined interface. The Common Object Request Broker Architecture (CORBA), a middleware standard defined by the Object Management Group (OMG), uses the Interface Definition Language (IDL) to specify such an interface for transparent communication between distributed objects. Since IDL can be mapped to any programming language, such as C++, Java, Smalltalk, etc., existing applications can be integrated into a new application and hence the tasks of code re-writing and software maintenance can be reduced. Many scientific applications in aerodynamics and solid mechanics are written in Fortran. Refitting these legacy Fortran codes with CORBA objects can increase the codes reusability. For example, scientists could link their scientific applications to vintage Fortran programs such as Partial Differential Equation(PDE) solvers in a plug-and-play fashion. Unfortunately, CORBA IDL to Fortran mapping has not been proposed and there seems to be no direct method of generating CORBA objects from Fortran without having to resort to manually writing C/C++ wrappers. In this paper, we present an efficient methodology to integrate Fortran legacy programs into a distributed object framework. Issues and strategies regarding the conversion and decomposition of Fortran codes into CORBA objects are discussed. The following diagram shows the conversion and decomposition mechanism we proposed. Our goal is to keep the Fortran codes unmodified. The conversion- aided tool takes the Fortran application program as input and helps programmers generate C/C++ header file and IDL file for wrapping the Fortran code. Programmers need to determine by themselves how to decompose the legacy application into several reusable components based on the cohesion and coupling factors among the functions and subroutines. However, programming effort still can be greatly reduced because function headings and types have been converted to C++ and IDL styles. Most Fortran applications use the COMMON block to facilitate the transfer of large amount of variables among several functions. The COMMON block plays the similar role of global variables used in C. In the CORBA-compliant programming environment, global variables can not be used to pass values between objects. One approach to dealing with this problem is to put the COMMON variables into the parameter list. We do not adopt this approach because it requires modification of the Fortran source code which violates our design consideration. Our approach is to extract the COMMON blocks and convert them into a structure-typed attribute in C++. Through attributes, each component can initialize the variables and return the computation result back to the client. We have tested successfully the proposed conversion methodology based on the f2c converter. Since f2c only translates Fortran to C, we still needed to edit the converted code to meet the C++ and IDL syntax. For example, C++/IDL requires a tag in the structure type, while C does not. In this paper, we identify the necessary changes to the f2c converter in order to directly generate the C++ header and the IDL file. Our future work is to add GUI interface to ease the decomposition task by simply dragging and dropping icons.

Sang, Janche↗