Search NASA⌕ Search

SEARCH · Search NASA

Results for “scripting”

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 631 records · Page 35

SCCS System SW Development

The original project to be completed, GenSim, was a Generic Simulator for Application Control Language scripts. This would mock the systems on which the scripts were meant to be run on so that you could run tests without access to the machine. Soon after the project was started, a different project took priority. Unit testing the Application Services Framework code became the focus of the team because of approaching deadlines. Communication was very important to ensure that code wasn't being duplicated and to keep the team up to date with what mock files are available to them. Because of this, daily meetings were conducted until the testing was complete.

computer programming↗

Unit Testing and Remote Display Development

The Kennedy Space Center is currently undergoing an extremely interesting transitional phase. The final Space Shuttle mission, STS-135, was completed in July of 2011. NASA is now approaching a new era of space exploration. The development of the Orion Multi- Purpose Crew Vehicle (MPCV) and the Space Launch System (SLS) launch vehicle that will launch the Orion are currently in progress. An important part of this transition involves replacing the Launch Processing System (LPS) which was previously used to process and launch Space Shuttles and their associated hardware. NASA is creating the Spaceport Command and Control System (SCCS) to replace the LPS. The SCCS will be much simpler to maintain and improve during the lifetime of the spaceflight program that it will support. The Launch Control System (LCS) is a portion of the SCCS that will be responsible for launching the rockets and spacecraft. The Integrated Launch Operations Applications (ILOA) group of SCCS is responsible for creating displays and scripts, both remote and local, that will be used to monitor and control hardware and systems needed to launch a spacecraft. It is crucial that the software contained within be thoroughly tested to ensure that it functions as intended. Unit tests must be written in Application Control Language (ACL), the scripting language used by LCS. These unit tests must ensure complete code coverage to safely guarantee there are no bugs or any kind of issue with the software.

LCS↗

Cloud-Based Numerical Weather Prediction for Near Real-Time Forecasting and Disaster Response

The use of cloud computing resources continues to grow within the public and private sector components of the weather enterprise as users become more familiar with cloud‐computing concepts, and competition among service providers continues to reduce costs and other barriers to entry. Cloud resources can also provide capabilities similar to high‐performance computing environments, supporting multi‐node systems required for near real‐time, regional weather predictions. Referred to as "Infrastructure as a Service", or IaaS, the use of cloud-based computing hardware in an on‐demand payment system allows for rapid deployment of a modeling system in environments lacking access to a large, supercomputing infrastructure. Use of IaaS capabilities to support regional weather prediction may be of particular interest to developing countries that have not yet established large supercomputing resources, but would otherwise benefit from a regional weather forecasting capability. Recently, collaborators from NASA Marshall Space Flight Center and Ames Research Center have developed a scripted, on‐demand capability for launching the NOAA/NWS Science and Training Resource Center (STRC) Environmental Modeling System (EMS), which includes pre‐compiled binaries of the latest version of the Weather Research and Forecasting (WRF) model. The WRF‐EMS provides scripting for downloading appropriate initial and boundary conditions from global models, along with higher‐resolution vegetation, land surface, and sea surface temperature data sets provided by the NASA Short‐term Prediction Research and Transition (SPoRT) Center. This presentation will provide an overview of the modeling system capabilities and benchmarks performed on the Amazon Elastic Compute Cloud (EC2) environment. In addition, the presentation will discuss future opportunities to deploy the system in support of weather prediction in developing countries supported by NASA's SERVIR Project, which provides capacity building activities in environmental monitoring and prediction across a growing number of regional hubs throughout the world. Capacity‐building applications that extend numerical weather prediction to developing countries are intended to provide near real‐time applications to benefit public health, safety, and economic interests, but may have a greater impact during disaster events by providing a source for local predictions of weather‐related hazards, or impacts that local weather events may have during the recovery phase.

Molthan, Andrew↗

Summary of Aqua, Aura, and Terra High Interest Events

