Search NASA⌕ Search

SEARCH · Search NASA

Results for “Time Service”

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 307 records · Page 17

2019 Argonne Leadership Computing Facility Science Report

The Argonne Leadership Computing Facility (ALCF) is a U.S. Department of Energy (DOE) Office of Science User Facility that enables breakthroughs in science and engineering by providing supercomputing resources and expertise to the research community. ALCF computing resources - available to researchers from academia, industry, and government agencies - support large-scale computing projects aimed at solving some of the world’s most complex and challenging scientific problems. Through awards of supercomputing time and support services, the ALCF enables its users to accelerate the pace of discovery and innovation across disciplines.

36 MATERIALS SCIENCE↗

A simulation study of test fixture attachment points for vibration test optimization (MEEN 5440 Final Project)

The aerospace industry uses vibration shaker tables to perform component durability testing. These dynamic environments tests often have a hard time replicating the service environment of a component due to a mismatch in the applied force or the boundary condition. Figure 1 shows the desired outcome of a dynamic environments test. The measured responses in a lab test, ideally, should match the measured response of the service environment field test. One way to address the mismatch between field environment and lab environment is with test fixture design. The test fixture attaches the component under test to the shaker table. Single-axis shakers are the industry standard type of shaker table, and, therefore, test fixtures are often rigid in order to minimize cross-axis responses.

42 ENGINEERING↗

HarDWR - Raw Water Rights Records

