Distributed Architectures and Constellations for γ-ray Burst Science

The gravitational wave/γ-ray burst GW/GRB170817 event marked the beginning of the era of multi-messenger astrophysics, in which new observations of Gravitational Waves (GW) are combined with traditional electromagnetic observations from the very same astrophysical source. In the next few years, Advanced LIGO/VIRGO and KAGRA in Japan and LIGO-India will reach their nominal/ultimate sensitivity. In the electromagnetic domain, the Vera C. Rubin Observatory and the Cherenkov Telescope Array (CTA) will come online in the next few years, and they will revolutionize the investigation of transient and variable cosmic sources in the optical and TeV bands. The operation of an efficient X-ray/γ-ray all-sky monitor with good localisation capabilities will play a pivotal role in providing the high-energy counterparts of the GW interferometers and Rubin Observatory, bringing multi-messenger astrophysics to maturity. To reach the required precision in localisation and timeliness for an unpredictable physical event in time and space requires a sensor distribution covering the whole sky. We discuss the potential of large-scale, small-platform-distributed architectures and constellations to build a sensitive X-ray/γ-ray all-sky monitor and the programmatic implications of this, including the set-up of an efficient assembly line for both hardware development and data analysis. We also discuss the potential of a constellation of small platforms operating at other wavelengths (UV/IR) that are capable of repointing quickly to follow-up high-energy transients.

Automotive Mechanical Vehicle Starter

This research is used to crank start automotive vehicle. There are many different system used in order to start-up vehicles using electric starter, in the time of battery low-power or totally drained. The purpose of this research is to help the driver to get out of this difficulty. Nowadays there are many people that have experienced such a bad moment, where they are stranded at road side due to malfunction starter in their car because of battery problem. Most of the vehicle electric starter failure is because of battery corrosion or battery undercharged. The importance of this research is to solve this problem. Starter is a vital part of the vehicle, without it no automotive vehicles able to operate. These starters will rotate an internal-combustion engine to initiate the engine’s operation under its own power. Starters also can be malfunction too due to corroded electrical connections or an undercharged battery. This system can be used to solve this problem. This system used human energy by using mechanical parts in order to produce electrical power. In order to produce electrical current, workforce will be applied by rotating the wheel that already linked by belt and from that rotations will trigger a magnetic force and it will produce an electrical current and supply it into battery. This system is divided into two development; hardware development and software development. The hardware development involved, mechanical device which is used and electrical device such as monitor. For software development, Fritzing is used to construct circuit.

Method and criteria for estimating the emergence and characteristics of architectures of interactive distributed computer and cyberphysical systems

The article analyzes the world level of software and hardware development of control, monitoring and management of complex distributed industrial and environmental facilities. The prospects of development and application of cyberphysical systems on the basis of the methodology of their organization offered by professor AO are noted. Miller. The urgency of solving the problem of synthesis of the theory, methodology and practice of IRKS construction by improving the architectures and data exchange systems of monitoring, interactive and dialogic RKS is emphasized. Based on the emergence criterion proposed by J. Martin, an improved criterion for estimating the emergence of the IRKS data node by taking into account the ratio of the number of reads to the number of data records is proposed. A method for estimating emergence based on the proposed classification of their architectures has been developed. The analysis of advantages and functional limitations of intellectual level of existing RKS architectures is carried out. The proposed architecture of a multilevel star-ring optical sensor network functionally and hardware-adapted to the conditions of application in landscape areas of nature reserves is given.

Recommended Methods Supporting Adoption of the Agile Philosophy for Hardware Development

