Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “interface capturing”

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 415 records · Page 23

Flow Analysis Tool White Paper

Faster networks are continually being built to accommodate larger data transfers. While it is intuitive to think that implementing faster networks will result in higher throughput rates, this is often not the case. There are many elements involved in data transfer, many of which are beyond the scope of the network itself. Although networks may get bigger and support faster technologies, the presence of other legacy components, such as older application software or kernel parameters, can often cause bottlenecks. Engineers must be able to identify when data flows are reaching a bottleneck that is not imposed by the network and then troubleshoot it using the tools available to them. The current best practice is to collect as much information as possible on the network traffic flows so that analysis is quick and easy. Unfortunately, no single method of collecting this information can sufficiently capture the whole endto- end picture. This becomes even more of a hurdle when large, multi-user systems are involved. In order to capture all the necessary information, multiple data sources are required. This paper presents a method for developing a flow analysis tool to effectively collect network flow data from multiple sources and provide that information to engineers in a clear, concise way for analysis. The purpose of this method is to collect enough information to quickly (and automatically) identify poorly performing flows along with the cause of the problem. The method involves the development of a set of database tables that can be populated with flow data from multiple sources, along with an easyto- use, web-based front-end interface to help network engineers access, organize, analyze, and manage all the information.

Boscia, Nichole K.↗

Hypersonic Inflatable Aerodynamic Decelerator (HIAD) Technology Development Overview

The successful flight of the Inflatable Reentry Vehicle Experiment (IRVE)-3 has further demonstrated the potential value of Hypersonic Inflatable Aerodynamic Decelerator (HIAD) technology. This technology development effort is funded by NASA's Space Technology Mission Directorate (STMD) Game Changing Development Program (GCDP). This paper provides an overview of a multi-year HIAD technology development effort, detailing the projects completed to date and the additional testing planned for the future. The effort was divided into three areas: Flexible Systems Development (FSD), Mission Advanced Entry Concepts (AEC), and Flight Validation. FSD consists of a Flexible Thermal Protection Systems (FTPS) element, which is investigating high temperature materials, coatings, and additives for use in the bladder, insulator, and heat shield layers; and an Inflatable Structures (IS) element which includes manufacture and testing (laboratory and wind tunnel) of inflatable structures and their associated structural elements. AEC consists of the Mission Applications element developing concepts (including payload interfaces) for missions at multiple destinations for the purpose of demonstrating the benefits and need for the HIAD technology as well as the Next Generation Subsystems element. Ground test development has been pursued in parallel with the Flight Validation IRVE-3 flight test. A larger scale (6m diameter) HIAD inflatable structure was constructed and aerodynamically tested in the National Full-scale Aerodynamics Complex (NFAC) 40ft by 80ft test section along with a duplicate of the IRVE-3 3m article. Both the 6m and 3m articles were tested with instrumented aerodynamic covers which incorporated an array of pressure taps to capture surface pressure distribution to validate Computational Fluid Dynamics (CFD) model predictions of surface pressure distribution. The 3m article also had a duplicate IRVE-3 Thermal Protection System (TPS) to test in addition to testing with the Aerocover configuration. Both the Aerocovers and the TPS were populated with high contrast targets so that photogrammetric solutions of the loaded surface could be created. These solutions both refined the aerodynamic shape for CFD modeling and provided a deformed shape to validate structural Finite Element Analysis (FEA) models. Extensive aerothermal testing has been performed on the TPS candidates. This testing has been conducted in several facilities across the country. The majority of the testing has been conducted in the Boeing Large Core Arc Tunnel (LCAT). HIAD is continuing to mature testing methodology in this facility and is developing new test sample fixtures and control methodologies to improve understanding and quality of the environments to which the samples are subjected. Additional testing has been and continues to be performed in the NASA LaRC 8ft High Temperature Tunnel, where samples up to 2ft by 2ft are being tested over representative underlying structures incorporating construction features such as sewn seams and through-thickness quilting. With the successful completion to the IRVE-3 flight demonstration, mission planning efforts are ramping up on the development of the HIAD Earth Atmospheric Reenty Test (HEART) which will demonstrate a relevant scale vehicle in relevant environments via a large-scale aeroshell (approximately 8.5m) entering at orbital velocity (approximately 7km/sec) with an entry mass on the order of 4MT. Also, the Build to Print (BTP) hardware built as a risk mitigation for the IRVE-3 project to have a "spare" ready to go in the event of a launch vehicle delivery failure is now available for an additional sub-orbital flight experiment. Mission planning is underway to define a mission that can utilize this existing hardware and help the HIAD project further mature this technology.

