Search NASA⌕ Search

SEARCH · Search NASA

Results for “base editing”

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 217 records · Page 12

Collaborative Planning of Robotic Exploration

The Science Activity Planner (SAP) software system includes an uplink-planning component, which enables collaborative planning of activities to be undertaken by an exploratory robot on a remote planet or on Earth. Included in the uplink-planning component is the SAP-Uplink Browser, which enables users to load multiple spacecraft activity plans into a single window, compare them, and merge them. The uplink-planning component includes a subcomponent that implements the Rover Markup Language Activity Planning format (RML-AP), based on the Extensible Markup Language (XML) format that enables the representation, within a single document, of planned spacecraft and robotic activities together with the scientific reasons for the activities. Each such document is highly parseable and can be validated easily. Another subcomponent of the uplink-planning component is the Activity Dictionary Markup Language (ADML), which eliminates the need for two mission activity dictionaries - one in a human-readable format and one in a machine-readable format. Style sheets that have been developed along with the ADML format enable users to edit one dictionary in a user-friendly environment without compromising

Norris, Jeffrey↗

Playbook for UAS: UX of Goal-Oriented Planning & Execution

We are evaluating Playbook for CASAS (Connected Autonomous Smart Aerospace Systems), a tool designed to aid first responders in disaster relief efforts. We are adapting an existing tool, Playbook, to support a future unmanned aircraft system (UAS) swarm demonstration. Playbook for CASAS will be used to plan, edit, and monitor simulated UAS swarms, and we are interested in evaluating the user experience of this prototype as well as developing recommendations for future UAS interfaces. Allocation of roles and responsibilities between human-automation systems is key to promoting productive cooperation between users and automation. Future interfaces, however, must allow for adaptive management of the swarm not a constant split in human-automation control. Our early research indicates that when a single pilot is controlling swarms of robotic agents, such as UAS or ground rovers, operators require a higher level, goal-based interface with usability at its core. Along with that high-level control, users can leverage sensors within the swarm to be notified when lower level actions must be taken by the pilot. First responders working in disaster relief efforts require a high level of situational awareness (SA) and precise control at key moments within a mission. This balance in operator workload paired with SA can lead to improved safety and mission outcomes. Our research below outlines leverage points as well as the balance between human involvement and autonomy in UAS interfaces.

UAS↗

The anisotropy in the xosmic microwave background at degree angular scales

We detect anisotropy in the cosmic microwave background (CMB) at degree angular scales and confirm a previous detection reported by Wollack et al. (1993). The root-mean-squared amplitude of the fluctuations is 44(sup+13)(sub -7)microK. This may be expressed as the square root of the angular power spectrum in a band of multiples between l(sub eff)=69(sup +29)(sub -22). We find delta T(sub l) = square root of (l(2l+1) expected value of ((absolute value of (a(sup m)(sub L)))(exp 2))/(4xpi))= 42(sup +12)(sub -7). The measured spectral index of the fluctuations is consistent with zero, the value expected for the CMB. The spectral index corresponding to Galactic free-free emission, the most likely foreground contaminant, is rejected at approximately 3 sigma. The analysis is based on three independent data sets. The first, taken in 1993, spans the 26-36 GHz frequency range with three frequency bands; the second was taken with the same radiometer as the first but during an independent observing campaign in 1994; and the third, also taken in 1994, spans the 36-46 GHz range in three bands. For each telescope position and radiometer channel, the drifts in the instrument offset are less than or equal to 4 microK/day averaged over a period of 1 month. The dependence of the inferred anisotropy on the calibration and data editing is addressed.

Netterfield, C. B.↗

Atmospheric Correction Inter-comparison eXercise, ACIX-II Land: An Assessment of Amospheric Correction Processors for Landsat 8 and Sentinel-2 Over Land

