Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “software differences”

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,765 records · Page 98

Assessing Alaskan boreal forest landcover affected by climate-wildfire interactions from ground truth surveys and NASA airborne remote sensing

Alaska’s boreal forest is facing unprecedented challenges under rapid climate warming (increasingly severe fires, droughts, pest/disease outbreaks) that may destabilize its function as a global carbon sink. Forests near Fairbanks may be especially vulnerable, impacting air quality and ecosystem services. We combined GT (ground truthing) with Airborne Visible InfraRed Imaging Spectrometer (AVIRIS-NG) images collected by the NASA Arctic-Boreal Vulnerability Experiment (ABoVE) program (2017-2019) to assess landcover change at five recently burned sites (2001-2019) of different fire severities and moisture regimes within 30 miles of Fairbanks. GT included tree seedling counts, understory % cover and >50% leaf canopy color assessment. 36 circular plots (1/30 ha radius) including 6 moderate to severely burned plots were selected across sites. 31 additional sites including 12 burned sites were geotagged in photos. AVIRIS images were processed from 29 spectral bands selected to identify changes in chlorophyll and water content. Images were segmented into natural boundaries (polygons) using ENVI 5.5 software. A spectral library of 8 AVIRIS bands with high between-class/low within-class variation was used in two random forest models to predict vegetation classes (model 1: 12 classes, model 2: 14 classes) in each AVIRIS scene, using 20% of the data as training data. Model 2 classified 20% more polygons overall, but only 42% of GT/geotagged polygons were correctly classified by both models. More forest sites were correctly classified (63%) than open vegetation (32%) or post-fire sites (46%). 50% of aspen forest and post-fire polygons were misclassified as shrubland. GT revealed that post-fire plots supported 134,000 (± 48,000) tree seedlings and saplings ha-1 (0.2 - 4 m height, 64% deciduous) versus 2500 (± 2100) shrubs ha-1 (1-6 m height). > 50% canopy browning was observed in conifer forest (8 plots) with no signs of insect infestation. Canopy herbivory > 50% (leaf miner, leaf beetle) and moose herbivory of tree bark was seen across aspen sites. Our study suggests: 1) low canopy vegetation presents challenges for improved landcover classification, and 2) aspen forest should be differentiated in vegetation maps which would aid in tracking herbivory.

Alaska↗

Flight Test of an Intelligent Flight-Control System

The F-15 Advanced Controls Technology for Integrated Vehicles (ACTIVE) airplane (see figure) was the test bed for a flight test of an intelligent flight control system (IFCS). This IFCS utilizes a neural network to determine critical stability and control derivatives for a control law, the real-time gains of which are computed by an algorithm that solves the Riccati equation. These derivatives are also used to identify the parameters of a dynamic model of the airplane. The model is used in a model-following portion of the control law, in order to provide specific vehicle handling characteristics. The flight test of the IFCS marks the initiation of the Intelligent Flight Control System Advanced Concept Program (IFCS ACP), which is a collaboration between NASA and Boeing Phantom Works. The goals of the IFCS ACP are to (1) develop the concept of a flight-control system that uses neural-network technology to identify aircraft characteristics to provide optimal aircraft performance, (2) develop a self-training neural network to update estimates of aircraft properties in flight, and (3) demonstrate the aforementioned concepts on the F-15 ACTIVE airplane in flight. The activities of the initial IFCS ACP were divided into three Phases, each devoted to the attainment of a different objective. The objective of Phase I was to develop a pre-trained neural network to store and recall the wind-tunnel-based stability and control derivatives of the vehicle. The objective of Phase II was to develop a neural network that can learn how to adjust the stability and control derivatives to account for failures or modeling deficiencies. The objective of Phase III was to develop a flight control system that uses the neural network outputs as a basis for controlling the aircraft. The flight test of the IFCS was performed in stages. In the first stage, the Phase I version of the pre-trained neural network was flown in a passive mode. The neural network software was running using flight data inputs with the outputs provided to instrumentation only. The IFCS was not used to control the airplane. In another stage of the flight test, the Phase I pre-trained neural network was integrated into a Phase III version of the flight control system. The Phase I pretrained neural network provided realtime stability and control derivatives to a Phase III controller that was based on a stochastic optimal feedforward and feedback technique (SOFFT). This combined Phase I/III system was operated together with the research flight-control system (RFCS) of the F-15 ACTIVE during the flight test. The RFCS enables the pilot to switch quickly from the experimental- research flight mode back to the safe conventional mode. These initial IFCS ACP flight tests were completed in April 1999. The Phase I/III flight test milestone was to demonstrate, across a range of subsonic and supersonic flight conditions, that the pre-trained neural network could be used to supply real-time aerodynamic stability and control derivatives to the closed-loop optimal SOFFT flight controller. Additional objectives attained in the flight test included (1) flight qualification of a neural-network-based control system; (2) the use of a combined neural-network/closed-loop optimal flight-control system to obtain level-one handling qualities; and (3) demonstration, through variation of control gains, that different handling qualities can be achieved by setting new target parameters. In addition, data for the Phase-II (on-line-learning) neural network were collected, during the use of stacked-frequency- sweep excitation, for post-flight analysis. Initial analysis of these data showed the potential for future flight tests that will incorporate the real-time identification and on-line learning aspects of the IFCS.