Hughes, Stephen J.↗

The Polstar High Resolution Spectropolarimetry MIDEX Mission

The Polstar mission will provide a space-borne 60 cm spectropolarimeter operating at ultraviolet (UV) wavelengths, capturing all four Stokes parameters (intensity, two linear polarization components, and circular polarization). Polstar’s capabilities are designed to meet its goal of determining how circumstellar gas flows alter and inform massive star evolution, affect the stellar remnant population, and stir and enrich the interstellar medium (ISM). These will be achieved by investigating the dynamical geometries in the winds and disks of hot stars, the composition and magnetic alignment of interstellar dust, and the star-forming accretion disks of UV-bright stars at an important transition boundary. Together these areas map out a kind of two-way interface between massive stars and their effect on our galaxy, wherein the stellar winds enrich the ISM with metals and kinetic energy, preconditioning their environment and the stellar endpoints prior to undergoing supernova. The ISM dust in turn reveals the composition and magnetic environment leading to new star formation, and the accretion disks of Herbig Ae/Be stars reveal how the ISM gas returns to make new massive stars. Polstar will combine high-resolution spectroscopy in the time domain with high-precision UV polarimetry. Doppler-shifted UV resonance line opacity will provide information about circumstellar kinematics, while polarization gives complementary geometric information about unseen structures. The composition and magnetic alignment of the smallest interstellar dust grains provides a probe of the ISM utilizing radiative alignment theory (RAT). Polstar will operate in the far-UV (FUV) at 122–200 nm at high spectral resolution of around R ∼ 30k, and at FUV and near-UV (NUV) wavelengths of 122–320 nm at lower spectral resolutions of 0.1 - 1k. Detection of polarization levels as weak as 0.1% are expected, with a temporal cadence ranging from 5–10 minutes for most wind variability studies, to hours or days for sampling rotation, to days or weeks for sampling binary orbits, to months to a year for sampling substructure in the inner regions of protoplanetary disks. Sub-meter-class aperture is well suited to access this wide array of time domain science, made possible by restricting to a few hundred bright, massive stars, necessarily extincted by a small to moderate column of interstellar dust, informing both the attributes of the stars and the ISM through which they are seen. As such, the focus is on our own galaxy and its evolutionary drivers, but a few targets in the Magellanic clouds offer the potential to extend this understanding to low-metallicity environments.

Paul A Scowen↗

Integration of the Remote Agent for the NASA Deep Space One Autonomy Experiment

This paper describes the integration of the Remote Agent (RA), a spacecraft autonomy system which is scheduled to control the Deep Space 1 spacecraft during a flight experiment in 1999. The RA is a reusable, model-based autonomy system that is quite different from software typically used to control an aerospace system. We describe the integration challenges we faced, how we addressed them, and the lessons learned. We focus on those aspects of integrating the RA that were either easier or more difficult than integrating a more traditional large software application because the RA is a model-based autonomous system. A number of characteristics of the RA made integration process easier. One example is the model-based nature of RA. Since the RA is model-based, most of its behavior is not hard coded into procedural program code. Instead, engineers specify high level models of the spacecraft's components from which the Remote Agent automatically derives correct system-wide behavior on the fly. This high level, modular, and declarative software description allowed some interfaces between RA components and between RA and the flight software to be automatically generated and tested for completeness against the Remote Agent's models. In addition, the Remote Agent's model-based diagnosis system automatically diagnoses when the RA models are not consistent with the behavior of the spacecraft. In flight, this feature is used to diagnose failures in the spacecraft hardware. During integration, it proved valuable in finding problems in the spacecraft simulator or flight software. In addition, when modifications are made to the spacecraft hardware or flight software, the RA models are easily changed because they only capture a description of the spacecraft. one does not have to maintain procedural code that implements the correct behavior for every expected situation. On the other hand, several features of the RA made it more difficult to integrate than typical flight software. For example, the definition of correct behavior is more difficult to specify for a system that is expected to reason about and flexibly react to its environment than for a traditional flight software system. Consequently, whenever a change is made to the RA it is more time consuming to determine if the resulting behavior is correct. We conclude the paper with a discussion of future work on the Remote Agent as well as recommendations to ease integration of similar autonomy projects.

