Search NASA⌕ Search

SEARCH · Search NASA

Results for “start up files”

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 127 records · Page 7

The Mission Transcript Collection: U.S. Human Spaceflight Missions from Mercury Redstone 3 to Apollo 17

Aboard every U.S. piloted spacecraft, from Mercury through Apollo, NASA installed tape recorders that captured nearly every word spoken by the astronauts during their history-making flights into space. For the first time ever, NASA has digitally scanned all of the transcripts made from both the onboard tapes and those tape recordings made on the ground from the air-to-ground transmissions and placed them on this two CD-ROM set. Gathered in this special collection are 80 transcripts totaling nearly 45,000 pages of text that cover every US human spaceflight from the first human Mercury mission through the last lunar landing flight of Apollo 17. Users of this CD will note that the quantity and type of transcripts made for each mission vary. For example, the Mercury flights each had one transcript whereas the Gemini missions produced several. Starting with the Gemini flights, NASA produced a Public Affairs Office (PAO) commentary version, as well as at least one "technical" air-to-ground transcript version, per mission. Most of the Apollo missions produced four transcripts per flight. These included the onboard voice data recorder transcripts made from the Data Storage Equipment (DSE) on the Command Module (CM), and the Data Storage Electronics Assembly (DSEA) onboard the Lunar Module (LM), in addition to the PAO commentary and air-to-ground technical transcripts. The CD set includes an index listing each transcript file by name. Some of the transcripts include a detailed explanation of their contents and how they were made. Also included in this collection is a listing of all the original air-to-ground audiotapes housed in NASA's archives from which many of these transcripts were made. We hope you find this collection of transcripts interesting and useful.

Source record↗

Development and Engineering Design in Support of "Rover Ranch": A K-12 Outreach Software Project

A continuation of the initial development started in the summer of 1999, the body of work performed in support of 'ROVer Ranch' Project during the present fellowship dealt with the concrete concept implementation and resolution of the related issues. The original work performed last summer focused on the initial examination and articulation of the concept treatment strategy, audience and market analysis for the learning technologies software. The presented work focused on finalizing the set of parts to be made available for building an AERCam Sprint type robot and on defining, testing and implementing process necessary to convert the design engineering files to VRML files. Through reverse engineering, an initial set of mission critical systems was designed for beta testing in schools. The files were created in ProEngineer, exported to VRML 1.0 and converted to VRML 97 (VRML 2.0) for final integration in the software. Attributes for each part were assigned using an in-house developed JAVA based program. The final set of attributes for each system, their mutual interaction and the identification of the relevant ones to be tracked, still remain to be decided.

Pascali, Raresh↗

NASA Tech Briefs, June 2009

Topics covered include: Device for Measuring Low Flow Speed in a Duct, Measuring Thermal Conductivity of a Small Insulation Sample, Alignment Jig for the Precise Measurement of THz Radiation, Autoignition Chamber for Remote Testing of Pyrotechnic Devices, Microwave Power Combiners for Signals of Arbitrary Amplitude, Synthetic Foveal Imaging Technology, Airborne Antenna System for Minimum-Cycle-Slip GPS Reception, Improved Starting Materials for Back-Illuminated Imagers, Multi-Modulator for Bandwidth-Efficient Communication, Some Improvements in Utilization of Flash Memory Devices, GPS/MEMS IMU/Microprocessor Board for Navigation, T/R Multi-Chip MMIC Modules for 150 GHz, Pneumatic Haptic Interfaces, Device Acquires and Retains Rock or Ice Samples, Cryogenic Feedthrough Test Rig, Improved Assembly for Gas Shielding During Welding or Brazing, Two-Step Plasma Process for Cleaning Indium Bonding Bumps, Tool for Crimping Flexible Circuit Leads, Yb14MnSb11 as a High-Efficiency Thermoelectric Material, Polyimide-Foam/Aerogel Composites for Thermal Insulation, Converting CSV Files to RKSML Files, Service Management Database for DSN Equipment, Chemochromic Hydrogen Leak Detectors, Compatibility of Segments of Thermoelectric Generators, Complementary Barrier Infrared Detector, JPL Greenland Moulin Exploration Probe, Ultra-Lightweight Self-Deployable Nanocomposite Structure for Habitat Applications, and Room-Temperature Ionic Liquids for Electrochemical Capacitors.

Source record↗

