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 145 records · Page 8

CERES BiDirectional Scans (BDS) data in HDF (CER_BDS_Aqua-FM4_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-04-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].

WN FILTERED RADIANCE UPWARDS↗

CERES BiDirectional Scans (BDS) data in HDF (CER_BDS_Aqua-FM3_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].

EOSDIS↗

CERES BiDirectional Scans (BDS) data in HDF (CER_BDS_Aqua-FM3_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].

SHORTWAVE FILTERED RADIANCE UPWARDS↗

CERES BiDirectional Scans (BDS) data in HDF (CER_BDS_Aqua-FM4_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=2005-03-29] [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_Edition1-CV)

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-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-CV)

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-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].

EOSDIS↗

CERES BiDirectional Scans (BDS) data in HDF (CER_BDS_Aqua-FM3_Edition1-CV)

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-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_Aqua-FM4_Edition1-CV)

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-03-30] [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 DETECTOR OUTPUT↗

Development of a User Interface for a Regression Analysis Software Tool

An easy-to -use user interface was implemented in a highly automated regression analysis tool. The user interface was developed from the start to run on computers that use the Windows, Macintosh, Linux, or UNIX operating system. Many user interface features were specifically designed such that a novice or inexperienced user can apply the regression analysis tool with confidence. Therefore, the user interface s design minimizes interactive input from the user. In addition, reasonable default combinations are assigned to those analysis settings that influence the outcome of the regression analysis. These default combinations will lead to a successful regression analysis result for most experimental data sets. The user interface comes in two versions. The text user interface version is used for the ongoing development of the regression analysis tool. The official release of the regression analysis tool, on the other hand, has a graphical user interface that is more efficient to use. This graphical user interface displays all input file names, output file names, and analysis settings for a specific software application mode on a single screen which makes it easier to generate reliable analysis results and to perform input parameter studies. An object-oriented approach was used for the development of the graphical user interface. This choice keeps future software maintenance costs to a reasonable limit. Examples of both the text user interface and graphical user interface are discussed in order to illustrate the user interface s overall design approach.

Ulbrich, Norbert Manfred↗

Creating a Voyager Thermal Model 39 Years Into the Flight Mission, Along with Model Correlation and Application

After 39 years of continuous operation in space, the output of the Voyager 1 & 2 spacecraft RTG power systems has decreased to the point where managing the power margin and maintaining thermal control has become increasingly difficult. As the total power dissipation in the bus has decreased, propellant line temperatures and margin above minimum AFTs have decreased, creating risk of the hydrazine freezing (at 1.6°C). This is further complicated by the lack of existing thermal models that can be used to assess propellant tank and line temperatures. In 2014, an effort was begun to create a Voyager spacecraft thermal model for that purpose.A steady-state Thermal Desktop model has been created from scratch over the past two years. The initial thermal model development was started by Applied Sciences Laboratory (ASL) under contract to JPL. The effort relied primarily on archived manufacturing drawings, limited documentation, interviews of senior engineers who worked on the Voyager design and implementation, and the experience of the Voyager Flight Operations team.Data from the Voyager System Thermal Vacuum tests is no longer available, making it necessary to correlate the model to more recent flight data and small in-flight tests. Correlation was achieved to within ±5°C for a hot case and a cold case (both data sets from 2014). However, the flight system has very few temperature sensors directly on propellant lines. So the task remains to determine how best to use the model, in conjunction with flight data, to make sure the Voyagers can continue to fly successfully. How does one go about creating a thermal model for a spacecraft that is already launched, has limited existing mechanical description files, no thermal model in order to do a maneuver that was never planned when the spacecraft was designed?

Ledeboer, William C.↗

NASA's EOSDIS, Trust and Certification

NASA's Earth Observing System Data and Information System (EOSDIS) has been in operation since August 1994, managing most of NASA's Earth science data from satellites, airborne sensors, filed campaigns and other activities. Having been designated by the Federal Government as a project responsible for production, archiving and distribution of these data through its Distributed Active Archive Centers (DAACs), the Earth Science Data and Information System Project (ESDIS) is responsible for EOSDIS, and is legally bound by the Office of Management and Budgets circular A-130, the Federal Records Act. It must follow the regulations of the National Institute of Standards and Technologies (NIST) and National Archive and Records Administration (NARA). It must also follow the NASA Procedural Requirement 7120.5 (NASA Space Flight Program and Project Management). All these ensure that the data centers managed by ESDIS are trustworthy from the point of view of efficient and effective operations as well as preservation of valuable data from NASA's missions. Additional factors contributing to this trust are an extensive set of internal and external reviews throughout the history of EOSDIS starting in the early 1990s. Many of these reviews have involved external groups of scientific and technological experts. Also, independent annual surveys of user satisfaction that measure and publish the American Customer Satisfaction Index (ACSI), where EOSDIS has scored consistently high marks since 2004, provide an additional measure of trustworthiness. In addition, through an effort initiated in 2012 at the request of NASA HQ, the ESDIS Project and 10 of 12 DAACs have been certified by the International Council for Science (ICSU) World Data System (WDS) and are members of the ICSUWDS. This presentation addresses questions such as pros and cons of the certification process, key outcomes and next steps regarding certification. Recently, the ICSUWDS and Data Seal of Approval (DSA) organizations merged their Core Trustworthy Data Repositories Requirements and require that members be recertified every three years. Given the rigor with which NASA manages the ESDIS Project and the DAACs, the recertification through WDSDSA, while involving some additional work, is a relatively simple process.

Certification↗

Single-Receiver GPS Phase Bias Resolution

Existing software has been modified to yield the benefits of integer fixed double-differenced GPS-phased ambiguities when processing data from a single GPS receiver with no access to any other GPS receiver data. When the double-differenced combination of phase biases can be fixed reliably, a significant improvement in solution accuracy is obtained. This innovation uses a large global set of GPS receivers (40 to 80 receivers) to solve for the GPS satellite orbits and clocks (along with any other parameters). In this process, integer ambiguities are fixed and information on the ambiguity constraints is saved. For each GPS transmitter/receiver pair, the process saves the arc start and stop times, the wide-lane average value for the arc, the standard deviation of the wide lane, and the dual-frequency phase bias after bias fixing for the arc. The second step of the process uses the orbit and clock information, the bias information from the global solution, and only data from the single receiver to resolve double-differenced phase combinations. It is called "resolved" instead of "fixed" because constraints are introduced into the problem with a finite data weight to better account for possible errors. A receiver in orbit has much shorter continuous passes of data than a receiver fixed to the Earth. The method has parameters to account for this. In particular, differences in drifting wide-lane values must be handled differently. The first step of the process is automated, using two JPL software sets, Longarc and Gipsy-Oasis. The resulting orbit/clock and bias information files are posted on anonymous ftp for use by any licensed Gipsy-Oasis user. The second step is implemented in the Gipsy-Oasis executable, gd2p.pl, which automates the entire process, including fetching the information from anonymous ftp

Bertiger, William I.↗

Verify MesoNAM Performance

The AMU conducted an objective analysis of the MesoNAM forecasts compared to observed values from sensors at specified KSC/CCAFS wind towers by calculating the following statistics to verify the performance of the model: 1) Bias (mean difference), 2) Standard deviation of Bias, 3) Root Mean Square Error (RMSE), and 4) Hypothesis test for Bias = O. The 45 WS LWOs use the MesoNAM to support launch weather operations. However, the actual performance of the model at KSC and CCAFS had not been measured objectively. The analysis compared the MesoNAM forecast winds, temperature and dew point to the observed values from the sensors on wind towers. The data were stratified by tower sensor, month and onshore/offshore wind direction based on the orientation of the coastline to each tower's location. The model's performance statistics were then calculated for each wind tower based on sensor height and model initialization time. The period of record for the data used in this task was based on the operational start of the current MesoNAM in mid-August 2006 and so the task began with the first full month of data, September 2006, through May 2010. The analysis of model performance indicated: a) The accuracy decreased as the forecast valid time from the model initialization increased, b) There was a diurnal signal in T with a cool bias during the late night and a warm bias during the afternoon, c) There was a diurnal signal in Td with a low bias during the afternoon and a high bias during the late night, and d) The model parameters at each vertical level most closely matched the observed parameters at heights closest to those vertical levels. The AMU developed a GUI that consists of a multi-level drop-down menu written in JavaScript embedded within the HTML code. This tool allows the LWO to easily and efficiently navigate among the charts and spreadsheet files containing the model performance statistics. The objective statistics give the LWOs knowledge of the model's strengths and weaknesses and the GUI allows quick access to the data which will result in improved forecasts for operations.