Dorais, Gregory A.↗

A Upgrade of the Aeroheating Software "MINIVER"

Many software packages assist engineers with performing flight vehicle analysis, but some of these packages have gone many years without updates or significant improvements to their workflows. One such software package, known as MINIVER, is a powerful yet lightweight tool used for aeroheating analyses. However, it is an aging program that has not seen major improvements within the past decade. As part of a collaborative effort with the Florida Institute of Technology, MINIVER has received a major user interface overhaul, a change in program language, and will be continually receiving updates to improve its capabilities. The user interface update includes a migration from a command-line interface to that of a graphical user interface supported in the Windows operating system. The organizational structure of the pre-processor has been transformed to clearly defined categories to provide ease of data entry. Helpful tools have been incorporated, including the ability to copy sections of cases as well as a generalized importer which aids in bulk data entry. A visual trajectory editor has been included, as well as a CAD Editor which allows the user to input simplified geometries in order to generate MINIVER cases in bulk. To demonstrate its continued effectiveness, a case involving the JAXA OREX flight vehicle will be included, providing comparisons to captured flight data as well as other computational solutions. The most recent upgrade effort incorporated the use of the CAD Editor, and current efforts are investigating methods to link MINIVER projects with SINDA/Fluint and Thermal Desktop.

Louderback, Pierce↗

The Use of UML for Software Requirements Expression and Management

It is common practice to write English-language "shall" statements to embody detailed software requirements in aerospace software applications. This paper explores the use of the UML language as a replacement for the English language for this purpose. Among the advantages offered by the Unified Modeling Language (UML) is a high degree of clarity and precision in the expression of domain concepts as well as architecture and design. Can this quality of UML be exploited for the definition of software requirements? While expressing logical behavior, interface characteristics, timeliness constraints, and other constraints on software using UML is commonly done and relatively straight-forward, achieving the additional aspects of the expression and management of software requirements that stakeholders expect, especially traceability, is far less so. These other characteristics, concerned with auditing and quality control, include the ability to trace a requirement to a parent requirement (which may well be an English "shall" statement), to trace a requirement to verification activities or scenarios which verify that requirement, and to trace a requirement to elements of the software design which implement that requirement. UML Use Cases, designed for capturing requirements, have not always been satisfactory. Some applications of them simply use the Use Case model element as a repository for English requirement statements. Other applications of Use Cases, in which Use Cases are incorporated into behavioral diagrams that successfully communicate the behaviors and constraints required of the software, do indeed take advantage of UML's clarity, but not in ways that support the traceability features mentioned above. Our approach uses the Stereotype construct of UML to precisely identify elements of UML constructs, especially behaviors such as State Machines and Activities, as requirements, and also to achieve the necessary mapping capabilities. We describe this approach in the context of a space-based software application currently under development at the Jet Propulsion Laboratory.

model-based engineering↗

Knowledge Engineering for Preservation and Future use of Institutional Knowledge

