Search NASA⌕ Search

SEARCH · Search NASA

Results for “owner”

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 73 records · Page 4

Develop and test fuel cell powered on-site integrated total energy system

Test results are given for a 5 kW stack and initial results for an integrated, grid connected system operating from methanol fuel. Site selection criteria are presented for future demonstration of a 50 or 100 kW OS/IES. Preliminary results are also given with approximate internal rates of return to the building owner. Progress in development and construction of a 50 kW modular methanol/steam reformer is reported.

Source record↗

The value of residential photovoltaic systems: A comprehensive assessment

Utility-interactive photovoltaic (PV) arrays on residential rooftops appear to be a potentially attractive, large-scale application of PV technology. Results of a comprehensive assessment of the value (i.e., break-even cost) of utility-grid connected residential photovoltaic power systems under a variety of technological and economic assumptions are presented. A wide range of allowable PV system costs are calculated for small (4.34 kW (p) sub ac) residential PV systems in various locales across the United States. Primary factor in this variation are differences in local weather conditions, utility-specific electric generation capacity, fuel types, and customer-load profiles that effect purchase and sell-back rates, and non-uniform state tax considerations. Additional results from this analysis are: locations having the highest insolation values are not necessary the most economically attractive sites; residential PV systems connected in parallel to the utility demonstrate high percentages of energy sold back to the grid, and owner financial and tax assumptions cause large variations in break-even costs. Significant cost reduction and aggressive resolution of potential institutional impediments (e.g., liability, standards, metering, and technical integration) are required for a residential PV marker to become a major electric-grid-connected energy-generation source.

Borden, C. S.↗

Interface standardization

Central-station applications create a large and attractive market for photovoltaics in the near future. However, some significant barriers lie between the industry of today and realization of that market. Manufacturing capacity and price are two principal impediments. The Utilities, which are the future system owners, are gaining experience with central-station PV power through the Sacramento Municipal Utility District, Hesperia and similar small central-station installations. SMUD has recognized that competition must be maintained to help reduce prices. So little standardization exists that the cost is driven upward to redefine mechanical and electrical interfaces for each vendor. New structues are required for each vendor and nonoptimum field geometries result from attempts to include more than one vendor in an array field. Standards at some hardware level are required.

Spencer, R.↗

Meteorological and Environmental Inputs to Aviation Systems

Reports on aviation meteorology, most of them informal, are presented by representatives of the National Weather Service, the Bracknell (England) Meteorological Office, the NOAA Wave Propagation Lab., the Fleet Numerical Oceanography Center, and the Aircraft Owners and Pilots Association. Additional presentations are included on aircraft/lidar turbulence comparison, lightning detection and locating systems, objective detection and forecasting of clear air turbulence, comparative verification between the Generalized Exponential Markov (GEM) Model and official aviation terminal forecasts, the evaluation of the Prototype Regional Observation and Forecast System (PROFS) mesoscale weather products, and the FAA/MIT Lincoln Lab. Doppler Weather Radar Program.

Camp, Dennis W.↗

Transparent process migration: Design alternatives and the Sprite implementation

The Sprite operating system allows executing processes to be moved between hosts at any time. We use this process migration mechanism to offload work onto idle machines, and also to evict migrated processes when idle workstations are reclaimed by their owners. Sprite's migration mechanism provides a high degree of transparency both for migrated processes and for users. Idle machines are identified, and eviction is invoked, automatically by daemon processes. On Sprite it takes up to a few hundred milliseconds on SPARCstation 1 workstations to perform a remote exec, while evictions typically occur in a few seconds. The pmake program uses remote invocation to invoke tasks concurrently. Compilations commonly obtain speedup factors in the range of three to six; they are limited primarily by contention for centralized resources such as file servers. CPU-bound tasks such as simulations can make more effective use of idle hosts, obtaining as much as eight-fold speedup over a period of hours. Process migration has been in regular service for over two years.

Douglis, Fred↗

Latest developments in the display of large-scale ionospheric and thermospheric data sets

