Search NASA⌕ Search

SEARCH · Search NASA

Results for “spacecraft data interfaces”

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 829 records · Page 46

Proof of Concept Study of Trade Space Configuration Tool for Spacecraft Design

Spacecraft design is a very difficult and time consuming process because requirements and criteria are often changed or modified as the design is refined. Accounting for these adjustments in the design constraints plays a significant role in furthering the overall progress. There are numerous aspects and variables that hold significant influence on various characteristics of the design. This can be especially frustrating when attempting to conduct rapid trade space analysis on system configurations. Currently, the data and designs considered for trade space evaluations can only be displayed by using the traditional interfaces of Excel spreadsheets or CAD (Computer Aided Design) models. While helpful, these methods of analyzing the data from a systems engineering approach can be rather complicated and overwhelming. As a result, a proof of concept was conducted on a dynamic data visualization software called Thinkmap SDK (Software Developer Kit) to allow for better organization and understanding of the relationships between the various aspects that make up an entire design. The Orion Crew Module Aft Bay Subsystem was used as the test case for this study because the design and layout of many of the subsystem components will be significant in ensuring the overall center of gravity of the capsule is correct. A simplified model of this subsystem was created and programmed using Thinkmap SDK to create a preliminary prototype application of a Trade Space Configuration Tool. The completed application ensures that the core requirements for the Tool can be met. Further development is strongly suggested to produce a full prototype application to allow final evaluations and recommendations of the software capabilities.

Glidden, Geoffrey L.↗

NASA GeneLab: Open Science for Life in Space

The NASA GeneLab project capitalizes on multi-omic technologies to maximize the return on spaceflight experiments. To do this, GeneLab maintains a publicly accessible database (GLDS) that houses spaceflight and spaceflight relevant multi-omics data and collaborates with NASA principal investigators and projects to generate additional omics data. GeneLab houses more than 350 transcriptomic, proteomic, metabolomic and epigenomic datasets from plant, animal and microbial experiments, with a growing number of these having been produced by the GeneLab Sequencing Lab. The GLDS contains rich metadata about each experiment and has integrated radiation dosimetry data from experiments flown on the Space Shuttle, International Space Station, and Free Flying spacecrafts. With the increasing amount and complexity of omics data being generated, GeneLab utilizes community-defined, common models for metadata and terminology so that omics data and results are discoverable and reliably reproducible. GeneLab uses the ISA-Tab specification and semantic model for organizing and representing omics metadata. In addition to metadata standards, data files must be open-source file or common exchange formats to ensure accessibility and usability by all users. To ease data ingestion and transfer, the web-based submission tool allows PIs a user-friendly user interface to curate, organize, and publish their space relevant omics data. In the more recent years, data curation and submission portal has incorporated the FAIR principles making data findable, accessible, interoperable, and reusable. To increase reusability of data, GeneLab has implemented an effort to present processed data in the GLDS in addition to the raw omics data. The processed data will enable interpretation of the data by a larger group of students, scientists and the general public. Standard pipelines for the transformation of raw data into visualizations were developed by four GeneLab Analysis Working Groups (animals, plants, microbes, multi-omics) comprised of over 200 scientists from NASA, industry, and academia. To explore the data, the GLDS provides users various tools for data analysis, collaborative workspace for file storage and sharing, and a visualization portal. The analysis platform built using the Galaxy toolshed provides access to a broad variety of users including those with limited bioinformatics experience and students to learn how to analyze spaceflight omics data. The visualization portal takes GeneLab one step closer to data democratization by removing all bioinformatics requisites to interpret transcriptomics data hosted in the repository. To train the next generation of scientists, NASA offers training programs such as GeneLab 4 High School (GL4HS) and GeneLab 4 Universities. NLM Curation at a Scale Workshop 2022 | NASA GeneLab (GL4U) to teach students bioinformatics and computational biology methods to analyze omics data. Discoveries made using GeneLab have begun and will continue to deepen our understanding of biology, advance the field of genomics, and help to discover cures for diseases, create better diagnostic tools, and ultimately allow astronauts to better withstand the rigors of long-duration spaceflight.

GeneLab↗

MERCATOR: Methods and Realization for Control of the Attitude and the Orbit of spacecraft