Davidson, Ron↗

Power Operations of the Mars Exploration Rovers

The rovers of the National Aeronautics and Space Administration’s (NASA) Mars Exploration Rovers (MER) project, Spirit (MER-A) and Opportunity (MER-B), safely landed on the surface of Mars three weeks apart during January 2004. Spirit and Opportunity were built and operated by the Jet Propulsion Laboratory (JPL), which is managed by the California Institute of Technology (Caltech) for NASA. Spirit landed at Gusev Crater, 14.8 degrees south of the equator, and operated continuously on the surface of Mars from January 4, 2004 until last contact from Spirit on March 22, 2010. Opportunity landed at Meridiani Planum, a location 2.5 degrees south of the Martian equator. Opportunity operated continuously on the Martian surface from January 25, 2004 until the last received transmission from Opportunity on June 10, 2018. The goal of the MER project was to determine if Mars ever had a habitable environment, in particular, if it ever had water. During their missions, both Spirit and Opportunity found evidence that liquid water once flowed on the surface of Mars. Both Spirit and Opportunity used a 1.33 m2 triple-junction solar array as their power sources. Based on observations of the original Mars rover, the Sojourner rover of the Mars Pathfinder mission that landed on Mars on July 4, 1997, the expectation was that the Martian dust would rapidly accumulate on the solar arrays of Spirit and Opportunity, and that the rovers would not have enough energy to continue operations after 90 Martian days (sols). Instead, due in part to lower dust accumulation rates than expected and numerous dust cleaning events, the Spirit and Opportunity rovers continued to operate on the Martian surface for over 2000 sols (MER-A) and 5000 sols (MER-B), respectively. During this time, the rovers experienced multiple Martian winters and several dust storms. Because the sources of solar array energy loss were known, the solar array energy output offered a method to scientifically estimate the loading and aeolian removal of dust from the solar arrays each sol. The MER Power operations team called this value that they calculated the solar array Dust Factor (DF). Dust Factor was defined as the fraction of sunlight that penetrates the accumulated dust on the surface of the solar array. A Dust Factor of 1.0 would indicate that the solar array was perfectly clean. A Dust Factor of 0.6 would indicate that only 60% of the available sunlight was able to penetrate the accumulated dust on the solar arrays. The MER Power subsystem operations team used the Multi-Mission Power Analysis Tool (MMPAT) to perform these Dust Factor calculations. The MMPAT software tool modeled the behavior of the solar arrays and the batteries as they interacted with the spacecraft power loads over the mission timeline. MMPAT also had knowledge (through telemetry and user inputs) of telemetered Power subsystem voltages and currents, atmospheric opacity (Tau), rover surface location, rover attitude, the planetary tilt and distance of Mars from the sun based on day of year, the instantaneous elevation of the sun based on time of day, temperatures (internal and external), terrain masking, and shadowing (due to the camera mast and antennas). Once all of the known sources of array energy loss are accounted, the remaining difference between the expected array energy and the actual array energy determines the solar array Dust Factor. The assumptions made while determining the Dust Factor are 1) that the single measured atmospheric opacity value (Tau) is constant over the course of the entire sol, 2) there is no measurable solar cell degradation, 3) there are no shorted strings and therefore, 4) all unexpected solar array energy losses are due to accumulated dust on the solar array. Although it cannot provide an absolute measure of dust loading, the determination of solar array Dust Factor provides a useful way of tracking dust accumulation and aeolian dust removal trends on Martian spacecraft. Any spacecraft on the Martian surface is vulnerable to dust, especially solar-powered spacecraft. The Spirit and Opportunity rovers were operational on the Martian surface for much longer than expected due in part to aeolian removal of dust from their solar arrays. The first few dust removal events were a pleasant surprise to the MER operations teams; however, over time a pattern began to arise. In over three Mars Years on the surface, the Power operations team tracked the solar array Dust Factor at Gusev Crater (location of MER-A) and observed that there were several significant dust removal and deposition events in Mars Year (MY) 27, even in the absence of a large dust storm. In MY 28 at Gusev Crater, the large atmospheric opacity (Tau) increase lagged significant dust removal events. Overall at Gusev Crater, there was a pattern of steady dust accumulation on the solar arrays, with a small number of significant dust cleaning events. At Meridiani Planum, where Opportunity rover operated for over seven Mars Years (late MY 26 to mid MY 34), a clear and consistent pattern of dust movement emerged. Meridiani Planum had a predictable, seasonally dependent pattern of gradual and continuous dust accumulation and removal. In summary, this paper explains the reasons for the development of the solar array Dust Factor and how it was used in mission operations. In particular, this paper describes the MMPAT software package, how it models array energy, including the important assumptions, model inputs and sources of error. And finally, this paper will show how the calculated solar array Dust Factor was used at Gusev Crater and Meridiani Planum to predict dust accumulation rates and weather patterns, and the importance of this generated data set for current and future solar- powered missions to Mars, such as the InSight lander and the planned Mars Sample Return rover.