The correction of the atmospheric effects on optical satellite images is essential for quantitative and multi-temporal remote sensing applications. In order to study the performance of the state-of-the-art methods in an integrated way, a voluntary and open-access benchmark Atmospheric Correction Inter-comparison eXercise (ACIX) was initiated in 2016 in the frame of Committee on Earth Observation Satellites (CEOS) Working Group on Calibration & Validation (WGCV). The first exercise was extended in a second edition wherein twelve atmospheric correction (AC) processors, a substantially larger testing dataset and additional validation metrics were involved. The sites for the inter-comparison analysis were defined by investigating the full catalogue of the Aerosol Robotic Network (AERONET) sites for coincident measurements with satellites' overpass. Although there were more than one hundred sites for Copernicus Sentinel-2 and Landsat 8 acquisitions, the analysis presented in this paper concerns only the common matchups amongst all processors, reducing the number to 79 and 62 sites respectively. Aerosol Optical Depth (AOD) and Water Vapour (WV) retrievals were consequently validated based on the available AERONET observations. The processors mostly succeeded in retrieving AOD for relatively light to medium aerosol loading (AOD < 0.2) with uncertainties <0.08, while the overall uncertainty values were typically 0.23 ± 0.15. Better performances were observed for WV retrievals with >90% of the results falling within the suggested empirical specifications and with the Root Mean Square Error (RMSE) being mostly <0.25 g/cm2. Regarding Surface Reflectance (SR) validation two main approaches were followed. For the first one, a simulated SR reference dataset was computed over all of the test sites by using the 6SV (Second Simulation of the Satellite Signal in the Solar Spectrum vector code) full radiative transfer modelling (RTM) and AERONET measurements for the required aerosol variables and water vapour content. The performance assessment demonstrated that the retrievals were not biased for most of the bands. The uncertainties ranged from approximately 0.003 to 0.01 (excluding B01) for the best performing processors in both sensors' analyses. For the second one, measurements from the radiometric calibration network RadCalNet over La Crau (France) and Gobabeb (Namibia) were involved in the validation. The performance of the processors was in general consistent across all bands for both sensors and with low standard deviations (<0.04) between on-site and estimated surface reflectance. Overall, our study provides a good insight of AC algorithms' performance to developers and users, pointing out similarities and differences for AOD, WV and SR retrievals. Such validation though still lacks of ground-based measurements of known uncertainty to better assess and characterize the uncertainties in SR retrievals.

Atmospheric correction↗

Using Cloud-to-Ground Lightning Climatologies to Initialize Gridded Lightning Threat Forecasts for East Central Florida

