SEARCH · Search NASA

Results for “reuse”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 289 records · Page 16

All sources NASA NTRS DOE OSTI

NASA NTRS1993

Small Business Innovations

Under an Army Small Business Innovation Research (SBIR) grant, Symbiotics, Inc. developed a software system that permits users to upgrade products from standalone applications so they can communicate in a distributed computing environment. Under a subsequent NASA SBIR grant, Symbiotics added additional tools to the SOCIAL product to enable NASA to coordinate conventional systems for planning Shuttle launch support operations. Using SOCIAL, data may be shared among applications in a computer network even when the applications are written in different programming languages. The product was introduced to the commercial market in 1993 and is used to monitor and control equipment for operation support and to integrate financial networks. The SBIR program was established to increase small business participation in federal R&D activities and to transfer government research to industry. InQuisiX is a reuse library providing high performance classification, cataloging, searching, browsing, retrieval and synthesis capabilities. These form the foundation for software reuse, producing higher quality software at lower cost and in less time. Software Productivity Solutions, Inc. developed the technology under Small Business Innovation Research (SBIR) projects funded by NASA and the Army and is marketing InQuisiX in conjunction with Science Applications International Corporation (SAIC). The SBIR program was established to increase small business participation in federal R&D activities and to transfer government research to industry.

Source record↗

NASA NTRS1992

Problem-Solving Software

CBR Express software solves problems by adapting sorted solutions to new problems specified by a user. It is applicable to a wide range of situations. The technology was originally developed by Inference Corporation for Johnson Space Center's Advanced Software Development Workstation. The project focused on the reuse of software designs, and Inference used CBR as part of the ACCESS prototype software. The commercial CBR Express is used as a "help desk" for customer support, enabling reuse of existing information when necessary. It has been adopted by several companies, among them American Airlines, which uses it to solve reservation system software problems.

Source record↗

NASA NTRS2002

Vehicle and Mission Design Options for the Human Exploration of Mars/Phobos Using "Bimodal" NTR and LANTR Propulsion

The nuclear thermal rocket (NTR) is one of the leading propulsion options for future human missions to Mars because of its high specific impulse (lsp~850-1000 s) capability and its attractive engine thrust-to-weight ratio (~3-10). To stay within the available mass and payload volume limits of a “Magnum” heavy lift vehicle, a high performance propulsion system is required for trans-Mars injection (TMI). An expendable TMI stage, powered by three 15 thousand pounds force (klbf) NTR engines is currently under consideration by NASA for its Design Reference Mission (DRM). However, because of the miniscule burnup of enriched uranium-235 during the Earth departure phase (~10 grams out of 33 kilograms in each NTR core), disposal of the TMI stage and its engines after a single use is a costly and inefficient use of this high performance stage. By reconfiguring the engines for both propulsive thrust and modest power generation (referred to as “bimodal” operation), a robust, multiple burn, “power-rich” stage with propulsive Mars capture and reuse capability is possible. A family of modular “bimodal” NTR (BNTR) vehicles are described which utilize a common “core” stage powered by three 15 klbf BNTRs that produce 50 kWe of total electrical power for crew life support, an active refrigeration / reliquification system for long term, zero-boiloff liquid hydrogen (LH 2 ) storage, and high data rate communications. An innovative, spine-like “saddle truss” design connects the core stage and payload element and is open underneath to allow supplemental “in-line” propellant tanks and contingency crew consumables to be easily jettisoned to improve vehicle performance. A “modified” DRM using BNTR transfer vehicles requires fewer transportation system elements, reduces IMLEO and mission risk, and simplifies space operations. By taking the next logical step—use of the BNTR for propulsive capture of all payload elements into Mars orbit—the power available in Mars orbit grows to 150 kWe compared to 30 kWe for the DRM. Propulsive capture also eliminates the complex, higher risk aerobraking and capture maneuver which is replaced by a simpler reentry using a standardized, lower mass “aerodescent” shell. The attractiveness of the “all BNTR” option is further increased by the substitution of the lightweight, inflatable “TransHab” module in place of the heavier, hard-shell hab module. Use of TransHab introduces the potential for propulsive recovery and reuse of the BNTR / Earth return vehicle (ERV). It also allows the crew to travel to and from Mars on the same BNTR transfer vehicle thereby cutting the duration of the ERV mission in half—from ~4.7 to 2.5 years. Finally, for difficult Mars options, such as Phobos rendezvous and sample return missions, volume (not mass) constraints limit the performance of the “all LH 2 ” BNTR stage. The use of “LOX-augmented” NTR (LANTR) engines, operating at a modest oxygen-to-hydrogen mixture ratio (MR) of 0.5, helps to increase “bulk” propellant density and total thrust during the TMI burn. On all subsequent burns, the bimodal LANTR engines operate on LH 2 only (MR=0) to maximize vehicle performance while staying within the mass limits of two Magnum launches.

