Carbon Catcher Design Report

Overview. The design of the overall Carbon Catcher project can be separated into four distinct systems, each of which is assigned a specialized committee. The committee names and responsibilities are listed below: Air Mover The overall goal for the Air Mover committee is the design of the turbine assembly. As the overall goal of the project is to collect and separate carbon dioxide from the air, one of the most important parts is to actually get the air to pass through the carbon-catching membrane. Passive air would not give a significant enough yield rate to make the carbon dioxide collection rate impactful, thus air must be sucked through a vacuum/turbine. Membrane The goal of Membrain is to create a membrane that can filter out CO2 through various methods. These methods are limited, due to there being such variety, to certain techniques and membrane material types that have been decided, prior, by the committee. Most membranes will be geared towards utilizing temperature and pressure along with gaseous speed and flow rate. In addition, examining certain treatments, such as regeneration of material, and replacements will be looked into as well, to see how it fares in sustainability. Carbon Storer The Carbon Storer committee will design a store and transport system for fluid CO2 after it is extracted from the atmosphere. Primary considerations include geological solutions, cost-effective materials, and analysis methods to improve overall capacity and efficiency. Additionally, the committee will select an environmentally and economically sustainable method of recycling the captured CO2. PyControl The PyControl committee will design a series of sensors and actuators, which will primarily support the sequestration and pipeline systems present in the Carbon Storer Committee and direct air capture system in Air Mover. The design can be broken into four control layers: Input/Output, Field Controllers, Data, and Supervisory. Goal The overarching goal of Carbon Catcher is to design a cost-effective, scalable atmospheric carbon dioxide removal system that is capable of being deployed in a variety of urban environments and may fit a variety of different customer requirements or requests

FAST: FAST Analysis of Sequences Toolbox.