Bauman, William H., III↗

Arctic and Antarctic Sea Ice Concentrations from Multichannel Passive-Microwave Satellite Data Sets: October 1978-September 1995 User's Guide

Satellite multichannel passive-microwave sensors have provided global radiance measurements with which to map, monitor, and study the Arctic and Antarctic polar sea ice covers. The data span over 18 years (as of April 1997), starting with the launch of the Scanning Multichannel Microwave Radiometer (SMMR) on NASA's SeaSat A and Nimbus 7 in 1978 and continuing with the Defense Meteorological Satellite Program (DMSP) Special Sensor Microwave/Imager (SSMI) series beginning in 1987. It is anticipated that the DMSP SSMI series will continue into the 21st century. The SSMI series will be augmented by new, improved sensors to be flown on Japanese and U.S. space platforms. This User's Guide provides a description of a new sea ice concentration data set generated from observations made by three of these multichannel sensors. The data set includes gridded daily ice concentrations (every-other-day for the SMMR data) for both the north and south polar regions from October 26, 1978 through September 30, 1995, with the one exception of a 6-week data gap from December 3, 1987 through January 12, 1988. The data have been placed on two CD-ROMs that include a ReadMeCD file giving the technical details on the file format, file headers, north and south polar grids, ancillary data sets, and directory structure of the CD-ROM. The CD-ROMS will be distributed by the National Snow and Ice Data Center in Boulder, CO.