Chin, Keith B.↗

Measurements of helicopter rotor tip vortices

This paper presents results from a recent wind-tunnel investigation of model helicopter rotor tip vortices. Measurements were made of the vortex positions, core sizes, and velocity distributions. A laser velocimeter was used to make the measurements, and a minicomputer-based data system was used to process the data and to aid in controlling the experiment. The velocimeter, the data system, and the software developed for the minicomputer are briefly described. The rotors investigated were two-bladed, teetering rotors with diameters of 2.1 m. Two sets of blades were used, one set with zero twist and one set with -11 deg of linear twist. The vortex positions were obtained by making flow field traverses while strobing the data system at a fixed azimuth. Aging of a vortex element was also studied by following the convected element while strobing the data system at different azimuths. By this method, the effects on the vortex of a close interaction with a blade and another vortex were studied.

Biggers, J. C.↗

User manual of the CATSS system (version 1.0) communication analysis tool for space station

The Communication Analysis Tool for the Space Station (CATSS) is a FORTRAN language software package capable of predicting the communications links performance for the Space Station (SS) communication and tracking (C & T) system. An interactive software package was currently developed to run on the DEC/VAX computers. The CATSS models and evaluates the various C & T links of the SS, which includes the modulation schemes such as Binary-Phase-Shift-Keying (BPSK), BPSK with Direct Sequence Spread Spectrum (PN/BPSK), and M-ary Frequency-Shift-Keying with Frequency Hopping (FH/MFSK). Optical Space Communication link is also included. CATSS is a C & T system engineering tool used to predict and analyze the system performance for different link environment. Identification of system weaknesses is achieved through evaluation of performance with varying system parameters. System tradeoff for different values of system parameters are made based on the performance prediction.