SUPIN: A Tool for the Aerodynamic Design and Analysis of Supersonic Inlets

The Supersonic Inlet Design and Analysis Tool (SUPIN) is a computational program that performs geometric modeling and aerodynamic design and analysis of a set of supersonic inlets whose types include the axisymmetric pitot, three-dimensional pitot, axisymmetric, two-dimensional, two-dimensional bifurcated-duct, and streamline-traced inlets. The inlets are modeled by dividing the inlet flowpath into components that start at the freestream and ends at the engine face. The primary components of the inlet include the external supersonic diffuser, throat section, and subsonic diffuser. Each component is characterized by a set of inputs that include geometric and aerodynamic factors. Examples of the geometric factors are angles, lengths, area ratios, and coordinates that describe the geometry of the components. Examples of the aerodynamic factors are Mach numbers, flow ratios, and pressure ratios that set constraints or desired aerodynamic properties of the component. These input factors are specified within a text-based input data file that is read into SUPIN. SUPIN is a Fortran 95 program that performs the inlet design and analysis as a batch or non-interactive process. SUPIN writes output data files describing the inlet geometry and aerodynamic performance. SUPIN uses analytic, empirical, and numerical methods to perform the inlet design and analysis. The inlet geometry is constructed using planar and three-dimensional geometry constructs and is represented by coordinates, angles, areas, profiles, and surfaces. Surfaces are output in the form of a Plot3D surface grid file. SUPIN does have some capability to automatically generate planar and three-dimensional, multi-block, structured grids for computational fluid dynamics (CFD) analysis. The aerodynamic analysis performed by SUPIN computes quasi-one-dimensional properties, such as Mach numbers, pressures, and temperatures, through the inlet flowpath. Planar aerodynamic properties, such as those for shock and Mach waves, are computed for the supersonic compression of the external supersonic diffuser and throat section. The inlet performance is characterized by the inlet flow rates, total pressure recovery, and inlet drag. The primary intent of this document is to describe the usage of SUPIN. The methods used within SUPIN are documented and may serve as a useful reference for understanding the aerodynamic design and analysis of supersonic inlets.

supersonic inlets↗

Parallel Eclipse Project Checkout

Parallel Eclipse Project Checkout (PEPC) is a program written to leverage parallelism and to automate the checkout process of plug-ins created in Eclipse RCP (Rich Client Platform). Eclipse plug-ins can be aggregated in a feature project. This innovation digests a feature description (xml file) and automatically checks out all of the plug-ins listed in the feature. This resolves the issue of manually checking out each plug-in required to work on the project. To minimize the amount of time necessary to checkout the plug-ins, this program makes the plug-in checkouts parallel. After parsing the feature, a request to checkout for each plug-in in the feature has been inserted. These requests are handled by a thread pool with a configurable number of threads. By checking out the plug-ins in parallel, the checkout process is streamlined before getting started on the project. For instance, projects that took 30 minutes to checkout now take less than 5 minutes. The effect is especially clear on a Mac, which has a network monitor displaying the bandwidth use. When running the client from a developer s home, the checkout process now saturates the bandwidth in order to get all the plug-ins checked out as fast as possible. For comparison, a checkout process that ranged from 8-200 Kbps from a developer s home is now able to saturate a pipe of 1.3 Mbps, resulting in significantly faster checkouts. Eclipse IDE (integrated development environment) tries to build a project as soon as it is downloaded. As part of another optimization, this innovation programmatically tells Eclipse to stop building while checkouts are happening, which dramatically reduces lock contention and enables plug-ins to continue downloading until all of them finish. Furthermore, the software re-enables automatic building, and forces Eclipse to do a clean build once it finishes checking out all of the plug-ins. This software is fully generic and does not contain any NASA-specific code. It can be applied to any Eclipse-based repository with a similar structure. It also can apply build parameters and preferences automatically at the end of the checkout.

Crockett, Thomas M.↗

Rotary engine performance computer program (RCEMAP and RCEMAPPC): User's guide

This report is a user's guide for a computer code that simulates the performance of several rotary combustion engine configurations. It is intended to assist prospective users in getting started with RCEMAP and/or RCEMAPPC. RCEMAP (Rotary Combustion Engine performance MAP generating code) is the mainframe version, while RCEMAPPC is a simplified subset designed for the personal computer, or PC, environment. Both versions are based on an open, zero-dimensional combustion system model for the prediction of instantaneous pressures, temperature, chemical composition and other in-chamber thermodynamic properties. Both versions predict overall engine performance and thermal characteristics, including bmep, bsfc, exhaust gas temperature, average material temperatures, and turbocharger operating conditions. Required inputs include engine geometry, materials, constants for use in the combustion heat release model, and turbomachinery maps. Illustrative examples and sample input files for both versions are included.

