Abstract

This article reflects on the concept of source code as it is applied to areas other than computer programming, and relates it to scientific communication, network activism, and micropolitical actions. The usefulness of learning the essential aspects of programming as a universal language and digitizing of objects, buildings, and historical sites in 3D, by digital libraries of cultural heritage, are discussed.

Abstract

The CFMU has developed mission critical applications for Europewide flight plan processing and air traffic management activities using Ada83. This paper presents the techniques and tools used for the migration from an Ada83 to an Ada95 compiler and run-time. It puts a particular emphasis on both the software management aspects and the technical aspects e.g. language aspects, run-time evolution, how to cater for incompatibilities between Ada83 and Ada95, elaboration order, etc... Document type: Part of book or chapter of book

Abstract

Historical activities at facilities producing nuclear materials for weapons released radioactivity into the air and water. Past studies in the United States have evaluated the release, atmospheric transport and environmental accumulation of 131I from the nuclear facilities at Hanford in Washington State and the resulting dose to members of the public (Farris et al. 1994). A multi-year dose reconstruction effort (Mokrov et al. 2004) is also being conducted to produce representative dose estimates for members of the public living near Mayak, Russia, from atmospheric releases of 131I at the facilities of the Mayak Production Association. The approach to calculating individual doses to members of the public from historical releases of airborne 131I has the following general steps: • Construct estimates of releases 131I to the air from production facilities. • Model the transport of 131I in the air and subsequent deposition on the ground and vegetation. • Model the accumulation of 131I in soil, water and food products (environmental media). • Calculate the dose for an individual by matching the appropriate lifestyle and consumption data for the individual to the concentrations of 131I in environmental media at their residence location. A number of computer codes were developed to facilitate themore » study of airborne 131I emissions at Hanford. The RATCHET code modeled movement of 131I in the atmosphere (Ramsdell Jr. et al. 1994). The DECARTES code modeled accumulation of 131I in environmental media (Miley et al. 1994). The CIDER computer code estimated annual doses to individuals (Eslinger et al. 1994) using the equations and parameters specific to Hanford (Snyder et al. 1994). Several of the computer codes developed to model 131I releases from Hanford are general enough to be used for other facilities. This document provides user instructions for computer codes calculating doses to members of the public from atmospheric 131I that have two major differences from the Hanford modeling sequence. First, the air transport code HYSPLIT (Draxler et al. 2012) is used instead of the RATCHET code. Second, the new individual dose code CiderF replaces the older CIDER code and five auxiliary codes.« le Document type: Report

Abstract

This document is the deliverable D4.1 "Developers toolkit and deployment support" and presents the outcome of the activities T4.1 "ACTIVAGE Development tools" and T4.3 "ACTIVAGE Deployment tools" which are part of Work Package WP4 "ACTIVAGE Application support tools and services layer". The document makes a status of existing development and deployment tools prior to the ACTIVAGE project and describes the ones that are under progress to fulfill ACTIVAGE dedicated requirements. The requirements are presented in Section 2, and the Use Cases in Section 3, precising the uses by the kind of developer profiles listed in section 3.1. The presented tools in Section 4 allow the development of applications (developed for ACTIVAGE by third parties) on top of each given platform among the seven selected as ACTIVAGE IoT platforms (Fiware, openiot, IoTivity, seniorsome, sensiNact, Sofia2 and universAAL). They are used by application developers and platform contributors. For more details about the seven ACTIVAGE IoT platforms, please refer to the D3.1 Report on IoT European Platforms. The presented tools in Section 5 are the ones used in the nine ACTIVAGE deployment sites to support their hardware device installations and middleware installation on the resulting IT infrastructure. They are used by installation/deployment and IT teams. These existing development and deployment tools are available today and constitute the first step of ACTIVAGE toolkit: they are heterogeneous tools available for dedicated platforms and for specific deployment sites. Further works in tasks T4.1 and T4.3 will aim to complete the IoT platform dedicated tools with ACTIVAGE common development and deployment tools based on the common ACTIVAGE APIs under specification.