A dataset within the Harmonized Database of Western U.S. Water Rights (HarDWR). For a detailed description of the database, please see the meta-record v2.0. Changelog v2.0 - Switched source data from collecting records from each state independently to using the WestDAAT dataset v1.0 - Initial public release Description In order to hold a water right in the western United States, an entity, (e.g., an individual, corporation, municipality, sovereign government, or non-profit) must register a physical document with the state's water regulatory agency. State water agencies each maintain their own database containing all registered water right documents within the state, along with relevant metadata such as the point of diversion and place of use of the water. All western U.S. states have digitized their individual water rights databases, as well as geospatial data defining the areas in which water rights are managed. Each state maintains and provides their own water rights data in accordance with individual state regulations and standards. In addition, while all states make their water rights publicly available, each provides their records in unique formats, meaning that file types, field availability, and terms vary from state to state. This leads to additional challenges to managing resources which cross state lines, or conducting consistent multi-state water analyses. For the first version of HarDWR, we collected the water rights databases from 11 Western States of the United States. In order to preform regional analyses with the collected data, the raw records had to be harmonized into one single format. The Water Data Exchange (WaDE) is a program dedicated to the sharing of water-related data for the Western U.S. in a singular consistent format. Created by the Western States Water Council (WSWC) to facilitate the collection and dissemination of water data among WSWC's member states and the public, WaDE provides an important service for those interested in water resource planning and management in their focus region. Of the services which WaDE provides, the one of the most interesting is the WestDAAT dataset, which is a collection of water rights data provided by the 18 WSWC member states that have been standardized into a single format, much like we had done on a more limited scale with HarDWR v1. For this version of HarDWR we decided to use WestDAAT, specifically a snapshot created in Feburary 2024, as our water rights source data. A full explanation of the benefits gained from this switch can be found in the description of the updated Harmonized Water Rights Records v2.0, but in short it has allowed us to focus more of our efforts on answering research questions and gaining a more realistic understanding of how water rights are allocated. For more information on how the data for WestDAAT was collected, please see the WaDE data summary. Terms of Use While WaDE works directly with the state agencies to collect and standardize the water rights records, the ultimate authority for the water rights data remains the individual states. Each state, and their respective water right authorities, have made their water right records available for non-commercial reference uses. In addition, the states make no guarantees as to the completeness, accuracy, or timeliness of their respective databases, let alone the modifications which we, the authors of this paper, have made to the collected records. None of the states should be held liable for using this data outside of its intended use. As several of the states update their water rights databases daily, the information provided here is not the latest possible, and should not be used for legal purposes. WestDAAT itself has irregular updates. Additional questions about the data the source states provided should be directed to the respective state agencies (see methods.csv and organization.csv files described below). In addition, although data was presented here was not collected directly from the states, several states requested specifically worked disclaimers when sharing their data. These disclaimers are included here as an acknowledgement from where the water rights data is primarily sourced. Colorado: "The data made available here has been modified for use from its original source, which is the State of Colorado. THE STATE OF COLORADO MAKES NO REPRESENTATIONS OR WARRANTY AS TO THE COMPLETENESS, ACCURACY, TIMELINESS, OR CONTENT OF ANY DATA MADE AVAILABLE THROUGH THIS SITE. THE STATE OF COLORADO EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the Web feed is being used at one's own risk." Montana: "The Montana State Library provides this product/service for informational purposes only. The Library did not produce it for, nor is it suitable for legal, engineering, or surveying purposes. Consumers of this information should review or consult the primary data and information sources to ascertain the viability of the information for their purposes. The Library provides these data in good faith but does not represent or warrant its accuracy, adequacy, or completeness. In no event shall the Library be liable for any incorrect results or analysis; any direct, indirect, special, or consequential damages to any party; or any lost profits arising out of or in connection with the use or the inability to use the data or the services provided. The Library makes these data and services available as a convenience to the public, and for no other purpose. The Library reserves the right to change or revise published data and/or services at any time." Oregon: "This product is for informational purposes and may not have been prepared for, or be suitable for legal, engineering, or surveying purposes. Users of this information should review or consult the primary data and information sources to ascertain the usability of the information." File Descriptions The unmodified February, 2024 WestDAAT snapshot is composed of nine files. Below is a brief description of each file, as well as how they were utilized for HarDWR. WaDEDataDictionaryTerms.xlsx: As the file's name implies, this is a data dictionary for all of the below named files. This file describes the column names for each of the following files, with the exception of citation.txt which does not have any columns. The descriptions for each file are divided by tab,with the same name as their associated file, within this document. allocationamount.csv: The "main" file of the group, it contains the water right records for each state. Of particular note, each water right is broken down into one or more water allocations. Allocations may be withdrawn from one or more locations, or even multiple allocations associated with a particular location. This is a more subtle and realistic representation of how water is used than what was available in the first version of HarDWR. For the records from some states, this can mean that multiple allocations listed under a single right will appear as rows within this file. citation.txt: A combination of contact information for WaDE personnel, disclaimer about how the data should be used, and guidelines for citing WestDAAT. methods.csv: A file describing the source and method by which WaDE collected water rights data from each state. organization.csv: A file listing the water rights authoritative agencies for each state. sites.csv: This file provides the geographic, and other descriptors, of the physical location of allocations, called 'sites'. To reiterate, it is possible for one allocation to be associated with multiple sites, as well as one site to be associated with multiple allocations. The two descriptors which we were most interested in where the site's coordinates, as well as whether the site was classified as a Point of Diversion (POD) or a Place of Use (POU). As a general rule, PODs are geographic points, while POUs are areas typically represented as property boundaries or irregularly shaped polygons. sites_pouGeometry.csv: For those allocations with a POU site, this file contains the defining points for the associated polygons. variables.csv: A file describing the units in which an allocation's water amount is reported within WestDAAT. This information is essentially a repeat of the 'AllocationFlow_CFS' and 'AllocationVolume_AF' columns within allocationamount.csv, at least for our purposes. watersources: This file describes the source of water from which each site extracts from. For our purposes, this table was used to determine whether the water came from Surface Water, Groundwater, or Unspecified Water.

Lisk, Matthew↗

The elements of a space operations system

The Space Shuttle has completed its flight test program and is entering operational service with its fifth flight in November 1982. With the completion of Shuttle development, its entry to operational service, and delivery of additional units into field service, it is timely to initiate development of the next elements of the system. The elements of a Space Operations System are the Shuttle, a Station in low earth orbit, and upper stages for low and high energy orbit delivery. To design these elements properly will require a substantial operations analysis effort to characterize the most effective performance tradeoffs among the discrete elements. The Shuttle establishes a new context for the design and execution of operations in space. The components of the Shuttle, Space Station, and upper stages will need to share technology and components to minimize the cost and complexity of the logistics of ownership and operation.

Loftus, J. P., Jr.↗

Assessment of the availability of the tracking and data relay satellite system for LANDSAT missions

The telecommunications availability that can realistically be provided by the tracking and data relay satellite system (TDRSS) for LANDSAT D type missions. Although the assessment focusses on the telecommunications requirements of the near Earth orbit missions of the 1985 - 1989 time frame, it emphasizes LANDSAT D and its competing demand for wideband, real-time RF link services from TDRSS. Limitations in availability of communications services are identified, including systematic TDRSS restrictions, conflicting telecommunication requirements and loading problems of all users (missions) which are to be supported by TDRSS. Several telecommunications alternatives for LANDSAT D utilization independent of TDRSS services are discussed.