This Project has two main thrusts-preservation of special knowledge and its useful representation via computers. NASA is losing the expertise of its engineers and scientists who put together the great missions of the past. We no longer are landing men on the moon. Some of the equipment still used today (such as the RL-10 rocket) was designed decades ago by people who are now retiring. Furthermore, there has been a lack, in some areas of technology, of new projects that overlap with the old and that would have provided opportunities for monitoring by senior engineers of the young ones. We are studying this problem and trying out a couple of methods of soliciting and recording rare knowledge from experts. One method is that of Concept Maps which produces a graphical interface to knowledge even as it helps solicit that knowledge. We arranged for experienced help in this method from John Coffey of the Institute of Human and Machine Technology at the University of West Florida. A second method which we plan to try out in May, is a video-taped review of selected failed missions (e.g., the craft tumbled and blew up). Five senior engineers (most already retired from NASA) will, as a team, analyze available data, illustrating their thought processes as they try to solve the problem of why a space craft failed to complete its mission. The session will be captured in high quality audio and with at least two video cameras. The video can later be used to plan future concept mapping interviews and, in edited form, be a product in itself. Our computer representations of the amassed knowledge may eventually, via the methods of expert systems, be joined with other software being prepared as a suite of tools to aid future engineers designing rocket engines. In addition to representation by multimedia concept maps, we plan to consider linking vast bodies of text (and other media) by hypertexting methods.

Moreman, Douglas↗

The D3 Middleware Architecture

DARWIN is a NASA developed, Internet-based system for enabling aerospace researchers to securely and remotely access and collaborate on the analysis of aerospace vehicle design data, primarily the results of wind-tunnel testing and numeric (e.g., computational fluid-dynamics) model executions. DARWIN captures, stores and indexes data; manages derived knowledge (such as visualizations across multiple datasets); and provides an environment for designers to collaborate in the analysis of test results. DARWIN is an interesting application because it supports high-volumes of data. integrates multiple modalities of data display (e.g., images and data visualizations), and provides non-trivial access control mechanisms. DARWIN enables collaboration by allowing not only sharing visualizations of data, but also commentary about and views of data. Here we provide an overview of the architecture of D3, the third generation of DARWIN. Earlier versions of DARWIN were characterized by browser-based interfaces and a hodge-podge of server technologies: CGI scripts, applets, PERL, and so forth. But browsers proved difficult to control, and a proliferation of computational mechanisms proved inefficient and difficult to maintain. D3 substitutes a pure-Java approach for that medley: A Java client communicates (though RMI over HTTPS) with a Java-based application server. Code on the server accesses information from JDBC databases, distributed LDAP security services, and a collaborative information system. D3 is a three tier-architecture, but unlike 'E-commerce' applications, the data usage pattern suggests different strategies than traditional Enterprise Java Beans - we need to move volumes of related data together, considerable processing happens on the client, and the 'business logic' on the server-side is primarily data integration and collaboration. With D3, we are extending DARWIN to handle other data domains and to be a distributed system, where a single login allows a user transparent access to test results from multiple servers and authority domains.

Walton, Joan↗

Solar Dynamics Observatory Guidance, Navigation, and Control System Overview