Bartrand, Timothy A.↗

Python Based Plume Dynamics Estimation Tool (PyPDET) Rapid Plume Strike Analysis for RPOD Maneuvers in Deep Space Operations

I worked as a NASA Intern during the Summer 2023 term in the DS-00 division under the supervision of my mentor, Dr. Jonathan Pitt. Our goal was to build on our previous work from 2022 to develop a plume strike estimation tool using a prescribed physics methodology and model plume impingement effects while considering the dynamics of a rendezvous, operations, proximity, and docking (RPOD) maneuver. This tool supports previously configured CFD-DSMC calculations by allowing for rapid analysis of initial designs using a low-fidelity source flow model. Engineers can then use the high-fidelity CFD-DSMC tool to consolidate results as they work towards finalizing a design. This year’s project was focused on developing a software application that other engineers would be using in their analysis. Thus, the user’s experience was considered in the development of this application. Proper documentation, testability, and modularity of the codebase was our priority. For example, the project included auto documentation procedures to start building towards a User Manual, while also including dedicated demonstration cases for more explicit communication of functionality. Also, this project included a framework for testing the source code for future developments. Additionally, care was taken to develop the code using an Object-Oriented Programming approach. Thus, allowing for a modular extensibility of functionality in anticipation of future developments. The core work of this project was developing an algorithm that would transform the visiting vehicle and associated thruster data according to the kinematics described in the jet firing history. It would then calculate the estimated plume strikes on two of the target vehicles and write data accordingly into a VTK file. Summer work is to conclude by developing and presenting a PowerPoint slide deck at the intern exit briefing on August 11 th , 2023. Once the model for simple plume strike calculations is developed and tested there are several avenues to explore to continue development of this tool. These are also discussed in this report.

Plume Impingement↗

Air Traffic Complexity Measurement Environment (ACME): Software User's Guide

A user's guide for the Air Traffic Complexity Measurement Environment (ACME) software is presented. The ACME consists of two major components, a complexity analysis tool and user interface. The Complexity Analysis Tool (CAT) analyzes complexity off-line, producing data files which may be examined interactively via the Complexity Data Analysis Tool (CDAT). The Complexity Analysis Tool is composed of three independently executing processes that communicate via PVM (Parallel Virtual Machine) and Unix sockets. The Runtime Data Management and Control process (RUNDMC) extracts flight plan and track information from a SAR input file, and sends the information to GARP (Generate Aircraft Routes Process) and CAT (Complexity Analysis Task). GARP in turn generates aircraft trajectories, which are utilized by CAT to calculate sector complexity. CAT writes flight plan, track and complexity data to an output file, which can be examined interactively. The Complexity Data Analysis Tool (CDAT) provides an interactive graphic environment for examining the complexity data produced by the Complexity Analysis Tool (CAT). CDAT can also play back track data extracted from System Analysis Recording (SAR) tapes. The CDAT user interface consists of a primary window, a controls window, and miscellaneous pop-ups. Aircraft track and position data is displayed in the main viewing area of the primary window. The controls window contains miscellaneous control and display items. Complexity data is displayed in pop-up windows. CDAT plays back sector complexity and aircraft track and position data as a function of time. Controls are provided to start and stop playback, adjust the playback rate, and reposition the display to a specified time.

Source record↗

Cursor Control Device Test Battery