Tsang, C. S.↗

Remote sensing research for agricultural applications

Materials and methods used to characterize selected soil properties and agricultural crops in San Joaquin County, California are described. Results show that: (1) the location and widths of TM bands are suitable for detecting differences in selected soil properties; (2) the number of TM spectral bands allows the quantification of soil spectral curve form and magnitude; and (3) the spatial and geometric quality of TM data allows for the discrimination and quantification of within field variability of soil properties. The design of the LANDSAT based multiple crop acreage estimation experiment for the Idaho Department of Water Resources is described including the use of U.C. Berkeley's Survey Modeling Planning Model. Progress made on Peditor software development on MIDAS, and cooperative computing using local and remote systems is reported as well as development of MIDAS microcomputer systems.

Colwell, R. N.↗

Leveraging Existing Mission Tools in a Re-Usable, Component-Based Software Environment

Emerging methods in component-based software development offer significant advantages but may seem incompatible with existing mission operations applications. In this paper we relate our positive experiences integrating existing mission applications into component-based tools we are delivering to three missions. In most operations environments, a number of software applications have been integrated together to form the mission operations software. In contrast, with component-based software development chunks of related functionality and data structures, referred to as components, can be individually delivered, integrated and re-used. With the advent of powerful tools for managing component-based development, complex software systems can potentially see significant benefits in ease of integration, testability and reusability from these techniques. These benefits motivate us to ask how component-based development techniques can be relevant in a mission operations environment, where there is significant investment in software tools that are not component-based and may not be written in languages for which component-based tools even exist. Trusted and complex software tools for sequencing, validation, navigation, and other vital functions cannot simply be re-written or abandoned in order to gain the advantages offered by emerging component-based software techniques. Thus some middle ground must be found. We have faced exactly this issue, and have found several solutions. Ensemble is an open platform for development, integration, and deployment of mission operations software that we are developing. Ensemble itself is an extension of an open source, component-based software development platform called Eclipse. Due to the advantages of component-based development, we have been able to vary rapidly develop mission operations tools for three surface missions by mixing and matching from a common set of mission operation components. We have also had to determine how to integrate existing mission applications for sequence development, sequence validation, and high level activity planning, and other functions into a component-based environment. For each of these, we used a somewhat different technique based upon the structure and usage of the existing application.

Greene, Kevin↗

Correlative visualization techniques for multidimensional data

Critical to the understanding of data is the ability to provide pictorial or visual representation of those data, particularly in support of correlative data analysis. Despite the advancement of visualization techniques for scientific data over the last several years, there are still significant problems in bringing today's hardware and software technology into the hands of the typical scientist. For example, there are other computer science domains outside of computer graphics that are required to make visualization effective such as data management. Well-defined, flexible mechanisms for data access and management must be combined with rendering algorithms, data transformation, etc. to form a generic visualization pipeline. A generalized approach to data visualization is critical for the correlative analysis of distinct, complex, multidimensional data sets in the space and Earth sciences. Different classes of data representation techniques must be used within such a framework, which can range from simple, static two- and three-dimensional line plots to animation, surface rendering, and volumetric imaging. Static examples of actual data analyses will illustrate the importance of an effective pipeline in data visualization system.

Treinish, Lloyd A.↗

Integrated flow and structural modeling for rocket engine component test facility propellant systems

