Search NASA⌕ Search

SEARCH · Search NASA

Results for “Tcl”

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 37 records · Page 2

Transportable Applications Environment Plus

Transportable Applications Environment Plus (TAE+) is integrated, portable program providing environment for developing and running interactive window, text, and graphical object-based application software systems. Enables construction of custom application interface and moving applications to different computers. Components are WorkBench, tool for design of user interface; WPT's (Window Programming Tools) package, set of callable subroutines controlling user interface; and TAE Command Language (TCL), providing ways to develop executable application prototype with run-time-interpreted language. Uses MIT X-Window System, WorkBench and WPT's written in C++, remaining code in C.

Source record↗

A versatile system for processing geostationary satellite data with run-time visualization capability

To better predict global climate change, scientists are developing climate models that require interdisciplinary and collaborative efforts in their building. We are currently involved in several such projects but will briefly discuss activities in support of two such complementary projects: the Atmospheric Radiation Measurement (ARM) program of the Department of Energy and Sequoia 2000, a joint venture of the University of California, the private sector, and government agencies. Our contribution to the ARM program is to investigate the role of clouds on the top of the atmosphere and on surface radiance fields through the data analysis of surface and satellite observations and complex modeling of the interaction of radiation with clouds. One of our first ARM research activities involves the computation of the broadband shortwave surface irradiance from satellite observations. Geostationary satellite images centered over the first ARM observation site are received hourly over the Internet network and processed in real time to compute hourly and daily composite shortwave irradiance fields. The images and the results are transferred via a high-speed network to the Sequoia 2000 storage facility in Berkeley, where they are archived These satellite-derived results are compared with the surface observations to evaluate the accuracy of the satellite estimate and the spatial representation of the surface observations. In developing the software involved in calculating the surface shortwave irradiance, we have produced an environment whereby we can easily modify and monitor the data processing as required. Through the principles of modular programming, we have developed software that is easily modified as new algorithms for computation are developed or input data availability changes. In addition, the software was designed so that it could be run from an interactive, icon-driven, graphical interface, TCL-TK, developed by Sequoia 2000 participants. In this way, the data flow can be interactively assessed and altered as needed. In this environment, the intermediate data processing 'images' can be viewed, enabling the investigator to easily monitor the various data processing steps as they progress. Additionally, this environment allows the rapid testing of new processing modules and allows their effects to be visually compared with previous results.

Landsfeld, M.↗

Tools for automating spacecraft ground systems: The Intelligent Command and Control (ICC) approach

The practical application of scripting languages and World Wide Web tools to the support of spacecraft ground system automation, is reported on. The mission activities and the automation tools used at the Goddard Space Flight Center (MD) are reviewed. The use of the Tool Command Language (TCL) and the Practical Extraction and Report Language (PERL) scripting tools for automating mission operations is discussed together with the application of different tools for the Compton Gamma Ray Observatory ground system.

Stoffel, A. William↗

HEASARC Software Archive