Source record↗

Determining Availability Characteristics of DSN Data Systems Using Discrepancy Report Data

A reasonably economical way was developed to determine availability characteristics of Deep Space Network (DSN) data systems, subsystems, and assemblies using the DSN discrepancy report (DR) data base and DSN operating schedule and history data bases. Operating mean time between failures (OMTBF), operating mean time to restore service (OMTTRS), and operating functional availability (OFA) can be computed by year, by system, by subsystem, by assembly, and by station. The effort required to produce the desired reports is described, specific data on the telemetry, command, and tracking systems are presented, and major contributors to system outages are identified. Future improvements in preparing and analyzing DR data are also outlined to enhance their use in correcting conditions that lead to outages.

Ruskin, A. M.↗

Fault-Tolerant Local-Area Network

Local-area network (LAN) for computers prevents single-point failure from interrupting communication between nodes of network. Includes two complete cables, LAN 1 and LAN 2. Microprocessor-based slave switches link cables to network-node devices as work stations, print servers, and file servers. Slave switches respond to commands from master switch, connecting nodes to two cable networks or disconnecting them so they are completely isolated. System monitor and control computer (SMC) acts as gateway, allowing nodes on either cable to communicate with each other and ensuring that LAN 1 and LAN 2 are fully used when functioning properly. Network monitors and controls itself, automatically routes traffic for efficient use of resources, and isolates and corrects its own faults, with potential dramatic reduction in time out of service.

Morales, Sergio↗

NASA Propagation Studies Website

This paper describes an Internet website which provides information to enable the development of new commerical satellite systems and services by providing timely data and models about the propagation of satellite radio signals. In partnership with industry and academia, the program leverages NASA assets, currently the Advanced Communications Technology Satellite (ACTS), to obtain propagation data. The findings of the study are disseminated through refereed journals, NASA reference publications, workshops, electronic media, and direct interface with industry.

Angkasa, Krisjani S.↗

NASA Propagation Studies Website

The NASA propagation studies objective is to enable the development of new commercial satellite communication systems and services by providing timely data and models about propagation of satellite radio signals through the intervening environment and to support NASA missions. In partnership with industry and academia, the program leverages unique NASA assets (currently Advanced Communications Technology Satellite) to obtain propagation data. The findings of the study are disseminated through referred journals, NASA reference publications, workshops, electronic media, and direct interface with industry.

Angkasa, Krisjani S.↗

Presentations of the Ninth Advanced Communications Technology Satellite Propagation Studies Workshop (APSW IX)

The Advanced Communications Technology Satellite Propagation Studies Workshop (APSW) is convened each year to present the results of the ACTS Propagation Campaign. Representatives from the satellite communications (satcom) industry, academia, and government are invited to APSW for discussions and exchange of information. The ACTS Propagation campaign is completing three years of Ka-Band data collection at seven sites in North America. Through this effort, NASA is making a major contribution to growth of satcom services by providing timely propagation data and models for predicting the performance of Ka-Band satellite communications systems.

Golshan, Nasser↗

Small Business Innovations

The purpose of QASE RT is to enable system analysts and software engineers to evaluate performance and reliability implications of design alternatives. The program resulted from two Small Business Innovation Research (SBIR) projects. After receiving a description of the system architecture and workload from the user, QASE RT translates the system description into simulation models and executes them. Simulation provides detailed performance evaluation. The results of the evaluations are service and response times, offered load and device utilizations and functional availability.

Source record↗

IGS Data Center Working Group Report

At its 18th meeting held December 09, 2001 in San Francisco, the IGS Governing Board recommended the formation of a working group to focus on data center issues. This working group will tackle many of the problems facing the IGS data centers as well as develop new ideas to aid users both internal and external to the IGS. The direction of the IGS has changed since its start in 1992 and many new working groups, projects, data sets, and products have been created and incorporated into the service since that time. Therefore, this may be an appropriate time to revisit the requirements of data centers within the IGS.

Noll, Carey E.↗

Time Synchronization and Distribution Mechanisms for Space Networks

