A Software Radio Challenge Accelerating Education and Innovation in Wireless Communications

This Innovative Practice Full Paper presents our methodology and tools for introducing competition in the electrical engineering curriculum to accelerate education and innovation in wireless communications. Software radio or software-defined radio (SDR) enables wireless technology, systems and standards education where the student acts as the radio developer or engineer. This is still a huge endeavor because of the complexity of current wireless systems and the diverse student backgrounds. We suggest creating a competition among student teams to potentiate creativity while leveraging the SDR development methodology and open-source tools to facilitate cooperation. The proposed student challenge follows the European UEFA Champions League format, which includes a qualification phase followed by the elimination round or playoffs. The students are tasked to build an SDR transmitter and receiver following the guidelines of the long-term evolution standard. The metric is system performance. After completing this course, the students will be able to (1) analyze alternative radio design options and argue about their benefits and drawbacks and (2) contribute to the evolution of wireless standards. We discuss our experiences and lessons learned with particular focus on the suitability of the proposed teaching and evaluation methodology and conclude that competition in the electrical engineering classroom can spur innovation.Comment: Frontiers in Education 2018 (FIE 2018

Which design decisions in AI-enabled mobile applications contribute to greener AI?

Background: The construction, evolution and usage of complex artificial intelligence (AI) models demand expensive computational resources. While currently available high-performance computing environments support well this complexity, the deployment of AI models in mobile devices, which is an increasing trend, is challenging. Mobile applications consist of environments with low computational resources and hence imply limitations in the design decisions during the AI-enabled software engineering lifecycle that balance the trade-off between the accuracy and the complexity of the mobile applications. Objective: Our objective is to systematically assess the trade-off between accuracy and complexity when deploying complex AI models (e.g. neural networks) to mobile devices, which have an implicit resource limitation. We aim to cover (i) the impact of the design decisions on the achievement of high-accuracy and low resource-consumption implementations; and (ii) the validation of profiling tools for systematically promoting greener AI. In this way, we aim to provide a quantitative analysis of the performance of AI-enabled applications in operation with respect to their design decisions. Method: This confirmatory registered report consists of a plan to conduct an empirical study to quantify the implications of the design decisions on AI-enabled applications performance and to report experiences of the end-to-end AI-enabled software engineering lifecycle. Concretely, we will implement both image-based and language-based neural networks in mobile applications to solve multiple image classification and text classification problems on different benchmark datasets. For that, we make use of the Android Studio and Unity3D frameworks for building mobile applications that work over Android; and TensorFlow Lite and Open Neural Network Exchange (ONNX) file formats for deploying the AI models in the applications. Overall, we plan to model the accuracy and complexity of AI-enabled applications in operation with respect to their design decisions and will provide tools for allowing practitioners to gain consciousness of the quantitative relationship between the design decisions and the green characteristics of study. Additionally, we will provide experiences in the end-to-end AI-enabled software lifecycle and discuss the challenges found, tools and practices for practitioners. Finally, we will provide an open-source data repository following the ESEM open science practices and containing all the experimentation, analysis and reports in our study.This work has been partially supported by the DOGO4ML Spanish research project (ref. PID2020-117191RB-I00) and by the the "Beatriz Galindo" Spanish Program BEAGAL18/00064.Peer ReviewedPostprint (published version

Low\u2010cost, High\u2010Capability, Embedded Systems for CNC Education and Research

Teaching of CNC and CAD/CAM technologies has recently taken a great importance, due to their development, to the great number of solutions available on the market, and to the frequent updates. Nevertheless, one of the most urgent need is to improve the quality of education coping with a rapidly growing number of students. Nowadays, in comparison to the past, many Open-Source technical solutions, both hardware and software, are available to realise easily and cheaply some scaled-down prototypes of numerical control machine tools: these are able to work perfectly and can be employed as a learning method. This paper shows some past experiences regarding the development of some degree thesis works. In particular, it is shown how to implement a numerical control (LinuxCNC) in two specific cheap embedded systems (Raspberry Pi and BeagleBone Black). In this way, a student has the possibility of simulating the working of a complete Numerical Control and of learning interactively its way of programming. The final result and student response have shown an excellent effectiveness of these experiences and easy to use as powerful tool in engineering education

Summary of the First Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE1)

Challenges related to development, deployment, and maintenance of reusable software for science are becoming a growing concern. Many scientists’ research increasingly depends on the quality and availability of software upon which their works are built. To highlight some of these issues and share experiences, the First Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE1) was held in November 2013 in conjunction with the SC13 Conference. The workshop featured keynote presentations and a large number (54) of solicited extended abstracts that were grouped into three themes and presented via panels. A set of collaborative notes of the presentations and discussion was taken during the workshop. Unique perspectives were captured about issues such as comprehensive documentation, development and deployment practices, software licenses and career paths for developers. Attribution systems that account for evidence of software contribution and impact were also discussed. These include mechanisms such as Digital Object Identifiers, publication of “software papers”, and the use of online systems, for example source code repositories like GitHub. This paper summarizes the issues and shared experiences that were discussed, including cross-cutting issues and use cases. It joins a nascent literature seeking to understand what drives software work in science, and how it is impacted by the reward systems of science. These incentives can determine the extent to which developers are motivated to build software for the long-term, for the use of others, and whether to work collaboratively or separately. It also explores community building, leadership, and dynamics in relation to successful scientific software

Report on the Second Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE2)

This technical report records and discusses the Second Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE2). The report includes a description of the alternative, experimental submission and review process, two workshop keynote presentations, a series of lightning talks, a discussion on sustainability, and five discussions from the topic areas of exploring sustainability; software development experiences; credit & incentives; reproducibility & reuse & sharing; and code testing & code review. For each topic, the report includes a list of tangible actions that were proposed and that would lead to potential change. The workshop recognized that reliance on scientific software is pervasive in all areas of world-leading research today. The workshop participants then proceeded to explore different perspectives on the concept of sustainability. Key enablers and barriers of sustainable scientific software were identified from their experiences. In addition, recommendations with new requirements such as software credit files and software prize frameworks were outlined for improving practices in sustainable software engineering. There was also broad consensus that formal training in software development or engineering was rare among the practitioners. Significant strides need to be made in building a sense of community via training in software and technical practices, on increasing their size and scope, and on better integrating them directly into graduate education programs. Finally, journals can define and publish policies to improve reproducibility, whereas reviewers can insist that authors provide sufficient information and access to data and software to allow them reproduce the results in the paper. Hence a list of criteria is compiled for journals to provide to reviewers so as to make it easier to review software submitted for publication as a “Software Paper.

Report on the Third Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE3)

This report records and discusses the Third Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE3). The report includes a description of the keynote presentation of the workshop, which served as an overview of sustainable scientific software. It also summarizes a set of lightning talks in which speakers highlighted to-the-point lessons and challenges pertaining to sustaining scientific software. The final and main contribution of the report is a summary of the discussions, future steps, and future organization for a set of self-organized working groups on topics including developing pathways to funding scientific software; constructing useful common metrics for crediting software stakeholders; identifying principles for sustainable software engineering design; reaching out to research software organizations around the world; and building communities for software sustainability. For each group, we include a point of contact and a landing page that can be used by those who want to join that group's future activities. The main challenge left by the workshop is to see if the groups will execute these activities that they have scheduled, and how the WSSSPE community can encourage this to happen