(1) Chandra Archive: SAO has maintained the interfaces through which HEASARC gains access to the Chandra Data Archive. At HEASARC's request, we have implemented an anonymous ftp copy of a major part of the public archive and we keep that archive up-to- date. SAO has participated in the ADEC interoperability working group, establishing guidelines or interoperability standards and prototyping such interfaces. We have provided an NVO-based prototype interface, intending to serve the HEASARC-led NVO demo project. HEASARC's Astrobrowse interface was maintained and updated. In addition, we have participated in design discussions surrounding HEASARC's Caldb project. We have attended the HEASARC Users Group meeting and presented CDA status and developments. (2) Chandra CALDB: SA0 has maintained and expanded the Chandra CALDB by including four new data file types, defining the corresponding CALDB keyword/identification structures. We have provided CALDB upgrades for the public (CIAO) and for Standard Data Processing. Approximately 40 new files have been added to the CALDB in these version releases. There have been in the past year ten of these CALDB upgrades, each with unique index configurations. In addition, with the inputs from software, archive, and calibration scientists, as well as CIAO/SDP software developers, we have defined a generalized expansion of the existing CALDB interface and indexing structure. The purpose of this is to make the CALDB more generally applicable and useful in new and future missions that will be supported archivally by HEASARC. The generalized interface will identify additional configurational keywords and permit more extensive calibration parameter and boundary condition specifications for unique file selection. HEASARC scientists and developers from SAO and GSFC have become involved in this work, which is expected to produce a new interface for general use within the current year. (3) DS9: One of the decisions that came from last year's HEADCC meeting was to make the ds9 image display program the primary vehicle for displaying line graphics (as well as images). The first step required to make this possible was to enhance the line graphics capabilities of ds9. SAO therefore spent considerable effort upgrading ds9 to use Tcl 8.4 so that the BLT line graphics package could be built and imported into ds9 from source code, rather than from a pre-built (and generally outdated) shared library. This task, which is nearly complete, allows us to extend BLT as needed for the HEAD community. Following HEADCC discussion concerning archiving and the display of archived data, we extended ds9 to support full access to many astronomical Web-based archives sites, including HEASARC, MAST, CHANDRA, SKYVIEW, ADS, NED, SIMBAD, IRAS, NVRO, SAO TDC, and FIRST. Using ds9's new internal Web access capabilities, these archives can be accessed via their Web page. FITS images, plots, spectra, and journal abstracts can be referenced, down-loaded, and displayed directly and easily in ds9. For more information, see: http://hea-www.harvard.edu/saord/ds9. Also after the HEADCC discussion concerning region filtering, we extended the Funtools sample implementation of region filtering as described in: http://hea-www.harvard.edu/saord/funtools/regions.html. In particular, we added several new composite regions for event and image filtering, including elliptical and box annuli. We also extended the panda (Pie AND Annulus) region support to include box pandas and elliptical pandas. These new composite regions are especially useful in programs that need to count photons in each separate region using only a single pass through the data. Support for these new regions was added to ds9. In the same vein, we developed new region support for filtering images using simple FITS image masks, i.e. 8-bit or 16-bit FITS images where the value of a pixel is the region id number for that pixel. Other important enhancements to DS9 this year, include supporor multiple world coordinate systems, three dimensional event file binning, image smoothing, region groups and tags, the ability to save images in a number of image formats (such as JPEG, TIFF, PNG, FITS), improvements in support for integrating external analysis tools, and support for the virtual observatory. In particular, a full-featured web browser has been implemented within D S 9 . This provides support for full access to HEASARC archive sites such as SKYVIEW and W3BROWSE, in addition to other astronomical archives sites such as MAST, CHANDRA, ADS, NED, SIMBAD, IRAS, NVRO, SA0 TDC, and FIRST. From within DS9, the archives can be searched, and FITS images, plots, spectra, and journal abstracts can be referenced, downloaded and displayed The web browser provides the basis for the built-in help facility. All DS9 documentation, including the reference manual, FAQ, Know Features, and contact information is now available to the user without the need for external display applications. New versions of DS9 maybe downloaded and installed using this facility. Two important features used in the analysis of high energy astronomical data have been implemented in the past year. The first is support for binning photon event data in three dimensions. By binning the third dimension in time or energy, users are easily able to detect variable x-ray sources and identify other physical properties of their data. Second, a number of fast smoothing algorithms have been implemented in DS9, which allow users to smooth their data in real time. Algorithms for boxcar, tophat, and gaussian smoothing are supported.

White, Nicholas↗

Automated testing of the Deep Space Network's Uplink Subsystem

This paper describes some of the lessons we learned in implementing two different Tcl-basedtest frameworks used to automate testing of the Deep Space Network's new Uplink Subsystem, and discusses the advantages and disadvantages of each. The first framework was external to the Uplink Subsystem's software and provided complete control of the environment; the second was integrated with the software and provided less control, but motivated more and better testing. Some implementation details of the second frameworkare discussed as well.