A set of PC-based computational Dynamic Fluid Flow Simulation models is presented for modeling facility gas and cryogenic systems. Data obtained provide important information regarding performance envelope parameters for the facility using different engine components; time-dependent valve setting for controlling steady-state, quasi-steady state, and transient profiles; optimum facility pipe and pipe component sizes and parameters; momentum transfer loads; and fluid conditions at critical points. A set of COSMIC NASTRAN-based finite element models is also presented to evaluate the loads and stresses on test facility piping systems from fluid and gaseous effects, thermal chill down, and occasional wind loads. The models are based on Apple Macintosh software which makes it possible to change numerous parameters.

Dequay, L.↗

An artificial reality environment for remote factory control and monitoring

Work has begun on the merger of two well known systems, VEOS (HITLab) and CLIPS (NASA). In the recent past, the University of Massachusetts Lowell developed a parallel version of NASA CLIPS, called P-CLIPS. This modification allows users to create smaller expert systems which are able to communicate with each other to jointly solve problems. With the merger of a VEOS message system, PCLIPS-V can now act as a group of entities working within VEOS. To display the 3D virtual world we have been using a graphics package called HOOPS, from Ithaca Software. The artificial reality environment we have set up contains actors and objects as found in our Lincoln Logs Factory of the Future project. The environment allows us to view and control the objects within the virtual world. All communication between the separate CLIPS expert systems is done through VEOS. A graphical renderer generates camera views on X-Windows devices; Head Mounted Devices are not required. This allows more people to make use of this technology. We are experimenting with different types of virtual vehicles to give the user a sense that he or she is actually moving around inside the factory looking ahead through windows and virtual monitors.

Kosta, Charles Paul↗

An Inviscid Computational Study of the Space Shuttle Orbiter and Several Damaged Configurations

Inviscid aerodynamic characteristics of the Space Shuttle Orbiter were computed in support of the Columbia Accident Investigation. The unstructured grid software FELISA was used and computations were done using freestream conditions corresponding to those in the NASA Langley 20-Inch Mach 6 CF4 tunnel test section. The angle of attack was held constant at 40 degrees. The baseline (undamaged) configuration and a large number of damaged configurations of the Orbiter were studied. Most of the computations were done on a half model. However, one set of computations was done using the full-model to study the effect of sideslip. The differences in the aerodynamic coefficients for the damaged and the baseline configurations were computed. Simultaneously with the computation reported here, tests were being done on a scale model of the Orbiter in the 20-Inch Mach 6 CF4 tunnel to measure the deltas . The present computations complemented the CF4 tunnel test, and provided aerodynamic coefficients of the Orbiter as well as its components. Further, they also provided details of the flow field.

Prabhu, Ramadas K.↗

NASA GES DISC DAAC Satellite Data for GIS

NASA's Goddard Earth Science (GES) Data and Information Services Center (DISC) Distributed Active Archive Center (DAAC) makes available a large and continually growing collection of spatially continuous global satellite observations of environmental parameters. These products include those from the MODIS (Moderate Resolution Imaging Spectroradiometer) on both Terra and Aqua platforms, and the Tropical Rainfall Measuring Mission (TRMM). These data products are well suited for use within Geographic Information Systems (GIS), as both backdrops to cartographic products as well as spatial analysis. However, data format, file size, and other issues have limited their widespread use by traditional GIS users. To address these data usability issues, the GES DISC DAAC recently updated tools and improved documentation of conversion procedures. In addition, the GES DISC DAAC has also been working with a major GIS software vendor to incorporate the ability to read the native Hierarchial Data Format (HDF), the format in which most of the NASA data is stored. The result is the enabling of GIS users to realize the benefit of GES DISC DAAC data without a substantial expenditure in resources to incorporate these data into their GIS. Several documents regarding the potential uses of GES DISC DAAC satellite data in GIS have recently been created. These show the combinations of concurrent data from different satellite products with traditional GIS vector products for given geographic areas. These map products include satellite imagery of Hurricane Isabel and the California wildfires, and can be viewed at http://daac.gsfc.nasa.gov/MODIS/GIS/.

Nickless, Darryl↗

The Development of NASA's Low Thrust Trajectory Tool Set

