Engineering PapersSearch

SEARCH · Engineering Papers

Results for “STL”

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 37 records · Page 2

STS-59 Space Shuttle mission report

The STS-59 Space Shuttle Program Mission Report summarizes the Payload activities as well as the Orbiter, External Tank (ET), Solid Rocket Booster (SRB), Redesigned Solid Rocket Motor (RSRM), and the Space Shuttle main engine (SSME) systems performance during the sixty-second flight of the Space Shuttle Program and sixth flight of the Orbiter vehicle Endeavor (OV-105). In addition to the Orbiter, the flight vehicle consisted of an ET designated as ET-63; three SSME's which were designated as serial numbers 2028, 2033, and 2018 in positions 1, 2, and 3, respectively; and two SRB's which were designated BI-065. The RSRM's that were installed in each SRB were designated as 360W037A (welterweight) for the left SRB, and 360H037B (heavyweight) for the right SRB. This STS-59 Space Shuttle Program Mission Report fulfills the Space Shuttle Program requirement as documented in NSTS 07700, Volume 8, Appendix E. That document requires that each major organizational element supporting the Program report the results of its hardware evaluation and mission performance plus identify all related in-flight anomalies. The primary objective of the STS-59 mission was to successfully perform the operations of the Space Radar Laboratory-1 (SRL-1). The secondary objectives of this flight were to perform the operations of the Space Tissue Loss-A (STL-A) and STL-B payloads, the Visual Function Tester-4 (VFT-4) payload, the Shuttle Amateur Radio Experiment-2 (SAREX-2) experiment, the Consortium for Materials Development in Space Complex Autonomous Payload-4 (CONCAP-4), and the three Get-Away Special (GAS) payloads.

Fricke, Robert W., Jr.

Development of the Fish Medaka in Microgravity

The goal of these experiments was to determine the effect of microgravity on the early development of the fish medaka. There were two objectives for this flight series. The primary objective was to assess the effects of microgravity on different stages of development and to ascertain whether the relevant developmental questions can be addressed at the gross morphological level or if the issues involve more subtle questions about regulation at the molecular and cellular levels. The secondary objective was the assessment of the utility of flight hardware with the capabilities to perform embryological studies. We have been able to take advantage of the flight testing phase of the STL-B hardware to also study the effects of microgravity on the early development of the fish, Medaka. Our initial studies involved monitoring the early Medaka development and raising flight embryos for breeding. Images of the developing embryos were collected either via video which was either taken by the astronauts or broadcast to Earth. Sample video images were digitized and stored on a hard drive resident within the on-board STL-B unit. Embryos were fixed at specific intervals, returned to Earth and are being analyzed for the timing and location of molecular events associated with controlling the morphological pattern for the onset of adult structures.

Wolgemuth, Debra J.

Pulsed Lidar Performance/Technical Maturity Assessment

This report describes the results of investigations performed by the Georgia Tech Research Institute (GTRI) and the National Center for Atmospheric Research (NCAR) under a task entitled 'Pulsed Lidar Performance/Technical Maturity Assessment' funded by the Crew Systems Branch of the Airborne Systems Competency at the NASA Langley Research Center. The investigations included two tasks, 1.1(a) and 1.1(b). The Tasks discussed in this report are in support of the NASA Virtual Airspace Modeling and Simulation (VAMS) program and are designed to evaluate a pulsed lidar that will be required for active wake vortex avoidance solutions. The Coherent Technologies, Inc. (CTI) WindTracer LIDAR is an eye-safe, 2-micron, coherent, pulsed Doppler lidar with wake tracking capability. The actual performance of the WindTracer system was to be quantified. In addition, the sensor performance has been assessed and modeled, and the models have been included in simulation efforts. The WindTracer LIDAR was purchased by the Federal Aviation Administration (FAA) for use in near-term field data collection efforts as part of a joint NASA/FAA wake vortex research program. In the joint research program, a minimum common wake and weather data collection platform will be defined. NASA Langley will use the field data to support wake model development and operational concept investigation in support of the VAMS project, where the ultimate goal is to improve airport capacity and safety. Task 1.1(a), performed by NCAR in Boulder, Colorado to analyze the lidar system to determine its performance and capabilities based on results from simulated lidar data with analytic wake vortex models provided by NASA, which were then compared to the vendor's claims for the operational specifications of the lidar. Task 1.1(a) is described in Section 3, including the vortex model, lidar parameters and simulations, and results for both detection and tracking of wake vortices generated by Boeing 737s and 747s. Task 1.1(b) was performed by GTRI in Atlanta, Georgia and is described in Section 4. Task 1.1(b) includes a description of the St. Louis Airport (STL) field test being conducted by the Volpe National Transportation Systems Center, and it also addresses the development of a test plan to validate simulation studies conducted as part of Task 1.1(a). Section 4.2 provides a description of the Volpe STL field tests, and Section 4.3 describes 3 possible ways to validate the WindTracer lidar simulations performed in Task 1.1(a).

