Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Programming”

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,513 records · Page 84

Novel approaches and application of contemporary sensory evaluation practices in iron fortification programs

Iron deficiency is the leading nutritional deficiency in the U.S. and the rest of the world, with its highest prevalences in the developing world. Iron fortification of food has been proposed as a strategy to reduce the high prevalence of iron deficiency. Poor consumer acceptance, unacceptable taste, and discoloration of the iron-fortified foods have been frequently listed as causes of unsuccessful iron fortification programs. An excellent prospect for improving consumer acceptance of iron-fortified foods is the incorporation of a thorough, organized, and unified approach to sensory evaluation practices into iron fortification programs for product optimization. The information gained from systematic sensory evaluation allows for the manipulation of the sensory attributes, and thus improvement of the sensory properties of the fortified food. However, iron fortification programs have not systematically measured the effect of fortification on the sensory quality of the food. Because sensory evaluation is an important criterion in successful iron fortification, an integrated approach is necessary. Therefore, nutritionists and sensory scientists should work closely with each other to select the most suitable sensory tests and methods. The objectives of this article are to: (1) critically review and discuss some traditional and contemporary approaches and applications of sensory evaluation practices in iron fortification programs, and (2) demonstrate the importance of incorporating a multidisciplinary, systematic sensory evaluation approach in iron fortification programs.

Review, Tutorial↗

The Role of Ontologies in Schema-based Program Synthesis

Program synthesis is the process of automatically deriving executable code from (non-executable) high-level specifications. It is more flexible and powerful than conventional code generation techniques that simply translate algorithmic specifications into lower-level code or only create code skeletons from structural specifications (such as UML class diagrams). Key to building a successful synthesis system is specializing to an appropriate application domain. The AUTOBAYES and AUTOFILTER systems, under development at NASA Ames, operate in the two domains of data analysis and state estimation, respectively. The central concept of both systems is the schema, a representation of reusable computational knowledge. This can take various forms, including high-level algorithm templates, code optimizations, datatype refinements, or architectural information. A schema also contains applicability conditions that are used to determine when it can be applied safely. These conditions can refer to the initial specification, to intermediate results, or to elements of the partially-instantiated code. Schema-based synthesis uses AI technology to recursively apply schemas to gradually refine a specification into executable code. This process proceeds in two main phases. A front-end gradually transforms the problem specification into a program represented in an abstract intermediate code. A backend then compiles this further down into a concrete target programming language of choice. A core engine applies schemas on the initial problem specification, then uses the output of those schemas as the input for other schemas, until the full implementation is generated. Since there might be different schemas that implement different solutions to the same problem this process can generate an entire solution tree. AUTOBAYES and AUTOFILTER have reached the level of maturity where they enable users to solve interesting application problems, e.g., the analysis of Hubble Space Telescope images. They are large (in total around 100kLoC Prolog), knowledge intensive systems that employ complex symbolic reasoning to generate a wide range of non-trivial programs for complex application do- mains. Their schemas can have complex interactions, which make it hard to change them in isolation or even understand what an existing schema actually does. Adding more capabilities by increasing the number of schemas will only worsen this situation, ultimately leading to the entropy death of the synthesis system. The root came of this problem is that the domain knowledge is scattered throughout the entire system and only represented implicitly in the schema implementations. In our current work, we are addressing this problem by making explicit the knowledge from Merent parts of the synthesis system. Here; we discuss how Gruber's definition of an ontology as an explicit specification of a conceptualization matches our efforts in identifying and explicating the domain-specific concepts. We outline the dual role ontologies play in schema-based synthesis and argue that they address different audiences and serve different purposes. Their first role is descriptive: they serve as explicit documentation, and help to understand the internal structure of the system. Their second role is prescriptive: they provide the formal basis against which the other parts of the system (e.g., schemas) can be checked. Their final role is referential: ontologies also provide semantically meaningful "hooks" which allow schemas and tools to access the internal state of the program derivation process (e.g., fragments of the generated code) in domain-specific rather than language-specific terms, and thus to modify it in a controlled fashion. For discussion purposes we use AUTOLINEAR, a small synthesis system we are currently experimenting with, which can generate code for solving a system of linear equations, Az = b.

Bures, Tomas↗

The 2003 NASA Faculty Fellowship Program Research Reports