Nuclear thermal rocket↗

NASA NTRS2003

RSRM Case Acceptance and Refurbishment Requirements

The RSRM (Reuseable Solid Rocket Motor) Program has been developed and implemented to support manned flight space travel. The Space Shuttle Vehicle utilizes two SRBs (Solid Rocket Boosters) to assist during the launch sequence and achieve the predefined orbit and mission objectives. A critical feature of this program involves post- flight SRB retrieval, disassembly and reuse of case structural components to manufacture future RSRM motors. To ensure these components can be safely reused, inspection criteria based on dimensional, structural and fracture requirements, has been established in the form of Engineering specifications and drawings. These criteria originated from actual hardware testing (both subscale and full scale) coupled with conventional Engineering hand calculations and computerized Finite Element Analyses (FEA). The intent of this paper is to provide an overview of the RSRM Case component refurbishment requirements and the associated case hardware inspection and evaluation processes that has been established to satisfy these requirements. Many of these processes have been recently upgraded to comply with environmental regulations, obsolescence concerns and technological advancements. Qualification of these process changes has been closely monitored and documented through test plans and reports.

Brinkerhoff, Gary Z.↗

NASA NTRS2004

Generative Representations for Computer-Automated Design Systems

With the increasing computational power of Computers, software design systems are progressing from being tools for architects and designers to express their ideas to tools capable of creating designs under human guidance. One of the main limitations for these computer-automated design programs is the representation with which they encode designs. If the representation cannot encode a certain design, then the design program cannot produce it. Similarly, a poor representation makes some types of designs extremely unlikely to be created. Here we define generative representations as those representations which can create and reuse organizational units within a design and argue that reuse is necessary for design systems to scale to more complex and interesting designs. To support our argument we describe GENRE, an evolutionary design program that uses both a generative and a non-generative representation, and compare the results of evolving designs with both types of representations.

Hornby, Gregory S.↗

NASA NTRS2004

Using Generative Representations to Evolve Robots

Recent research has demonstrated the ability of evolutionary algorithms to automatically design both the physical structure and software controller of real physical robots. One of the challenges for these automated design systems is to improve their ability to scale to the high complexities found in real-world problems. Here we claim that for automated design systems to scale in complexity they must use a representation which allows for the hierarchical creation and reuse of modules, which we call a generative representation. Not only is the ability to reuse modules necessary for functional scalability, but it is also valuable for improving efficiency in testing and construction. We then describe an evolutionary design system with a generative representation capable of hierarchical modularity and demonstrate it for the design of locomoting robots in simulation. Finally, results from our experiments show that evolution with our generative representation produces better robots than those evolved with a non-generative representation.

Hornby, Gregory S.↗

NASA NTRS1988

Cultural systems for growing potatoes in space

Higher plants are being evaluated for life support to provide needed food, oxygen and water as well as removal of carbon dioxide from the atmosphere. The successful utilization of plants in space will require the development of not only highly productive growing systems but also highly efficient bioregenerative systems. It will be necessary to recycle all inedible plant parts and all human wastes so that the entire complement of elemental compounds can be reused. Potatoes have been proposed as one of the desirable crops because they are 1) extremely productive, yielding more than 100 metric tons per hectare from field plantings, 2) the edible tubers are high in digestible starch (70%) and protein (10%) on a dry weight basis, 3) up to 80% of the total plant production is in tubers and thus edible, 4) the plants are easily propagated either from tubers or from tissue culture plantlets, 5) the tubers can be utilized with a minimum of processing, and 6) potatoes can be prepared in a variety of different forms for the human diet (Tibbitts et al., 1982). However potatoes have a growth pattern that complicates the development of growing the plants in controlled systems. Tubers are borne on underground stems that are botanically termed 'rhizomes', but in common usage termed 'stolons'. The stolons must be maintained in a dark, moist area with sufficient provision for enlargement of tubers. Stems rapidly terminate in flowers forcing extensive branching and spreading of plants so that individual plants will cover 0.2 m2 or more area. Thus the growing system must be developed to provide an area that is darkened for tuber and root growth and of sufficient size for plant spread. A system developed for growing potatoes, or any plants, in space will have certain requirements that must be met to make them a useful part of a life support system. The system must 1) be constructed of materials, and involve media, that can be reused for many successive cycles of plant growth, 2) involve a minimum quantity of media, 3) contain media that is essentially inert and not oxidize or degrade with use, 4) utilize a recirculating nutrient solution to permit regulation of pH and nutrient concentrations, and 5) be capable of complete automation of all planting, maintenance and harvesting procedures.