Single-obs tracking Sparsely tracked objects are an unfortunate reality of CARA operations Terra vs. 32081: new track with bad data was included in OD solution for secondary object and risk became high CARA and JSpOC discussed tracking and OSAs threw out the bad data. Event no longer presented high risk based on new OD Improvement: CARA now sends JSpOC a flag indicating when a single obs is included, so OSAs can evaluate if manual update to OD is required. Missing ASW OCMsAura vs. 87178, TCA: 317 at 08:04 UTC. Post-maneuver risk (conjunction was identified in OO results)CARA confirmed with JSpOC that ASW OCMs should have been received in addition to OO OCMsJSpOC corrected the manual error in their script that prevented the data from being delivered to CARAJSpOC QAd their other scripts to ensure this error did not exist in other places.

Conjunction↗

Software Development: 3D Animations and Creating User Interfaces for Realistic Simulations

My fall 2015 semester was spent at the Lyndon B. Johnson Space Center working in the Integrated Graphics, Operations, and Analysis Laboratory (IGOAL). My first project was to create a video animation that could tell the story of OMICS. OMICS is a term being used in the field of biomedical science to describe the collective technologies that study biological systems, such as what makes up a cell and how it functions with other systems. In the IGOAL I used a large 23 inch Wacom monitor to draw storyboards, graphics, and line art animations. I used Blender as the 3D environment to sculpt, shape, cut or modify the several scenes and models for the video. A challenge creating this video was to take a term used in biomedical science and describe it in such a way that an 8th grade student can understand. I used a line art style because it would visually set the tone for what we thought was an educational style. In order to get a handle on the perspective and overall feel for the animation without overloading my workspace, I split up the 2 minute animation into several scenes. I used Blender's python scripting capabilities which allowed for the addition of plugins to add or modify tools. The scripts can also directly interact with the objects to create naturalistic patterns or movements. After collecting the rendered scenes, I used Blender's built-in video editing workspace to output the animation. My second project was to write software that emulates a physical system's interface. The interface was to simulate a boat, ROV, and winch system. Simulations are a time and cost effective way to test complicated data and provide training for operators without having to use expensive hardware. We created the virtual controls with 3-D Blender models and 2-D graphics, and then add functionality in C# using the Unity game engine. The Unity engine provides several essential behaviors of a simulator, such as the start and update functions. A framework for Unity, which was developed in the lab, provided a way to place the different widgets on the virtual console dock and have them resize correctly based on the window dimensions.. My task in this project was to create the controls and visualizations for the data coming in from the simulator for the boat portion of the project. I wrote a class for each control window to handle the functionality of that widget. I implemented 11 widgets that make up the ship portion of the simulator. The members of the lab were each masters of their craft and I'm glad I had the opportunity to learn from them. I learned to plan strategically so I could finish this project on time. I allotted time for storyboarding, development, and refinement. In regards to animating I learned to use modifiers like lattice, boolean and build deformers. I also learned how to animate with drivers, how to use the dope sheet, and how to use the graph editor. In coding I learned to limit the chances for bugs by privatizing functions that should be exclusive to their class. I learned how to use the GIT repository to commit, stash and pull the latest build. I learned a bit of everything because I had the chance to see the entire application development process from the artwork, to the implementation.

Gordillo, Orlando Enrique↗

Space Mobile Network: A Near Earth Communications and Navigation Architecture