For the 39th consecutive year, the NASA Faculty Fellowship Program (NFFP) was conducted at Marshall Space Flight Center. The program was sponsored by NASA Headquarters, Washington, DC, and operated under contract by The University of Alabama in Huntsville. In addition, promotion and applications are managed by the American Society for Engineering Education (ASEE) and assessment is completed by Universities Space Research Association (USRA). The nominal starting and finishing dates for the 10-week program were May 27 through August 1, 2003. The primary objectives of the NASA Faculty Fellowship Program are to: (1) Increase the quality and quantity of research collaborations between NASA and the academic community that contribute to NASA s research objectives; (2) provide research opportunities for college and university faculty that serve to enrich their knowledge base; (3) involve students in cutting-edge science and engineering challenges related to NASA s strategic enterprises, while providing exposure to the methods and practices of real-world research; (4) enhance faculty pedagogy and facilitate interdisciplinary networking; (5) encourage collaborative research and technology transfer with other Government agencies and the private sector; and (6) establish an effective education and outreach activity to foster greater awareness of this program.

Nash-Stevenson, S. K.↗

Evaluation of the Advanced Subsonic Technology Program Noise Reduction Benefits

This report presents a detailed evaluation of the aircraft noise reduction technology concepts developed during the course of the NASA/FAA Advanced Subsonic Technology (AST) Noise Reduction Program. In 1992, NASA and the FAA initiated a cosponsored, multi-year program with the U.S. aircraft industry focused on achieving significant advances in aircraft noise reduction. The program achieved success through a systematic development and validation of noise reduction technology. Using the NASA Aircraft Noise Prediction Program, the noise reduction benefit of the technologies that reached a NASA technology readiness level of 5 or 6 were applied to each of four classes of aircraft which included a large four engine aircraft, a large twin engine aircraft, a small twin engine aircraft and a business jet. Total aircraft noise reductions resulting from the implementation of the appropriate technologies for each class of aircraft are presented and compared to the AST program goals.

Golub, Robert A.↗

An Overview of the NASA Aerospace Flight Battery Systems Program

The NASA Aerospace Flight Battery Systems Program is an agency-wide effort aimed at ensuring the quality, safety, reliability and performance of flight battery systems for NASA applications. The program provides for the validation of primary and secondary cell and battery level technology advances to ensure their availability and readiness for use in NASA missions. It serves to bridge the gap between the development of technology advances and the realization and incorporation of these advances into mission applications. The program is led by the Glenn Research Center and involves funded task activities at each of the NASA mission centers and JPL. The overall products are safe, reliable, high quality batteries for mission applications. The products are defined along three product lines: 1. Battery Systems Technology - Elements of this task area cover the systems aspects of battery operation and generally apply across chemistries. This includes the development of guidelines documents, the establishment and maintenance of a central battery database that serves a central repository for battery characterization and verification test data from tests performed under the support of this program, the NASA Battery Workshop, and general test facility support. 2. Secondary Battery Technology - l h s task area focuses on the validation of battery technology for nickel-cadmium, nickel-hydrogen, nickel-metal-hydride and lithium-ion secondary battery systems. Standardized test regimes are used to validate the quality of a cell lot or cell design for flight applications. In this area, efforts are now concentrated on the validation and verification of lithium-ion battery technology for aerospace applications. 3. Primary Battery Technology - The safety and reliability aspects for primary lithium battery systems that are used in manned operations on the Shuttle and International Space Station are addressed in the primary battery technology task area. An overview of the task areas supported under this program will be presented.

Manzo, Michelle A.↗

Communicating Risk to Program Managers

Program Managers (PM) can protect program resources and improve chances of success by anticipating, understanding and managing risks. Understanding the range of potential risks helps one to avoid or manage the risks. A PM must choose which risks to accept to reduce fire fighting, must meet the expectations of stakeholders consistently, and avoid falling into costly "black holes" that may open. A good risk management process provides the PM more confidence to seize opportunities save money, meet schedule, even improve relationships with people important to the program. Evidence of managing risk and sound internal controls can mean better support from superiors for the program by building a trust and reputation from being on top of issues. Risk managers have an obligation to provide the PM with the best information possible to allow the benefits to be realized (Small Business Consortium, 2004). The Institute for Chartered Accountants in England and Wales sees very important benefits for companies in providing better information about what they do to assess and manage key business risks. Such information will: a) provide practical forward-looking information; b) reduce the cost of capital; c) encourage better risk management; and d) improve accountability for stewardship, investor protection and the usefulness of financial reporting. We are particularly convinced that enhanced risk reporting will help listed companies obtain capital at the lowest possible cost (The Institute of Chartered Accountants in England &Wales, June 2002). Risk managers can take a significant role in quantifying the success of their department and communicating those figures to executive (program) management levels while pushing for a broader risk management role. Overall, risk managers must show that risk management work matters in the most crucial place-the bottom line- as they prove risk management can be a profit center (Sullivan, 2004).