The Solar Dynamics Observatory (SDO) was designed and built at the Goddard Space Flight Center, launched from Cape Canaveral on February 11, 2010, and reached its final geosynchronous science orbit on March 16, 2010. The purpose of SDO is to observe the Sun and continuously relay data to a dedicated ground station. SDO remains Sun-pointing throughout most of its mission for the instruments to take measurements of the Sun. The SDO attitude control system (ACS) is a single-fault tolerant design. Its fully redundant attitude sensor complement includes sixteen coarse Sun sensors (CSSs), a digital Sun sensor (DSS), three two-axis inertial reference units (IRUs), and two star trackers (STs). The ACS also makes use of the four guide telescopes included as a part of one of the science instruments. Attitude actuation is performed using four reaction wheels assemblies (RWAs) and eight thrusters, with a single main engine used to provide velocity-change thrust for orbit raising. The attitude control software has five nominal control modes, three wheel-based modes and two thruster-based modes. A wheel-based Safehold running in the attitude control electronics box improves the robustness of the system as a whole. All six modes are designed on the same basic proportional-integral-derivative attitude error structure, with more robust modes setting their integral gains to zero. This paper details the final overall design of the SDO guidance, navigation, and control (GN&C) system and how it was used in practice during SDO launch, commissioning, and nominal operations. This overview will include the ACS control modes, attitude determination and sensor calibration, the high gain antenna (HGA) calibration, and jitter mitigation operation. The Solar Dynamics Observatory mission is part of the NASA Living With a Star program, which seeks to understand the changing Sun and its effects on the Solar System, life, and society. To this end, the SDO spacecraft carries three Sun-observing instruments: Helioseismic and Magnetic Imager (HMI), led by Stanford University; Atmospheric Imaging Assembly (AIA), led by Lockheed Martin Space and Astrophysics Laboratory; and Extreme Ultraviolet Variability Experiment (EVE), led by the University of Colorado. The basic mission is to observe the Sun for a very high percentage of the 5-year mission (10-year goal) with long stretches of uninterrupted observations and with constant, high-data-rate transmission to a dedicated ground station to be located in White Sands, New Mexico. These goals guided the design of the spacecraft bus that will carry and service the three-instrument payload. Overarching design goals for the bus are geosynchronous orbit, near-constant Sun observations with the ability to fly through eclipses, and constant HGA contact with the dedicated ground station. A three-axis stabilized ACS is needed both to point at the Sun accurately and to keep the roll about the Sun vector correctly positioned with respect to the solar north pole. This roll control is especially important for the magnetic field imaging of HM I. The mission requirements have several general impacts on the ACS design. Both the AIA and HMI instruments are very sensitive to the blurring caused by jitter. Each has an image stabilization system (ISS) with some ability to filter out high frequency motion, but below the bandwidth of the ISS the control system must compensate for disturbances within the ACS bandwidth or avoid exciting jitter at higher frequencies. Within the ACS bandwidth, the control requirement imposed by AIA is to place the center of the solar disk no more than 2 arc sec, 3 , from a body-defined target based on one of the GTs that accompany the instrument. This body-defined target, called the science reference boresight (SRB), was determined from the postlaunch orientation of the GTs by averaging the bounding telescope boresights for pitch to get a pitch SRB coordinate, and by averaging the bounding boresights for yaw toet the yaw SRB coordinate. The location of this SRB in the 0.5-deg field-of-view for each GT then becomes the central target for each telescope; one GT is selected for use as the ACS controlling guide telescope (CGT) at any given time. Fine Sun-pointing is effected based on this SRB for all three instruments when the Sun is within the linear range of the CGT. In addition to limiting jitter, HMI science requires averaging several observations, making the instrument sensitive to low frequency motion that induces differential motion between each observation. This requires the spacecraft attitude to be stable about the roll axis to approximately 10 arcsec over a ten-minute period. Instrument calibrations require that the spacecraft point the SRB up to 2.5 degrees in pitch and yaw away from the center of the Sun, placing the Sun outside the field-of-view of the guide telescopes. In such instances, when the GTs cannot provide the definitive target for the ACS, on-board attitude determination combined with ephemeris prediction of the Sun direction must provide the definitive target. EVE is capable of observing the Sun with less dependence on attitude control. However, the ground data processing needs for calibrations result in the most strict attitude knowledge requirements for the mission: [35,70,70] arcsec, 3 , of knowledge with respect to the center of the solar disk. In addition to driving the ACS sensor selection, the knowledge requirements, which have their effect primarily during Inertial mode calibrations, drive the accuracy requirements for the solar ephemeris. The need to achieve and maintain geosynchronous orbit (GEO) drove the need for high-efficiency propulsive systems and appropriate attitude control. The main engine provided high specific impulse for the maneuvers to attain GEO, while the smaller ACS thrusters managed the disturbance torques of the larger engine and provided the capability for much smaller adjustment burns on orbit. SDO s large solar profile means that solar radiation pressure is a large torque disturbance, and the momentum buildup from this disturbance and the GEO altitude drives the ACS to use thrusters to manage vehicle momentum. The demanding data capture budget for the mission, however, requires SDO to avoid frequent thruster maneuvers, while concerns about on-orbit jitter restrict the maximum desired wheel speeds desired from the RWAs. The plan for on-orbit wheel speed and momentum management will be discussed as well as what is now being done in operation after the jitter environment was characterized. The SDO ACS hardware complement is single-fault tolerant. Two main processors carry virtually identical copies of the command and data handling and ACS software, and two identical attitude control electronics (ACE) boxes carry Coldfire processors with contingency ACS software and other hardware interface cards; the ACE structure allows reaction wheels to be commanded by the Sun-pointing Safehold independent of the Mil Std 1553 data bus. The sixteen Adcole CSSs are grouped into primary and backup sets of eight sensors, each set providing the ability to calculate a sun vector. Each set of eight eyes provides full 4 -steradian coverage. The Adcole DSS comprises an optics head and a separate electronics box providing a 1553 data interface. The electronics box is mounted inside the Faraday cage created by the spacecraft bus module. The DSS head with its 32- deg square FOV is mounted on the instrument module with its boresight along the spacecraft X axis, nearly aligned with the Sun during observations. Adcole has designed the DSS calibration parameters so that the accuracy is 0.24 arcminutes within 10 deg of the boresight, and diminishes to 3 arcminutes as the Sun moves towards the edges of its FOV . This DSS calibration scheme provides higher accuracy attitude determination over the range of the instrument calibration maneuvers.