Sea ice concentration↗

Graphical User Interface Development for Representing Air Flow Patterns

In the Turbine Branch, scientists carry out experimental and computational work to advance the efficiency and diminish the noise production of jet engine turbines. One way to do this is by decreasing the heat that the turbine blades receive. Most of the experimental work is carried out by taking a single turbine blade and analyzing the air flow patterns around it, because this data indicates the sections of the turbine blade that are getting too hot. Since the cost of doing turbine blade air flow experiments is very high, researchers try to do computational work that fits the experimental data. The goal of computational fluid dynamics is for scientists to find a numerical way to predict the complex flow patterns around different turbine blades without physically having to perform tests or costly experiments. When visualizing flow patterns, scientists need a way to represent the flow conditions around a turbine blade. A researcher will assign specific zones that surround the turbine blade. In a two-dimensional view, the zones are usually quadrilaterals. The next step is to assign boundary conditions which define how the flow enters or exits one side of a zone. way of setting up computational zones and grids, visualizing flow patterns, and storing all the flow conditions in a file on the computer for future computation. Such a program is necessary because the only method for creating flow pattern graphs is by hand, which is tedious and time-consuming. By using a computer program to create the zones and grids, the graph would be faster to make and easier to edit. Basically, the user would run a program that is an editable graph. The user could click and drag with the mouse to form various zones and grids, then edit the locations of these grids, add flow and boundary conditions, and finally save the graph for future use and analysis. My goal this summer is to create a graphical user interface (GUI) that incorporates all of these elements. I am writing the program in Java, a language that is portable among platforms, because it can run on different operating systems such as Windows and Unix without having to be rewritten. I had no prior experience of programming in Java at the start of my internship; I am continuously learning as I create the program. I have written the part of the program that enables a user to draw several zones, edit them, and store their locations. The next phase of my project is to allow the user to click on the side of a zone and create a boundary condition for it. A previous intern wrote a program that allows the user to input boundary conditions. I can integrate the two programs to create a larger, more usable program. After that, I will develop a way for the user to save the graph for future reference. Another eventual goal is to make the GUI capable of creating three-dimensional zones as well. Researchers such as my mentor, Dr. David Ashpis, need a quick, user-friendly