This paper shares key findings of NASA's Earth Regime Network Evolution Study (ERNESt) team resulting from its 18-month effort to define a wholly new architecture-level paradigm for the exploitation of space by civil space and commercial sector organizations. Since the launch of Sputnik in October 1957 spaceflight missions have remained highly scripted activities from launch through disposal. The utilization of computer technology has enabled dramatic increases in mission complexity; but, the underlying premise that the diverse actions necessary to meet mission goals requires minute-by-minute scripting, defined weeks in advance of execution, for the life of the mission has remained. This archetype was appropriate for a "new frontier" but now risks overtly constraining the potential market-based opportunities for the innovation considered necessary to efficiently address the complexities associated with meeting communications and navigation requirements projected to be characteristics of the next era of space exploration: a growing number of missions in simultaneous execution, increased variance of mission types and growth in location/orbital regime diversity. The resulting ERNESt architectural cornerstone - the Space Mobile Network (SMN) - was envisioned as critical to creating an environment essential to meeting these future challenges in political, programmatic, technological and budgetary terms. The SMN incorporates technologies such as: Disruption Tolerant Networking (DTN) and optical communications, as well as new operations concepts such as User Initiated Services (UIS) to provide user services analogous to today's terrestrial mobile network user. Results developed in collaboration with NASA's Space Communications and Navigation (SCaN) Division and field centers are reported on. Findings have been validated via briefings to external focus groups and initial ground-based demonstrations. The SMN opens new niches for exploitation by the marketplace of mission planners and service providers.

Space Communication Spacecraft↗

Ocular Coherence Tomography in the Evaluation of Anterior Eye Injuries in Space Flight

While Ocular Coherence Tomography (OCT) is not a first-line modality to evaluate anterior eye structures terrestrially, it is a resource already available on the International Space Station (ISS) that can be used in medical contingencies that involve the anterior eye. With remote guidance and subject matter expert (SME) support from the ground, a minimally trained crewmember can now use OCT to evaluate anterior eye pathologies on orbit. OCT utilizes low-coherence interferometry to produce detailed cross-sectional and 3D images of the eye in real time. Terrestrially, it has been used to evaluate macular pathologies and glaucoma. Since 2013, OCT has been used onboard the ISS as one part of a suite of hardware to evaluate the Visual Impairment/Intracranial Pressure risk faced by astronauts, specifically assessing changes in the retina and choroid during space flight. The Anterior Segment Module (ASM), an add-on lens, was also flown for research studies, providing an opportunity to evaluate the anterior eye in real time if clinically indicated. Anterior eye pathologies that could be evaluated using OCT were identified. These included corneal abrasions and ulcers, scleritis, and acute angle closure glaucoma. A remote guider script was written to provide ground specialists with step-by-step instructions to guide ISS crewmembers, who do not get trained on the ASM, to evaluate the anterior eye. The instructions were tested on novice subjects and/or operators, whose feedback was incorporated iteratively. The final remote guider script was reviewed by SME optometrists and NASA flight surgeons. The novel application of OCT technology to space flight allows for the acquisition of objective data to diagnose anterior eye pathologies when other modalities are not available. This demonstrates the versatility of OCT and highlights the advantages of using existing hardware and remote guidance skills to expand clinical capabilities in space flight.

Fer, Dan M.↗

UAS in the NAS Flight Test Series 4 Overview

Flight Test Series 4 (FT4) provides the researchers with an opportunity to expand on the data collected during the first flight tests. Following Flight Test Series 3, additional scripted encounters with different aircraft performance and sensors will be conducted. FT4 is presently planned for Spring of 2016 to ensure collection of data to support the validation of the final RTCA Phase 1 DAA (Detect and Avoid) Minimum Operational Performance Standards (MOPS). There are three research objectives associated with this goal: Evaluate the performance of the DAA system against cooperative and non-cooperative aircraft encounters Evaluate UAS (Unmanned Aircraft Systems) pilot performance in response to DAA maneuver guidance and alerting with live intruder encounters Evaluate TCAS/DAA (Traffic Alert and Collision Avoidance System/Detect and Avoid) interoperability. This flight test series will focus on only the Scripted Encounters configuration, supporting the collection of data to validate the interoperability of DAA and collision avoidance algorithms.

flight test↗

A Dose of Reality: Radiation Analysis for Realistic Human Spacecraft