Since 1974, CNES has been involved in geostationary positioning. Among different entities participating in operations and their preparation, the Flight Dynamics Center (FDC) is in charge of performing the following tasks: orbit determination; attitude determination; computation, monitoring, and calibration of orbit maneuvers; computation, monitoring, and calibration of attitude maneuvers; and operational predictions. In order to fulfill this mission, the FDC receives telemetry from the satellite and localization measurements from ground stations (e.g., CNES, NASA, INTELSAT). These data are processed by space dynamics programs integrated in the MERCATOR system which is run on SUN workstations (UNIX O.S.). The main features of MERCATOR are redundancy, modularity, and flexibility: efficient, flexible, and user friendly man-machine interface; and four identical SUN stations redundantly linked in an Ethernet network. Each workstation can perform all the tasks from data acquisition to computation results dissemination through a video network. A team of four engineers can handle the space mechanics aspects of a complete geostationary positioning from the injection into a transfer orbit to the final maneuvers in the station-keeping window. MERCATOR has been or is to be used for operations related to more than ten geostationary positionings. Initially developed for geostationary satellites, MERCATOR's methodology was also used for satellite control centers and can be applied to a wide range of satellites and to future manned missions.

Tavernier, Gilles↗

The Space Telescope SI C&DH system

The Hubble Space Telescope Scientific Instrument Control and Data Handling Subsystem (SI C&DH) is designed to interface with five scientific instruments of the Space Telescope to provide ground and autonomous control and collect health and status information using the Standard Telemetry and Command Components (STACC) multiplex data bus. It also formats high throughput science data into packets. The packetized data is interleaved and Reed-Solomon encoded for error correction and Pseudo Random encoded. An inner convolutional coding with the outer Reed-Solomon coding provides excellent error correction capability. The subsystem is designed with the capacity for orbital replacement in order to meet a mission life of fifteen years. The spacecraft computer and the SI C&DH computer coordinate the activities of the spacecraft and the scientific instruments to achieve the mission objectives.

Gadwal, Govind R.↗

PV-Diesel Hybrid SCADA Experiment Network Design

The essential features of an experimental network for renewable power system satellite based supervisory, control and data acquisition (SCADA) are communication links, controllers, diagnostic equipment and a hybrid power system. Required components for implementing the network consist of two satellite ground stations, to satellite modems, two 486 PCs, two telephone receivers, two telephone modems, two analog telephone lines, one digital telephone line, a hybrid-power system equipped with controller and a satellite spacecraft. In the technology verification experiment (TVE) conducted by Savannah State University and Florida Solar Energy Center, the renewable energy hybrid system is the Apex-1000 Mini-Hybrid which is equipped with NGC3188 for user interface and remote control and the NGC2010 for monitoring and basic control tasks. This power system is connected to a satellite modem via a smart interface, RS232. Commands are sent to the power system control unit through a control PC designed as PC1. PC1 is thus connected to a satellite model through RS232. A second PC, designated PC2, the diagnostic PC is connected to both satellite modems via separate analog telephone lines for checking modems'health. PC2 is also connected to PC1 via a telephone line. Due to the unavailability of a second ground station for the ACTS, one ground station is used to serve both the sending and receiving functions in this experiment. Signal is sent from the control PC to the Hybrid system at a frequency f(sub 1), different from f(sub 2), the signal from the hybrid system to the control PC. f(sub l) and f(sub 2) are sufficiently separated to avoid interference.

Kalu, Alex↗

High-Power Radar Sounders for the Investigation of Jupiter Icy Moons

The high power and high data rate capability made available by a Prometheus class spacecraft could significantly enhance our ability to probe the subsurface of the planets/moons and asteroid/comets. The main technology development driver for our radar is the proposed Jupiter Icy Moon Orbiter (or JIMO) mission due to its harsh radiation environment. We plan to develop a dual-band radar at 5 and 50 MHz in response to the two major science requirements identified by the JIMO Science Definition Team: studying the near subsurface (less than 2 km) at high resolution and detection of the ice/ocean interface for Europa (depth up to 30 km). The 50-MHz band is necessary to provide high spatial resolution (footprint and depth) as required by the JIMO mission science requirements as currently defined. Our preliminary assessment indicates that the 50-MHz system is not required to be as high-power as the 5-MHz system since it will be more limited by the surface clutter than the Jupiter or galactic background noise. The low frequency band (e.g. 5 MHz), which is the focus of this effort, would be necessary to mitigate the performance risks posed by the unknown subsurface structure both in terms of unknown attenuation due to volumetric scattering and also the detection of the interface through the attenuative transition region at the ice/ocean interface. Additionally, the 5-MHz band is less affected by the surface roughness that can cause loss of coherence and clutter noise. However, since the Signal-to-Noise-Ratio (SNR) of the 5-MHz radar band is reduced due to Jupiter noise when operating in the Jupiter side of the moon, it is necessary to increase the radiated power. Our challenge is to design a high-power HF radar that can hnction in Jupiter's high radiation environment, yet be able to fit into spacecraft resource constraints such as mass and thermal limits. Our effort to develop the JIMO radar sounder will rely on our team's experience with planetary radar sounder design gained during our participation in the MARSIS radar sounder implementation.