Gimmestad, Gary G.

Loft: An Automated Mesh Generator for Stiffened-Shell Aerospace Vehicles

Loft is an automated mesh generation code designed for aerospace vehicle structures. Based on user input, it can generate meshes for wings, noses, tanks, fuselage sections, thrust structures, etc. As the mesh is generated, each element is assigned properties that mark what part of the vehicle it is associated with. This property assignment is an extremely powerful feature making possible detailed analysis tasks such as load application and sizing. Loft can save its meshes in NASTRAN bulk data deck, EDS’ I-DEAS Universal File format, Abaqus input file format, VRML 2.0 (Virtual Reality Modeling Language) and STL (Stereo Lithography) files. The property assignment scheme was designed to make sizing in Collier Research’s HyperSizer easy. Support for other mesh storage formats can be added as needed.

Structural modeling

Testing the Activation Analysis for Fusion in OpenMC

OpenMC is a community-developed Monte Carlo neutron and photon transport simulation code. It can perform fission simulations such as fixed-source, k-eigenvalue, and subcritical multiplication calculations on models built using either a constructive solid geometry or CAD representation. To explore the use of OpenMC for fusion activation analysis, a detailed model of the Fusion Neutronics Science Facility (FNSF) was first developed for comparisons against an existing SERPENT model. A 90-degree model of FNSF in Standard-Triangle-Language (STL) CAD format was converted to Constructive Solid Geometry (CSG) using each code's built-in functions, and the geometries were validated by ensuring no cells overlapped and no particles were lost during simulations. The neutron fluxes were calculated and compared for multiple components close to the plasma. The results show differences mostly below 1% in fluxes and averaged 8% for activity and decay heat. Here, the work described in this study tests the CAD-based geometry using the DagMC toolkit in OpenMC and compares the activation analysis of OpenMC to SERPENT code.

70 PLASMA PHYSICS AND FUSION TECHNOLOGY

stl2points

STL to Particle Conversion Tool

Lei, Zhou

ROSE Castor

ROSE Castor is a tool enabling automated verification of C++, built off of the ROSE compiler framework and the Why3 framework. Castor defines a verification language for providing specifications of C++ code, letting users perform automated functional formal verification of their C++ code. Castor is designed to target C++17, and supports a subset of the language, including classes, functions, templates, integers and booleans, pointers and references, and single inheritance. Castor currently does not support multiple or virtual inheritance, virtual functions, floating-point, threading, lambda functions, or the C++ STL, though some of these are planned in future updates. Castor ships with an in-house parser for parsing verification conditions.