INTRODUCTION As with most computational analyses, a tradeoff exists between problem complexity, resource availability and response accuracy when modeling radiation transport from the source to a detector. The largest amount of analyst time for setting up an analysis is often spent ensuring that any simplifications made have minimal impact on the results. The vehicle shield geometry of interest is typically simplified from the original CAD design in order to reduce computation time, but this simplification requires the analyst to "re-draw" the geometry with a limited set of volumes in order to accommodate a specific radiation transport software package. The resulting low-fidelity geometry model cannot be shared with or compared to other radiation transport software packages, and the process can be error prone with increased model complexity. The work presented here demonstrates the use of the DAGMC (Direct Accelerated Geometry for Monte Carlo) Toolkit from the University of Wisconsin, to model the impacts of several space radiation sources on a CAD drawing of the US Lab module. METHODS The DAGMC toolkit workflow begins with the export of an existing CAD geometry from the native CAD to the ACIS format. The ACIS format file is then cleaned using SpaceClaim to remove small holes and component overlaps. Metadata is then assigned to the cleaned geometry file using CUBIT/Trelis from csimsoft (Registered Trademark). The DAGMC plugin script removes duplicate shared surfaces, facets the geometry to a specified tolerance, and ensures that the faceted geometry is water tight. This step also writes the material and scoring information to a standard input file format that the analyst can alter as desired prior to running the radiation transport program. The scoring results can be transformed, via python script, into a 3D format that is viewable in a standard graphics program. RESULTS The CAD model of the US Lab module of the International Space Station, inclusive of all the racks and components, was simplified to remove holes and volume overlaps. Problematic features within the drawing were also removed or repaired to prevent runtime issues. The cleaned drawing was then run through the DAGMC workflow to prepare for analysis. Pilot tests modeling transport of 1GeV proton and 800MeV/A oxygen sources show that reasonable results are converged upon in an acceptable amount of overall computation time from drawing preparation to data analysis. The FLUKA radiation transport code will next be used to model both a GCR and a trapped radiation source. These results will then be compared with measurements that have been made by the radiation instrumentation deployed inside the US Lab module. DISCUSSION Early analyses have indicated that the DAGMC workflow is a promising toolkit for running vehicle geometries of interest to NASA through multiple radiation transport codes. In addition, recent work has shown that a realistic human phantom, provided via a subcontract with the University of Florida, can be placed inside any vehicle geometry for a combinatorial analysis. This added functionality gives the user the ability to score various parameters at the organ level, and the results can then be used as input for cancer risk models.

Barzilla, J. E.↗

Update: Advancement of Contact Dynamics Modeling for Human Spaceflight Simulation Applications

Pong is a new software tool developed at the NASA Johnson Space Center that advances interference-based geometric contact dynamics based on 3D graphics models. The Pong software consists of three parts: a set of scripts to extract geometric data from 3D graphics models, a contact dynamics engine that provides collision detection and force calculations based on the extracted geometric data, and a set of scripts for visualizing the dynamics response with the 3D graphics models. The contact dynamics engine can be linked with an external multibody dynamics engine to provide an integrated multibody contact dynamics simulation. This paper provides a detailed overview of Pong including the overall approach and modeling capabilities, which encompasses force generation from contact primitives and friction to computational performance. Two specific Pong-based examples of International Space Station applications are discussed, and the related verification and validation using this new tool are also addressed.

Contact dynamics↗

Software Verification of Orion Cockpit Displays

NASA's latest spacecraft Orion is in the development process of taking humans deeper into space. Orion is equipped with three main displays to monitor and control the spacecraft. To ensure the software behind the glass displays operates without faults, rigorous testing is needed. To conduct such testing, the Rapid Prototyping Lab at NASA's Johnson Space Center along with the University of Texas at Tyler employed a software verification tool, EggPlant Functional by TestPlant. It is an image based test automation tool that allows users to create scripts to verify the functionality within a program. A set of edge key framework and Common EggPlant Functions were developed to enable creation of scripts in an efficient fashion. This framework standardized the way to code and to simulate user inputs in the verification process. Moreover, the Common EggPlant Functions can be used repeatedly in verification of different displays.

Biswas, M. A. Rafe↗