NASA Discipline Number 61-10↗

NASA NTRS2003

XML: James Webb Space Telescope Database Issues, Lessons, and Status

This paper will present the current concept using extensible Markup Language (XML) as the underlying structure for the James Webb Space Telescope (JWST) database. The purpose of using XML is to provide a JWST database, independent of any portion of the ground system, yet still compatible with the various systems using a variety of different structures. The testing of the JWST Flight Software (FSW) started in 2002, yet the launch is scheduled for 2011 with a planned 5-year mission and a 5-year follow on option. The initial database and ground system elements, including the commands, telemetry, and ground system tools will be used for 19 years, plus post mission activities. During the Integration and Test (I&T) phases of the JWST development, 24 distinct laboratories, each geographically dispersed, will have local database tools with an XML database. Each of these laboratories database tools will be used for the exporting and importing of data both locally and to a central database system, inputting data to the database certification process, and providing various reports. A centralized certified database repository will be maintained by the Space Telescope Science Institute (STScI), in Baltimore, Maryland, USA. One of the challenges for the database is to be flexible enough to allow for the upgrade, addition or changing of individual items without effecting the entire ground system. Also, using XML should allow for the altering of the import and export formats needed by the various elements, tracking the verification/validation of each database item, allow many organizations to provide database inputs, and the merging of the many existing database processes into one central database structure throughout the JWST program. Many National Aeronautics and Space Administration (NASA) projects have attempted to take advantage of open source and commercial technology. Often this causes a greater reliance on the use of Commercial-Off-The-Shelf (COTS), which is often limiting. In our review of the database requirements and the COTS software available, only very expensive COTS software will meet 90% of requirements. Even with the high projected initial cost of COTS, the development and support for custom code over the 19-year mission period was forecasted to be higher than the total licensing costs. A group did look at reusing existing database tools and formats. If the JWST database was already in a mature state, the reuse made sense, but with the database still needing to handing the addition of different types of command and telemetry structures, defining new spacecraft systems, accept input and export to systems which has not been defined yet, XML provided the flexibility desired. It remains to be determined whether the XML database will reduce the over all cost for the JWST mission.

Detter, Ryan↗

NASA NTRS1999

Conformal, Transparent Printed Antenna Developed for Communication and Navigation Systems

Conformal, transparent printed antennas have advantages over conventional antennas in terms of space reuse and aesthetics. Because of their compactness and thin profile, these antennas can be mounted on video displays for efficient integration in communication systems such as palmtop computers, digital telephones, and flat-panel television displays. As an array of multiple elements, the antenna subsystem may save weight by reusing space (via vertical stacking) on photovoltaic arrays or on Earth-facing sensors. Also, the antenna could go unnoticed on automobile windshields or building windows, enabling satellite uplinks and downlinks or other emerging high-frequency communications.

Lee, Richard Q.↗

NASA NTRS2003

Mission interactive scenarion studio for autonomous spacecraft

We propose building a Studio enabling the use of diverse existing mission activity and scenario patterns, the creation of new ones, and the modeling of their effects using existing modeling tools. The core of the Studio is a component-based Type Library, which captures years of mission adaptation patterns in various forms. The Studio works as a content server to capture the developed adaptation knowledge for reuse and provides bridging into different mission uplink implementations, including the Mission Data System [l] (MDS) state/goal machinery. Various activities can be coordinated, controlled, and reused through the Studio's component interface to establish and model a mission scenario. A special component Factory mechanism will be in place to facilitate the adaptation of projects into the Studio. The architecture of the Studio reflects and enforces a division of knowledge and actions into three parts: Model, Controller, Viewer. The Model contains information about (a proposed version of) the spacecraft and mission. The Controller contains logic for constructing scenarios of mission activities. The information in the Model and Controller is principally in the form of reusable patterns. A Viewer can be a simple or complex software system. For example, Apgen [2,3] is one possible viewer, MDS is another. A 3-tiered infrastructure is used for the Studio, reflecting the Model, Controller, Viewer architecture [4,5]. The Studio is useful in pre-phase A of a project by enabling spacecraft design options to be played against desired mission scenarios. In later design phases of a project, the construction and modeling of more detailed scenarios is supported by the Studio.