Each morning, the forecasters at the National Weather Service in Melbourn, FL (NWS MLB) produce an experimental cloud-to-ground (CG) lightning threat index map for their county warning area (CWA) that is posted to their web site (http://www.srh.weather.gov/mlb/ghwo/lightning.shtml) . Given the hazardous nature of lightning in central Florida, especially during the warm season months of May-September, these maps help users factor the threat of lightning, relative to their location, into their daily plans. The maps are color-coded in five levels from Very Low to Extreme, with threat level definitions based on the probability of lightning occurrence and the expected amount of CG activity. On a day in which thunderstorms are expected, there are typically two or more threat levels depicted spatially across the CWA. The locations of relative lightning threat maxima and minima often depend on the position and orientation of the low-level ridge axis, forecast propagation and interaction of sea/lake/outflow boundaries, expected evolution of moisture and stability fields, and other factors that can influence the spatial distribution of thunderstorms over the CWA. The lightning threat index maps are issued for the 24-hour period beginning at 1200 UTC (0700 AM EST) each day with a grid resolution of 5 km x 5 km. Product preparation is performed on the AWIPS Graphical Forecast Editor (GFE), which is the standard NWS platform for graphical editing. Currently, the forecasters create each map manually, starting with a blank map. To improve efficiency of the forecast process, NWS MLB requested that the Applied Meteorology Unit (AMU) create gridded warm season lightning climatologies that could be used as first-guess inputs to initialize lightning threat index maps. The gridded values requested included CG strike densities and frequency of occurrence stratified by synoptic-scale flow regime. The intent is to increase consistency between forecasters while enabling them to focus on the mesoscale detail of the forecast, ultimately benefiting the end-users of the product. Several studies took place at the Florida State University (FSU) and NWS Tallahassee (TAE) for which they created daily flow regimes using Florida 1200 UTC synoptic soundings and CG strike densities from National Lightning Detection Network (NLDN) data. The densities were created on a 2.5 km x 2.5 km grid for every hour of every day during the warm seasons in the years 1989-2004. The grids encompass an area that includes the entire state of Florida and adjacent Atlantic and Gulf of Mexico waters. Personnel at the two organizations provided this data and supporting software for the work performed by the AMU. The densities were first stratified by flow regime, then by time in 1-, 3-, 6-, 12-, and 24-hour increments while maintaining the 2.5 km x 2.5 km grid resolution. A CG frequency of occurrence was calculated for each stratification and grid box by counting the number of days with lightning and dividing by the total number of days in the data set. New CG strike densities were calculated for each stratification and grid box by summing the strike number values over all warm seasons, then normalized by dividing the summed values by the number of lightning days. This makes the densities conditional on whether lightning occurred. The frequency climatology values will be used by forecasters as proxy inputs for lightning prObability, while the density climatology values will be used for CG amount. In addition to the benefits outlined above, these climatologies will provide improved temporal and spatial resolution, expansion of the lightning threat area to include adjacent coastal waters, and potential to extend the forecast to include the day-2 period. This presentation will describe the lightning threat index map, discuss the work done to create the maps initialized with climatological guidance, and show examples of the climatological CG lightning densities and frequencies of occurren based on flow regime.

Lambert, Winnie↗

Software Assists in Extensive Environmental Auditing

The Base Enivronmental Management System (BEMS) is a Web-based application program for managing and tracking audits by the Environmental Office of Stennis Space Center in conformity with standard 14001 of the International Organization for Standardization (ISO 14001). (This standard specifies requirements for an environmental-management system.) BEMS saves time by partly automating what were previously manual processes for creating audit checklists; recording and tracking audit results; issuing, tracking, and implementing corrective-action requests (CARs); tracking continuous improvements (CIs); and tracking audit results and statistics. BEMS consists on an administration module and an auditor module. As its name suggests, the administration module is used to administer the audit. It helps administrators to edit the list of audit questions; edit the list of audit locations; assign manditory questions to locations; track, approve, and edit CARs; and edit completed audits. The auditor module is used by auditors to perform audits and record audit results: It helps the auditors to create audit checklists, complete audits, view completed audits, create CARs, record and acknowledge CIs, and generate reports from audit results.

Callac, Christopher↗

Software Assists in Extensive Environmental Auditing

The Base Environmental Management System (BEMS) is a Web-based application program for managing and tracking audits by the Environmental Office of Stennis Space Center in conformity with standard 14001 of the International Organization for Standardization (ISO 14001). (This standard specifies requirements for an environmental-management system.) BEMS saves time by partly automating what were previously manual processes for creating audit checklists; recording and tracking audit results; issuing, tracking, and implementing corrective-action requests (CARs); tracking continuous improvements (CIs); and tracking audit results and statistics. BEMS consists of an administration module and an auditor module. As its name suggests, the administration module is used to administer the audit. It helps administrators to edit the list of audit questions; edit the list of audit locations; assign mandatory questions to locations; track, approve, and edit CARs; and edit completed audits. The auditor module is used by auditors to perform audits and record audit results: it helps the auditors to create audit checklists, complete audits, view completed audits, create CARs, record and acknowledge CIs, and generate reports from audit results.

Callac, Christopher↗

Software Assists in Extensive Environmental Auditing

The Base Environmental Management System (BEMS) is a Web-based application program for managing and tracking audits by the Environmental Office of Stennis Space Center in conformity with standard 14001 of the International Organization for Standardization (ISO 14001). (This standard specifies requirements for an environmental-management system.) BEMS saves time by partly automating what were previously manual processes for creating audit checklists; recording and tracking audit results; issuing, tracking, and implementing corrective-action requests (CARs); tracking continuous improvements (CIs); and tracking audit results and statistics. BEMS consists of an administration module and an auditor module. As its name suggests, the administration module is used to administer the audit. It helps administrators to edit the list of audit questions; edit the list of audit locations; assign mandatory questions to locations; track, approve, and edit CARs; and edit completed audits. The auditor module is used by auditors to perform audits and record audit results: it helps the auditors to create audit checklists, complete audits, view completed audits, create CARs, record and acknowledge CIs, and generate reports from audit results.

Callac, Christopher↗

GMI-IPS: Python Processing Software for Aircraft Campaigns

NASA's Atmospheric Tomography Mission (ATom) seeks to understand the impact of anthropogenic air pollution on gases in the Earth's atmosphere. Four flight campaigns are being deployed on a seasonal basis to establish a continuous global-scale data set intended to improve the representation of chemically reactive gases in global atmospheric chemistry models. The Global Modeling Initiative (GMI), is creating chemical transport simulations on a global scale for each of the ATom flight campaigns. To meet the computational demands required to translate the GMI simulation data to grids associated with the flights from the ATom campaigns, the GMI ICARTT Processing Software (GMI-IPS) has been developed and is providing key functionality for data processing and analysis in this ongoing effort. The GMI-IPS is written in Python and provides computational kernels for data interpolation and visualization tasks on GMI simulation data. A key feature of the GMI-IPS, is its ability to read ICARTT files, a text-based file format for airborne instrument data, and extract the required flight information that defines regional and temporal grid parameters associated with an ATom flight. Perhaps most importantly, the GMI-IPS creates ICARTT files containing GMI simulated data, which are used in collaboration with ATom instrument teams and other modeling groups. The initial main task of the GMI-IPS is to interpolate GMI model data to the finer temporal resolution (1-10 seconds) of a given flight. The model data includes basic fields such as temperature and pressure, but the main focus of this effort is to provide species concentrations of chemical gases for ATom flights. The software, which uses parallel computation techniques for data intensive tasks, linearly interpolates each of the model fields to the time resolution of the flight. The temporally interpolated data is then saved to disk, and is used to create additional derived quantities. In order to translate the GMI model data to the spatial grid of the flight path as defined by the pressure, latitude, and longitude points at each flight time record, a weighted average is then calculated from the nearest neighbors in two dimensions (latitude, longitude). Using SciPya's Regular Grid Interpolator, interpolation functions are generated for the GMI model grid and the calculated weighted averages. The flight path points are then extracted from the ATom ICARTT instrument file, and are sent to the multi-dimensional interpolating functions to generate GMI field quantities along the spatial path of the flight. The interpolated field quantities are then written to a ICARTT data file, which is stored for further manipulation. The GMI-IPS is aware of a generic ATom ICARTT header format, containing basic information for all flight campaigns. The GMI-IPS includes logic to edit metadata for the derived field quantities, as well as modify the generic header data such as processing dates and associated instrument files. The ICARTT interpolated data is then appended to the modified header data, and the ICARTT processing is complete for the given flight and ready for collaboration. The output ICARTT data adheres to the ICARTT file format standards V1.1. The visualization component of the GMI-IPS uses Matplotlib extensively and has several functions ranging in complexity. First, it creates a model background curtain for the flight (time versus model eta levels) with the interpolated flight data superimposed on the curtain. Secondly, it creates a time-series plot of the interpolated flight data. Lastly, the visualization component creates averaged 2D model slices (longitude versus latitude) with overlaid flight track circles at key pressure levels. The GMI-IPS consists of a handful of classes and supporting functionality that have been generalized to be compatible with any ICARTT file that adheres to the base class definition. The base class represents a generic ICARTT entry, only defining a single time entry and 3D spatial positioning parameters. Other classes inherit from this base class; several classes for input ICARTT instrument files, which contain the necessary flight positioning information as a basis for data processing, as well as other classes for output ICARTT files, which contain the interpolated model data. Utility classes provide functionality for routine procedures such as: comparing field names among ICARTT files, reading ICARTT entries from a data file and storing them in data structures, and returning a reduced spatial grid based on a collection of ICARTT entries. Although the GMI-IPS is compatible with GMI model data, it can be adapted with reasonable effort for any simulation that creates Hierarchical Data Format (HDF) files. The same can be said of its adaptability to ICARTT files outside of the context of the ATom mission. The GMI-IPS contains just under 30,000 lines of code, eight classes, and a dozen drivers and utility programs. It is maintained with GIT source code management and has been used to deliver processed GMI model data for the ATom campaigns that have taken place to date.

Damon, M. R.↗

The Fleet Application for Scheduling and Tracking (FAST) Management Website

The FAST application was designed to replace the paper and pen method of checking out and checking in GSA Vehicles at KSC. By innovating from a paper and pen based checkout system to a fully digital one, not only the resources wasted by printing the checkout forms have been reduced, but it also reduces significantly the time that users and fleet managers need to interact with the system as well as improving the record accuracy for each vehicle. The vehicle information is pulled from a centralized database server in the SPSDL. In an attempt to add a new feature to the FAST application, the author of this report (alongside the FAST developers) has been designing and developing the FAST Management Website. The GSA fleet managers had to rely on the FAST developers in order to add new vehicles, edit vehicles and previous transactions, or for generating vehicles reports. By providing an easy-to-use FAST Management Website portal, the GSA fleet managers are now able to easily move vehicles, edit records, and print reports.

Object-Oriented Programming↗

Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners (Second Edition)

Probabilistic Risk Assessment (PRA) is a comprehensive, structured, and logical analysis method aimed at identifying and assessing risks in complex technological systems for the purpose of cost-effectively improving their safety and performance. NASA's objective is to better understand and effectively manage risk, and thus more effectively ensure mission and programmatic success, and to achieve and maintain high safety standards at NASA. NASA intends to use risk assessment in its programs and projects to support optimal management decision making for the improvement of safety and program performance. In addition to using quantitative/probabilistic risk assessment to improve safety and enhance the safety decision process, NASA has incorporated quantitative risk assessment into its system safety assessment process, which until now has relied primarily on a qualitative representation of risk. Also, NASA has recently adopted the Risk-Informed Decision Making (RIDM) process [1-1] as a valuable addition to supplement existing deterministic and experience-based engineering methods and tools. Over the years, NASA has been a leader in most of the technologies it has employed in its programs. One would think that PRA should be no exception. In fact, it would be natural for NASA to be a leader in PRA because, as a technology pioneer, NASA uses risk assessment and management implicitly or explicitly on a daily basis. NASA has probabilistic safety requirements (thresholds and goals) for crew transportation system missions to the International Space Station (ISS) [1-2]. NASA intends to have probabilistic requirements for any new human spaceflight transportation system acquisition. Methods to perform risk and reliability assessment in the early 1960s originated in U.S. aerospace and missile programs. Fault tree analysis (FTA) is an example. It would have been a reasonable extrapolation to expect that NASA would also become the world leader in the application of PRA. That was, however, not to happen. Early in the Apollo program, estimates of the probability for a successful roundtrip human mission to the moon yielded disappointingly low (and suspect) values and NASA became discouraged from further performing quantitative risk analyses until some two decades later when the methods were more refined, rigorous, and repeatable. Instead, NASA decided to rely primarily on the Hazard Analysis (HA) and Failure Modes and Effects Analysis (FMEA) methods for system safety assessment.

Stamatelatos,Michael↗

Editing ERTS-1 data to exclude land aids cluster analysis of water targets

The author has identified the following significant results. It has been determined that an increase in the number of spectrally distinct coastal water types is achieved when data values over the adjacent land areas are excluded from the processing routine. This finding resulted from an automatic clustering analysis of ERTS-1 system corrected MSS scene 1002-18134 of 25 July 1972 over Monterey Bay, California. When the entire study area data set was submitted to the clustering only two distinct water classes were extracted. However, when the land area data points were removed from the data set and resubmitted to the clustering routine, four distinct groupings of water features were identified. Additionally, unlike the previous separation, the four types could be correlated to features observable in the associated ERTS-1 imagery. This exercise demonstrates that by proper selection of data submitted to the processing routine, based upon the specific application of study, additional information may be extracted from the ERTS-1 MSS data.

Erb, R. B.↗

GRASP/Ada 95: Reverse Engineering Tools for Ada

The GRASP/Ada project (Graphical Representations of Algorithms, Structures, and Processes for Ada) has successfully created and prototyped an algorithmic level graphical representation for Ada software, the Control Structure Diagram (CSD), and a new visualization for a fine-grained complexity metric called the Complexity Profile Graph (CPG). By synchronizing the CSD and the CPG, the CSD view of control structure, nesting, and source code is directly linked to the corresponding visualization of statement level complexity in the CPG. GRASP has been integrated with GNAT, the GNU Ada 95 Translator to provide a comprehensive graphical user interface and development environment for Ada 95. The user may view, edit, print, and compile source code as a CSD with no discernible addition to storage or computational overhead. The primary impetus for creation of the CSD was to improve the comprehension efficiency of Ada software and, as a result, improve reliability and reduce costs. The emphasis has been on the automatic generation of the CSD from Ada 95 source code to support reverse engineering and maintenance. The CSD has the potential to replace traditional prettyprinted Ada source code. The current update has focused on the design and implementation of a new Motif compliant user interface, and a new CSD generator consisting of a tagger and renderer. The Complexity Profile Graph (CPG) is based on a set of functions that describes the context, content, and the scaling for complexity on a statement by statement basis. When combined graphicafly, the result is a composite profile of complexity for the program unit. Ongoing research includes the development and refinement of the associated functions, and the development of the CPG generator prototype. The current Version 5.0 prototype provides the capability for the user to generate CSDs and CPGs from Ada 95 source code in a reverse engineering as well as forward engineering mode with a level of flexibility suitable for practical application. This report provides an overview of the GRASP/Ada project with an emphasis on the current update.

Cross, James H., II↗

The Conference Proceedings of the 1998 Air Transport Research Group (ATRG) of the WCTR Society

The Air Transport Research Group of the WCTR Society was formally launched as a special interest group at the 7h Triennial WCTR in Sydney, Australia in 1995. Since then, our membership base has expanded rapidly, and now includes over 400 active transportation researchers, policy-makers, industry executives, major corporations and research institutes from 28 countries. It became a tradition that the ATRG would hold an international conference at least once a year. In 1998, the ATRG organized a consecutive stream of 14 aviation sessions at the 8th Triennial WCTR Conference (July 12-17: Antwerp). Again, on 19-21 July, 1998, the ATRG Symposium was organized and executed every successfully by Dr. Aisling Reynolds-Feighan of the University College of Dublin. The Aviation Institute at the University of Nebraska at Omaha has published the Proceedings of the 1998 ATRG Dublin Symposium (being co-edited by Dr. Aisling Reynolds-Feighan and Professor Brent Bowen), and the Proceedings of the 1998 WCTR- ATRG Conference (being co-edited by Professors Tae H. Oum and Brent Bowen).

Bowen, Brent D.↗

The Symposium Proceedings of the 1998 Air Transport Research Group (ATRG)

The Air Transport Research Group of the World Conference on Transportation Research (WCTR) Society was formally launched as a special interest group at the 7th Triennial WCTR in Sydney, Australia in 1995. Since then, our membership base has expanded rapidly, and now includes over 400 active transportation researchers, policy-makers, industry executives, major corporations and research institutes from 28 countries. It became a tradition that the ATRG would hold an international conference at least once a year. In 1998, the ATRG organized a consecutive stream of 14 aviation sessions at the 8th Triennial WCTR Conference (July 12-17: Antwerp). Again, on 19-21 July, 1998, the ATRG Symposium was organized and executed very successfully by Dr. Aisling Reynolds-Feighan of the University College of Dublin. The Aviation Institute at the University of Nebraska at Omaha has published the Proceedings of the 1998 ATRG Dublin Symposium (being co-edited by Dr. Aisling Reynolds-Feighan and Professor Brent Bowen), and the Proceedings of the 1998 WCTR-ATRG Conference (being co-edited by Professors Tae H. Oum and Brent Bowen).

Reynolds-Feighan, Aisling↗

Tethers in Space Handbook

A new edition of the Tethers in Space Handbook was needed after the last edition published in 1989. Tether-related activities have been quite busy in the 90's. We have had the flights of TSSI and TSSI-R, SEDS-1 and -2, PMG, TIPS and OEDIPUS. In less than three years there have been one international Conference on Tethers in Space, held in Washington DC, and three workshops, held at ESA/Estec in the Netherlands, at ISAS in Japan and at the University of Michigan, Ann Harbor. The community has grown and we finally have real flight data to compare our models with. The life of spaceborne tethers has not been always easy and we got our dose of setbacks, but we feel pretty optimistic for the future. We are just stepping out of the pioneering stage to start to use tethers for space science and technological applications. As we are writing this handbook TiPs, a NRL tether project is flying above our heads. There is no emphasis in affirming that as of today spacebome tethers are a reality and their potential is far from being fully appreciated. Consequently, a large amount of new information had to be incorporated into this new edition. The general structure of the handbook has been left mostly unchanged. The past editors have set a style which we have not felt needed change. The section on the flights has been enriched with information on the scientific results. The categories of the applications have not been modified, and in some cases we have mentioned the existence of related flight data. We felt that the section contributed by Joe Carroll, called Tether Data, should be maintained as it was, being a "classic" and still very accurate and not at all obsolete. We have introduced a new chapter entitled Space Science and Tethers since flight experience has shown that tethers can complement other space-based investigations. The bibliography has been updated. Due to the great production in the last few years %e had to restrict our search to works published in refereed journal. The production, however, is much more extensive. In addition, we have included the summary of the papers presented at the last International Conference which was a forum for first-hand information on all the flights.

Cosmo, M. L.↗

Probabilistic Assessment of Tunguska-Scale Asteroid Impacts

The Tunguska meteor airburst that felled trees across >2000 sq km of Siberian forest in 1908 has been extensively studied and modeled in attempts to deduce its size, properties, and impact characteristics. However, most of the existing modeling and simulation studies have investigated a small subset of cases based on assumptions of representative densities, velocities, or other properties. In this study, we use the Probabilistic Asteroid Impact Risk (PAIR) model to assess 50 million Tunguska-scale asteroid impacts, covering a full range of potential impactor properties. The impact cases are sampled from probabilistic distributions representing our current knowledge of asteroid properties, entry trajectories, and size frequencies, and the entry, airburst, and resulting ground damage are modeled for each case. The results provide a broader characterization of the range and relative likelihood of asteroid properties that could yield Tunguska-scale impacts. The full results of this study and a companion study on impact frequencies are pending publication in an upcoming Tunguska special edition of Icarus [1,2].

Wheeler, Lorien↗

Data processing system and interfacing elements time base analysis

The processing of time in the Orbiter System Services software and the associated facilities provided to the user community are described. The descriptions are directed toward showing the functional intent of the design rather than the actual implementation. Simplified flow diagrams are included. Based upon detailed analysis of a preliminary review copy of the Approach and Landing Test (ALT) System Software Detailed Design Specification and the Program Listings for Version 17 Prime, the processing of time has the potential for error free operations. The processing of time is not expected to change between ALT and the Operational Flight Test (OFT) other than differences in value of some constants for control and limit checking. Due to the dynamic nature of onboard time processing and its criticality to the successful operation of the orbiter, it is recommended that a comprehensive list of external variables, their locations, initial values, and a 'where used' listing be produced, as a by-product of the link edit process, for all non-HAL coding. In addition, a careful review of the verification test procedures for the System Services time-related software is recommended.

Blackburn, J. D.↗