Chaudhary, Nilika↗

Monitoring Airspace Complexity and Determining Contributing Factors

The national airspace has evolved over many years to accommodate increased traffic demand [1] while simultaneously maintaining one of the safest forms of transportation [2], [3]. One of the reasons for this success is the ability of the system and the operators to adapt and accommodate to situations that routinely disrupt optimal operations. These situations may include: adverse weather, delays, early arrivals, equipment outages, and other factors that are outside the operators ability to control. These factors can lead to states where automation is unable to properly handle these issues and therefore air traffic controllers and pilots have to intervene, ultimately increasing communication between operators resulting in higher workload. As controller workload increases to handle sub-optimal operating conditions this can be viewed as an increase in complexity. The reasoning for this is because humans are now required to make tactical decisions in response to external factors, resulting in a departure from the strategic plan where operations would be more efficiently managed. Human operators control airspace complexity under rigid regulations that are constantly changing. The airspace is divided into sectors and the number of aircraft assigned to each controller is limited for safe handling. There has been past work that devised airspace complexity metrics in commercial aviation and related these metrics to controller workload (e.g., [4],[5]). The upper bounds on the system load are pre-determined. Such bounds on complexity make for a safe system, but the system cannot scale and adapt to autonomous, dense, and heterogeneous traffic, including the many types of Unmanned Aerial Vehicles (UAVs) envisioned to be added to the operations. We hypothesize that, as traffic density and heterogeneity grow, and other key metrics change, there will be phase transitions at which the way traffic should be managed changes significantly [6]. We offer a method for in-time detection of contributing factors that lead to phase transitions, characterized by increased complexity. To the best of our knowledge, there is no tool similar to our proposed effort that identifies such contributing factors or precursor patterns. To define the scope we are proposing to measure complexity from the viewpoint of the Terminal Radar Approach Control Facilities (TRACON) controller’s perspective. In particular we are analyzing arrivals into KSFO. With safety as the top concern for airspace operators, it is important to recognize that as density and heterogeneity grow, the focus of the system will change. Times of the day when the airspace has low density and heterogeneity, the flights will follow more efficient paths where the aircraft move on established routes that are more or less directly to the destination. However, when density and heterogeneity increases, the system will begin changing focus to avoiding conflicts and collisions and route the flights in a more flexible way. Higher flexibility requires more communication and coordination between controllers and pilots which the current automation is unable to handle. This paper proposes a novel approach that monitors airspace complexity at multiple scales, uses a Machine Learning-based tool that predicts when operations will transition to a regime of greater complexity, and identifies actions that can reduce the complexity while still maintaining efficient and safe operations. We demonstrate our proposed approach using data from multiple complementary sources. This includes, but is not limited to: historical aircraft surveillance data from NASA’s Sherlock Data Warehouse [7], METAR weather data, and airport configuration data from Aviation System Performance Metrics (ASPM). The surveillance data flight paths are sampled at a variable sample rate — increasing as the aircraft approaches the airport. This is due to how Sherlock manages flight track stitching between different radar facilities which have different sampling rates. The weather and performance data are logged at defined intervals throughout the day at a courser refresh rate. In addition to the logged data and metrics, we leverage pre-defined Standard Terminal Arrival Routes (STARs) procedures to characterize the path of each flight. Each flight files for one of these routes in the flight plan well before entering the terminal airspace, and approximately follows the route until it leaves the STAR, typically on the final fix of a runway transition. However, most flights do not always fly the full STAR procedure to completion [8], but the majority do adhere to the fixes within the common route of the procedure. Our approach leverages fixes in the common route of each of the STARs to build a reference path to the airport. This allows us to characterize the flight paths in what we are defining as the “maneuvering area” (the airspace between the STAR and before the flight is lined up on the runway’s final approach) to determine how off nominal the flights are to calculate its complexity score. Determining airspace complexity is a concept that does not have a concrete answer. In designing this metric, we consider what increases the workload for the air traffic controllers. Consequently more specialized vectoring maneuvers results in higher workload. Accordingly, we start with a theory: each flight has a direct path it takes from the STAR’s common route to the final approach’s outer marker fix for the flight’s landing runway. It is important to note that the direct path is only used as a reference. If the majority of the flights have a large consistent offset as compared to other routes it does not necessarily mean that those flights have higher complexity. We are merely building a distribution based on this direct path for that particular STAR and runway pair to determine the normal mode of operations for that route. Flights that are in the upper tail of these distributions will result in higher complexity scores and flights that fly in the median will represent the normal mode of operations and therefore will have lower complexity scores. Since flights following each STAR route take different paths to the airport, we have a different distribution for each STAR route and therefore can model these distributions to compute a complexity score from their respective normalized distributions. To evaluate the effectiveness of our proposed airspace complexity metric we will compare against an established approach based on trajectory clustering [9]. This unsupervised learning technique consists of the following steps: (1) identify the general maneuvering areas (waypoints) by performing $\kappa$-means or DBSCAN clustering on locations where aircraft frequently turn based on the surveillance radar track data, (2) map flight trajectories onto sequences of waypoints, and (3) cluster the sequences based on their common subsequences. From a high-level perspective, this baseline model learns nominal operations in the airspace through the sequence of waypoints that are representative of where aircraft change direction and defines deviations from the nominal operations as “complex.” Therefore, more deviations from the nominal operations correspond to higher complexity values. For our validation, we re-implemented this technique and tune model hyper-parameters to correctly detect waypoints for the arrival traffic into the San Francisco bay area. We will compute the complexity measure over a one-year period using our proposed technique as well as the baseline. Our validation will be based on each technique’s ability to detect a set of undesirable outcomes (e.g., go-arounds, holding patterns, average time in the airspace, etc.). Since our current complexity metric is derived from the offset from the direct reference path, it’s important to understand what causes these offsets. In many of the flights with high offset distance, flights performing holding patterns and S turns can be observed. These maneuvering tactics are utilized to add distance between the aircraft and the destination runway to prevent multiple flights from having conflicting arrival times. In order to predict a rise in complexity (or the precursor to complexity), it’s necessary to be able to identify these potential conflicts (which in turn, result in higher offsets). To do this, we define a “representative flight” for each STAR route and runway pair. This flight is approximately the path the flight would take if there was a clear path with no other flights in the airspace — including the time remaining to the airport. We first identify the flights for a given STAR runway pair using the offset to the reference path distributions that fall between the 44-55 percentiles. This yields the flights that conform to the most normal mode of operation. Each of these flights is partitioned based on the percent complete from the entry point into the maneuvering areas from 0\% – 100\% complete. Then for each percent “bin”, we take the median value of the flight’s latitude/longitude coordinates, airspeed, and (non causal) time remaining to the airport to construct a lookup table for each percent complete bin on a given route. As a flight enters the maneuvering area, we can find the estimated arrival time of a flight to the airport by finding the closest point to the representative path’s percent complete bin (relative to the flight’s current position at any snapshot in the airspace) and therefore retrieve the corresponding remaining time left on the “representative path”. We assume that the flight will follow the representative path to completion when deriving these estimates. We can then compare these estimated arrival times against other flights for the same snapshot in time to identify potential conflicts. If more flights are estimated to arrive within a tolerance window than there are runways available, then we have a potential conflict. We can use this derived measure along with other factors expected to add disruption to the operation such as weather and runway configuration changes as an input to machine learning tools to detect precursors that increases in our complexity measure. This novel method will assist in uncovering insights into the contributing factors that lead to increased complexity that may allow for in-time responses to avoid reaching a high complexity state in the airspace.