Shivers, C. Herbert↗

Introduction of the ASP3D Computer Program for Unsteady Aerodynamic and Aeroelastic Analyses

A new computer program has been developed called ASP3D (Advanced Small Perturbation 3D), which solves the small perturbation potential flow equation in an advanced form including mass-consistent surface and trailing wake boundary conditions, and entropy, vorticity, and viscous effects. The purpose of the program is for unsteady aerodynamic and aeroelastic analyses, especially in the nonlinear transonic flight regime. The program exploits the simplicity of stationary Cartesian meshes with the movement or deformation of the configuration under consideration incorporated into the solution algorithm through a planar surface boundary condition. The new ASP3D code is the result of a decade of developmental work on improvements to the small perturbation formulation, performed while the author was employed as a Senior Research Scientist in the Configuration Aerodynamics Branch at the NASA Langley Research Center. The ASP3D code is a significant improvement to the state-of-the-art for transonic aeroelastic analyses over the CAP-TSD code (Computational Aeroelasticity Program Transonic Small Disturbance), which was developed principally by the author in the mid-1980s. The author is in a unique position as the developer of both computer programs to compare, contrast, and ultimately make conclusions regarding the underlying formulations and utility of each code. The paper describes the salient features of the ASP3D code including the rationale for improvements in comparison with CAP-TSD. Numerous results are presented to demonstrate the ASP3D capability. The general conclusion is that the new ASP3D capability is superior to the older CAP-TSD code because of the myriad improvements developed and incorporated.

Batina, John T.↗

The NASA Beyond Einstein Program

Einstein's legacy is incomplete, his theory of General relativity raises -- but cannot answer --three profound questions: What powered the big bang? What happens to space, time, and matter at the edge of a black hole? and What is the mysterious dark energy pulling the Universe apart? The Beyond Einstein program within NASA's Office of Space Science aims to answer these questions, employing a series of missions linked by powerful new technologies and complementary approaches towards shared science goals. The Beyond Einstein program has three linked elements which advance science and technology towards two visions; to detect directly gravitational wave signals from the earliest possible moments of the BIg Bang, and to image the event horizon of a black hole. The central element is a pair of Einstein Great Observatories, Constellation-X and LISA. Constellation-X is a powerful new X-ray observatory dedicated to X-Ray Spectroscopy. LISA is the first spaced based gravitational wave detector. These powerful facilities will blaze new paths to the questions about black holes, the Big Bang and dark energy. The second element is a series of competitively selected Einstein Probes, each focused on one of the science questions and includes a mission dedicated resolving the Dark Energy mystery. The third element is a program of technology development, theoretical studies and education. The Beyond Einstein program is a new element in the proposed NASA budget for 2004. This talk will give an overview of the program and the missions contained within it.

White, Nicholas E.↗

(abstract) Formal Inspection Technology Transfer Program

A Formal Inspection Technology Transfer Program, based on the inspection process developed by Michael Fagan at IBM, has been developed at JPL. The goal of this program is to support organizations wishing to use Formal Inspections to improve the quality of software and system level engineering products. The Technology Transfer Program provides start-up materials and assistance to help organizations establish their own Formal Inspection program. The course materials and certified instructors associated with the Technology Transfer Program have proven to be effective in classes taught at other NASA centers as well as at JPL. Formal Inspections (NASA tailored Fagan Inspections) are a set of technical reviews whose objective is to increase quality and reduce the cost of software development by detecting and correcting errors early. A primary feature of inspections is the removal of engineering errors before they amplify into larger and more costly problems downstream in the development process. Note that the word 'inspection' is used differently in software than in a manufacturing context. A Formal Inspection is a front-end quality enhancement technique, rather than a task conducted just prior to product shipment for the purpose of sorting defective systems (manufacturing usage). Formal Inspections are supporting and in agreement with the 'total quality' approach being adopted by many NASA centers.

certified instructors Formal Inspections↗

SACD's Support of the Hyper-X Program