MagicDraw Report Generation for the Resource Prospector Payload

Magic Draw is a tool currently being used by System Engineers to design model-based representations of the Resource Prospector (RP) Payload. Often, reports are needed to display and communicate the information and schematics within the MagicDraw model. Since constant changes are being made to the model, these reports also need to be maintained with each change. Because this is tedious and time consuming, I was assigned to implement MagicDraw Report Wizard Templates using Velocity Template Language (VTL) scripts. These report template scripts pull specific images, data, and elements directly from the MagicDraw model, allowing the user to have a report that is updated with the current state of the model upon its generation.

MagicDraw↗

Research and Development of The Immersive Simulations and Engineering Environment

March of 2018 marked the conclusion of the primary updates to the immersive Simulations and Engineering Environment (iSEE) at Kennedy Space Center (KSC). Many of the problems that had arisen during the previous semester have been addressed and rectified. These included the malfunction to one of the lab's primary routers, the inefficiency of the capture environment, and various interface issues in the analysis software, Jack. This semester was primarily research and development oriented with some focus on implementation of the new hardware and software that was received last semester. The new computers and cameras that arrived sometime during the winter were installed, and the lab received its second operation opportunity. The second operation was a major milestone for the lab, both in terms of what the abilities were and what can be learned from its use. The operation performed was a virtual simulation of a critical task that would occur, if it should be needed, in the Multi Payload Processing Facility. It was done to gather human factors data on its safety and process controls. The technicians were able to come to a number of conclusions about how to perform their task as a result of utilizing iSEE. Another key breakthrough this semester was the introduction to Jack Script, a scripting language built into our analysis software that further extend Jack capabilities. In addition to the aforementioned, many preparations were made for family day, an exposition for KSC families to come out and tour the spaceport. Due to family day being moved to the spring, the video made last fall had to be updated with recent environment changes in preparation for the Family Day demonstrations.

Motion Capture↗

Multi-UAS HITL: Primary Results & Automation Workshop Summaries

This presentation covers the primary results from a recently completed human-in-the-loop (HITL) simulation conducted as part of the UAS (Unmanned Aircraft System) integration into the NAS (National Airspace System) project. The HITL examined the impact of multiple (simultaneous) UAS control while performing a demanding mission task and managing scripted conflicts. The scripted conflicts were designed to trigger the detect-and-avoid (DAA) system. This was the first time the DAA system as designed as part of the UAS-NAS project has been applied to multi-UAS control. The second part of the presentation briefly summarizes the takeaways from two workshops held on human-automation interaction considerations for UAS integration. NASA co-hosted and participated in both workshops.

unmanned aircraft systems↗

Multi UAS Demo System Example Video

This presentation covers the primary results from a recently completed human-in-the-loop (HITL) simulation conducted as part of the UAS (Unmanned Aircraft Systems) integration into the NAS (National Airspace System) project. The HITL examined the impact of multiple (simultaneous) UAS control while performing a demanding mission task and managing scripted conflicts. The scripted conflicts were designed to trigger the detect-and-avoid (DAA) system. This was the first time the DAA system as designed as part of the UAS-NAS project has been applied to multi-UAS control. The second part of the presentation briefly summarizes the takeaways from two workshops held on human-automation interaction considerations for UAS integration. NASA co-hosted and participated in both workshops.

Rorie, Robert C.↗

Julia Programming Language Benchmark Using a Flight Simulation

Julia’s goal to provide scripting language ease-of-coding with compiled language speed is explored. The runtime speed of the relatively new Julia programming language is assessed against other commonly used languages including Python, Java, and C++. An industry-standard missile and rocket simulation, coded in multiple languages, was used as a test bench for runtime speed. All language versions of the simulation, including Julia, were coded to a highly-developed object-oriented simulation architecture tailored specifically for time-domain flight simulation. A “speed-of-coding” second-dimension is plotted against runtime for each language to portray a space that characterizes Julia’s scripting language efficiencies in the context of the other languages. With caveats, Julia runtime speed was found to be in the class of compiled or semi-compiled languages. However, some factors that affect runtime speed at the cost of ease-of-coding are shown. Julia’s built-in functionality for multi-core processing is briefly examined as a means for obtaining even faster runtime speed. The major contribution of this research to the extensive language benchmarking body-of-work is comparing Julia to other mainstream languages using a complex flight simulation as opposed to benchmarking with single algorithms.