autonomous spacecraft↗

NASA NTRS2003

Managing a project's legacy: implications for organizations and project management

Organizations that rely on projects to implement their products must find effective mechanisms for propagating lessons learned on one project throughout the organization. A broad view of what constitutes a project's 'legacy' is presented that includes not just the design products and leftover parts, but new processes, relationships, technology, skills, planning data, and performance metrics. Based on research evaluating knowledge reuse in innovative contexts, this paper presents an approach to project legacy management that focuses on collecting and using legacy knowledge to promote organizational learning and effective reuse, while addressing factors of post-project responsibility, information obsolescence, and the importance of ancillary contextual information. .

risk management↗

NASA NTRS2006

YAM- A Framework for Rapid Software Development

YAM is a software development framework with tools for facilitating the rapid development and integration of software in a concurrent software development environment. YAM provides solutions for thorny development challenges associated with software reuse, managing multiple software configurations, the development of software product-lines, multiple platform development and build management. YAM uses release-early, release-often development cycles to allow developers to incrementally integrate their changes into the system on a continual basis. YAM facilitates the creation and merging of branches to support the isolated development of immature software to avoid impacting the stability of the development effort. YAM uses modules and packages to organize and share software across multiple software products. It uses the concepts of link and work modules to reduce sandbox setup times even when the code-base is large. One side-benefit is the enforcement of a strong module-level encapsulation of a module s functionality and interface. This increases design transparency, system stability as well as software reuse. YAM is in use by several mid-size software development teams including ones developing mission-critical software.

simulations↗

NASA NTRS2008

The Manufacturing Process for the NASA Composite Crew Module Demonstration Structure

This paper will describe the approaches and methods selected in fabrication of a carbon composite demonstration structure for the Composite Crew Module (CCM) Program. The program is managed by the NASA Safety and Engineering Center with participants from ten NASA Centers and AFRL. Multiple aerospace contractors are participating in the design development, tooling and fabrication effort as well. The goal of the program is to develop an agency wide design team for composite habitable spacecraft. The specific goals for this development project are: a).To gain hands on experience in design, building and testing a composite crew module. b) To validate key assumptions by resolving composite spacecraft design details through fabrication and testing of hardware. This abstract is based on Preliminary Design data..The final design will continue to evolve through the fall of 2007 with fabrication mostly completed by conference date. From a structures perspective, the.CCM can be viewed as a pressure module with variable pressure time histories and a series of both impact and quasi-static, high intensity point, line, and area distributed loads. The portion of the overall space vehicle being designed and. fabricated by the CCM team is just the pressure module and primary loading points. The heaviest point loads are applied and distributed to the pressure module at.an aluminum Service Module/Alternate Launch Abort System (SM/ALAS) fittings and at Main and Drogue Chute fittings. Significant line loads with metal to metal impact is applied at.the Lids ring. These major external point and line loads as well as pressure impact loads (blast and water landing) are applied to the lobed floor though the reentry shield and crushable materials. The pressure module is divided into upper and lower. shells that mate together with a bonded belly band splice joint to create the completed structural assembly. The benefits of a split CCM far outweigh the risks of a joint. These benefits include lower tooling cost and less manufacturing risk. Assembly of the top and bottom halves of the pressure shell will allow access to the interior of the shell throughout remaining fabrication sequence and can also potentially permit extensive installation of equipment and .crew facilities prior to final assembly of the two shell halves. A Pi pre-form is a woven carbon composite material which is provided in pre-impregnated form and frozen for long term storage. The cross-section shape allows the top of the pi to be bonded to a flat or curved surface with a second flat plate composite section bonded between two upstanding legs of the Pi. One of the regions relying on the merits of the Pi pre-form is the backbone. All connections among plates of the backbone structure, including the upper flanges, and to the lobe base of the pressure shell are currently joined by Pi pre-forms. The intersection of backbone composite plates is formed by application of two Pi pre-forms, top flanges and lobed surfaces are bonded with one Pi pre-form. The process of applying the pre-impregnated pi-preform will be demonstrated to include important steps like surface preparation, forming, application of pressure dams, vacuum bagging for consolidation, and curing techniques. Chopped carbon fiber tooling was selected over other traditional metallic and carbon fiber tooling. The requirement of schedule and cost economy for a moderate reuse cure tool warranted composite tooling options. Composite tooling schedule duration of 18 weeks compared favorably against other metallic tooling including invar tooling. Composite tooling also shows significant cost savings over low CTE metallic options. The composite tooling options were divided into two groups and the final decision was based on the cost, schedule, tolerance, temperature, and reuse requirements.