The objective of this research is to understand the historical evolution of software development, identify desirable characteristics of methods supporting agile for hardware, and recommend potential methods enabling agile development of hardware products. As technology and markets change, product development increasingly operates in a volatile, uncertain, complex, and ambiguous (VUCA) environment. While originally applied to software development, organizations are starting to see opportunity in adapting the agile philosophy for hardware development. A comparison of philosophies is made between waterfall, spiral, and agile development. The historical evolutions of software development, after agile, including Continuous Integration Continuous Deployment (CICD), Development and Operations (DevOps), and Development Security and Operations (DevSecOps) is presented. Benefits and challenges in the application of agile methods for hardware are presented. Benefits include improvements in flexibility in response to change and soft factors such as team communication, transparency and commitment. However, many challenges still remain. These are grouped into theme areas including lack of product flexibility, difficulty in separating deliverables, challenges with breaking down tasks within a sprint, changes needed in culture and mindset, difficulty scaling beyond pilot programs, team distribution, and development of an integrated approach across the product lifecycle. Potential methods to aid in the adoption of agile for hardware are discussed using the phases of the hardware development lifecycle as a framework. Recommended methods include the adaptation of Model Based Systems Engineering (MBSE) for problem definition, the use of generative methods for design, the application of Virtual Reality (VR) for prototyping, leveraging additive manufacturing for production, and favoring software defined systems to help in operations. By reducing both the duration and person-hours, these methods enable higher iteration rates for hardware products needed for an agile philosophy. The paper concludes with a discussion on future research efforts supporting the enabling agile development of hardware.

HardOps: Utilising the software development toolchain for hardware design

<div>Preprint of journal article.</div><div><br></div><div><b>Abstract</b>:</div><div>Collaborative design of physical products between remote partners poses unique challenges. This is due to both the complex and interconnected data required for product design and manufacture, and to the centralised computing infrastructure traditionally used to manage product lifecycle data. While modern cloud based solutions to collaborative design are gaining popularity, they diminish the control of each design partner. In contrast, software designers readily collaborate on highly complex software, while retaining direct control of the files they are editing due to the dominance of distributed version control. This version control can be coupled with ``Developer Operations'' or DevOps tools to automate critical processes and facilitate communication. In this paper we explore how DevOps workflows can be adapted to the development of hardware. We include concrete examples of how this can be implemented in practice from a case study of the OpenFlexure Microscope project. While much ground remains to be broken in this field, we believe DevOps for hardware can support a new paradigm of distributed hardware development, with enormous benefits for both commercial and open-source hardware.<br></div>

HardOps: Utilising the software development toolchain for hardware design

<div>Preprint of journal article.</div><div><br></div><div><b>Abstract</b>:</div><div>Collaborative design of physical products between remote partners poses unique challenges. This is due to both the complex and interconnected data required for product design and manufacture, and to the centralised computing infrastructure traditionally used to manage product lifecycle data. While modern cloud based solutions to collaborative design are gaining popularity, they diminish the control of each design partner. In contrast, software designers readily collaborate on highly complex software, while retaining direct control of the files they are editing due to the dominance of distributed version control. This version control can be coupled with ``Developer Operations'' or DevOps tools to automate critical processes and facilitate communication. In this paper we explore how DevOps workflows can be adapted to the development of hardware. We include concrete examples of how this can be implemented in practice from a case study of the OpenFlexure Microscope project. While much ground remains to be broken in this field, we believe DevOps for hardware can support a new paradigm of distributed hardware development, with enormous benefits for both commercial and open-source hardware.<br></div>

WHEN WORLDS COLLIDE – A COMPARATIVE ANALYSIS OF ISSUES IMPEDING ADOPTION OF AGILE FOR HARDWARE

The objective of this paper is to explore challenges identified for implementation of scrum for hardware development intersect with agile principles found in the literature. A series of comparative analyses are done at the textual level, through logical intersections, and through thematic analysis. It is shown that there are five underlying themes found across two sets of scrum challenges (constraints of physicality and the 13 principles). These five themes include: flexiblity, chunkability, scalability, endurability, and teamability. These five themes further are found related to the defining principles of the agile manifesto. Using this understanding, future efforts will include empirical case study work to determine the impact that these have on application of scrum methods and tools. Additionally, guidelines should be developed to help hardware product engineers in applying scrum.