NASA s highly successful Hyper-X program demonstrated numerous hypersonic air-breathing vehicle related technologies including scramjet performance, advanced materials and hot structures, GN&C, and integrated vehicle performance resulting in, for the first time ever, acceleration of a vehicle powered by a scramjet engine. The Systems Analysis and Concepts Directorate (SACD) at NASA s Langley Research Center played a major role in the integrated team providing critical support, analysis, and leadership to the Hyper-X Program throughout the program s entire life and were key to its ultimate success. Engineers in SACD s Vehicle Analysis Branch (VAB) were involved in all stages and aspects of the program, from conceptual design prior to contract award, through preliminary design and hardware development, and in to, during, and after each of the three flights. Working closely with other engineers at Langley and Dryden, as well as industry partners, roughly 20 members of SACD were involved throughout the evolution of the Hyper-X program in nearly all disciplines, including lead roles in several areas. Engineers from VAB led the aerodynamic database development, the propulsion database development, and the stage separation analysis and database development effort. Others played major roles in structures, aerothermal, GN&C, trajectory analysis and flight simulation, as well as providing CFD support for aerodynamic, propulsion, and aerothermal analysis.

Robinson, Jeffrey S.↗

Model Checking Abstract PLEXIL Programs with SMART

We describe a method to automatically generate discrete-state models of abstract Plan Execution Interchange Language (PLEXIL) programs that can be analyzed using model checking tools. Starting from a high-level description of a PLEXIL program or a family of programs with common characteristics, the generator lays the framework that models the principles of program execution. The concrete parts of the program are not automatically generated, but require the modeler to introduce them by hand. As a case study, we generate models to verify properties of the PLEXIL macro constructs that are introduced as shorthand notation. After an exhaustive analysis, we conclude that the macro definitions obey the intended semantics and behave as expected, but contingently on a few specific requirements on the timing semantics of micro-steps in the concrete executive implementation.

Siminiceanu, Radu I.↗

Computer Programs (Turbomachinery)

NASA computer programs are extensively used in design of industrial equipment. Available from the Computer Software Management and Information Center (COSMIC) at the University of Georgia, these programs are employed as analysis tools in design, test and development processes, providing savings in time and money. For example, two NASA computer programs are used daily in the design of turbomachinery by Delaval Turbine Division, Trenton, New Jersey. The company uses the NASA splint interpolation routine for analysis of turbine blade vibration and the performance of compressors and condensers. A second program, the NASA print plot routine, analyzes turbine rotor response and produces graphs for project reports. The photos show examples of Delaval test operations in which the computer programs play a part. In the large photo below, a 24-inch turbine blade is undergoing test; in the smaller photo, a steam turbine rotor is being prepared for stress measurements under actual operating conditions; the "spaghetti" is wiring for test instrumentation

Source record↗

Verification and Planning Based on Coinductive Logic Programming

Coinduction is a powerful technique for reasoning about unfounded sets, unbounded structures, infinite automata, and interactive computations [6]. Where induction corresponds to least fixed point's semantics, coinduction corresponds to greatest fixed point semantics. Recently coinduction has been incorporated into logic programming and an elegant operational semantics developed for it [11, 12]. This operational semantics is the greatest fix point counterpart of SLD resolution (SLD resolution imparts operational semantics to least fix point based computations) and is termed co- SLD resolution. In co-SLD resolution, a predicate goal p( t) succeeds if it unifies with one of its ancestor calls. In addition, rational infinite terms are allowed as arguments of predicates. Infinite terms are represented as solutions to unification equations and the occurs check is omitted during the unification process. Coinductive Logic Programming (Co-LP) and Co-SLD resolution can be used to elegantly perform model checking and planning. A combined SLD and Co-SLD resolution based LP system forms the common basis for planning, scheduling, verification, model checking, and constraint solving [9, 4]. This is achieved by amalgamating SLD resolution, co-SLD resolution, and constraint logic programming [13] in a single logic programming system. Given that parallelism in logic programs can be implicitly exploited [8], complex, compute-intensive applications (planning, scheduling, model checking, etc.) can be executed in parallel on multi-core machines. Parallel execution can result in speed-ups as well as in larger instances of the problems being solved. In the remainder we elaborate on (i) how planning can be elegantly and efficiently performed under real-time constraints, (ii) how real-time systems can be elegantly and efficiently model- checked, as well as (iii) how hybrid systems can be verified in a combined system with both co-SLD and SLD resolution. Implementations of co-SLD resolution as well as preliminary implementations of the planning and verification applications have been developed [4]. Co-LP and Model Checking: The vast majority of properties that are to be verified can be classified into safety properties and liveness properties. It is well known within model checking that safety properties can be verified by reachability analysis, i.e, if a counter-example to the property exists, it can be finitely determined by enumerating all the reachable states of the Kripke structure.