Highly efficient electric propulsion systems can enable interesting classes of missions; unfortunately, they provide only a limited amount of thrust. Low-thrust (LT) trajectories are much more difficult to design than impulsive-type (chemical propulsion) trajectories. Previous low-thrust (LT) trajectory optimization software was often difficult to use, often had difficulties converging, and was somewhat limited in the types of missions it could support. A new state-of-the-art suite (toolbox) of low-thrust (LT) tools along with improved algorithms and methods was developed by NASA's MSFC, JPL, JSC, and GRC to address the needs of our customers to help foster technology development in the areas of advanced LT propulsion systems, and to facilitate generation of similar results by different analysts.

Sims, Jon↗

[Interview Questions]

The Goddard Mission Services Evolution Center, or GMSEC, was started in 2001 to create a new standard approach for managing GSFC missions. Standardized approaches in the past involved selecting and then integrating the most appropriate set of functional tools. Assumptions were made that "one size fits all" and that tool changes would not be necessary for many years. GMSEC took a very different approach and has proven to be very successful. The core of the GMSEC architecture consists of a publish/subscribe message bus, standardized message formats, and an Applications Programming Interface (API). The API supports multiple operating systems, programming languages and messaging middleware products. We use a GMSEC-developed free middleware for low-cost development. A high capacity, robust middleware is used for operations and a messaging system with a very small memory footprint is used for on-board flight software. Software components can use the standard message formats or develop adapters to convert from their native formats to the GMSEC formats. We do not want vendors to modify their core products. Over 50 software components are now available for use with the GMSEC architecture. Most available commercial telemetry and command systems, including the GMV hifly Satellite Control System, have been adapted to run in the GMSEC labs.

Smith, Dan↗

VLBI-SLR Combination Solution Using GEODYN

We would like to generate a multi-technique solution combining all of the geodetic techniques (VLBI, SLR, GPS, and DORIS) using the same software and using the same a priori models. Here we use GEODYN software and consider only the VLBI-SLR combination. Here we report initial results of our work on the combination. We first performed solutions with GEODYN using only VLBI data and found that VLBI EOP solution results produced with GEODYN agree with results using CALC/SOLVE at the 1-sigma level. We then combined the VLBI normal equations in GEODYN with weekly SLR normal equations for the period 2007-2008. Agreement of estimated Earth orientation parameters with IERS C04 were not significantly different for the VLBI-only, SLR-only, and VLBI+SLR solutions

MacMillan, Dan↗

Diffusivities of Redox-Sensitive Elements in Basalt vs. Oxygen Fugacity Determined by LA-ICP-MS

Several diffusion experiments were conducted in a piston cylinder device across a range of oxygen fugacities (FMQ-3 FMQ-1.2, FMQ+6) at 1 GPa and 1300 C. This was done to explore the effects of oxygen fugacity (fO2) on diffusivity of redox sensitive trace elements. This allows investigation of how these elements diffuse across the fO2 range encountered in different reservoirs on planets and moons in our solar system. The University of Rochester LA-ICP-MS system was used for analysis of samples. Analyses were conducted using an Agilent 7900 quadrupole mass spectrometer connected to a Photon Machines 193 nm G2 laser ablation (LA) system equipped with a HelEx 2-volume sample chamber. Spots used were 35 micrometers circles spaced at 65 micrometers intervals. Laser fluence was 7.81 J/cm^2 with a rep rate of 10 Hz. The iolite software package was used to reduce data collected from laser ablation analysis of experiments with Si-29 used as the internal standard isotope. Iolite's global fit module was used to simultaneously fit elements' diffusivities in each experiment while keeping the Matano interface constant. Elements analysed include V, Nb, W, Mo, La, Ce, Pr, Sm, Eu, Gd, Ta, and W. Figures

Szumila, Ian↗

Rapid Model Import Tool (RMIT)