complexity↗

The New Cloud Absorption Radiometer (CAR) Software: One Model for NASA Remote Sensing Virtual Instruments

The Cloud Absorption Radiometer (CAR) instrument has been the most frequently used airborne instrument built in-house at NASA Goddard Space Flight Center, having flown scientific research missions on-board various aircraft to many locations in the United States, Azores, Brazil, and Kuwait since 1983. The CAR instrument is capable of measuring scattered light by clouds in fourteen spectral bands in UV, visible and near-infrared region. This document describes the control, data acquisition, display, and file storage software for the new version of CAR. This software completely replaces the prior CAR Data System and Control Panel with a compact and robust virtual instrument computer interface. Additionally, the instrument is now usable for the first time for taking data in an off-aircraft mode. The new instrument is controlled via a LabVIEW v5. 1.1-developed software interface that utilizes, (1) serial port writes to write commands to the controller module of the instrument, and (2) serial port reads to acquire data from the controller module of the instrument. Step-by-step operational procedures are provided in this document. A suite of other software programs has been developed to complement the actual CAR virtual instrument. These programs include: (1) a simulator mode that allows pretesting of new features that might be added in the future, as well as demonstrations to CAR customers, and development at times when the instrument/hardware is off-location, and (2) a post-experiment data viewer that can be used to view all segments of individual data cycles and to locate positions where 'start' and stop' byte sequences were incorrectly formulated by the instrument controller. The CAR software described here is expected to be the basis for CAR operation for many missions and many years to come.