FAST (FAST Analysis of Sequences Toolbox) provides simple, powerful open source command-line tools to filter, transform, annotate and analyze biological sequence data. Modeled after the GNU (GNU's Not Unix) Textutils such as grep, cut, and tr, FAST tools such as fasgrep, fascut, and fastr make it easy to rapidly prototype expressive bioinformatic workflows in a compact and generic command vocabulary. Compact combinatorial encoding of data workflows with FAST commands can simplify the documentation and reproducibility of bioinformatic protocols, supporting better transparency in biological data science. Interface self-consistency and conformity with conventions of GNU, Matlab, Perl, BioPerl, R, and GenBank help make FAST easy and rewarding to learn. FAST automates numerical, taxonomic, and text-based sorting, selection and transformation of sequence records and alignment sites based on content, index ranges, descriptive tags, annotated features, and in-line calculated analytics, including composition and codon usage. Automated content- and feature-based extraction of sites and support for molecular population genetic statistics make FAST useful for molecular evolutionary analysis. FAST is portable, easy to install and secure thanks to the relative maturity of its Perl and BioPerl foundations, with stable releases posted to CPAN. Development as well as a publicly accessible Cookbook and Wiki are available on the FAST GitHub repository at https://github.com/tlawrence3/FAST. The default data exchange format in FAST is Multi-FastA (specifically, a restriction of BioPerl FastA format). Sanger and Illumina 1.8+ FastQ formatted files are also supported. FAST makes it easier for non-programmer biologists to interactively investigate and control biological data at the speed of thought

Index to NASA Tech Briefs, 1975

This index contains abstracts and four indexes--subject, personal author, originating Center, and Tech Brief number--for 1975 Tech Briefs

A gearbox model for processing large volumes of data by using pipeline systems encapsulated into virtual containers

Software pipelines enable organizations to chain applications for adding value to contents (e.g., confidentially, reliability, and integrity) before either sharing them with partners or sending them to the cloud. However, the pipeline components add overhead when processing large volumes of data, which can become critical in real-world scenarios. This paper presents a gearbox model for processing large volumes of data by using pipeline systems encapsulated into virtual containers. In this model, the gears represent applications, whereas gearboxes represent software pipelines. This model was implemented as a collaborative system that automatically performs Gear up (by using parallel patterns) and/or Gear down (by using in-memory storage) until all gears produce uniform data processing velocities. This model reduces delays and bottlenecks produced by the heterogeneous performance of applications included in software pipelines. The new container tool has been designed to encapsulate both the collaborative system and the software pipelines into a virtual container and deploy it on IT infrastructures. We conducted case studies to evaluate the performance of when processing medical images and PDF repositories. The incorporation of a capsule to a cloud storage service for pre-processing medical imagery was also studied. The experimental evaluation revealed the feasibility of applying the gearbox model to the deployment of software pipelines in real-world scenarios as it can significantly improve the end-user service experience when pre-processing large-scale data in comparison with state-of-the-art solutions such as Sacbe and Parsl.This work has been partially supported by the “Spanish Ministerio de Economia y Competitividad ” under the project grant TIN2016-79637-P “Towards Unification of HPC and Big Data paradigms”

Better abstractions for reusable components & architectures

Software architecture (SA) is a crucial component of Model Driven Engineering (MDE), since it eases the communication and reuse of designs and components. However, existing languages (e.g., UML, AADL, SysML) are lacking many needed features. In particular, they provide rudimentary support for connectors, a first-class element in the components and connectors (C&C) architectural view and one of the most reusable architectural elements. This is unfortunate, since the difficult properties that need to be guaranteed for complex systems are mainly the non-functional properties, like throughput, security and dependability, which are greatly influenced by the employed connectors. This work reviews the basic abstractions of the C&C view of SA and examines extra architectural elements which can support the detailed, explicit and separate description of behaviour, interaction and control logic

Status description and evaluation of the complete water supply system of Hinnerup

El trabajo realizado evalúa el estado de la planta de abastecimiento de agua de Hinnerup en todas sus fases: abstracción (incluyendo una evaluación del estado de los acuíferos), tratamiento, almacenamiento y distribución. Además, se espera un crecimiento de la zona urbana en los próximos años, con lo que se evalúa la posibilidad de mantener el suministro de calidad para la nueva cantidad que hay que abastecer, de nuevo en todas las fases del proceso. Para ello, se realiza una pertinente estimación del consumo en esta nueva zona urbana; así como una evaluación del punto de conexión de la misma y de la compatibilidad con el sistema existente. Por último, se realiza una evaluación de riesgos con el fin de determinar la vulnerabilidad del suministro de agua potable de la zona abastecida por esta planta, concluyendo en que el riesgo es bajo.The conducted report assesses the status of the Hinnerup water supply plant in all its phases: abstraction (including an assessment of the state of the aquifers), treatment, storage and distribution in the water supply area. Moreover, an urban area growth is expected in the upcoming years. Hence, the quality provided must still accomplish certain parameters in all the phases of the process. On this purpose, a justified estimation of the consumption in this new urban area is conducted, as well as an assessment of its connection point and compatibility with the existing system. Lastly, a risk assessment is performed in order to determine the vulnerability of the water supply system, concluding that the risk in general terms is low.Departamento de Construcciones Arquitectónicas, Ingeniería del Terreno y Mecánica de los Medios Continuos y Teoría de EstructurasGrado en Ingeniería Mecánic

Analysing tactics in architectural patterns

We present an approach to analyse the application of tactics in architectural patterns. We define and illustrate the approach by resorting to Archery, a language for specifying, analysing and verifying architectural patterns. The approach consists of characterising the design principles of an architectural pattern as constraints, expressed in the language, and then, establishing a refinement relation based on their satisfaction. The application of tactics preserving refinement preserves the original design principles expressed themselves as constraints for the architectural pattern. The paper’s focus on fault-tolerance tactics, and identifies a set of requirements for a semantic framework characterising them. Model transformations to represent their application are discussed and illustrated through two case studies.FC

Classifying and evaluating architecture design methods

The concept of software architecture has gained a wide popularity and is generally considered to play a fundamental role in coping with the inherent difficulties of the development of large-scale and complex software systems. This document first gives a definition of architectures. Second, a meta-model for architecture design methods is presented. This model is used for classifying and evaluating various architecture design approaches. The document concludes with the description of the identified problems