Safaeinili, A.↗

The design and fabrication of the Centaur neutral buoyancy trainer and related hardware

Two full scale mockups of the Centaur upper stage were designed, fabricated and delivered to NASA. One was the Centaur Weightless Environment Training Facility (WETF) trainer and the other was the Centaur 1-G mockup. The Centaur upper stage booster is designed to carry the spacecraft Galileo to Jupiter, and the spacecraft Ulysses to an orbit around the Sun after launch from the Space Shuttle. The flight vehicle has several Extravehicular Activity (EVA) contingency tasks that require crew training. This need for crew training generated the requirement for the Centaur WETF crew trainer, which is high fidelity in areas of expected crew interface. During the production of the Centaur WETF crew trainer, the need for a jumper cable from Centaur to the Orbiter was identified. This EVA contingency task would be the installation of a cable from the Orbiter cargo bay sill to various command data boxes on Centaur to allow crew control deployment should a failure occur. This task required the upgrading of volumetric boxes on the trainer to a high fidelity configuration including electrical connector installation and cable routing.

Ware, Alan S.↗

Ring Bus Architecture for a Solid-State Recorder

A document concisely describes a ring bus architecture for a proposed solid-state recorder (SSR) that would serve as buffer of data to be transmitted from a spacecraft to Earth. This architecture would afford fault tolerance needed for reliable operation in an anticipated high-radiation environment in which traditional SSRs cannot operate reliably. Features of the architecture include one or more controller boards and multiple memory boards interconnected in a ringlike topology. The interconnections would be high-speed serial links complying with the Institute of Electrical and Electronics Engineers (IEEE) standard 1393 (which pertains to a spaceborne fiber-optic data bus). Accordingly, each controller and memory board would be equipped with an IEEE-1393-compliant ring-bus-interface unit. The ringlike topology and the multiplicity of memory boards (and, optionally, of controller boards) would afford the redundancy needed for fault tolerance. Each board would be a fault-containment region. The IEEE 1393 links could be routed so that the SSR would continue to function even in the event of multiple failures. This architecture would also support scalability over a wide range. In a fully redundant configuration, it could accommodate between 1 and 125 memory boards.

Walker, W. John↗

Active Missions and the VxOs with THEMIS as an Example

The Virtual Observatories (VxOs) provide a host of services to data producers and researchers. They help data producers to describe their data in standard Space Physics Archive Search and Extract (SPASE) terms that enable scientists to understand data products from a wide range of missions. They offer search interfaces based on specified criteria that help researchers discover conjunctions, prominent events, and intervals of interest. In this talk, we show how VMO services can be used with Time History of Events and Macroscale Interactions during Substorms (THEMIS) observations to identify magnetotail intervals marked by high speed flows, enhanced densities, or high temperatures. We present statistical surveys of when and where these phenomena occur. We then show how the VMO services can be used to identify events in which two or more THEMIS spacecraft observe specified features for more detailed analysis. We conclude by discussing the current limitations of VMO tools and outline plans for the future.

Sibeck, D. G.↗

Space Station Freedom capabilities for users

Space Station Freedom's major objectives are to prepare for human space exploration by providing a long-duration, continuously habitable spacecraft in low earth orbit for physiology studies and for development of systems to support human presence in space and to enable laboratory and observational research in space. As a result of restructuring and the preliminary design review, designs of Space Station Freedom architecture and systems have progressed to the point where the accommodations for users can be well described. These capabilities are enumerated, covering such important resources as power and cooling, rack volume and external accommodations, crew time, data and command rates, and acceleration environment. Related items such as total energy, data management systems, and interfaces, station attitude, payload transportation, and on board and ground facilities are considered.

Taylor, William W. L.↗