Bansal, Ajay↗

New Directions for NASA's Advanced Life Support Program

Advanced Life Support (ALS), an element of Human Systems Research and Technology s (HSRT) Life Support and Habitation Program (LSH), has been NASA s primary sponsor of life support research and technology development for the agency. Over its history, ALS sponsored tasks across a diverse set of institutions, including field centers, colleges and universities, industry, and governmental laboratories, resulting in numerous publications and scientific articles, patents and new technologies, as well as education and training for primary, secondary and graduate students, including minority serving institutions. Prior to the Vision for Space Exploration (VSE) announced on January 14th, 2004 by the President, ALS had been focused on research and technology development for long duration exploration missions, emphasizing closed-loop regenerative systems, including both biological and physicochemical. Taking a robust and flexible approach, ALS focused on capabilities to enable visits to multiple potential destinations beyond low Earth orbit. ALS developed requirements, reference missions, and assumptions upon which to structure and focus its development program. The VSE gave NASA a plan for steady human and robotic space exploration based on specific, achievable goals. Recently, the Exploration Systems Architecture Study (ESAS) was chartered by NASA s Administrator to determine the best exploration architecture and strategy to implement the Vision. The study identified key technologies required to enable and significantly enhance the reference exploration missions and to prioritize near-term and far-term technology investments. This technology assessment resulted in a revised Exploration Systems Mission Directorate (ESMD) technology investment plan. A set of new technology development projects were initiated as part of the plan s implementation, replacing tasks previously initiated under HSRT and its sister program, Exploration Systems Research and Technology (ESRT). The Exploration Life Support (ELS) Project, under the Exploration Technology Development Program, has recently been initiated to perform directed life support technology development in support of Constellation and the Crew Exploration Vehicle (CEV). ELS) has replaced ALS, with several major differences. Thermal Control Systems have been separated into a new stand alone project (Thermal Systems for Exploration Missions). Tasks in Advanced Food Technology have been relocated to the Human Research Program. Tasks in a new discipline area, Habitation Engineering, have been added. Research and technology development for capabilities required for longer duration stays on the Moon and Mars, including bioregenerative system, have been deferred.

Barta, Daniel J.↗

Implementing an Applied Science Program

The work implied in the NASA Applied Science Program requires a delicate balancing act for the those doing it. At the implementation level there are multiple tensions intrinsic to the program. For example each application of an existing product to a decision support process requires deep knowledge about the data and deep knowledge about the decision making process. It is highly probable no one person has this range of knowledge. Otherwise the decision making process would already be using the data. Therefore, a team is required. But building a team usually requires time, especially across agencies. Yet the program mandates efforts of relatively short duration. Further, those who know the data are scientists, which makes them essential to the program. But scientists are evaluated on their publication record. Anything which diverts a scientist from the research for his next publication is an anathema to him and potential death to their career. Trying to get another agency to use NASA data does not strike most scientists as material inherently suitable for publication. Also, NASA wishes to rapidly implement often substantial changes to another agency's process. For many reasons, such as budget and program constraints, speed is important. But the owner of a decision making process is tightly constrained, usually by law, regulation, organization and custom. Changes when made are slow, cautious, even hesitant, and always done according a process specific to the situation. To manage this work MSFC must balance these and other tensions. Some things we have relatively little control over, such as budget. These we try to handle by structural techniques. For example by insisting all of our people work on multiple projects simultaneously we inherently have diversification of funding for all of our people. In many cases we explicitly use some elements of tension to be productive. For example the need for the scientists to constantly publish is motivation to keep tasks short and to the immediate point. As another example, the DSS agency and it personnel are treated as integral to the effort at every step. Thus, their ways of doing things, their problems and their assets become part of the solution. MSFC also manages the Applied Science work' within a strategic framework.' First, the scientists are necessarily at the core of all of this work as well as all of the work within the larger' organization. We therefore strive to keep a roughly 50-50 balance between the work done on tasks funded directly by the research side of NASA's Science Mission Directorate and funding from the applied side. Done at both the organization level and the level of the individual, this keeps the scientist both happy and productive over the long term. We also try diligently to remove as much burden from the scientist as practical by employing people such as the authors and others to do tasks not requiring; scientific knowledge. We also have designed our effort to take full use of external partners. We actively seek and support, including fund, people from multiple organizations to join us as committed collaborators. In this we use today's money and today's problem to help us diversify and strengthen for tomorrow. MSFC also considers the Applied Science work holistically. Each element is viewed as a step in a larger process. At a management level we can chose to emphasize or encourage certain areas which service long term goals. Thus, if we think work in a particular area should be developed, we can start with the smaller, less costly elements and grow.