Morgenstern, Wendy M.↗

Generating Customized Verifiers for Automatically Generated Code

Program verification using Hoare-style techniques requires many logical annotations. We have previously developed a generic annotation inference algorithm that weaves in all annotations required to certify safety properties for automatically generated code. It uses patterns to capture generator- and property-specific code idioms and property-specific meta-program fragments to construct the annotations. The algorithm is customized by specifying the code patterns and integrating them with the meta-program fragments for annotation construction. However, this is difficult since it involves tedious and error-prone low-level term manipulations. Here, we describe an annotation schema compiler that largely automates this customization task using generative techniques. It takes a collection of high-level declarative annotation schemas tailored towards a specific code generator and safety property, and generates all customized analysis functions and glue code required for interfacing with the generic algorithm core, thus effectively creating a customized annotation inference algorithm. The compiler raises the level of abstraction and simplifies schema development and maintenance. It also takes care of some more routine aspects of formulating patterns and schemas, in particular handling of irrelevant program fragments and irrelevant variance in the program structure, which reduces the size, complexity, and number of different patterns and annotation schemas that are required. The improvements described here make it easier and faster to customize the system to a new safety property or a new generator, and we demonstrate this by customizing it to certify frame safety of space flight navigation code that was automatically generated from Simulink models by MathWorks' Real-Time Workshop.

Denney, Ewen↗

Validation of a CFD Model Predicting the Effect of High Level Lateral Acceleration Sloshing on the Heat Transfer and Pressure Drop in a Small-Scale Tank in Normal Gravity

A two-phase CFD model is developed to study the effects of sloshing with high level lateral acceleration on the heat transfer and pressure drop in a small scale tank. Computational results are compared to the data provided by a non-isothermal sloshing experiment without phase change conducted by T. Himeno et al. at the University of Tokyo and JAXA in 2011. The results of the current model are, also, compared to CFD predictions reported by Himeno et al. A step change in lateral acceleration was applied in the experiment. Different levels of lateral acceleration amplitude, varying between 0G and 0.5G, were considered. CFD results for interface movement and tank pressure are presented and compared in this paper to the experimental data for the case in which the value of lateral acceleration was set to 0.5G. The effects of initial and boundary conditions and turbulence modeling approach on the tank pressure change during sloshing are discussed in detail. The effect of conjugate heat transfer in the tank wall is also studied to show its important role in determining the tank pressure evolution. The results of the Reynolds Averaged Navier Stokes (RANS) models are compared to the results of the Large Eddy Simulation model (LES) to underscore the importance of correctly capturing the effects of turbulence for high fidelity predictions.

multiphase flow↗

Validation of A CFD Model Predicting the Effect of High Level Lateral Acceleration Sloshing on the Heat Transfer and Pressure Drop in A Small-Scale Tank in Normal Gravity