NASA Tech Briefs, November 2005

Topics covered include: Laser System for Precise, Unambiguous Range Measurements; Flexible Cryogenic Temperature and Liquid-Level Probes; Precision Cryogenic Dilatometer; Stroboscopic Interferometer for Measuring Mirror Vibrations; Some Improvements in H-PDLCs; Multiple-Bit Differential Detection of OQPSK; Absolute Position Encoders With Vertical Image Binning; Flexible, Carbon-Based Ohmic Contacts for Organic Transistors; GaAs QWIP Array Containing More Than a Million Pixels; AutoChem; Virtual Machine Language; Two-Dimensional Ffowcs Williams/Hawkings Equation Solver; Full Multigrid Flow Solver; Doclet To Synthesize UML; Computing Thermal Effects of Cavitation in Cryogenic Liquids; GUI for Computational Simulation of a Propellant Mixer; Control Program for an Optical-Calibration Robot; SQL-RAMS; Distributing Data from Desktop to Hand-Held Computers; Best-Fit Conic Approximation of Spacecraft Trajectory; Improved Charge-Transfer Fluorescent Dyes; Stability-Augmentation Devices for Miniature Aircraft; Tool Measures Depths of Defects on a Case Tang Joint; Two Heat-Transfer Improvements for Gas Liquefiers; Controlling Force and Depth in Friction Stir Welding; Spill-Resistant Alkali-Metal-Vapor Dispenser; A Methodology for Quantifying Certain Design Requirements During the Design Phase; Measuring Two Key Parameters of H3 Color Centers in Diamond; Improved Compression of Wavelet-Transformed Images; NASA Interactive Forms Type Interface - NIFTI; Predicting Numbers of Problems in Development of Software; Hot-Electron Photon Counters for Detecting Terahertz Photons; Magnetic Variations Associated With Solar Flares; and Artificial Intelligence for Controlling Robotic Aircraft.

Source record↗

The Substructure of a Flux Transfer Event Observed by the MMS Spacecraft

On 15 August 2015, MMS (Magnetospheric Multiscale mission), skimming the dusk magnetopause, detected an isolated region of an increased magnetic strength and bipolar Bn, indicating a flux transfer event (FTE). The four spacecraft in a tetrahedron allowed for investigations of the shape and motion of the FTE. In particular, high-resolution particle data facilitated our exploration of FTE substructures and their magnetic connectivity inside and surrounding the FTE. Combined field and plasma observations suggest that the core fields are open, magnetically connected to the northern magnetosphere from which high-energy particles leak; ion "D" distributions characterize the axis of flux ropes that carry old-opened field lines; counter streaming electrons superposed by parallel-heated components populate the periphery surrounding the FTE; and the interface between the core and draped regions contains a separatrix of newlyopened magnetic field lines that emanate from the X line above the FTE.

Hwang, K.-J.↗

On-demand Command and Control of ASTERIA with Cloud-based Ground Station Services

ASTERIA (Arcsecond Space Telescope Enabling Research in Astrophysics) was a 6-unit CubeSat technology demonstration mission that deployed from the International Space Station on November 20th, 2017. After successfully completing its 90-day primary mission that demonstrated arcsecond-level line-of-sight pointing and focal plane thermal stability for exoplanet detection, it entered an extended mission performing onboard software demonstrations to mature technology both in space and on the ground. One of the technologies was a completely cloud-based ground system leveraging Amazon Web Services (AWS) Ground Station service. Announced in December 2018 and launched in May 2019, AWS Ground Station is a fully managed ground station service that aims to reduce the overhead associated with developing and maintaining ground system infrastructure throughout the mission lifecycle. AWS Ground Station makes available the suite of features required for any ground system in support of low-Earth orbit (LEO) and medium-Earth Orbit (MEO) satellite operations on-demand and without setting up or maintaining long-term contracts. Charges are incurred on a per-minute basis for antenna usage during scheduled tracks. Support is available for S-band uplink and downlink, along with X-band narrowband and wideband downlink. Missions that use the service may reserve tracks with any licensed AWS Ground Station antennas located across each service region and have direct access to any AWS services in support of mission operations. The cloud-based architecture built around the AWS Ground Station service greatly enhanced ASTERIA mission operations by enabling end-to-end pass automation, on-demand contact scheduling and contingency planning, along with more efficient data downlink through station availability and station-tostation handovers. It incorporated open-source software, particularly NASA's AMMOS Instrument Toolkit (AIT) and Open Mission Control Technologies (OpenMCT), along with the AWS application programming interfaces (API) to the Ground Station, Elastic Compute Cloud (EC2) and Simple Storage Service (S3) services. After showcasing operability in August 2019, the team continued using and improving this novel ground system architecture until the end of mission in December 2019. This paper describes the cloud-based ground system, how it was designed, tested, and evaluated with an inorbit spacecraft, the operational capabilities that it enabled, along with lessons learned and recommendations for future missions.

