Kirjahaku

This book covers the topic of the technology and applications of Embedded Graphics Processing Units. We first discuss what a graphics processing unit is, and how they have taken over the high performance computing market. We take a look at massively parallel microprocessor-based systems, an evolution from parallel mainframes, and see how this is applied to GPU's. Then, we take a look at embedded processors, derived from CPU's, and how multicore architectures are applied. We can then see how all of this practice was rapidly applied to GPU's.A major topic is the software to program and debug these unit, which are capable of Tera-mistakes per second. We will explore some of the commercial products, and applications. Fasten your seatbelt - it's that kind of a technology

This book covers the topic of On-orbit repair and servicing of spacecraft. Putting a communications satellite in synchronous orbit will set you back 100's of millions of dollars. Once on orbit, you hope it survived the launch environment, and operates correctly. And, you further hope it works at least for its design lifetime, and as long as possible. This approach, based on good engineering design practices, lessons learned, and hope, it the equivalent of buying a new S-class Mercedes with a sealed gas tank, and driving it until it stops. Then buying a new one.We will discuss the history and the technology of on-orbit servicing, and the projects currently being conducted. We'll take a look at ambitious planned projects, and the enabling technologies that will make them a success. We'll speculate what this means to missions to other planets in our solar system, and the challenges to manned expeditions to follow the robotic ones. By developing a Orbital Servicing Infrastructure, we could extend the life of very expensive resources, and clean up some of the orbital clutter that is endangering current and future space assets. IOn addition, we can derive a stong business case for on-orbit repair.

This book is about the topic of Mobile Cloud Robotics. Cloud Robotics emerged in 2010. This leverages the fusion of multiple technologies, such as the Internet of Things, mobile robotic platforms, Multicore Graphics Processing Units, and the Cloud platform. The Cloud concept involves virtualizing the compute element, as we'll explain in detail later. Mostly, we will focus on mobile robots, as opposed to robotic assembly, and warehousing. At the heart of the problem is a computation-communication-power usage trade-off. We will look at the integration of these topics, with a roadmap and a defined architecture. The Cloud-supplied services augment the more limited computation resources embedded in the mobile robot. It provides services on demand. These services can be related to data storage, downloading code, or computation. This allows a relatively simple and constrained architecture to have vastly greater resources. We will extend this concept. We can build a swarm of robotic platforms, not necessarily homogeneous, that can self-organize into a cluster computer, using, for example, the Open Source Beowulf software from NASA. There is no reason the Cloud server has to be static, it can be a member of the swarm. The swarm members will share an architecture, differing only in their sensor payload (This is one usage model). The Swarm mothership can host the cloud, wherever the swarm happens to be. I use the term "mothership" here to indicate that the robot platforms are deployed from (and possibly retrieved by) the mothership. The mothership is a supernode, as members of the group or swarm are nodes. With the current generation of GPU-based supercomputer architectures, the mothership can certainly be a Cloud host. It shares the problems of power usage, and communication with members of the swarm. Depending on the operational environment, these issues can be addressed. The more real-time operations have to be handled locally, onboard the various members, due to communications delays. Up front, at the architecture level, the load balancing must be considered in a trade-off with communications and power usage. The mobile platform must always be able to meet the goals, even if a bit late. In some real-time scenarios, late means wrong.

Unfortunately, we learn more from failures than from successes. This book continues an examination of a cross-section of engineering failures, and analyzes them to define the lessons-learned. It also presents some additional methodologies to prevent failures, or, at least, minimize the effects. The first volume presented a cross-section of failure studies, mostly drawn from the engineering and aerospace context. Each study includes specific references and a definition of the root cause of the failure. I said, "Let's try to learn from other's mistakes. It is less painful to learn from others' failures than your own." So, almost nobody listened, and I have enough material for a new book. We will see continuing errors of omission, errors of commission, and just plain ignorance of the facts. Since its publication, I have had more than enough material for a second book. The first book discussed System Engineering processes and procedures that can and should be applied to an architecture before the fact, and, unfortunately, after the fact as a post-mortem analysis. It is important to do a good post-mortem analysis of failures, and document them, for the benefit of the next generation of implementers. This helps to prevent the repeating of mistakes. And yet, we keep repeating mistakes, not building on our work, and going on to create larger, more creative mistakes. I will try to minimize the overlap in the books, but some times there is further information or corrections on material in Volume 1. A major new area of interest is self-driving cars, not just their technology, but the insurance and legal issues they introduce. I am presenting this from an engineering standpoint, because that is my background. But the concepts apply across all disciplines and endeavors. If your are responsible for a design, a device, a policy, or a program, you must think through the consequences. Always have a plan B. Always have a Plan C Always think about safety and security. Don't make the same mistake twice. Don't make a second mistake. I have included an updated glossary and a list of reference material at the end of the book, and specific references for the failure cases discussed.