This work discusses research on the problems of synchronizing and distributing time information between spacecraft based on the Network Time Protocol (NTP), where NTP is a standard time synchronization protocol widely used in the terrestrial network. The Proximity-1 Space Link Interleaved Time Synchronization (PITS) Protocol was designed and developed for synchronizing spacecraft that are in proximity where proximity is less than 100,000 km distant. A particular application is synchronization between a Mars orbiter and rover. Lunar scenarios as well as outer-planet deep space mother-ship-probe missions may also apply. Spacecraft with more accurate time information functions as a time-server, and the other spacecraft functions as a time-client. PITS can be easily integrated and adaptable to the CCSDS Proximity-1 Space Link Protocol with minor modifications. In particular, PITS can take advantage of the timestamping strategy that underlying link layer functionality provides for accurate time offset calculation. The PITS algorithm achieves time synchronization with eight consecutive space network time packet exchanges between two spacecraft. PITS can detect and avoid possible errors from receiving duplicate and out-of-order packets by comparing with the current state variables and timestamps. Further, PITS is able to detect error events and autonomously recover from unexpected events that can possibly occur during the time synchronization and distribution process. This capability achieves an additional level of protocol protection on top of CRC or Error Correction Codes. PITS is a lightweight and efficient protocol, eliminating the needs for explicit frame sequence number and long buffer storage. The PITS protocol is capable of providing time synchronization and distribution services for a more general domain where multiple entities need to achieve time synchronization using a single point-to-point link.

Woo, Simon S.↗

Comparison of Different Control Schemes for Strategic Departure Metering

Airports and their terminal airspaces are key choke points in the air transportation system causing major delays and adding to pollution. A solution aimed at mitigating these chokepoints integrates the scheduling of runway operations, flight release from the gates and ramp into the airport movement area, and merging with other traffic competing for downstream airspace points. Within this integrated concept, we present a simulation-based analysis of the departure metering process, which delays the release of flights into the airport movement area while balancing two competing objectives: (1) maintaining large enough queues at the airport resources to maximize throughput and (2) absorbing excess delays at the gates or in ramp areas to save on fuel consumption, emissions, noise, and passenger discomfort. Three metering strategies are compared which respectively attempt to control the number of flights that (1) left the gate but did not take off, (2) left the ramp but did not take off, and (3) spent their unimpeded transit time to the runway but did not take off. It was observed that under deterministic and demand uncertainty conditions, the first strategy performed better than the other two strategies in terms of maintaining the runway throughput while transferring a significant average delay of two minutes to the gate. On the other hand, under uncertainties of flight transit time and runway service rate, all the strategies struggled to delay flights at the gate without a significant impact on the runway throughput.

air traffic management↗

Next Steps: Laying the Groundwork for Bundle Protocol v7

Delay/Disruption Tolerant Networking (DTN) is a networking model and protocol suite that extends the terrestrial internet to the challenging communication environments of space. These environments are typically subject to frequent disruptions, which can cause delays or errors. DTN protects data transmission by wrapping data into bundles (similar to Internet Protocol packets), storing them until a connection can be established between two nodes (similar to terrestrial routers or computers), and forwarding them to their destinations. Bundle Protocol (BP) is responsible for generating those bundles and creates the transport layer of DTN, much like how Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) create the transport layer of the Internet Protocol. BPv6 is the current, accepted version of the Bundle Protocol standard. However, recent missions and test implementations have revealed missing components and areas for improvement in the standard. Using lessons learned from NASA missions and gathering inspiration from the Internet Protocol, BPv7 is intended to be a more robust Bundle Protocol that improves upon its predecessor and increases the technology readiness level of the DTN architecture. The DTN Standard Interface Design team, a sub-team of the DTN Infusion Project at the Goddard Space Flight Center, worked to create a dictionary of terms for bundle components and functional decomposition of the protocol. These efforts aided in the standardization of BP interfaces, something missing from BPv6, and supported parallel network management and configuration work. This standardization will ultimately contribute to LunaNet (a lunar communications and navigation architecture that will bring networking, positioning, navigation, timing and science services to the Moon), the Solar System Internet (SSI), and expand crewed and uncrewed space exploration opportunities.

DTN↗

Next Steps: Laying the Groundwork for Bundle Protocol v7