Fesq, Lorraine↗

Mars Exploration Rovers navigation results

The twin Mars Exploration Rovers, Spirit and Opportunity, were launched on June 10, 2003(dagger), and July 8, 2003, from Cape Canaveral, Florida. Spirit and Opportunity were targeted for landings at Gusev Crater (arrival on January 4, 2004) and Meridiani Planum (arrival on January 25, 2004). The primary navigation challenge was to deliver each spacecraft to the desired atmospheric entry interface point with sufficient accuracy such that each lander would touch down within a specified landing ellipse (about 70 km x 5 km) determined to be safe for landing and also judged to be scientifically interesting. In order to achieve landing within the target ellipse, precise control of the inertial entry flight path angle (FPA) at atmospheric entry was required. The maximum allowable errors in FPA following TCM-5 (trajectory correction maneuver #5) at Entry (E) - 2 days were +/-0.12(deg) (3(sigma)) for Spirit and +/-0.14(deg) (3(sigma)) for Opportunity. Achieving these entry delivery accuracies necessitated significant improvements to the interplanetary avigation system used for MER. These improvements included new processes and software for orbit determination, propulsive maneuver design, and entry, descent, and landing (EDL) trajectory simulation. The actual achieved atmospheric entry accuracies for Spirit and Opportunity significantly exceeded the requirements. At the navigation data cutoff for the TCM-5 final design, the orbit determination FPA knowledge error was +/-0.028(deg) (3(sigma) ) for Spirit and +/-0.035(deg) (3(sigma)) for Opportunity. Because of exceptionally accurate navigation performance, TCM-5 (E - 2 days) and TCM-6 (E - 4 hours) were canceled for both Spirit and Opportunity. The actual landing locations (determined from in-situ Doppler tracking between the MER rovers and the Mars Odyssey orbiter) differed from the target landing points by 10.1 km (downtrack) for Spirit and 24.6 km (downtrack) for Opportunity. The majority of the landing position offsets for both landers was primarily caused by variations in atmosphere and spacecraft aerodynamic modeling from what was predicted. The amount of the landing position offset caused by navigation-only errors was only 3.3 km (uptrack) for Spirit and 9.7 km (downtrack) for Opportunity.

Mars Exploration Rover (MER)↗

Mars Exploration Rovers navigation results

The twin Mars Exploration Rovers, Spirit and Opportunity, were launched on June 10, 2003, and July 8, 2003, from Cape Canaveral, Florida. Spirit and Opportunity were targeted for landings at Gusev Crater (arrival on January 4, 2004) and Meridiani Planum (arrival on January 25, 2004). The primary navigation challenge was to deliver each spacecraft to the desired atmospheric entry interface point with sufficient accuracy such that each lander would touch down within a specified landing ellipse (about 70 km x 5 km) determined to be safe for landing and also judged to be scientifically interesting. In order to achieve landing within the target ellipse, precise control of the inertial entry flight path angle (FPA) at atmospheric entry was required. The maximum allowable errors in FPA following TCM-5 (trajectory correction maneuver #5) at Entry (E) -2 days were +/-0.12 deg(3 sigma) for Spirit and +/-0.14 deg(3 sigma) for Opportunity. Achieving these entry delivery accuracies necessitated significant improvements to the interplanetary navigation system used for MER. These improvements included new processes and software for orbit determination, propulsive maneuver design, and entry, descent, and landing (EDL) trajectory simulation. The actual achieved atmospheric entry accuracies for Spirit and Opportunity significantly exceeded the requirements. At the navigation data cutoff for the TCM-5 final design, the orbit determination FPA knowledge error was 0.028 deg(3 sigma) for Spirit and 0.035 deg(3 sigma) for Opportunity. Because of exceptionally accurate navigation performance, TCM-5 (E - 2 days) and TCM-6 (E - 4 hours) were canceled for both Spirit and Opportunity. The actual landing locations (determined from in-situ Doppler tracking between the MER rovers and the Mars Odyssey orbiter) differed from the target landing points by 10.1 km (downtrack) for Spirit and 24.6 km (downtrack) for Opportunity. The majority of the landing position offsets for both landers was primarily caused by variations in atmosphere and spacecraft aerodynamic modeling from what was predicted. The amount of the landing position offset caused by navigation-only errors was only 3.3 km (uptrack) for Spirit and 9.7 km (downtrack) for Opportunity.

Mars Exploration Rover (MER)↗

MUSTANG: A Workhorse for NASA Spaceflight Avionics

The Modular Unified Space Technology Avionics for Next Generation (MUSTANG) is a small integrated Avionics system including Command and Data Handling (C&DH), Power System Electronics (PSE), Attitude Control System Interfaces (ACS), and Propulsion Electronics. The MUSTANG Avionics Architecture is built upon many years of knowledge capture and lessons learned at the Goddard Space Flight Center. With a motivation towards modularity and keeping board redesign costs to a minimum, MUSTANG offers flexibility in features with a backplane-less design and allows the user to choose the options (cards) needed for their system. It incorporates a distributed power system that provides secondary power to all its subcomponents reducing the number of primary services needed for an Avionics. MUSTANG can be integrated into one system or divided into several smaller components. MUSTANG supports redundancy and cross-strap ability for a more robust and reliable Avionics system. A variation of MUSTANG exists for Instrument Electronics called iMUSTANG and allows the user to select functionality applicable to the instrument electronics. MUSTANG is not meant to replace Avionics for all spacecraft. There are limitations due to its relatively compact size, but the MUSTANG design has proven broadly applicable on many spacecraft and instrument bus avionics architectures.

MUSTANG↗

EOS MLS Level 1B Data Processing, Version 2.2

A computer program performs level- 1B processing (the term 1B is explained below) of data from observations of the limb of the Earth by the Earth Observing System (EOS) Microwave Limb Sounder (MLS), which is an instrument aboard the Aura spacecraft. This software accepts, as input, the raw EOS MLS scientific and engineering data and the Aura spacecraft ephemeris and attitude data. Its output consists of calibrated instrument radiances and associated engineering and diagnostic data. [This software is one of several computer programs, denoted product generation executives (PGEs), for processing EOS MLS data. Starting from level 0 (representing the aforementioned raw data, the PGEs and their data products are denoted by alphanumeric labels (e.g., 1B and 2) that signify the successive stages of processing.] At the time of this reporting, this software is at version 2.2 and incorporates improvements over a prior version that make the code more robust, improve calibration, provide more diagnostic outputs, improve the interface with the Level 2 PGE, and effect a 15-percent reduction in file sizes by use of data compression.

Perun, Vincent↗

Ascent Heating Thermal Analysis on Spacecraft Adaptor Fairings

When the Crew Exploration Vehicle (CEV) is launched, the spacecraft adaptor (SA) fairings that cover the CEV service module (SM) are exposed to aero heating. Thermal analysis is performed to compute the fairing temperatures and to investigate whether the temperatures are within the material limits for nominal ascent aeroheating case. The ascent heating is analyzed by using computational fluid dynamics (CFD) and engineering codes at Marshall Space Flight Center. The aeroheating environment data used for this work is known as Thermal Environment 3 (TE3) heating data. One of the major concerns is with the SA fairings covering the CEV SM and the SM/crew launch vehicle (CLV) flange interface. The TE3 heating rate is a function of time, wall temperature, and the spatial locations. The implementation of the TE3 heating rate as boundary conditions in the thermal analysis becomes challenging. The ascent heating thermal analysis on SA fairings and SM/CLV flange interface are performed using two commercial software packages: Cullimore & Ring (C&R) Thermal Desktop (TD) 5.1 and MSC Patran 2007r1 b. TD is the pre-and post-processor for SINDA, which is a finite-difference-based solver. In TD, the geometry is built and meshed, the boundary conditions are defined, and then SINDA is used to compute temperatures. MSC Pthermal is a finite-element- based thermal solver. MSC Patran is the pre- and post-processor for Pthermal. Regarding the boundary conditions, the convection, contact resistance, and heat load can be imposed in different ways in both programs. These two software packages are used to build the thermal model for the same analysis to validate each other and show the differences in the modeling details.

Wang, Xiao Yen↗