Over the past decade, data base sizes have continually increased and will continue to do so in the future. This problem of size is further compounded because the trend in present-day studies is to use data from many different locations and different instruments and then compare it with data from global scale physical models. The latter produce data bases of comparable if not even larger size. Much of the data can be viewed as 'image' time sequences and is most readily viewed on color display terminals. These data sets reside in national or owner-generated data bases linked together by computer networks. As the size increases, just moving this data around, taking 'quick-looks' at the data, or even storing it locally become severe problems compromising the scientific return from the data. Is the present-day technology with these analysis techniques being used in the best way? What are the prospects for reducing the storage and transmission size of the data sets? Examples of such problems and potential solutions are described in this paper.

Sojka, J. J.↗

Microlabels For Auto Parts

Proposed method of unique labeling and identification of automotive parts greatly simplifies recall campaigns and reduces effort and expense associated. Compressed symbols fully characterize each part by type and manufacturing history. Manufacturers notify only those owners whose cars need repairs or modifications. Similar compressed symbology developed for possible use on spacecraft.

Ash, John P.↗

Satellite situation report, volume 32, no. 4

This report consists of data computed at the U.S. Space Command, GSFC, or provided by satellite owners. A space objects box score table is presented with data under the following headings: source/organization, objects in orbit, and decayed objects. The objects in orbit and decayed objects headings have payload, debris, and total as subheadings. The bulk of the document is objects-in-orbit tables with data under the following headings: international designation, name, catalog number, source, launch date, period minutes, inclination, apogee (km), perigee (km), and notes.

Source record↗

Automatic array alignment in data-parallel programs

FORTRAN 90 and other data-parallel languages express parallelism in the form of operations on data aggregates such as arrays. Misalignment of the operands of an array operation can reduce program performance on a distributed-memory parallel machine by requiring nonlocal data accesses. Determining array alignments that reduce communication is therefore a key issue in compiling such languages. We present a framework for the automatic determination of array alignments in array-based, data-parallel languages. Our language model handles array sectioning, reductions, spreads, transpositions, and masked operations. We decompose alignment functions into three constituents: axis, stride, and offset. For each of these subproblems, we show how to solve the alignment problem for a basic block of code, possibly containing common subexpressions. Alignments are generated for all array objects in the code, both named program variables and intermediate results. We assign computation to processors by virtue of explicit alignment of all temporaries; the resulting work assignment is in general better than that provided by the 'owner-computes' rule. Finally, we present some ideas for dealing with control flow, replication, and dynamic alignments that depend on loop induction variables.

Chatterjee, Siddhartha↗

Satellite situation report, volume 32, no. 1

This report consists of data computed at the U.S. Space Command, GSFC, or provided by satellite owners. A space objects box score table is presented with data under the following headings: source/organization, objects in orbit, and decayed objects. The objects in orbit and decayed objects headings have payload, debris, and total as subheadings. The bulk of the document is objects-in-orbit tables with data under the following headings: international designation, name, catalog number, source, launch date, period minutes, inclination, apogee (km), perigee (km), and notes.

Source record↗

Satellite situation report, volume 32, no. 2

This report consists of data computed at the U.S. Space Command, GSFC, or provided by satellite owners. A space objects box score table is presented with data under the following headings: source/organization, objects in orbit, and decayed objects. The objects in orbit and decayed objects headings have payload, debris, and total as subheadings. The bulk of the document is objects-in-orbit tables with data under the following headings: international designation, name, catalog number, source, launch date, period minutes, inclination, apogee (km), perigee (km), and notes.

Source record↗

Satellite situation report, volume 31, no. 4

This report consists of data computed at the U.S. Space Command, GSFC, or provided by satellite owners. A space objects box score table is presented with data under the following headings: source/organization, objects in orbit, and decayed objects. The objects in orbit and decayed objects headings have payload, debris, and total as subheadings. The bulk of the document is objects-in-orbit tables with data under the following headings: international designation, name, catalog number, source, launch date, period minutes, inclination, apogee (km), perigee (km), and notes.

Source record↗

Satellite situation report, volume 33, no. 3

This report consists of data computed at the U.S. Space Command, GSFC, or provided by satellite owners. A space objects box score table is presented with data under the following headings: source/organization, objects in orbit, and decayed objects. The objects in orbit and decayed objects headings have payload, debris, and total as subheadings. The bulk of the document is objects-in-orbit tables with data under the following headings: international designation, name, catalog number, source, launch date, period minutes, inclination, apogee (km), perigee (km), and notes.