Delay/Disruption Tolerant Networking (DTN) is a networking model and protocol suite that extends the terrestrial internet to the challenging communication environments of space. These environments are typically subject to frequent disruptions, which can cause delays or errors. DTN protects data transmission by wrapping data into bundles (similar to Internet Protocol packets), storing them until a connection can be established between two nodes (similar to terrestrial routers or computers), and forwarding them to their destinations. Bundle Protocol (BP) is responsible for generating those bundles and creates the transport layer of DTN, much like how Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) create the transport layer of the Internet Protocol. BPv6 is the current, accepted version of the Bundle Protocol standard. However, recent missions and test implementations have revealed missing components and areas for improvement in the standard. Using lessons learned from NASA missions and gathering inspiration from the Internet Protocol, BPv7 is intended to be a more robust Bundle Protocol that improves upon its predecessor and increases the technology readiness level of the DTN architecture. The DTN Standard Interface Design team, a sub-team of the DTN Infusion Project at the Goddard Space Flight Center, worked to create a dictionary of terms for bundle components and functional decomposition of the protocol. These efforts aided in the standardization of BP interfaces, something missing from BPv6, and supported parallel network management and configuration work. This standardization will ultimately contribute to LunaNet (a lunar communications and navigation architecture that will bring networking, positioning, navigation, timing and science services to the Moon), the Solar System Internet (SSI), and expand crewed and uncrewed space exploration opportunities.

dtn↗

Application of Analytical Hierarchy Process for Narrowing Down Nep Candidate Reactor Designs

Nuclear electric propulsion (NEP)-powered vehicles have been contemplated for human Mars missions. The nuclear power system contemplates using a high temperature light-weight nuclear reactor for the production of electrical power in the range of 2-5 MWe with a 3-10 year service life. A myriad of technology options exist for achieving these mission objectives. The analytic hierarchy process (AHP), a multi-attribute decision method, is being used to narrow down the candidate designs. The AHP is a structured decision process that fuses model-supplied quantitative data with subjective assessments to facilitate decisions that involve multiple competing criteria. Proven end-to-end nuclear design and systems analysis tools will be used to provide quantitative performance data such as end-to-end system reliability, system robustness to recover from off-normal conditions, system specific weight (α in kg/kWe), and the ability to meet the service life-time and power level requirements. Three high assay low enriched uranium (HALEU) reactor concepts, namely, gas-, heat pipe- and pumped liquid-cooled nuclear cores coupled to a He/Xe gas or supercritical CO2- Brayton power conversion system are being modeled using the AHP to understand the trade-offs associated with these design combinations. In addition to the reactor and power conversion options, there are a myriad of additional components and subsystems – e.g., radiators, heat exchangers, and recuperators – that also figure into the evaluation process. The choice of the right overall system is a multidimensional problem that has to include not only quantitative data, but also the so called “external factors”, examples of which include the component and subsystem Technology Readiness Levels (TRLs), the associated Advancement Degrees of Difficulty (AD2), the cost and schedule required to achieve a technical maturity consistent with mission infusion, alignment with the priorities of NASA’s Space Nuclear Propulsion program, and alignment with other ongoing government and commercial investments in micro reactors. Focused expert elicitations form the basis for qualitative data set. As a final step, decision-makers individually express their opinions regarding the relative importance of the criteria and preferences among the alternatives through pairwise comparisons. The paper will describe the AHP approach, progress to-date applying it to the NEP human Mars mission problem, and preliminary results. Use of AHP provides sufficient flexibility for incorporating industry input at different stages as the technologies evolve through additional research and development. It is expected that the decision process will be ongoing and expanded to examine additional options and technology choices, culminating in a defensible set of candidate reactor concepts that will form the basis for developing a multi-year NEP technology maturation strategy. .

Dasari V Rao↗

Is the Last Inflight Rest Break Really the Best?

As pilots experienced in augmented long-haul flights know, current FAA regulations limit options for scheduling in-flight rest periods, such that on many long-haul operations the landing pilot needs to use the final bunk period, closest to top of descent (TOD). However, the logistics of a particular flight (e.g., timing of the flight, timing of passenger service) and the pilot’s own physiology may mean that the last rest break isn’t always the best. To study this, we conducted a large survey of pilots flying these operations. Pilots completed the survey after eligible flights and provided us with information on which rest break they used, how much sleep they received, factors that disrupted sleep and ratings on the quality of their sleep, and they also provided fatigue and alertness ratings at top-of-descent. Pilots from another US-based carrier were also surveyed, in collaboration with our research partners at Washington State University, to increase the sample size and gather insights between operations.

in-flight rest↗