Our project is about developing a tool to implement conversion of 3D Computer Aided Design (CAD) models produced with software such as Delmia, 3DS Max, or Maya, into a size and format compatible with the Unity 3D environment. RMIT will be used to aid KSC engineering personnel in the design, development, testing, operations, and training on spacecraft, launch vehicles, facilities, and ground support equipment. For our project, we are using Blender, a free/open-source 3D graphics software, with the goal of developing, testing, and deploying a 3D CAD model converter tool. I worked on using Blender to import 3D CAD models exported from CATIA software into Collada file format. The Collada file format has file extension DAE. Importing the Collada DAE file as is into Blender, generates dots and dashes. In 3DS Max, there is an existing OpenCollada plugin and with that plugin, 3DS Max can import the DAE file successfully. But, Blender does not seem to have an OpenCollada plugin, so I worked on writing a new OpenCollada plugin for Blender. Since 3DS Max was able to display the image, I looked into comparing differences between the original DAE file and the DAE file exported from 3DS Max using the OpenCollada plugin. As Collada documents describing digital assets are XML files with file extension DAE, Collada files contains XML tags, making them easily modifiable. After some research, it appears that Blender does not like primitive 2D tags like tristrips and trifans. Changing those tags to polygons slightly improved the image, but the pieces were exploded. I found after further research comparing differences between the original file and the file exported from 3DS Max that the values inside the translate tags in the original file are scaled down by a factor of 25.4 in the exported file from 3DS Max, representing the millimeters to inches conversion (1 inch = 25.4 millimeters). After scaling down values inside all of the translate tags by 25.4, the exploded pieces stuck back in, but the image needed further improvement. I have been able to create a new plugin in Blender that takes the original DAE file, replaces the primitive 2D tags tristrips and trifans with polygons, scales down the values inside the translate tags by a factor of 25.4, and saves the changes into a temporary DAE file. After the temporary DAE file is imported into Blender, the temp file is then deleted, keeping the original DAE file intact. Starting with a DAE file that is exported using the NASA Enterprise Visualization Application (NEVA), a Collada exporter, from CATIA gives better results. NEVA is a Design Visualization product that is used for exporting 3D models from CATIA. With NEVA, the up axis is defined in the top-level node if navigation gravity is enabled. With that file, just replacing the primitive tags tristrips and trifans with polygons in yields a much improved image in Blender. As we identify more differences between the original DAE file and the DAE file exported from 3DS Max, this plugin can be improved further. Our goal is to have a model that is formatted and sized for import into Unity, and we are trying out different 3D programs to see which will work best.

Ayyangar, Arjun↗

Development of a Dynamically Configurable, Object-Oriented Framework for Distributed, Multi-modal Computational Aerospace Systems Simulation: Second Year Progress Report

Mesh generation has long been recognized as a bottleneck in the CFD process. While much research on automating the volume mesh generation process have been relatively successful,these methods rely on appropriate initial surface triangulation to work properly. Surface discretization has been one of the least automated steps in computational simulation due to its dependence on implicitly defined CAD surfaces and curves. Differences in CAD peometry engines manifest themselves in discrepancies in their interpretation of the same entities. This lack of "good" geometry causes significant problems for mesh generators, requiring users to "repair" the CAD geometry before mesh generation. The problem is exacerbated when CAD geometry is translated to other forms (e.g., IGES )which do not include important topological and construction information in addition to entity geometry. One technique to avoid these problems is to access the CAD geometry directly from the mesh generating software, rather than through files. By accessing the geometry model (not a discretized version) in its native environment, t h s a proach avoids translation to a format which can deplete the model of topological information. Our approach to enable models developed in the Denali software environment to directly access CAD geometry and functions is through an Application Programming Interface (API) known as CAPRI. CAPRI provides a layer of indirection through which CAD-specific data may be accessed by an application program using CAD-system neutral C and FORTRAN language function calls. CAPRI supports a general set of CAD operations such as truth testing, geometry construction and entity queries.

Afjeh, Abdollah A.↗