Rickman, Doug↗

PrimeSupplier Cross-Program Impact Analysis and Supplier Stability Indicator Simulation Model

PrimeSupplier, a supplier cross-program and element-impact simulation model, with supplier solvency indicator (SSI), has been developed so that the shuttle program can see early indicators of supplier and product line stability, while identifying the various elements and/or programs that have a particular supplier or product designed into the system. The model calculates two categories of benchmarks to determine the SSI, with one category focusing on agency programmatic data and the other focusing on a supplier's financial liquidity. PrimeSupplier was developed to help NASA smoothly transition design, manufacturing, and repair operations from the Shuttle program to the Constellation program, without disruption in the industrial supply base.

Calluzzi, Michael↗

The New Weather Radar for America's Space Program in Florida: A Temperature Profile Adaptive Scan Strategy

A new weather radar is being acquired for use in support of America s space program at Cape Canaveral Air Force Station, NASA Kennedy Space Center, and Patrick AFB on the east coast of central Florida. This new radar replaces the modified WSR-74C at Patrick AFB that has been in use since 1984. The new radar is a Radtec TDR 43-250, which has Doppler and dual polarization capability. A new fixed scan strategy was designed to best support the space program. The fixed scan strategy represents a complex compromise between many competing factors and relies on climatological heights of various temperatures that are important for improved lightning forecasting and evaluation of Lightning Launch Commit Criteria (LCC), which are the weather rules to avoid lightning strikes to in-flight rockets. The 0 C to -20 C layer is vital since most generation of electric charge occurs within it and so it is critical in evaluating Lightning LCC and in forecasting lightning. These are two of the most important duties of 45 WS. While the fixed scan strategy that covers most of the climatological variation of the 0 C to -20 C levels with high resolution ensures that these critical temperatures are well covered most of the time, it also means that on any particular day the radar is spending precious time scanning at angles covering less important heights. The goal of this project is to develop a user-friendly, Interactive Data Language (IDL) computer program that will automatically generate optimized radar scan strategies that adapt to user input of the temperature profile and other important parameters. By using only the required scan angles output by the temperature profile adaptive scan strategy program, faster update times for volume scans and/or collection of more samples per gate for better data quality is possible, while maintaining high resolution at the critical temperature levels. The temperature profile adaptive technique will also take into account earth curvature and refraction when geo-locating the radar beam (i.e., beam height and arc distance), including non-standard refraction based on the user-input temperature profile. In addition to temperature profile adaptivity, this paper will also summarize the other requirements for this scan strategy program such as detection of low-level boundaries, detection of anvil clouds, reducing the Cone Of Silence, and allowing for times when deep convective clouds will not occur. The adaptive technique will be carefully compared to and benchmarked against the new fixed scan strategy. Specific environmental scenarios in which the adaptive scan strategy is able to optimize and improve coverage and resolution at critical heights, scan time, and/or sample numbers relative to the fixed scan strategy will be presented.

Carey, L. D.↗

Infrastructure for Rapid Development of Java GUI Programs

The Java Application Shell (JAS) is a software framework that accelerates the development of Java graphical-user-interface (GUI) application programs by enabling the reuse of common, proven GUI elements, as distinguished from writing custom code for GUI elements. JAS is a software infrastructure upon which Java interactive application programs and graphical user interfaces (GUIs) for those programs can be built as sets of plug-ins. JAS provides an application- programming interface that is extensible by application-specific plugins that describe and encapsulate both specifications of a GUI and application-specific functionality tied to the specified GUI elements. The desired GUI elements are specified in Extensible Markup Language (XML) descriptions instead of in compiled code. JAS reads and interprets these descriptions, then creates and configures a corresponding GUI from a standard set of generic, reusable GUI elements. These elements are then attached (again, according to the XML descriptions) to application-specific compiled code and scripts. An application program constructed by use of JAS as its core can be extended by writing new plug-ins and replacing existing plug-ins. Thus, JAS solves many problems that Java programmers generally solve anew for each project, thereby reducing development and testing time.

Jones, Jeremy↗