Source record↗

Distributed computing feasibility in a non-dedicated homogeneous distributed system

The low cost and availability of clusters of workstations have lead researchers to re-explore distributed computing using independent workstations. This approach may provide better cost/performance than tightly coupled multiprocessors. In practice, this approach often utilizes wasted cycles to run parallel jobs. The feasibility of such a non-dedicated parallel processing environment assuming workstation processes have preemptive priority over parallel tasks is addressed. An analytical model is developed to predict parallel job response times. Our model provides insight into how significantly workstation owner interference degrades parallel program performance. A new term task ratio, which relates the parallel task demand to the mean service demand of nonparallel workstation processes, is introduced. It was proposed that task ratio is a useful metric for determining how large the demand of a parallel applications must be in order to make efficient use of a non-dedicated distributed system.

Leutenegger, Scott T.↗

Satellite situation report, volume 31, number 1

Data computed at GSFC, NORAD, or provided by satellite owners is reported. A space objects box score is presented of objects in orbit and decayed objects. Data of objects in orbit is presented in tabular form and the table headings include name of the object, catalog number, source, launch date, period minutes, inclination, apogee KM., perigee KM., and transmitting frequency.

Source record↗

Satellite situation report, volume 33, number 4

The Satellite Situation Report is a listing of those satellites (objects) currently in orbit and those which have previously orbited the Earth. Some objects are too small or too far from the Earth's surface to be detected; therefore, the Satellite Situation Report does not include all manmade objects orbiting the Earth. Generally, satellites are classified as follows: (1) Payloads may contain one or more functioning or nonfunctioning experiments. Usually only the owners of the satellites know if the experiments are functioning, and there is no one source which indicates the operational status of all payloads and/or experiments. Payloads are normally the first listed in the Satellite Situation Report, i.e., 1982 087A, unless there are multiple payloads for the launch. In which case, the first objects cataloged are usually all payloads, unless a subsequent payload is later identified after objects other than payloads have been cataloged. (2) Platforms are used to support a payload while it is being placed into orbit. A platform may remain in orbit long after its purpose is served, usually longer than rocket bodies. It is usually the first object identified in the Satellite Situation Report listing after the payload(s), i.e., 1982 087B (when a platform is not used, the first object after the payload(s) is usually the rocket body). (3) Rocket bodies are used to place the payload and platform (if one is used) into orbit. Some launches may have more than one rocket body because of the payload weight or the type of orbit or experiment. Most rocket bodies decay within a short time after the payload (and platform) have achieved orbit. Rocket bodies are usually the third object listed in the Satellite Situation Report after the payload(s), i.e., 1982 087C. (4) Debris in orbit occurs when parts (nose cone shrouds, lens or hatch covers) are separated from the payload, when rocket bodies or payloads disintegrate or explode, or when objects are placed into free space from manned orbiting spacecraft during operations. Debris is detected by its size and distance from the Earth. Debris objects are the last objects after payload(s), platform, and rocket body(s) listed in the Satellite Situation Report, i.e., 1982 087D, 1982 087E, 1982 087F.

Source record↗

Satellite situation report, volume 33, number 2

This report consists of data computed at United States Space Command, GFSC, or provided by satellite owners. A space objects box score table is presented with data under the following headings: source/organization, objects in orbit, and decayed objects. The objects in orbit and decayed objects' headings have payload, debris, and total as subheadings. The bulk of the document is objects in orbit tables with data under the following headings: international designation, name, catalog number, source, launch date, period minutes, inclination, apogee (km), perigee (km) and notes.

Source record↗

Microgravity Experiments Safety and Integration Requirements Document Tree

This report is a document tree of the safety and integration documents required to develop a space experiment. Pertinent document information for each of the top level (tier one) safety and integration documents, and their applicable and reference (tier two) documents has been identified. This information includes: document title, revision level, configuration management, electronic availability, listed applicable and reference documents, source for obtaining the document, and document owner. One of the main conclusions of this report is that no single document tree exists for all safety and integration documents, regardless of the Shuttle carrier. This document also identifies the need for a single point of contact for customers wishing to access documents. The data in this report serves as a valuable information source for the NASA Lewis Research Center Project Documentation Center, as well as for all developers of space experiments.

Hogan, Jean M.↗