Members Can Post Anonymously On This Site
-
Similar Topics
-
By NASA
Chris Wade is a visiting vehicle integration manager for SpaceX vehicles in the International Space Station Transportation Integration Office. He plays a key role in ensuring that all vehicle requirements are on track to support SpaceX missions to the space station. Chris also manages a team of real-time mission support personnel who follow launch, docking, undocking, and splashdown operations. Read on to learn about his career with NASA and more!
Where are you from?
I am from Clarksdale, Mississippi.
Tell us about your role at NASA.
I manage horizontal integration between the SpaceX vehicle provider and the Commercial Crew and International Space Station Programs. In this role, I work to ensure all vehicle requirements will close in time to support upcoming SpaceX missions to the orbiting laboratory and achieve final certification prior to launch. Additionally, as a vehicle integration manager, I manage a team of real-time mission support personnel who follow launch, docking, undocking, and splashdown operations.
Chris Wade in Mission Control Center at Johnson Space Center following the arrival of a visiting vehicle to the International Space Station. I enjoy telling people that we have a space station that has been in low Earth orbit with people on it for nearly 25 years.
cHRIS wade
Visiting Vehicle Integration Manager for SpaceX Vehicles
How would you describe your job to family or friends who may not be familiar with NASA?
In my current position, I am responsible for ensuring SpaceX Dragon vehicles have met all requirements to conduct missions to the space station.
How long have you been working for NASA?
I have been working at Johnson Space Center for 25 years.
What advice would you give to young individuals aspiring to work in the space industry or at NASA?
I would advise young individuals to focus their studies on the STEM fields and work hard. I would also advise aspiring candidates to start applying for NASA internships as soon as feasible and don’t be opposed to opportunities in the contractor workforce.
What was your path to NASA?
My path to NASA was through the contractor workforce. I started working in space station robotic assembly analysis for Lockheed Martin directly out of college, then later became a civil servant at NASA.
Is there someone in the space, aerospace, or science industry that motivated or inspired you to work for the space program? Or someone you discovered while working for NASA who inspires you?
The Space Shuttle Challenger STS-51-L crew motivated me to pursue a career at NASA. I vividly remember watching the launch from an elementary classroom in Mississippi and thinking, I wish I could do something to help one day. When I got an opportunity to work at Johnson, it was a no-brainer for me to accept the offer.
What is your favorite NASA memory?
My favorite NASA memory is when I saw my first rocket launch, which was HTV-1 in Kagoshima, Japan.
Chris Wade accepting a group achievement award as a member of the Latching End Effector Return Team with Johnson Space Center’s Deputy Center Director Vanessa Wyche and Center Director Mark Geyer in 2019.NASA/Robert Markowitz What do you love sharing about station? What’s important to get across to general audiences to help them understand its benefits to life on Earth?
I enjoy telling people that we have a space station that has been in low Earth orbit with people on it for nearly 25 years and we rotate crews of astronauts every six months.
If you could have dinner with any astronaut, past or present, who would it be?
I would have dinner with NASA astronaut Ron McNair. Growing up in a small southern town, my path to NASA was very similar to his. I find it fascinating how individuals from different eras can end up on similar paths in life, and I would love to have a conversation with him about the choices he made that lead to his career as an astronaut.
Do you have a favorite space-related memory or moment that stands out to you?
My favorite space-related memory is watching the SpaceX Demo-2 Crew Mission arrive at the International Space Station. That was the first launch of NASA astronauts from American soil since the Space Shuttle Program had ended almost 10 years prior.
What are some of the key projects you’ve worked on during your time at NASA? What have been your favorite?
Some of the key projects I’ve worked on include:
Robotic assembly of the International Space Station Robotic visiting vehicle capture Cargo and crew dragon visiting vehicle mission certification Of these, my favorite was the robotic visiting vehicle capture project. For this project, I got to work with the Canadian Space Agency and develop a method of using the space station’s robotic arm to grab unmanned visiting resupply vehicles.
Chris Wade at Kennedy Space Center in front of NASA’s Space Launch System rocket with the Orion spacecraft aboard atop a mobile launcher at Launch Complex 39B. What are your hobbies/things you enjoy outside of work?
Some of my favorite hobbies include running, reading, listening to audio books, and visiting family and friends back in Mississippi.
Day launch or night launch?
Day launch!
Favorite space movie?
Armageddon
NASA “worm” or “meatball” logo?
Worm
Every day, we’re conducting exciting research aboard our orbiting laboratory that will help us explore further into space and bring benefits back to people on Earth. You can keep up with the latest news, videos, and pictures about space station science on the Station Research & Technology news page. It’s a curated hub of space station research digital media from Johnson and other centers and space agencies.
Sign up for our weekly email newsletter to get the updates delivered directly to you.
Follow updates on social media at @ISS_Research on Twitter, and on the space station accounts on Facebook and Instagram.
View the full article
-
By NASA
NASA’s Ames Research Center in Silicon Valley invites media to learn more about Distributed Spacecraft Autonomy (DSA), a technology that allows individual spacecraft to make independent decisions while collaborating with each other to achieve common goals – without human input. The DSA team achieved multiple firsts during tests of such swarm technology as part of the agency’s project.
DSA develops software tools critical for future autonomous, distributed, and intelligent spacecraft that will need to interact with each other to achieve complex mission objectives. Testing onboard the agency’s Starling mission resulted in accomplishments including the first fully distributed autonomous operation of multiple spacecraft, the first use of space-to-space communications to autonomously share status information between multiple spacecraft, and more.
DSA’s accomplishments mark a significant milestone in advancing autonomous systems that will make new types of science and exploration possible.
Caleb Adams, DSA project manager, is available for interview on Wednesday, Feb. 5 and Thursday, Feb. 6. To request an interview, media can contact the Ames Office of Communications by email at arc-dl-newsroom@nasa.gov or by phone at 650-604-4789.
Learn more about NASA Ames’ world-class research and development in aeronautics, science, and exploration technology at:
https://www.nasa.gov/ames
-end-
Tiffany Blake
Ames Research Center, Silicon Valley
650-604-4789
tiffany.n.blake@nasa.gov
To receive local NASA Ames news, email local-reporters-request@lists.arc.nasa.gov with “subscribe” in the subject line. To unsubscribe, email the same address with “unsubscribe” in the subject line.
View the full article
-
By NASA
1 min read
Preparations for Next Moonwalk Simulations Underway (and Underwater)
The Airspace Operations and Safety Program (AOSP) enables safe, sustainable, and efficient aviation transportation operations to benefit the flying public and ensure the global competitiveness of the U.S. aviation industry. We are transforming the future of aviation into a digital, federated, and service-oriented architecture that fosters the growth of safe airspace for all users.
By partnering with FAA, academia, safety experts, operators, manufacturers, municipalities, and other government agencies, we facilitate the integration of new aviation technologies, ensure airspace access for new entrants, and champion the success of increasingly autonomous operations. At AOSP, safety is at the heart of everything we do. We stand firm in our unwavering commitment to the safe integration of these vehicles.
AOSP Approach:
Efficient, Sustainable Aviation Operations Seamless Integration of Heterogeneous and Emergent Aviation Prognostic In-Time Aviation Safety Management System of Future Operations System Level Autonomy for Aviation Operations, Vehicle Command and Control Systems, and Safety Meet the diversity, density, and complexity challenges of future aviation AOSP Projects
Advanced Capabilities for Emergency Response Operations Project
Air Mobility Pathfinders
Air Traffic Management—Exploration (ATM-X)
System-Wide Safety (SWS)
Facebook logo @NASA@NASAaero@NASA_es @NASA@NASAaero@NASA_es Instagram logo @NASA@NASAaero@NASA_es Linkedin logo @NASA Explore More
2 min read Media Invited to Speak to NASA Ames Experts – Celebrating 85 Years
Article 2 hours ago 3 min read NASA Sees Progress on Starlab Commercial Space Station Development
Article 24 hours ago 4 min read Helium Conservation by Diffusion Limited Purging of Liquid Hydrogen Tanks
Article 5 days ago Keep Exploring Discover More Topics From NASA
Missions
Humans In Space
Solar System Exploration
Solar System Overview Our solar system has one star, eight planets, five officially named dwarf planets, hundreds of moons, thousands…
Explore NASA’s History
Share
Details
Last Updated Dec 17, 2024 EditorLillian GipsonContactJim Bankejim.banke@nasa.gov Related Terms
General View the full article
-
By NASA
This article is from the 2024 Technical Update
Autonomous flight termination systems (AFTS) are being progressively employed onboard launch vehicles to replace ground personnel and infrastructure needed to terminate flight or destruct the vehicle should an anomaly occur. This automation uses on-board real-time data and encoded logic to determine if the flight should be self-terminated. For uncrewed launch vehicles, FTS systems are required to protect the public and governed by the United States Space Force (USSF). For crewed missions, NASA must augment range AFTS requirements for crew safety and certify each flight according to human rating standards, thus adding unique requirements for reuse of software originally intended for uncrewed missions. This bulletin summarizes new information relating to AFTS to raise awareness of key distinctions, summarize considerations and outline best practices for incorporating AFTS into human-rated systems.
Key Distinctions – Crewed v. Uncrewed
There are inherent behavioral differences between uncrewed and crewed AFTS related to design philosophy and fault tolerance. Uncrewed AFTS generally favor fault tolerance against failure-to-destruct over failing silent
in the presence of faults. This tenet permeates the design, even downto the software unit level. Uncrewed AFTS become zero-fault-to-destruct tolerant to many unrecoverable AFTS errors, whereas general single fault
tolerance against vehicle destruct is required for crewed missions. Additionally, unique needs to delay destruction for crew escape, provide abort options and special rules, and assess human-in-the-loop insight, command, and/or override throughout a launch sequence must be considered and introduces additional requirements and integration complexities.
AFTS Software Architecture Components and Best-Practice Use Guidelines
A detailed study of the sole AFTS currently approved by USSF and utilized/planned for several launch vehicles was conducted to understand its characteristics, and any unique risk and mitigation techniques for effective human-rating reuse. While alternate software systems may be designed in the future, this summary focuses on an architecture employing the Core Autonomous Safety Software (CASS). Considerations herein are intended for extrapolation to future systems. Components of the AFTS software architecture are shown, consisting of the CASS, “Wrapper”, and Mission Data Load (MDL) along with key characteristics and use guidelines. A more comprehensive description of each and recommendations for developmental use is found in Ref. 1.
Best Practices Certifying AFTS Software
Below are non-exhaustive guidelines to help achieve a human-rating
certification for an AFTS.
References
NASA/TP-20240009981: Best Practices and Considerations for Using
Autonomous Flight Termination Software In Crewed Launch Vehicles
https://ntrs.nasa.gov/citations/20240009981 “Launch Safety,” 14 C.F.R., § 417 (2024). NPR 8705.2C, Human-Rating Requirements for Space Systems, Jul 2017,
nodis3.gsfc.nasa.gov/ NASA Software Engineering Requirements, NPR 7150.2D, Mar 2022,
nodis3.gsfc.nasa.gov/ RCC 319-19 Flight Termination Systems Commonality Standard, White
Sands, NM, June 2019. “Considerations for Software Fault Prevention and Tolerance”, NESC
Technical Bulletin No. 23-06 https://ntrs.nasa.gov/citations/20230013383 “Safety Considerations when Repurposing Commercially Available Flight
Termination Systems from Uncrewed to Crewed Launch Vehicles”, NESC
Technical Bulletin No. 23-02 https://ntrs.nasa.gov/citations/20230001890 View the full article
-
By NASA
9 Min Read Towards Autonomous Surface Missions on Ocean Worlds
Artist’s concept image of a spacecraft lander with a robot arm on the surface of Europa. Credits:
NASA/JPL – Caltech Through advanced autonomy testbed programs, NASA is setting the groundwork for one of its top priorities—the search for signs of life and potentially habitable bodies in our solar system and beyond. The prime destinations for such exploration are bodies containing liquid water, such as Jupiter’s moon Europa and Saturn’s moon Enceladus. Initial missions to the surfaces of these “ocean worlds” will be robotic and require a high degree of onboard autonomy due to long Earth-communication lags and blackouts, harsh surface environments, and limited battery life.
Technologies that can enable spacecraft autonomy generally fall under the umbrella of Artificial Intelligence (AI) and have been evolving rapidly in recent years. Many such technologies, including machine learning, causal reasoning, and generative AI, are being advanced at non-NASA institutions.
NASA started a program in 2018 to take advantage of these advancements to enable future icy world missions. It sponsored the development of the physical Ocean Worlds Lander Autonomy Testbed (OWLAT) at NASA’s Jet Propulsion Laboratory in Southern California and the virtual Ocean Worlds Autonomy Testbed for Exploration, Research, and Simulation (OceanWATERS) at NASA’s Ames Research Center in Silicon Valley, California.
NASA solicited applications for its Autonomous Robotics Research for Ocean Worlds (ARROW) program in 2020, and for the Concepts for Ocean worlds Life Detection Technology (COLDTech) program in 2021. Six research teams, based at universities and companies throughout the United States, were chosen to develop and demonstrate autonomy solutions on OWLAT and OceanWATERS. These two- to three-year projects are now complete and have addressed a wide variety of autonomy challenges faced by potential ocean world surface missions.
OWLAT
OWLAT is designed to simulate a spacecraft lander with a robotic arm for science operations on an ocean world body. The overall OWLAT architecture including hardware and software components is shown in Figure 1. Each of the OWLAT components is detailed below.
Figure 1. The software and hardware components of the Ocean Worlds Lander Autonomy Testbed and the relationships between them. NASA/JPL – Caltech The hardware version of OWLAT (shown in Figure 2) is designed to physically simulate motions of a lander as operations are performed in a low-gravity environment using a six degrees-of-freedom (DOF) Stewart platform. A seven DOF robot arm is mounted on the lander to perform sampling and other science operations that interact with the environment. A camera mounted on a pan-and-tilt unit is used for perception. The testbed also has a suite of onboard force/torque sensors to measure motion and reaction forces as the lander interacts with the environment. Control algorithms implemented on the testbed enable it to exhibit dynamics behavior as if it were a lightweight arm on a lander operating in different gravitational environments.
Figure 2. The Ocean Worlds Lander Autonomy Testbed. A scoop is mounted to the end of the testbed robot arm. NASA/JPL – Caltech The team also developed a set of tools and instruments (shown in Figure 3) to enable the performance of science operations using the testbed. These various tools can be mounted to the end of the robot arm via a quick-connect-disconnect mechanism. The testbed workspace where sampling and other science operations are conducted incorporates an environment designed to represent the scene and surface simulant material potentially found on ocean worlds.
Figure 3. Tools and instruments designed to be used with the testbed. NASA/JPL – Caltech The software-only version of OWLAT models, visualizes, and provides telemetry from a high-fidelity dynamics simulator based on the Dynamics And Real-Time Simulation (DARTS) physics engine developed at JPL. It replicates the behavior of the physical testbed in response to commands and provides telemetry to the autonomy software. A visualization from the simulator is shown on Figure 4.
To view this video please enable JavaScript, and consider upgrading to a web browser that
supports HTML5 video
Figure 7. Screenshot of OceanWATERS lander on a terrain modeled from the Atacama Desert. A scoop operation has just been completed. NASA/JPL – Caltech The autonomy software module shown at the top in Figure 1 interacts with the testbed through a Robot Operating System (ROS)-based interface to issue commands and receive telemetry. This interface is defined to be identical to the OceanWATERS interface. Commands received from the autonomy module are processed through the dispatcher/scheduler/controller module (blue box in Figure 1) and used to command either the physical hardware version of the testbed or the dynamics simulation (software version) of the testbed. Sensor information from the operation of either the software-only or physical testbed is reported back to the autonomy module using a defined telemetry interface. A safety and performance monitoring and evaluation software module (red box in Figure 1) ensures that the testbed is kept within its operating bounds. Any commands causing out of bounds behavior and anomalies are reported as faults to the autonomy software module.
Figure 5. Erica Tevere (at the operator’s station) and Ashish Goel (at the robot arm) setting up the OWLAT testbed for use. NASA/JPL – Caltech OceanWATERS
At the time of the OceanWATERS project’s inception, Jupiter’s moon Europa was planetary science’s first choice in searching for life. Based on ROS, OceanWATERS is a software tool that provides a visual and physical simulation of a robotic lander on the surface of Europa (see Figure 6). OceanWATERS realistically simulates Europa’s celestial sphere and sunlight, both direct and indirect. Because we don’t yet have detailed information about the surface of Europa, users can select from terrain models with a variety of surface and material properties. One of these models is a digital replication of a portion of the Atacama Desert in Chile, an area considered a potential Earth-analog for some extraterrestrial surfaces.
Figure 6. Screenshot of OceanWATERS. NASA/JPL – Caltech JPL’s Europa Lander Study of 2016, a guiding document for the development of OceanWATERS, describes a planetary lander whose purpose is collecting subsurface regolith/ice samples, analyzing them with onboard science instruments, and transmitting results of the analysis to Earth.
The simulated lander in OceanWATERS has an antenna mast that pans and tilts; attached to it are stereo cameras and spotlights. It has a 6 degree-of-freedom arm with two interchangeable end effectors—a grinder designed for digging trenches, and a scoop for collecting ground material. The lander is powered by a simulated non-rechargeable battery pack. Power consumption, the battery’s state, and its remaining life are regularly predicted with the Generic Software Architecture for Prognostics (GSAP) tool. To simulate degraded or broken subsystems, a variety of faults (e.g., a frozen arm joint or overheating battery) can be “injected” into the simulation by the user; some faults can also occur “naturally” as the simulation progresses, e.g., if components become over-stressed. All the operations and telemetry (data measurements) of the lander are accessible via an interface that external autonomy software modules can use to command the lander and understand its state. (OceanWATERS and OWLAT share a unified autonomy interface based on ROS.) The OceanWATERS package includes one basic autonomy module, a facility for executing plans (autonomy specifications) written in the PLan EXecution Interchange Language, or PLEXIL. PLEXIL and GSAP are both open-source software packages developed at Ames and available on GitHub, as is OceanWATERS.
Mission operations that can be simulated by OceanWATERS include visually surveying the landing site, poking at the ground to determine its hardness, digging a trench, and scooping ground material that can be discarded or deposited in a sample collection bin. Communication with Earth, sample analysis, and other operations of a real lander mission, are not presently modeled in OceanWATERS except for their estimated power consumption. Figure 7 is a video of OceanWATERS running a sample mission scenario using the Atacama-based terrain model.
To view this video please enable JavaScript, and consider upgrading to a web browser that
supports HTML5 video
Figure 7. Screenshot of OceanWATERS lander on a terrain modeled from the Atacama Desert. A scoop operation has just been completed. NASA/JPL – Caltech Because of Earth’s distance from the ocean worlds and the resulting communication lag, a planetary lander should be programmed with at least enough information to begin its mission. But there will be situation-specific challenges that will require onboard intelligence, such as deciding exactly where and how to collect samples, dealing with unexpected issues and hardware faults, and prioritizing operations based on remaining power.
Results
All six of the research teams funded by the ARROW and COLDTech programs used OceanWATERS to develop ocean world lander autonomy technology and three of those teams also used OWLAT. The products of these efforts were published in technical papers, and resulted in development of software that may be used or adapted for actual ocean world lander missions in the future. The following table summarizes the ARROW and COLDTech efforts.
Principal Investigator (PI) PI Institution Project Testbed Used Purpose of Project ARROW Projects Jonathan Bohren Honeybee Robotics Stochastic PLEXIL (SPLEXIL) OceanWATERS Extended PLEXIL with stochastic decision-making capabilities by employing reinforcement learning techniques. Pooyan Jamshidi University of South Carolina Resource Adaptive Software Purpose-Built for Extraordinary Robotic Research Yields (RASPBERRY SI) OceanWATERS & OWLAT Developed software algorithms and tools for fault root cause identification, causal debugging, causal optimization, and causal-induced verification. COLDTech Projects Eric Dixon Lockheed Martin Causal And Reinforcement Learning (CARL) for COLDTech OceanWATERS Integrated a model of JPL’s mission-ready Cold Operable Lunar Deployable Arm (COLDarm) into OceanWATERS and applied image analysis, causal reasoning, and machine learning models to identify and mitigate the root causes of faults, such as ice buildup on the arm’s end effector. Jay McMahon University of Colorado Robust Exploration with Autonomous Science On-board, Ranked Evaluation of Contingent Opportunities for Uninterrupted Remote Science Exploration (REASON-RECOURSE) OceanWATERS Applied automated planning with formal methods to maximize science return of the lander while minimizing communication with ground team on Earth. Melkior Ornik U Illinois, Urbana-Champaign aDaptive, ResIlient Learning-enabLed oceAn World AutonomY (DRILLAWAY) OceanWATERS & OWLAT Developed autonomous adaptation to novel terrains and selecting scooping actions based on the available image data and limited experience by transferring the scooping procedure learned from a low-fidelity testbed to the high-fidelity OWLAT testbed. Joel Burdick Caltech Robust, Explainable Autonomy for Scientific Icy Moon Operations (REASIMO) OceanWATERS & OWLAT Developed autonomous 1) detection and identification of off-nominal conditions and procedures for recovery from those conditions, and 2) sample site selection Acknowledgements: The portion of the research carried out at the Jet Propulsion Laboratory, California Institute of Technology was performed under a contract with the National Aeronautics and Space Administration (80NM0018D0004). The portion of the research carried out by employees of KBR Wyle Services LLC at NASA Ames Research Center was performed under a contract with the National Aeronautics and Space Administration (80ARC020D0010). Both were funded by the Planetary Science Division ARROW and COLDTech programs.
Project Leads: Hari Nayar (NASA Jet Propulsion Laboratory, California Institute of Technology), K. Michael Dalal (KBR, Inc. at NASA Ames Research Center)
Sponsoring Organizations: NASA SMD PESTO
View the full article
-
-
Check out these Videos
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.