DSN automated testing Tcl/Tk↗

An Idealized, Single Radial Swirler, Lean-Direct-Injection (LDI) Concept Meshing Script

To easily study combustor design parameters using computational fluid dynamics codes (CFD), a Gridgen Glyph-based macro (based on the Tcl scripting language) dubbed BladeMaker has been developed for the meshing of an idealized, single radial swirler, lean-direct-injection (LDI) combustor. BladeMaker is capable of taking in a number of parameters, such as blade width, blade tilt with respect to the perpendicular, swirler cup radius, and grid densities, and producing a three-dimensional meshed radial swirler with a can-annular (canned) combustor. This complex script produces a data format suitable for but not specific to the National Combustion Code (NCC), a state-of-the-art CFD code developed for reacting flow processes.

Iannetti, Anthony C.↗

Solving Equations of Multibody Dynamics

Darts++ is a computer program for solving the equations of motion of a multibody system or of a multibody model of a dynamic system. It is intended especially for use in dynamical simulations performed in designing and analyzing, and developing software for the control of, complex mechanical systems. Darts++ is based on the Spatial-Operator- Algebra formulation for multibody dynamics. This software reads a description of a multibody system from a model data file, then constructs and implements an efficient algorithm that solves the dynamical equations of the system. The efficiency and, hence, the computational speed is sufficient to make Darts++ suitable for use in realtime closed-loop simulations. Darts++ features an object-oriented software architecture that enables reconfiguration of system topology at run time; in contrast, in related prior software, system topology is fixed during initialization. Darts++ provides an interface to scripting languages, including Tcl and Python, that enable the user to configure and interact with simulation objects at run time.

Jain, Abhinandan↗

Evaluation of the Rotational Throttle Interface for Converting Aircraft Utilizing the NASA Ames Vertical Motion Simulator

An experiment was conducted to compare a conventional helicopter Thrust Control Lever (TCL) to the Rotational Throttle Interface (RTI) for tiltrotor aircraft. The RTI is designed to adjust its orientation to match the angle of the tiltrotor s nacelles. The underlying principle behind the design is to increase pilot awareness of the vehicle s configuration state (i.e. nacelle angle). Four test pilots flew multiple runs on seven different experimental courses. Three predominant effects were discovered in the testing of the RTI: 1. Unintentional binding along the control axis resulted in difficulties with precision power setting, 2. Confusion in which way to move the throttle grip was present during RTI transition modes, and 3. Pilots were not able to distinguish small angle differences during RTI transition. In this experiment the pilots were able to successfully perform all of the required tasks with both inceptors although the handling qualities ratings were slightly worse for the RTI partly due to unforeseen deficiencies in the design. Pilots did however report improved understanding of nacelle movement during transitions with the RTI.

Rozovski, David↗

Unmanned Aircraft Systems Traffic Management (UTM) Safely Enabling UAS Operations in Low-Altitude Airspace