A two-phase CFD model is developed to study the effects of sloshing with high level lateral acceleration on the heat transfer and pressure drop in a small scale tank. Computational results are compared to the data provided by a non-isothermal sloshing experiment without phase change conducted by T. Himeno et al. at the University of Tokyo and JAXA in 2011 [1]. The results of the current model are, also, compared to CFD predictions reported by Himeno et al. [2]. A step change in lateral acceleration was applied in the experiment. Different levels of lateral acceleration amplitude, varying between 0G and 0.5G, were considered. CFD results for interface movement and tank pressure are presented and compared in this paper to the experimental data for the case in which the value of lateral acceleration was set to 0.5G. The effects of initial and boundary conditions and turbulence modeling approach on the tank pressure change during sloshing are discussed in detail. The effect of conjugate heat transfer in the tank wall is also studied to show its important role in determining the tank pressure evolution. The results of the Reynolds Averaged Navier Stokes (RANS) models are compared to the results of the Large Eddy Simulation model (LES) to underscore the importance of correctly capturing the effects of turbulence for high fidelity predictions.

multiphase flow↗

HALE UAS Concept of Operations. Version 3.0

This document is a system level Concept of Operations (CONOPS) from the perspective of future High Altitude Long Endurance (HALE) Unmanned Aircraft Systems (UAS) service providers and National Airspace System (NAS) users. It describes current systems (existing UAS), describes HALE UAS functions and operations to be performed (via sample missions), and offers insight into the user s environment (i.e., the UAS as a system of systems). It is intended to be a source document for NAS UAS operational requirements, and provides a construct for government agencies to use in guiding their regulatory decisions, architecture requirements, and investment strategies. Although it does not describe the technical capabilities of a specific HALE UAS system (which do, and will vary widely), it is intended to aid in requirements capture and to be used as input to the functional requirements and analysis process. The document provides a basis for development of functional requirements and operational guidelines to achieve unrestricted access into the NAS. This document is an FY06 update to the FY05 Access 5 Project-approved Concept of Operations document previously published in the Public Domain on the Access 5 open website. This version is recommended to be approved for public release also. The updates are a reorganization of materials from the previous version with the addition of an updated set of operational requirements, inclusion of sample mission scenarios, and identification of roles and responsibilities of interfaces within flight phases.

Source record↗

Distributed Capacitive Sensor for Sample Mass Measurement

Previous robotic sample return missions lacked in situ sample verification/ quantity measurement instruments. Therefore, the outcome of the mission remained unclear until spacecraft return. In situ sample verification systems such as this Distributed Capacitive (DisC) sensor would enable an unmanned spacecraft system to re-attempt the sample acquisition procedures until the capture of desired sample quantity is positively confirmed, thereby maximizing the prospect for scientific reward. The DisC device contains a 10-cm-diameter pressure-sensitive elastic membrane placed at the bottom of a sample canister. The membrane deforms under the weight of accumulating planetary sample. The membrane is positioned in close proximity to an opposing rigid substrate with a narrow gap. The deformation of the membrane makes the gap narrower, resulting in increased capacitance between the two parallel plates (elastic membrane and rigid substrate). C-V conversion circuits on a nearby PCB (printed circuit board) provide capacitance readout via LVDS (low-voltage differential signaling) interface. The capacitance method was chosen over other potential approaches such as the piezoelectric method because of its inherent temperature stability advantage. A reference capacitor and temperature sensor are embedded in the system to compensate for temperature effects. The pressure-sensitive membranes are aluminum 6061, stainless steel (SUS) 403, and metal-coated polyimide plates. The thicknesses of these membranes range from 250 to 500 m. The rigid substrate is made with a 1- to 2-mm-thick wafer of one of the following materials depending on the application requirements glass, silicon, polyimide, PCB substrate. The glass substrate is fabricated by a microelectromechanical systems (MEMS) fabrication approach. Several concentric electrode patterns are printed on the substrate. The initial gap between the two plates, 100 m, is defined by a silicon spacer ring that is anodically bonded to the glass substrate. The fabricated proof-of-concept devices have successfully demonstrated tens to hundreds of picofarads of capacitance change when a simulated sample (100 g to 500 g) is placed on the membrane.