Lane, PhillipA [Lawrence Livermore National Labora

LayerOver

Library for handling DIW-related gcode, producing novel metrics, analyzing PSPP relationships, and limited visualization of structures (STL, point clouds).

Pital, Aaron

Field and Model Data Associated with the Manuscript “Drivers of Streamflow Intermittency in Humid Regions: 1. Evaluating Above- and Below-ground Controls of Flow Persistence in a Forested Catchment”

This package contains field data, modeling files, and scripts supporting the investigation of the drivers of streamflow intermittency in a forested catchment. It includes the field data collected from electrical resistivity tomography (ERT) surveys, ground penetrating radar (GPR), continuous self-potential (SP) monitoring, electromagnetic (EM) imaging, groundwater and stilling well. In addition, it contains the data and results of the coupled water- and electrical-flow model developed using the COMSOL Multiphysics and Advanced Terrestrial Simulator (ATS), as well as software files and Jupyter notebooks used to process the data and generate figures in the manuscript submitted for peer review. The data archive is organized in the following directories: 1) Climate Includes hourly precipitation and daily evapotranspiration time series (2024 – 2025) provided as CSV files, alongside a text file detailing dataset units. 2) Coupled_model Contains two subfolders: Synthetic and Field_Application subfolder. Synthetic subfolder contains the ATS XML input script (can be opened using any code editor) for the four synthetic hydrological cases tested (Connected and gaining, Connected and losing, Disconnected and losing, and dry stream). It also includes other experimental cases to test the influence of precipitation and concentration gradient. For each synthetic case, the flow model simulation is executed using the ATS XML scripts and the included Python script (generate_data_set.py) to convert ATS output to COMSOL-ready input. COMSOL Multiphysics template (.mph can be opened with the commercial software COMSOL and requires a license) is executed using the ATS output data to simulate the potential field. It also includes the Synthetic_model_plot.ipynb (can be opened using any code editor) to visualize the SP result and generate manuscript figures. The data subfolder contains mesh files to run both the ATS (.exo and .stl files can be viewed using Paraview; .h5 files can be opened using HDFView software and h5py Python package) and COMSOL models. Field_Application subfolder contains two subfolders: ES_MDA_inversion and Final_Model. ES_MDA_inversion contains the Python script (.py can be opened using any code editor) and SP observation data used to run the Ensemble Smoother with Multiple Data Assimilation (ES-MDA) inversion sequence to get the optimal model parameters. The Final_model subfolder contains the ATS XML input scripts, data files, output data for the two SP sites. The same workflow steps outlined for the Synthetic subfolder apply here. It also contains the Jupyter notebook (Plot_final_calib.ipynb) to visualize the results of the modeled SP, stream-groundwater exchange and moisture content. 3) Discharge Includes the electrical conductivity (EC) time series (provided as CSV files) from salt slug injections. It also includes the Jupyter notebook (Discharge_process.ipynyb) used to estimate discharge. All discharge measurements collated into rating_curve_processed.csv 4) EM Contains the CSV file of the EM data from the DUALEM-42, including spatial coordinates (x, y, z), apparent conductivity, and in-phase measurements at 2 m coil separations for horizontal coplanar (HCP) and perpendicular (PRP) geometries. 5) ERT Contains raw resistivity data (provided as CSV files), spatial location of each of the electrodes (provided as CSV files), and files used for the resistivity inversion (.resipy can be opened with the open-source ResIPy software). 6) GPR Includes GPR field datasets collected at 100 MHz and 250 MHz antenna frequencies, along with the processing/interpretation project file (GPR_process.gpz can be viewed using EKKO_Project 6, a commercial software by Sensors & Software that requires a license). 7) Slug_test Includes the slug test data at all the groundwater wells provided as CSV files, as well as the Jupyter notebook (Slug_test.ipynb) for calculating hydraulic conductivity. 8) SP Contains the SP data collected in field at the two SP sites (one in the perennial reach and the other in the intermittent reach), provided as DAT files. 9) Well_data Contains two subfolders: 1) Raw, which provides unprocessed pressure, electrical conductivity and temperature timeseries downloaded from the loggers in all the groundwater and stilling wells, and 2) Processed, which contains sorted, QA/QC timeseries data for each well. The data archive also contains data_process.ipynb, a Jupyter notebook used for field data analysis and generating figures (plotting well, SP, climate, and discharge data, as well as calculating head gradient at sites with nested groundwater wells). It also includes DTW.ipynb, a Jupyter notebook containing the code for the dynamic time warping (DTW) with sliding window to evaluate SP signal synchronicity.

ATS

automesh: Automatic mesh generation in Rust

automesh is an open-source Rust software program that uses a segmentation, typically generated from a 3D image stack, to create a finite element mesh, composed either of hexahedral (volumetric) or triangular (isosurface) elements. automesh converts between segmentation formats (.npy, .spn) and mesh formats (.exo, .inp, .mesh, .stl, .vtk). automesh can defeature voxel domains, apply Laplacian and Taubin smoothing, and output mesh quality metrics. automesh uses an internal octree for fast performance.