This book covers the topic of Astronomy in the context of STEM Education. Astronomy is the branch of Science that deals with other objects in the Universe. At night, we can see other stars, sometimes planets, and, if we are lucky, comets. Astronomy dates back far in the history of mankind, starting with observations of the sky, and the development of theories of what it all meant, and how it all worked. The initial assumption was that the Earth was the center of the Universe, and everything traveled around it. But, by observations, some "heavenly bodies" wander about in the sky, and increasingly complex theories were developed to address this. Later, when the Earth was dethroned as the center of the universe, it was understood that other planets and the Earth were in orbit around the Sun. And, the Sun was just another star, like those that could be seen in the night sky. Some suggested projects are included to get student interest going.

The book discusses the Engineering process, a road map developed over time to simplify design, implementation, and testing. It is applicable across a broad range of applications, from building a cathedral, to designing ap software.One key part of the process is that it can be enhanced and modified, to incorporated new knowledge. Although the teachers are experts in their particular area, and know how to present grade-appropriate material, they may not know how to find and access the advanced resources they need, or where to get help in a particular topic area.STEM programs are seen as critically important in the education system, world-wide. It is getting to be a complex, interconnected, global ecosystem. Advances in the subject areas of STEM will take place only by those who know how to exploit this ecosystem for knowledge.

This book is an introduction to Cubesats, those popular and relatively inexpensive modular spacecraft that are upending the aerospace world. They have been built and deployed by colleges and Universities around the world, as well as high schools and elementary schools, even individuals. This is because Cubesats are modular, standard, and relatively low cost. The expensive part is the launch, but that is addressed by launch fixtures compatible with essentially ever launch on the planet. Although you may not have much of a choice in the orbit.Student Cubesat Projects are usually open source, may be world-wide in scope, and collaborative.At the same time, professionals in aerospace have not failed to consider the Cubesat architecture as an alternative for small-sat missions. This can reduce costs by one or two orders of magnitude. There are Cubesats on the International Space Station, and these can be returned to Earth on a resupply mission. There is a large "cottage industry' developed around the Cubesat architecture, addressing "professional" projects with space-rated hardware. NASA itself has developed Cubesat hardware (Pi-Sat) and Software (cfs).Cubesats are modular, built to a standard, and mostly open-source. The downside is, approximately 50% of Cubesat missions fail. We hope to point out some approaches to improve this. If you define and implement your own Cubesat mission, or work as a team member on a larger project, this book presents and points to information that will be valuable. Even if you never get your own Cubesat to orbit, you can be a valuable addition to a Cubesat or larger aerospace project. Shortly, two NASA Cubesats will be heading to Mars. The unique Cubesat architecture introduces a new Paradigm for exploring the many elements of our Solar System. Best of luck on your mission.

This book documents the development of missile and spacecraft guidance computers from the earliest efforts to the current Space Station and satellite onboard systems. This book developed from the author's presentation at the Johns Hopkins University's Applied Physics Laboratory in 2009 for the Workshop on Flight Software. The second and third editions were expanded with new material and references. The fourth edition updated the material to the state of the art in 2014, with discussions of the latest approaches and architectures, including Orion. More references wee included, and errors were corrected. This sixth edition in 2019, adds new material, and corrects some information. There is coverage of new missions and systems, particularly the emerging Cubesat architecture, and the ISS's spiffy new Supercomputer.