Pelham, Larry↗

NASA NTRS2008

STRS Compliant FPGA Waveform Development

The Space Telecommunications Radio System (STRS) Architecture Standard describes a standard for NASA space software defined radios (SDRs). It provides a common framework that can be used to develop and operate a space SDR in a reconfigurable and reprogrammable manner. One goal of the STRS Architecture is to promote waveform reuse among multiple software defined radios. Many space domain waveforms are designed to run in the special signal processing (SSP) hardware. However, the STRS Architecture is currently incomplete in defining a standard for designing waveforms in the SSP hardware. Therefore, the STRS Architecture needs to be extended to encompass waveform development in the SSP hardware. The extension of STRS to the SSP hardware will promote easier waveform reconfiguration and reuse. A transmit waveform for space applications was developed to determine ways to extend the STRS Architecture to a field programmable gate array (FPGA). These extensions include a standard hardware abstraction layer for FPGAs and a standard interface between waveform functions running inside a FPGA. A FPGA-based transmit waveform implementation of the proposed standard interfaces on a laboratory breadboard SDR will be discussed.

Nappier, Jennifer↗

NASA NTRS2009

Economical Implementation of a Filter Engine in an FPGA

A logic design has been conceived for a field-programmable gate array (FPGA) that would implement a complex system of multiple digital state-space filters. The main innovative aspect of this design lies in providing for reuse of parts of the FPGA hardware to perform different parts of the filter computations at different times, in such a manner as to enable the timely performance of all required computations in the face of limitations on available FPGA hardware resources. The implementation of the digital state-space filter involves matrix vector multiplications, which, in the absence of the present innovation, would ordinarily necessitate some multiplexing of vector elements and/or routing of data flows along multiple paths. The design concept calls for implementing vector registers as shift registers to simplify operand access to multipliers and accumulators, obviating both multiplexing and routing of data along multiple paths. Each vector register would be reused for different parts of a calculation. Outputs would always be drawn from the same register, and inputs would always be loaded into the same register. A simple state machine would control each filter. The output of a given filter would be passed to the next filter, accompanied by a "valid" signal, which would start the state machine of the next filter. Multiple filter modules would share a multiplication/accumulation arithmetic unit. The filter computations would be timed by use of a clock having a frequency high enough, relative to the input and output data rate, to provide enough cycles for matrix and vector arithmetic operations. This design concept could prove beneficial in numerous applications in which digital filters are used and/or vectors are multiplied by coefficient matrices. Examples of such applications include general signal processing, filtering of signals in control systems, processing of geophysical measurements, and medical imaging. For these and other applications, it could be advantageous to combine compact FPGA digital filter implementations with other application-specific logic implementations on single integrated-circuit chips. An FPGA could readily be tailored to implement a variety of filters because the filter coefficients would be loaded into memory at startup.

Kowalski, James E.↗

NASA NTRS2009

Using Drained Spacecraft Propellant Tanks for Habitation

A document proposes that future spacecraft for planetary and space exploration be designed to enable reuse of drained propellant tanks for occupancy by humans. This proposal would enable utilization of volume and mass that would otherwise be unavailable and, in some cases, discarded. Such utilization could enable reductions in cost, initial launch mass, and number of launches needed to build up a habitable outpost in orbit about, or on the surface of, a planet or moon. According to the proposal, the large propellant tanks of a spacecraft would be configured to enable crews to gain access to their interiors. The spacecraft would incorporate hatchways, between a tank and the crew volume, that would remain sealed while the tank contained propellant and could be opened after the tank was purged by venting to outer space and then refilled with air. The interior of the tank would be pre-fitted with some habitation fixtures that were compatible with the propellant environment. Electrical feed-throughs, used originally for gauging propellants, could be reused to supply electric power to equipment installed in the newly occupied space. After a small amount of work, the tank would be ready for long-term use as a habitation module.

Thomas, Andrew S. W.↗

NASA NTRS2009