The test battery was developed to provide a standard procedure for cursor control device evaluation. The software was built in Visual Basic and consists of nine tasks and a main menu that integrates the set-up of the tasks. The tasks can be used individually, or in a series defined in the main menu. Task 1, the Unidirectional Pointing Task, tests the speed and accuracy of clicking on targets. Two rectangles with an adjustable width and adjustable center- to-center distance are presented. The task is to click back and forth between the two rectangles. Clicks outside of the rectangles are recorded as errors. Task 2, Multidirectional Pointing Task, measures speed and accuracy of clicking on targets approached from different angles. Twenty-five numbered squares of adjustable width are arranged around an adjustable diameter circle. The task is to point and click on the numbered squares (placed on opposite sides of the circle) in consecutive order. Clicks outside of the squares are recorded as errors. Task 3, Unidirectional (horizontal) Dragging Task, is similar to dragging a file into a folder on a computer desktop. Task 3 requires dragging a square of adjustable width from one rectangle and dropping it into another. The width of each rectangle is adjustable, as well as the distance between the two rectangles. Dropping the square outside of the rectangles is recorded as an error. Task 4, Unidirectional Path Following, is similar to Task 3. The task is to drag a square through a tunnel consisting of two lines. The size of the square and the width of the tunnel are adjustable. If the square touches any of the lines, it is counted as an error and the task is restarted. Task 5, Text Selection, involves clicking on a Start button, and then moving directly to the underlined portion of the displayed text and highlighting it. The pointing distance to the text is adjustable, as well as the to-be-selected font size and the underlined character length. If the selection does not include all of the underlined characters, or includes non-underlined characters, it is recorded as an error. Task 6, Multi-size and Multi-distance Pointing, presents the participant with 24 consecutively numbered buttons of different sizes (63 to 163 pixels), and at different distances (60 to 80 pixels) from the Start button. The task is to click on the Start button, and then move directly to, and click on, each numbered target button in consecutive order. Clicks outside of the target area are errors. Task 7, Standard Interface Elements Task, involves interacting with standard interface elements as instructed in written procedures, including: drop-down menus, sliders, text boxes, radio buttons, and check boxes. Task completion time is recorded. In Task 8, a circular track is presented with a disc in it at the top. Track width and disc size are adjustable. The task is to move the disc with circular motion within the path without touching the boundaries of the track. Time and errors are recorded. Task 9 is a discrete task that allows evaluation of discrete cursor control devices that tab from target to target, such as a castle switch. The task is to follow a predefined path and to click on the yellow targets along the path.

Kritina Holden↗

Satellite Broadcast of Graphical Weather Data Flight Tested

NASA Glenn Research Center at Lewis Field's aviation Weather Information Communications (WINCOMM) and NASA Langley Research Center's Aviation Weather Information (AWIN) programs collaborated in a flight test and evaluation of a worldwide weather data-link capability using satellites. This successful flight testing moves NASA closer to its goal of developing advanced communications and information technologies to enable high-quality and timely dissemination of aviation weather information to all relevant users on the aviation information network. Recognized as a major contributing factor in aviation accidents and incidents, weather contributes directly or indirectly to nearly 80 percent of fatal general aviation (small private aircraft) accidents. In 1997, the Aeronautics Safety Investment Strategy Team s weather team produced a prioritized list of investment areas under weather accident prevention. Weather data dissemination is the most critical and highest ranked priority on the list. NASA's Aviation Safety Program founded the Aviation Weather Information initiative to focus efforts on significantly reducing the number of weather-related aviation fatalities. Access to accurate and timely weather data could contribute to a major reduction of weather-related incidents and accidents. However, a cost-effective solution has eluded most general aviation pilots because of the high cost of onboard weather radar equipment. Rockwell Collins, through a contract with NASA and in cooperation with WorldSpace Corporation, successfully completed ground and flight testing of a receiver and antenna in Johannesburg, South Africa. This NASA/Rockwell Collins project is an evaluation of worldwide weather data-link capability using transmissions from the Satellite Digital Audio Radio Services (S DARS) AfriStar satellite. Owned and operated by WorldSpace, AfriStar is a geostationary satellite that broadcasts commercial digital audio services to stationary and mobile platforms. S DARS satellites are the most powerful communications satellites produced to date, allowing users to receive signals using simple, low-cost patch antennas instead of more expensive, beam-steered antenna arrays. Engineers connected an inexpensive, commercially available radio receiver to a laptop computer and an antenna designed and built by Rockwell Collins, enabling them to receive WorldSpace signals from the AfriStar satellite during flight tests. WorldSpace broadcast their composite color graphical weather data files, which were multiplexed with normal audio streams, to the flat patch antenna mounted on a single-engine aircraft. The aircraft was equipped with a modified commercial S-DARS receiver, a Global Positioning Satellite (GPS) receiver, and a laptop computer with color display. Continuous data reception occurred during normal aircraft maneuvers performed throughout takeoff, cruise, and landing operations. In addition, engineers monitored receiver power levels during steep turns and banks. In most instances, the receiver was able to maintain acceptable power levels during all phases of flight and to obtain weather data with little or with the successful completion of ground and flight testing of a receiver and antenna in Johannesburg, South Africa, the team has started to prepare for experiments using highspeed aircraft in areas of the world with limited access to timely weather data. NASA plans to provide a more advanced antenna design and consultation support. This successful test of real-time aviation-related weather data is a positive step toward solving communications-specific issues associated with the dissemination of weather data directly to the cockpit.