Unmanned Aircraft System (UAS) Traffic Management (UTM) Enabling Civilian Low-Altitude Airspace and Unmanned Aircraft System Operations What is the problem? Many beneficial civilian applications of UAS have been proposed, from goods delivery and infrastructure surveillance, to search and rescue, and agricultural monitoring. Currently, there is no established infrastructure to enable and safely manage the widespread use of low-altitude airspace and UAS operations, regardless of the type of UAS. A UAS traffic management (UTM) system for low-altitude airspace may be needed, perhaps leveraging concepts from the system of roads, lanes, stop signs, rules and lights that govern vehicles on the ground today, whether the vehicles are driven by humans or are automated. What system technologies is NASA exploring? Building on its legacy of work in air traffic management for crewed aircraft, NASA is researching prototype technologies for a UAS Traffic Management (UTM) system that could develop airspace integration requirements for enabling safe, efficient low-altitude operations. While incorporating lessons learned from the today's well-established air traffic management system, which was a response that grew out of a mid-air collision over the Grand Canyon in the early days of commercial aviation, the UTM system would enable safe and efficient low-altitude airspace operations by providing services such as airspace design, corridors, dynamic geofencing, severe weather and wind avoidance, congestion management, terrain avoidance, route planning and re-routing, separation management, sequencing and spacing, and contingency management. One of the attributes of the UTM system is that it would not require human operators to monitor every vehicle continuously. The system could provide to human managers the data to make strategic decisions related to initiation, continuation, and termination of airspace operations. This approach would ensure that only authenticated UAS could operate in the airspace. In its most mature form, the UTM system could be developed using autonomicity characteristics that include self-configuration, self-optimization and self-protection. The self-configuration aspect could determine whether the operations should continue given the current andor predicted windweather conditions. NASA envisions concepts for two types of possible UTM systems. The first type would be a Portable UTM system, which would move from between geographical areas and support operations such as precision agriculture and disaster relief. The second type of system would be a Persistent UTM system, which would support low-altitude operations and provide continuous coverage for a geographical area. Either system would require persistent communication, navigation, and surveillance (CNS) coverage to track, ensure, and monitor conformance. What is NASA doing to test the technologies? NASA's near-term goal is the development and demonstration of a possible future UTM system that could safely enable low-altitude airspace and UAS operations. Working alongside many committed government, industry and academic partners, NASA is leading the research, development and testing that is taking place in a series of activities called Technology Capability Levels (TCL), each increasing in complexity. UTM TCL1 concluded field testing in August 2015 and is undergoing additional testing at an FAA site.

UTM Low-altitude↗

TCL2 Ocean Scenario Replay

This is a video replay of system data that was generated from the UAS Traffic Management (UTM) Technical Capability Level (TCL) 2 flight demonstration in Nevada and rendered in Google Earth. What is depicted in the replay is a particular set of flights conducted as part of what was referred to as the Ocean scenario. The test range and surrounding area are presented followed by an overview of operational volumes. System messaging is also displayed as well as a replay of all of the five test flights as they occurred.

Mohlenbrink, Christoph P.↗

Unmanned Aircraft Systems (UAS) Traffic Management (UTM) National Campaign II

The Unmanned Aircraft System (UAS) Traffic Management (UTM) effort at NASA aims to enable access to low-altitude airspace for small UAS. This goal is being pursued partly through partnerships that NASA has developed with the UAS stakeholder community, the FAA, other government agencies, and the designated FAA UAS Test Sites. By partnering with the FAA UAS Test Sites, NASA's UTM project has performed a geographically diverse, simultaneous set of UAS operations at locations in six states. The demonstrations used an architecture that was developed by NASA in partnership with the FAA to safely coordinate such operations. These demonstrations-the second or 'Technical Capability Level (TCL 2)' National Campaign of UTM testing-was performed from May 15 through June 9, 2017. Multiple UAS operations occurred during the testing at sites located in Alaska, Nevada, Texas, North Dakota, Virginia, and New York with multiple organizations serving as UAS Service Suppliers and/or UAS Operators per the specifications provided by NASA. By engaging various members of the UAS community in development and operational roles, this campaign provided initial validation of different aspects of the UTM concept including: UAS Service Supplier technologies and procedures; geofencing technologies/conformance monitoring; ground-based surveillance/sense and avoid; airborne sense and avoid; communication, navigation, surveillance; and human factors related to UTM data creation and display. Additionally, measures of performance were defined and calculated from the flight data to establish quantitative bases for comparing flight test activities and to provide potential metrics that might be routinely monitored in future operational UTM systems.

Aweiss, Arwa S.↗

Unmanned Aircraft System Traffic Management (UTM) Research Transition Team (RTT) Concept Working Group - Concept & Use Cases Package #2 Addendum: Technical Capability Level 3

This document is a product of the joint NASA and FAA Research Transition Team's (RTT) Concept Working Group (CWG) as part of the UAS Traffic Management (UTM) project. The scope of the document covers Technical Capability Level (TCL) 3 of the UTM research path and presents the 1) Terms and Definitions, 2) Foundational Principles, 3) Concept Narratives, 4) Use Cases, 5) Operational Views (OVs), and 6) Roles and Responsibilities of actors interacting within a TCL3 environment. The document includes additional use cases to accompany the RTT CWG Package #2 document.