Connecting Research and Practice: An Experience Report on Research Infusion with SAVE

NASA systems need to be highly dependable to avoid catastrophic mission failures. This calls for rigorous engineering processes including meticulous validation and verification. However, NASA systems are often highly distributed and overwhelmingly complex, making the software portion of these systems challenging to understand, maintain, change, reuse, and test. NASA's systems are long-lived and the software maintenance process typically constitutes 60-80% of the total cost of the entire lifecycle. Thus, in addition to the technical challenges of ensuring high life-time quality of NASA's systems, the post-development phase also presents a significant financial burden. Some of NASA's software-related challenges could potentially be addressed by some of the many powerful technologies that are being developed in software research laboratories. Many of these research technologies seek to facilitate maintenance and evolution by for example architecting, designing and modeling for quality, flexibility, and reuse. Other technologies attempt to detect and remove defects and other quality issues by various forms of automated defect detection, architecture analysis, and various forms of sophisticated simulation and testing. However promising, most such research technologies nevertheless do not make the transition from the research lab to the software lab. One reason the transition from research to practice seldom occurs is that research infusion and technology transfer is difficult. For example, factors related to the technology are sometimes overshadowed by other types of factors such as reluctance to change and therefore prohibits the technology from sticking. Successful infusion might also take very long time. One famous study showed that the discrepancy between the conception of the idea and its practical use was 18 years plus or minus three. Nevertheless, infusing new technology is possible. We have found that it takes special circumstances for such research infusion to succeed: 1) there must be evidence that the technology works in the practitioner's particular domain, 2) there must be a potential for great improvements and enhanced competitive edge for the practitioner, 3) the practitioner has to have strong individual curiosity and continuous interest in trying out new technologies, 4) the practitioner has to have support on multiple levels (i.e. from the researchers, from management, from sponsors etc), and 5) to remain infused, the new technology has to be integrated into the practitioner's processes so that it becomes a natural part of the daily work. NASA IV&V's Research Infusion initiative sponsored by NASA's Office of Safety & Mission Assurance (OSMA) through the Software Assurance Research Program (SARP), strives to overcome some of the problems related to research infusion.

Lindvall, Mikael↗

NASA NTRS2007

Generative Representations for Automated Design of Robots

A method of automated design of complex, modular robots involves an evolutionary process in which generative representations of designs are used. The term generative representations as used here signifies, loosely, representations that consist of or include algorithms, computer programs, and the like, wherein encoded designs can reuse elements of their encoding and thereby evolve toward greater complexity. Automated design of robots through synthetic evolutionary processes has already been demonstrated, but it is not clear whether genetically inspired search algorithms can yield designs that are sufficiently complex for practical engineering. The ultimate success of such algorithms as tools for automation of design depends on the scaling properties of representations of designs. A nongenerative representation (one in which each element of the encoded design is used at most once in translating to the design) scales linearly with the number of elements. Search algorithms that use nongenerative representations quickly become intractable (search times vary approximately exponentially with numbers of design elements), and thus are not amenable to scaling to complex designs. Generative representations are compact representations and were devised as means to circumvent the above-mentioned fundamental restriction on scalability. In the present method, a robot is defined by a compact programmatic form (its generative representation) and the evolutionary variation takes place on this form. The evolutionary process is an iterative one, wherein each cycle consists of the following steps: 1. Generative representations are generated in an evolutionary subprocess. 2. Each generative representation is a program that, when compiled, produces an assembly procedure. 3. In a computational simulation, a constructor executes an assembly procedure to generate a robot. 4. A physical-simulation program tests the performance of a simulated constructed robot, evaluating the performance according to a fitness criterion to yield a figure of merit that is fed back into the evolutionary subprocess of the next iteration. In comparison with prior approaches to automated evolutionary design of robots, the use of generative representations offers two advantages: First, a generative representation enables the reuse of components in regular and hierarchical ways and thereby serves a systematic means of creating more complex modules out of simpler ones. Second, the evolved generative representation may capture intrinsic properties of the design problem, so that variations in the representations move through the design space more effectively than do equivalent variations in a nongenerative representation. This method has been demonstrated by using it to design some robots that move, variously, by walking, rolling, or sliding. Some of the robots were built (see figure). Although these robots are very simple, in comparison with robots designed by humans, their structures are more regular, modular, hierarchical, and complex than are those of evolved designs of comparable functionality synthesized by use of nongenerative representations.

Homby, Gregory S.↗