Mallasch, Paul G.↗

The Role and Evolution of NASA's Earth Science Data Systems

One of the three strategic goals of NASA is to Advance understanding of Earth and develop technologies to improve the quality of life on our home planet (NASA strategic plan 2014). NASA's Earth Science Data System (ESDS) Program directly supports this goal. NASA has been launching satellites for civilian Earth observations for over 40 years, and collecting data from various types of instruments. Especially since 1990, with the start of the Earth Observing System (EOS) Program, which was a part of the Mission to Planet Earth, the observations have been significantly more extensive in their volumes, variety and velocity. Frequent, global observations are made in support of Earth system science. An open data policy has been in effect since 1990, with no period of exclusive access and non-discriminatory access to data, free of charge. NASA currently holds nearly 10 petabytes of Earth science data including satellite, air-borne, and ground-based measurements and derived geophysical parameter products in digital form. Millions of users around the world are using NASA data for Earth science research and applications. In 2014, over a billion data files were downloaded by users from NASAs EOS Data and Information System (EOSDIS), a system with 12 Distributed Active Archive Centers (DAACs) across the U. S. As a core component of the ESDS Program, EOSDIS has been operating since 1994, and has been evolving continuously with advances in information technology. The ESDS Program influences as well as benefits from advances in Earth Science Informatics. The presentation will provide an overview of the role and evolution of NASAs ESDS Program.

Remote Sensing↗

Changes in Exercise Data Management

The suite of exercise hardware aboard the International Space Station (ISS) generates an immense amount of data. The data collected, treadmill, cycle ergometer, and resistance strength training hardware, are basic exercise parameters (time, heart rate, speed, load, etc.). The raw data are processed in the laboratory and more detailed parameters are calculated from each exercise data file. Updates recently have been made to how these valuable data are stored, adding an additional level of security, increasing accessibility, and resulting in overall increased efficiency of medical report delivery. Questions regarding exercise performance or how exercise may influence other variables of crew health frequently arise within the crew health care community. Inquiries regarding the health of the exercise hardware often need quick analysis and response to ensure the exercise system is operable on a continuous basis. Consolidating all of the exercise system data in a single repository enables a quick response to both the medical and engineering communities. A SQL server database is currently in use, and provides a secure location for all of the exercise data starting at ISS Expedition 1 to current date. The database has been structured to update derived metrics automatically, making analysis and reporting available within minutes of dropping the in-flight data into the database. Commercial tools were evaluated to help aggregate and visualize data from the SQL database. The Tableau software provides manageable interface, which has improved the laboratory’s output time of crew reports by 67%. Expansion of the SQL database, to be inclusive of additional medical requirement metrics, addition of ‘app-like’ tools for mobile visualization, and collaborative use (e.g., operational support teams, research groups, and International Partners) of the data system, is currently being explored.

Buxton, R. E.↗

Changes in Exercise Data Management

The suite of exercise hardware aboard the International Space Station (ISS) generates an immense amount of data. The data collected from the treadmill, cycle ergometer, and resistance strength training hardware are basic exercise parameters (time, heart rate, speed, load, etc.). The raw data are post processed in the laboratory and more detailed parameters are calculated from each exercise data file. Updates have recently been made to how this valuable data are stored, adding an additional level of data security, increasing data accessibility, and resulting in overall increased efficiency of medical report delivery. Questions regarding exercise performance or how exercise may influence other variables of crew health frequently arise within the crew health care community. Inquiries over the health of the exercise hardware often need quick analysis and response to ensure the exercise system is operable on a continuous basis. Consolidating all of the exercise system data in a single repository enables a quick response to both the medical and engineering communities. A SQL server database is currently in use, and provides a secure location for all of the exercise data starting at ISS Expedition 1 - current day. The database has been structured to update derived metrics automatically, making analysis and reporting available within minutes of dropping the inflight data it into the database. Commercial tools were evaluated to help aggregate and visualize data from the SQL database. The Tableau software provides manageable interface, which has improved the laboratory's output time of crew reports by 67%. Expansion of the SQL database to be inclusive of additional medical requirement metrics, addition of 'app-like' tools for mobile visualization, and collaborative use (e.g. operational support teams, research groups, and International Partners) of the data system is currently being explored.

