Management, design and developement of a mesh generation environment using open source software

In this paper we present an object oriented implementation of a general-purpose mesh generation environment for geometry-based simulations. The aim of this application is to unify available legacy code and new research algorithms in only one mesh generation suite. We focus in two aspects that can be of the general interest for managers, designers and developers of similar projects. On the one hand, we analyze the software engineering practices that we have followed in the management and development process. In addition, we detail and discuss the Open Source tools and libraries that we have used. On the other hand, we discuss the design and the data structure of the environment. In particular, we first summarize the topological and geometrical representation. Second, we detail our implementation of the hierarchical mesh generation structure. Third we present our design to mediate collaboration between classes. Finally, we present some of the mesh generation features to show the capabilities of the environment

Some issues in the 'archaeology' of software evolution

During a software project's lifetime, the software goes through many changes, as components are added, removed and modified to fix bugs and add new features. This paper is intended as a lightweight introduction to some of the issues arising from an `archaeological' investigation of software evolution. We use our own work to look at some of the challenges faced, techniques used, findings obtained, and lessons learnt when measuring and visualising the historical changes that happen during the evolution of software

The space physics environment data analysis system (SPEDAS)

With the advent of the Heliophysics/Geospace System Observatory (H/GSO), a complement of multi-spacecraft missions and ground-based observatories to study the space environment, data retrieval, analysis, and visualization of space physics data can be daunting. The Space Physics Environment Data Analysis System (SPEDAS), a grass-roots software development platform (www.spedas.org), is now officially supported by NASA Heliophysics as part of its data environment infrastructure. It serves more than a dozen space missions and ground observatories and can integrate the full complement of past and upcoming space physics missions with minimal resources, following clear, simple, and well-proven guidelines. Free, modular and configurable to the needs of individual missions, it works in both command-line (ideal for experienced users) and Graphical User Interface (GUI) mode (reducing the learning curve for first-time users). Both options have “crib-sheets,” user-command sequences in ASCII format that can facilitate record-and-repeat actions, especially for complex operations and plotting. Crib-sheets enhance scientific interactions, as users can move rapidly and accurately from exchanges of technical information on data processing to efficient discussions regarding data interpretation and science. SPEDAS can readily query and ingest all International Solar Terrestrial Physics (ISTP)-compatible products from the Space Physics Data Facility (SPDF), enabling access to a vast collection of historic and current mission data. The planned incorporation of Heliophysics Application Programmer’s Interface (HAPI) standards will facilitate data ingestion from distributed datasets that adhere to these standards. Although SPEDAS is currently Interactive Data Language (IDL)-based (and interfaces to Java-based tools such as Autoplot), efforts are under-way to expand it further to work with python (first as an interface tool and potentially even receiving an under-the-hood replacement). We review the SPEDAS development history, goals, and current implementation. We explain its “modes of use” with examples geared for users and outline its technical implementation and requirements with software developers in mind. We also describe SPEDAS personnel and software management, interfaces with other organizations, resources and support structure available to the community, and future development plans.Published versio

Some issues in the 'archaeology' of software evolution

During a software project's lifetime, the software goes through many changes, as components are added, removed and modified to fix bugs and add new features. This paper is intended as a lightweight introduction to some of the issues arising from an `archaeological' investigation of software evolution. We use our own work to look at some of the challenges faced, techniques used, findings obtained, and lessons learnt when measuring and visualising the historical changes that happen during the evolution of software

Results from the 2006 Classroom Evaluation of Hackystat-UH

This report presents the results from a classroom evaluation of Hackystat by ICS 413 and ICS 613 students at the end of Fall, 2006. The students had used Hackystat-UH for approximately six weeks at the time of the evaluation. The survey requests their feedback regarding the installation, configuration, overhead of use, usability, utility, and future use of the Hackystat-UH configuration. This classroom evaluation is a semi-replication of an evaluation performed on Hackystat by ICS 413 and 613 students at the end of Fall, 2003, which is reported in "Results from the 2003 Classroom Evaluation of Hackystat-UH". As the Hackystat system has changed significantly since 2003, some of the evaluation questions were changed. The data from this evaluation, in combination with the data from the 2003 evaluation, provide an interesting perspective on the past, present, and possible future of Hackystat. Hackystat has increased significantly in functionality since 2003, which has enabled the 2006 usage to more closely reflect industrial application, and which has resulted in significantly less overhead with respect to client-side installation. On the other hand, results appear to indicate that this increase in functionality has resulted in a decrease in the usability and utility of the system, due to inadequacies in the server-side user interface. Based upon the data, the report proposes a set of user interface enhancements to address the problems raised by the students, including Ajax-based menus and parameters, workflow based organization of the user interface, real-time display for ongoing project monitoring, annotations, and simplified data exploration facilities

Tournament Wizard: Simple and Lightweight Software for Running Fencing Tournaments

Many sports use technology to assist in officiating and administration. Fencing tournament organizers use specialized software to help determine how their matches occur, and to help them administer a tournament. However, the software most commonly used to run these tournaments has some significant limitations, and is not well-suited for use with small events. As a former President of Cal Poly’s Fencing Club, I have had a chance to interact with one popular application for running fencing tournaments a number of times, and made note of its shortcomings. These included issues with operating system compatibility, license transference, and amount of space needed to maintain the database of fencers. After struggling to cope with the limitations of the existing software, I began to wonder how this software would be used if it was scaled down to fit the level of a local club team or a youth league. The purpose of this project is to create a light-weight alternative to these large scale systems. Designing a system like this would result in an application customized to the needs of smaller events, and could also serve as a basic training tool, familiarizing users to the format of larger fencing tournaments. The end goals are simplicity, portability, and usability

Performance analysis of persistence technologies for cloud repositories of models

The growing adoption of Model Driven Development (MDD) in companies during last decade arises some model interchange problems. Companies need support to interchange models and reuse parts of them for developing new projects. Traditional tools for model edition and model interchange have different performance issues related to the models storage. There are mainly two styles to organize the persistence of models into repositories: a complex and large model or a large amount of small models. This last approach is common in companies that generate software from models. In this paper, we analyse performance properties of different persistence technologies to store small/medium-scale models, the analysis results should be considered in the design of model repositories in the cloud. With this aim, we have designed and developed a generic architecture to evaluate each persistence technology under similar situations

Improvements to the Copernicus Trajectory Design and Optimization System for Complex Space Trajectories

The purpose of this assessment was to develop updates and new features for the NASA Copernicus Spacecraft Trajectory Design and Optimization analysis tool (version 5.0) for application to NASA programs and projects. These updates will significantly improve the ability to design and optimize complex trajectories over multiple trajectory phases; will allow the use of unique vehicle-specific guidance, control, and trajectory strategies and constraints; and the creation of an almost unlimited number of unique user-defined capabilities. The primary stakeholders for this assessment are the trajectory design and optimization analysts and engineers, and the chief engineers and project managers for existing programs, projects, and/or tasks that involve impulsive, finite burn, and/or continuous thrust trajectories (e.g., Sun, planet, comet, asteroid, halo orbit, Lagrange point, and distant retrograde orbit). The breadth of application spans the preliminary engineering and mission design concepts and optimization, to the development of candidate reference missions and integrated mission design for vehicle system design and operation, to the design and development of flight trajectories and associated propulsive maneuvers for real-time operations