Sells, Ray↗

Abrstract - OnePlace Redesign Spring 2020 Internship

The project I worked on was the OnePlace Redesign. In that, I converted the OnePlace home page to the Service Portal to match NASA OnePlace’s current application design standards, I was able to allow users to easily find applications in OnePlace and I was able to allow users to easily find and request OnePlace services (new app development, new knowledge base, etc.). It was a major accomplishment to be able to remodel a website that soon the entire Langley center that uses OnePlace will use. The website was made through ServiceNow’s Service Portal, and I organized the applications like never before, allowed a clear styling to applications a user does not have access to and/or are new applications, browsing of applications with clear button divisions, and allowing for different options depending if app is accessible or not, with proper error checking in place and very-well documented code. It was amazing to incorporate all this logic into one widget so that whoever wants to utilize this feature has no trouble at all to do so. The 3 most important things I learned were being able to do this work within ServiceNow, as it is such an important enterprise platform for CRM and boosting the connected workforce of NASA, incorporate built-in APIs from ServiceNow Glide Records to connect Server Scripts to Client Scripts and HTML, and be able to use agile to get another experience of managing work capacity with stories, and having proper communication with the team if every feature is done correctly and steps for continuing forward. The part that I enjoyed the most was the training I did for ServiceNow and I freedom I had to experiment to see how to structure the Service Portal. I was not tied down, and I believe this allowed for a better outcome of the product. As part of the internship, I created a very in-depth design document with the help of my team to document the project goals before it was started and technical documentation (including the design document) summarizing the final result of the product in terms of the new features added and the explanation of the logic thoroughly so that anyone can understand the project easily. The technical documentation will be published as a Knowledge Article within OnePlace Knowledge Base documentation.

Ariel Wald↗

UAS Integration in the NAS Project: Overview of Flight Test Series 6

The National Aeronautics and Space Administration (NASA) Unmanned Aircraft Systems Integration in the National Airspace System (UAS-NAS) Project has conducted a series of flight test campaigns intended to support the reduction of barriers that prevent unmanned aircraft from flying without the required waivers from the Federal Aviation Administration (FAA). The 2019 Flight Test Series 6 (FT6) campaign furthered this path and supported three test configurations: 1) Radar Characterization, 2) Scripted Encounters and 3) Full Mission. Radar Characterization assessed the performance of Honeywell’s low size, weight, and power (low SWaP) radar system; Scripted Encounters investigated the timing of Detect and Avoid (DAA) alerting thresholds using a Department of Defense (DoD) Group 3 unmanned aircraft system (UAS) equipped with low SWaP sensors and three different live intruder aircraft flown at varying encounter geometries; and Full Mission validated human-in-the-loop simulations by collecting pilot performance data from a ground control station while controlling a live unmanned aircraft on a mission in both virtual and live air traffic controlled airspace. The subject pilot observed a research display that presented DAA advisories to maintain separation from live and virtual aircraft. The test was conducted over a twenty-week period within the R-2508 special use airspace located near Edwards Air Force Base (EAFB), CA. Over 240 encounters were flown during the test series and FT6 proved to be invaluable for the purposes of planning, managing, and executing this type of integrated flight test in both live and virtual environments. Data collected from FT6 was provided to the RTCA Special Committee 228 (SC-228) to help inform the Phase 2 Minimum Operational Performance Standards (MOPS). FT6 was the final test series for the UAS-NAS project that began in 2012. This paper provides an overview of FT6 and its success can be directly attributed to the diligent work of the men and women who supported this effort.

UAS in the NAS↗