Buxton, R. E.↗

CERES BiDirectional Scans (BDS) data in HDF (CER_BDS_TRMM-PFM_Edition1)

Each BiDirectional Scans (BDS) data product contains twenty-four hours of Level-1b data for each CERES scanner instrument mounted on each spacecraft. The BDS includes samples taken in normal and short Earth scan elevation profiles in both fixed and rotating azimuth scan modes (including space, internal calibration, and solar calibration views). The BDS contains Level-0 raw (unconverted) science and instrument data as well as the geolocated converted science and instrument data. The BDS contains additional data not found in the Level-0 input file, including converted satellite position and velocity data, celestial data, converted digital status data, and parameters used in the radiance count conversion equations. The following CERES BDS data sets are currently available: CER_BDS_TRMM-PFM_Edition1 CER_BDS_Terra-FM1_Edition1 CER_BDS_Terra-FM2_Edition1 CER_BDS_Terra-FM1_Edition2 CER_BDS_Terra-FM2_Edition2 CER_BDS_Aqua-FM3_Edition1 CER_BDS_Aqua-FM4_Edition1 CER_BDS_Aqua-FM3_Edition2 CER_BDS_Aqua-FM4_Edition2 CER_BDS_Aqua-FM3_Edition1-CV CER_BDS_Aqua-FM4_Edition1-CV CER_BDS_Terra-FM1_Edition1-CV CER_BDS_Terra-FM2_Edition1-CV. [Location=GLOBAL] [Temporal_Coverage: Start_Date=1997-12-27; Stop_Date=2000-12-31] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Temporal_Resolution=1 day; Temporal_Resolution_Range=Daily - < Weekly].

SHORTWAVE FILTERED RADIANCE UPWARDS↗

CERES BiDirectional Scans (BDS) data in HDF (CER_BDS_Terra-FM1_Edition1)

Each BiDirectional Scans (BDS) data product contains twenty-four hours of Level-1b data for each CERES scanner instrument mounted on each spacecraft. The BDS includes samples taken in normal and short Earth scan elevation profiles in both fixed and rotating azimuth scan modes (including space, internal calibration, and solar calibration views). The BDS contains Level-0 raw (unconverted) science and instrument data as well as the geolocated converted science and instrument data. The BDS contains additional data not found in the Level-0 input file, including converted satellite position and velocity data, celestial data, converted digital status data, and parameters used in the radiance count conversion equations. The following CERES BDS data sets are currently available: CER_BDS_TRMM-PFM_Edition1 CER_BDS_Terra-FM1_Edition1 CER_BDS_Terra-FM2_Edition1 CER_BDS_Terra-FM1_Edition2 CER_BDS_Terra-FM2_Edition2 CER_BDS_Aqua-FM3_Edition1 CER_BDS_Aqua-FM4_Edition1 CER_BDS_Aqua-FM3_Edition2 CER_BDS_Aqua-FM4_Edition2 CER_BDS_Aqua-FM3_Edition1-CV CER_BDS_Aqua-FM4_Edition1-CV CER_BDS_Terra-FM1_Edition1-CV CER_BDS_Terra-FM2_Edition1-CV. [Location=GLOBAL] [Temporal_Coverage: Start_Date=1997-12-27; Stop_Date=2005-11-02] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Temporal_Resolution=1 day; Temporal_Resolution_Range=Daily - < Weekly].

WINDOW DETECTOR OUTPUT↗

CERES BiDirectional Scans (BDS) data in HDF (CER_BDS_Terra-FM2_Edition1)