Roth, Don J.↗

STK Integrated Message Production List Editor (SIMPLE) for CEO Operations

Late in fiscal year 2011, the Crew Earth Observations (CEO) team was tasked to upgrade and replace its mission planning and mission operations software systems, which were developed in the Space Shuttle era of the 1980s and 1990s. The impetuses for this change were the planned transition of all workstations to the Windows 7 64-bit operating system and the desire for more efficient and effective use of Satellite Tool Kit (STK) software required for reliable International Space Station (ISS) Earth location tracking. An additional requirement of this new system was the use of the same SQL database of CEO science sites from the SMMS, which was also being developed. STK Integrated Message Production List Editor (SIMPLE) is the essential, all-in-one tool now used by CEO staff to perform daily ISS mission planning to meet its requirement to acquire astronaut photography of specific sites on Earth. The sites are part of a managed, long-term database that has been defined and developed for scientific, educational, and public interest. SIMPLE's end product is a set of basic time and location data computed for an operator-selected set of targets that the ISS crew will be asked to photograph (photography is typically planned 12 to 36 hours out). The CEO operator uses SIMPLE to (a) specify a payload operations planning period; (b) acquire and validate the best available ephemeris data (vectors) for the ISS during the planning period; (c) ingest and display mission-specific site information from the CEO database; (d) identify and display potential current dynamic event targets as map features; (e) compute and display time and location information for each target; (f) screen and select targets based on known crew availability constraints, obliquity constraints, and real-time evaluated constraints to target visibility due to illumination (sun elevation) and atmospheric conditions (weather); and finally (g) incorporate basic, computed time and location information for each selected target into the daily CEO Target List product (message) for submission to ISS payload planning and integration teams for their review and approval prior to uplink. SIMPLE requires and uses the following resources: an ISS mission planning period Greenwich Mean Time start date/time and end date/time), the best available ISS mission ephemeris data (vectors) for that planning period, the STK software package configured for the ISS, and an ISS mission-specific subset of the CEO sites database. The primary advantages realized by the development and implementation of SIMPLE into the CEO payload operations support activity are a smooth transition to the Windows 7 operating system upon scheduled workstation refresh; streamlining of the input and verification of the current ISS ephemeris (vector data); seamless incorporation of selected contents of the SQL database of science sites; the ability to tag and display potential dynamic event opportunities on orbit track maps; simplification of the display and selection of encountered sites based on crew availability, illumination, obliquity, and weather constraints; the incorporation of high-quality mapping of the Earth with various satellite-based datasets for use in describing targets; and the ability to encapsulate and export the essential selected target elements in XML format for use by onboard Earth-location systems, such as Worldmap. SIMPLE is a carefully designed and crafted in-house software package that includes detailed help files for the user and meticulous internal documentation for future modifications. It was delivered in February 2012 for test and evaluation. Following acceptance, it was implemented for CEO mission operations support in May 2012.

Trenchard, Mike↗