UTM↗

UTM UAS Serivce Supplier Development: Sprint 1 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density and large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider(ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the first step in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and the underlying specifications for them, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and proposed specifications for USSs to participate in TCL4. This report describes Sprint One. In this Sprint, the focus was on establishing a baseline for the Application Programming Interfaces (APIs) and their associated data models. In addition, the concept of UAS Volume Reservations (UVR) (areas that impose restrictions on sUAS that are allowed to operate) was tested. NASA provided the specifications and iterated on them with partners while implementers developed to those specifications. NASA then tested each partner's implementation to ensure compatibility with all other implementers. This process helped all stakeholders gain confidence that the foundation for future Sprints was solid.

UAS service supplier↗

UTM UAS Service Supplier Development: Sprint 2 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the UTM Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density environments, large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider (ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the second of four planned steps in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and their underlying specifications, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and develop proposed specifications for USSs in order to to participate in TCL4. This report describes Sprint Two. In this Sprint, there was a major theme with four goals. The theme was the development and testing of a new USS discovery system, to better enable USSs to find and communicate with each other. The goals supporting this theme were: participants needed to implement and exercise the discovery service for USS-USS communications; USSs needed to demonstrate strategic deconfliction through operation sharing; the systems were to use discovery to aid in handling off-nominal operations; and finally, there was an investigation of an initial off-nominal reporting capability.

software engineering↗

Technical Capability Level 2 Unmanned Aircraft System Traffic Management (UTM) Flight Demonstration: Description and Analysis

NASA's UAS Traffic Management (UTM) project concluded its second flight demonstration activity in late October 2016. This activity demonstrated the capabilities and functionality incorporated into its Technical Capability Level 2 (TCL2) concept, which envisions future operations that are low density, capable of being performed over sparsely populated areas, and allow for a concurrent mix of longer duration, beyond visual-line-of-sight flights and shorter flights within visual-line-of-sight (VLOS). To incorporate these features into a flight demonstration, a scenario-based approach was taken to address different aspects of the TCL2 environment and to meet defined objectives. This paper will describe elements of how the flight activity was conducted and present analyses regarding UTM operations, system messages, and alerting as they pertained to meeting the demonstration objectives and shedding light on research questions and lessons learned.NASA was able to successfully demonstrate complex UTMoperations in a TCL 2 environment in collaboration withindustry partners and the Reno-Stead Airport UAS test range.A scenario-based approach to the demonstration provided arelevant means through which the key elements and objectivesof the test could be captured. Although issues were identifiedthrough the testing and feedback of test participants, theoverall results were in line with the overall UTM objective ofsafely enabling large-scale UAS operations in low altitudeairspace.

Homola, Jeffrey↗

Analysis of At-Altitude LTE Power Spectra for C2 Communications for UAS Traffic Management

The National Aeronautics and Space Administration’s (NASA) Unmanned Aircraft Systems Traffic Management (UTM) project works to develop tools and technologies essential for safely enabling civilian low-altitude small Unmanned Aerial Systems (sUAS, also known as drones) operations. This paper presents results of work completed in the paper [1] presented at the 2018 ICNS conference where proposed approaches were explored for evaluating and analyzing sUAS Command and Control (C2) links based on commercial cellular networks. This paper focuses on the UTM Project’s Technology Capability Level 3 (TCL-3) test results which address the communications portion identified within the same paper. A software defined radio (SDR) was flown as a sUAS payload to capture received signal spectrum in Long Term Evolution (LTE) frequency bands of interest. The purpose was to measure the RF environment at UTM altitudes to characterize the interference potential. The SDR payload was flown at various stationary altitudes where the LTE over-the-air complex (I/Q) samples were captured by the SDR and later post-processed. The SDR received inputs through an omnidirectional antenna. The complex samples captured were an aggregate of transmissions received from all line-of-sight (LOS) towers within the geographic area for the specific radio frequency bandwidth the SDR is programmed to capture. Using this approach, the complex samples captured do not distinguish between the various eNodeB's (Long Term Evolution (LTE) transmitting towers). The complex samples were post processed via a Discrete Fourier Transform (DFT) algorithm to view the captured spectrum along with the power levels across the captured LTE bandwidth. This SDR payload process of capturing complex samples was done at two different regions within the US: 1) NASA's Ames Research Center (ARC) in Moffett Field, CA, and 2) Griffiss Airfield in Rome, NY. The data capture at the ARC site was done at two physical locations within the Ames campus where many stationary altitude captures where done as high as 800 ft. above ground level (AGL). The data captured at the Griffiss Airport (also known as the NY Corridor Site) were acquired at one location with three specific stationary altitude levels – {Ground Level (GL), 300 ft., and 400 ft.}. The LTE spectrum power levels were captured for two LTE carriers, AT&T and Verizon, at both sites where their respective spectra and power levels were measured and compared at various altitudes. The overall results show that there is an increase in LTE spectrum power levels at higher altitudes for drones. A detailed analysis of this data and conclusions drawn from the results are presented in this paper.

Kerczewski, Robert J.↗

Unmanned Aircraft Systems (UAS) Traffic Management (UTM) National Campaign II

The Unmanned Aircraft System (UAS) Traffic Management (UTM) effort at NASA aims to enable access to low-altitude airspace for small UAS. This goal is being pursued partly through partnerships that NASA has developed with the UAS stakeholder community, the FAA, other government agencies, and the designated FAA UAS Test Sites. By partnering with the FAA UAS Test Sites, NASA's UTM project has performed a geographically diverse, simultaneous set of UAS operations at locations in six states. The demonstrations used an architecture that was developed by NASA in partnership with the FAA to safely coordinate such operations. These demonstrations—the second or "Technical Capability Level (TCL 2)" National Campaign of UTM testing—was performed from May 15 through June 9, 2017. Multiple UAS operations occurred during the testing at sites located in Alaska, Nevada, Texas, North Dakota, Virginia, and New York with multiple organizations serving as UAS Service Suppliers and/or UAS Operators per the specifications provided by NASA. By engaging various members of the UAS community in development and operational roles, this campaign provided initial validation of different aspects of the UTM concept including: UAS Service Supplier technologies and procedures; geofencing technologies/conformance monitoring; ground-based surveillance/sense and avoid; airborne sense and avoid; communication, navigation, surveillance; and human factors related to UTM data creation and display. Additionally, measures of performance were defined and calculated from the flight data to establish quantitative bases for comparing flight test activities and to provide potential metrics that might be routinely monitored in future operational UTM systems.

Aweiss, Arwa↗

Giving the Public a Perspective into Unmanned Aircraft Systems' Operations

NASA is currently engaged in research to safely enable large-scale commercial applications of small Unmanned Aerial Systems (UAS) in low altitude airspace. This research effort, referred to as UAS Traffic Management (UTM), encompasses the concepts and technologies needed to accommodate the projected demand of UAS operating in the national airspace. One aspect related to the successful implementation of UTM in the future is public acceptance. Transparency will heavily influence this acceptance, and a public portal will provide much of that transparency through ease of access to information about the operations - mainly who, why, and where such operations are taking place. Related concerns to the public are individual privacy, security, and accountability of the operators. Providing the aforementioned information about operations can mitigate these concerns, but a balance will have to be achieved between the need for transparency from the public and the privacy of the operators. The proper balance and the needs of the various UTM stakeholders with regard to information access will be explored through the development and testing of a public portal as part of NASA's Technical Capability 3 (TCL 3) demonstration. Additionally, various approaches to the display of information and user interfaces will be surveyed through the development of a public portal by multiple UTM industry partners across different test sites.

UAS↗