Each BiDirectional Scans (BDS) data product contains twenty-four hours of Level-1b data for each CERES scanner instrument mounted on each spacecraft. The BDS includes samples taken in normal and short Earth scan elevation profiles in both fixed and rotating azimuth scan modes (including space, internal calibration, and solar calibration views). The BDS contains Level-0 raw (unconverted) science and instrument data as well as the geolocated converted science and instrument data. The BDS contains additional data not found in the Level-0 input file, including converted satellite position and velocity data, celestial data, converted digital status data, and parameters used in the radiance count conversion equations. The following CERES BDS data sets are currently available: CER_BDS_TRMM-PFM_Edition1 CER_BDS_Terra-FM1_Edition1 CER_BDS_Terra-FM2_Edition1 CER_BDS_Terra-FM1_Edition2 CER_BDS_Terra-FM2_Edition2 CER_BDS_Aqua-FM3_Edition1 CER_BDS_Aqua-FM4_Edition1 CER_BDS_Aqua-FM3_Edition2 CER_BDS_Aqua-FM4_Edition2 CER_BDS_Aqua-FM3_Edition1-CV CER_BDS_Aqua-FM4_Edition1-CV CER_BDS_Terra-FM1_Edition1-CV CER_BDS_Terra-FM2_Edition1-CV. [Location=GLOBAL] [Temporal_Coverage: Start_Date=1997-12-27; Stop_Date=2005-11-02] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Temporal_Resolution=1 day; Temporal_Resolution_Range=Daily - < Weekly].

TOTAL DETECTOR OUTPUT↗

CERES BiDirectional Scans (BDS) data in HDF (CER_BDS_Terra-FM1_Edition2)

Each BiDirectional Scans (BDS) data product contains twenty-four hours of Level-1b data for each CERES scanner instrument mounted on each spacecraft. The BDS includes samples taken in normal and short Earth scan elevation profiles in both fixed and rotating azimuth scan modes (including space, internal calibration, and solar calibration views). The BDS contains Level-0 raw (unconverted) science and instrument data as well as the geolocated converted science and instrument data. The BDS contains additional data not found in the Level-0 input file, including converted satellite position and velocity data, celestial data, converted digital status data, and parameters used in the radiance count conversion equations. The following CERES BDS data sets are currently available: CER_BDS_TRMM-PFM_Edition1 CER_BDS_Terra-FM1_Edition1 CER_BDS_Terra-FM2_Edition1 CER_BDS_Terra-FM1_Edition2 CER_BDS_Terra-FM2_Edition2 CER_BDS_Aqua-FM3_Edition1 CER_BDS_Aqua-FM4_Edition1 CER_BDS_Aqua-FM3_Edition2 CER_BDS_Aqua-FM4_Edition2 CER_BDS_Aqua-FM3_Edition1-CV CER_BDS_Aqua-FM4_Edition1-CV CER_BDS_Terra-FM1_Edition1-CV CER_BDS_Terra-FM2_Edition1-CV. [Location=GLOBAL] [Temporal_Coverage: Start_Date=1997-12-27; Stop_Date=2006-01-01] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Temporal_Resolution=1 day; Temporal_Resolution_Range=Daily - < Weekly].

SW FILTERED RADIANCE UPWARDS↗

CERES BiDirectional Scans (BDS) data in HDF (CER_BDS_Terra-FM2_Edition2)

Each BiDirectional Scans (BDS) data product contains twenty-four hours of Level-1b data for each CERES scanner instrument mounted on each spacecraft. The BDS includes samples taken in normal and short Earth scan elevation profiles in both fixed and rotating azimuth scan modes (including space, internal calibration, and solar calibration views). The BDS contains Level-0 raw (unconverted) science and instrument data as well as the geolocated converted science and instrument data. The BDS contains additional data not found in the Level-0 input file, including converted satellite position and velocity data, celestial data, converted digital status data, and parameters used in the radiance count conversion equations. The following CERES BDS data sets are currently available: CER_BDS_TRMM-PFM_Edition1 CER_BDS_Terra-FM1_Edition1 CER_BDS_Terra-FM2_Edition1 CER_BDS_Terra-FM1_Edition2 CER_BDS_Terra-FM2_Edition2 CER_BDS_Aqua-FM3_Edition1 CER_BDS_Aqua-FM4_Edition1 CER_BDS_Aqua-FM3_Edition2 CER_BDS_Aqua-FM4_Edition2 CER_BDS_Aqua-FM3_Edition1-CV CER_BDS_Aqua-FM4_Edition1-CV CER_BDS_Terra-FM1_Edition1-CV CER_BDS_Terra-FM2_Edition1-CV. [Location=GLOBAL] [Temporal_Coverage: Start_Date=1997-12-27; Stop_Date=2006-01-01] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Temporal_Resolution=1 day; Temporal_Resolution_Range=Daily - < Weekly].

TOTAL DETECTOR OUTPUT↗