Toda, Risaku↗

Six degree of freedom FORTRAN program, ASTP docking dynamics, users guide

The digital program ASTP Docking Dynamics as outlined is intended to aid the engineer using the program to determine the docking system loads and attendant vehicular motion resulting from docking two vehicles that have an androgynous, six-hydraulic-attenuator, guide ring, docking interface similar to that designed for the Apollo/Soyuz Test Project (ASTP). This program is set up to analyze two different vehicle combinations: the Apollo CSM docking to Soyuz and the shuttle orbiter docking to another orbiter. The subroutine modifies the vehicle control systems to describe one or the other vehicle combinations; the rest of the vehicle characteristics are changed by input data. To date, the program has been used to predict and correlate ASTP docking loads and performance with docking test program results from dynamic testing. The program modified for use on IBM 360 computers. Parts of the original docking system equations in the areas of hydraulic damping and capture latches are modified to better describe the detail design of the ASTP docking system.

Mount, G. O., Jr.↗

Design of Flexures for Deployable Reflectarrays Using High Strain Composites

This paper presents a novel flexure design for small scale refelectarrays, specifically CubeSats, that requires high level of deployment precision. Advantages of using a HSC flexure includes additional thermal stability, lesser part count and passive deployment mechanism using the stored strain energy. The proposed design is to use two flat HSC strips of thickness ℎ, length 2𝐿ℎ, width 𝑊ℎ that attach to the core-reflector panel interface. The flexure satisfies two main requirements: ability to fold to a specific compaction 𝑑 without material failure and sufficient stiffness in the deployed configuration. The elastica analysis was implemented to identify the maximum strains in the flexure when folded and provide relations that combine Δ, ℎ, 𝐿ℎ with the maximum allowable strain. A simplified analysis was performed of the vibration of a panel-flexure combination using a two degree of freedom system. The vibration analysis reveals a dimensionless length parameter 𝛽 = (𝐿ℎ/𝐿𝑃) (Δ/ℎ) that determines the transition between bending and shear modes. A non-dimensional relationship was obtained between the natural frequency and 𝛽 that captures the impact of each parameter on the response of the structure. Our current work involves fabricating and testing of the proposed flexures using High Strain Composite materials, with plans to build a prototype for a deployable reflectarray.

López Jiménez, Francisco↗

Provenance Representation in the Global Change Information System (GCIS)

Global climate change is a topic that has become very controversial despite strong support within the scientific community. It is common for agencies releasing information about climate change to be served with Freedom of Information Act (FOIA) requests for everything that led to that conclusion. Capturing and presenting the provenance, linking to the research papers, data sets, models, analyses, observation instruments and satellites, etc. supporting key findings has the potential to mitigate skepticism in this domain. The U.S. Global Change Research Program (USGCRP) is now coordinating the production of a National Climate Assessment (NCA) that presents our best understanding of global change. We are now developing a Global Change Information System (GCIS) that will present the content of that report and its provenance, including the scientific support for the findings of the assessment. We are using an approach that will present this information both through a human accessible web site as well as a machine readable interface for automated mining of the provenance graph. We plan to use the developing W3C PROV Data Model and Ontology for this system.

Tilmes, Curt↗

Redistribution of subsurface neutrons caused by ground ice on Mars

The purpose of this study is to build on that of Squyres and Evans to approach the specific problem of the buried ice deposits explored by Mellon and Jakosky. Therefore, we calculated the depth dependence of equilibrium neutron energy spectra and related neutron-capture gamma ray production rates for a semi-infinite layer of regolith having a Chryse-fines composition containing 5, 10, and 18 wt percent of water. This high water-content layer was buried beneath the same regolith containing 1 percent water at depths of 20, 40, and 80 g/ sq. cm. A 16-g/sq. cm atmosphere having the abundances measured by Owen et al. was included throughout. We also calculated the effects of a 30-g/sq. cm-thick layer containing 18 percent water embedded within a semi-finite regolith containing 1 percent water, at depths of 20, 40, and 80 g/sq. cm below the atmosphere-surface interface.

Feldman, W. C.↗