Hovey, Chad Brian [Sandia National Laboratories (S

Speed Optimizations for Physics Ray Trace Algorithms

Ray tracing is a process used commonly in computer graphics and in physics to track light photons and particles, respectively. Much research was found on improving execution times for the computer graphics applications; however, in the short time frame of this literary review, almost no research was found on improving the execution times for the physics applications that were relevant to this problem. Two ray trace algorithms, a STL raytrace and a conebeam raytrace, were optimized using OpenMP and CUDA.

97 MATHEMATICS AND COMPUTING

SOME TYPICAL SHELL STABILITY PROBLEMS ENCOUNTERED IN THE DESIGN OF BALLISTIC MISSILES

Investigations carried out at STL on three current problems involving instability of thin shells in applications to aerospace vehicles are discussed. The first concerns the experimental determination of the buckling behavior of longitudinally stiffened pressurized cylinders; the second, the analytic prediction and experimental confirmation of the buckling behavior of multi-layer cylinders and the third involves the behavior of cylinders under combined axial load and lateral pressure. In each case the background of the application is reviewed, followed by a short description of the work. It is indicated that the longitudinally stiffened cylinder shows considerable promise in taking maximum advantage of the strengthening effect of internal pressure, that the use of an external low modulus layer as an insulator can have a significant effect on the buckling capability of a shell, and that the assumption of a linear interaction for pressure and axial load is unnecessarily conservative.

SHELL STABILITY

Comet Intercept Study

STL (Space Technology Laboratories, Inc.) has been studying, during the past year, the problems of carrying out a comet intercept mission. During the course of this study, the properties of 31 short-term comets have been examined to determine the feasibility of a mission to any of them during the next 15 years. In the process of selecting these comets, injection energies for each of these comets at a suitable launch period were determined. In addition, the distance of the earth at intercept, the transit and flight times, and the guidance requirements were evaluated. Also, to determine the effectiveness of such a mission, possible scientific instruments which could be used to measure the various characteristics of the comets have been studied. Finally, to determine the present feasibility of such a mission, the payload capability of available boosters was examined, and a spacecraft configuration with appropriate subsystems was also studied.

INTERCEPTION

Subtabulated Lunar and Planetary Ephemerides

In a joint JPL-STL effort the planetary ephemerides have been collected on IBM 704-709 magnetic tape, and a series of routines have been written to utilize these tapes. This paper describes the contents and preparation of the ephemeris tapes.

Hudson, R. H.

Analysis of effect of internal and operating variables on performance of SVDS constraint model (ABIND)

An examination of the factors which modify the simulation of a constraint in the motion of the aft attach points of the orbiter and external tank during separation has been made. The factors considered were both internal (spring and damper constants) and external (friction coefficient and dynamic pressure). The results show that an acceptable choice of spring/damper constant combinations exist over the expected range of the external factors and that the choice is consistent with a practical integration interval. The constraint model is shown to produce about a 10 percent increase in the relative body pitch angles over the unconstrained case whereas the MDC-STL constraint model is shown to produce about a 38 percent increase.

Pendergrass, J. R.

STS-45 Space Shuttle mission report

The STS-45 Space Shuttle Program Mission Report contains a summary of the vehicle subsystem operations during the forty-sixth flight of the Space Shuttle Program and the eleventh flight of the Orbiter Vehicle Atlantis (OV-104). In addition to the Atlantis vehicle, the flight vehicle consisted of the following: an External Tank (ET) designated as ET-44 (LWT-37); three Space Shuttle main engines (SSME's), which were serial numbers 2024, 2012, and 2028 in positions 1, 2, and 3, respectively; and two Solid Rocket Boosters (SRB's) designated as BI-049. The lightweight redesigned Solid Rocket Motors (RSRM's) installed in each of the SRB's were designated as 360L021A for the left SRM and 360W021B for the right SRM. The primary objective of this mission was to successfully perform the planned operations of the Atmospheric Laboratory for Applications and Science-1 (ATLAS-1) and the Shuttle Solar Backscatter Ultraviolet Instrument (SSBUV) payloads. The secondary objectives were to successfully perform all operations necessary to support the requirements of the following: the Space Tissue Loss-01 (STL-01) experiment; the Radiation Monitoring Equipment-3 (RME-3) experiment; the Visual Function Tester-2 (VFT-2) experiment; the Cloud Logic to Optimize use of Defense System (CLOUDS-1A) experiment; the Shuttle Amateur Radio Experiment 2 (SAREX-2) Configuration B; the Investigation into Polymer Membranes Processing experiment; and the Get-Away Special (GAS) payload G-229. The Ultraviolet Plume Instrument (UVPI) was a payload of opportunity that required no special maneuvers. In addition to the primary and secondary objectives, the crew was tasked to perform as many as 10 Development Test Objectives (DTO'S) and 14 Detailed Supplementary Objectives (DSO's).

Fricke, Robert W.

STS-53 Space Shuttle mission report

The STS-53 Space Shuttle Program Mission Report provides a summary of the Orbiter, External Tank (ET), Solid Rocket Booster/Redesigned Solid Rocket Motor (SRB/RSRM), and the Space Shuttle Main Engine (SSME) subsystems performance during the fifty-second flight of the Space Shuttle Program, and the fifteenth flight of the Orbiter vehicle Discovery (OV-103). In addition to the Orbiter, the flight vehicle consisted of an ET, which was designated as ET-49/LWT-42; three SSME's, which were serial numbers 2024, 2012, and 2017 in positions 1, 2, and 3, respectively; and two SRB's, which were designated BI-055. The lightweight RSRM's that were installed in each SRB were designated 360L028A for the left SRB, and 360L028B for the right SRB. The primary objective of this flight was to successfully deploy the Department of Defense 1 (DOD-1) payload. The secondary objectives of this flight were to perform the operations required by the Glow Experiment/Cryogenic Heat Pipe Experiment Payload (GCP); the Hand-Held, Earth-Oriented, Real-Time, Cooperative, User-Friendly, Location-Targeting and Environmental System (HERCULES); the Space Tissue Loss (STL); the Battlefield Laser Acquisition Sensor Test (BLAST); the Radiation Monitoring Equipment-III (RME-III); the Microcapsules in Space-1 (MIS-1); the Visual Function Tester-2 (VFT-2); the Cosmic Radiation Effects and Activation Monitor (CREAM); the Clouds Logic to Optimize Use of Defense Systems-1A (CLOUDS-1A); the Fluids Acquisition and Resupply Experiment (FARE); and the Orbital Debris Radar Calibration Spheres (ODERACS). In addition to presenting a summary of subsystem performance, this report also discusses each Orbiter, ET, SSME, SRB, and RSRM in-flight anomaly in the applicable section of the report. Listed in the discussion of each anomaly is the officially assigned tracking number as published by each Project Office in their respective Problem Tracking List. All times given in this report are in Greenwich mean time (G.m.t.) as well as mission elapsed time (MET).

Fricke, Robert W., Jr.

A convertor and user interface to import CAD files into worldtoolkit virtual reality systems

Virtual Reality (VR) is a rapidly developing human-to-computer interface technology. VR can be considered as a three-dimensional computer-generated Virtual World (VW) which can sense particular aspects of a user's behavior, allow the user to manipulate the objects interactively, and render the VW at real-time accordingly. The user is totally immersed in the virtual world and feel the sense of transforming into that VW. NASA/MSFC Computer Application Virtual Environments (CAVE) has been developing the space-related VR applications since 1990. The VR systems in CAVE lab are based on VPL RB2 system which consists of a VPL RB2 control tower, an LX eyephone, an Isotrak polhemus sensor, two Fastrak polhemus sensors, a folk of Bird sensor, and two VPL DG2 DataGloves. A dynamics animator called Body Electric from VPL is used as the control system to interface with all the input/output devices and to provide the network communications as well as VR programming environment. The RB2 Swivel 3D is used as the modelling program to construct the VW's. A severe limitation of the VPL VR system is the use of RB2 Swivel 3D, which restricts the files to a maximum of 1020 objects and doesn't have the advanced graphics texture mapping. The other limitation is that the VPL VR system is a turn-key system which does not provide the flexibility for user to add new sensors and C language interface. Recently, NASA/MSFC CAVE lab provides VR systems built on Sense8 WorldToolKit (WTK) which is a C library for creating VR development environments. WTK provides device drivers for most of the sensors and eyephones available on the VR market. WTK accepts several CAD file formats, such as Sense8 Neutral File Format, AutoCAD DXF and 3D Studio file format, Wave Front OBJ file format, VideoScape GEO file format, Intergraph EMS stereolithographics and CATIA Stereolithographics STL file formats. WTK functions are object-oriented in their naming convention, are grouped into classes, and provide easy C language interface. Using a CAD or modelling program to build a VW for WTK VR applications, we typically construct the stationary universe with all the geometric objects except the dynamic objects, and create each dynamic object in an individual file.

Wang, Peter Hor-Ching