69 research outputs found

    The E-ARK Data Mining Showcase

    Get PDF
    This report focuses on recent developments that support the deployment of the IPRIP in different configurations at E-ARK stakeholder sites. These configurations are specifically targeting the processing of E-ARK Archival Information Packages (AIPs), as detailed in D4.4 Part A. A flexible packaging mechanism combined with a standalone backend implementation enables custom single-server deployments on demand. Work on the single-server deployment has been carried out jointly with WP4 in the context of the E-ARK Web project. For a detailed description of the E-ARK Web SIP to AIP conversion component, the reader is referred to deliverable D4.4 Part B

    Archival Information Package (AIP) Pilot Specification

    Get PDF
    This report presents the E-ARK AIP format specification as it will be used by the pilots (implementations in pilot organizations). The deliverable is a follow-up version of E-ARK deliverable D4.2. The report describes the structure, metadata, and physical container format of the E-ARK AIP, a container which is the result of converting an E-ARK Submission Information Package (SIP) into the E-ARK Archival Information Package (AIP). The conversion will be implemented in the Integrated Platform as part of the component earkweb

    SIP-AIP conversion component: Reference Implementation

    Get PDF
    This report is about the E-ARK AIP format specification. There is a common structure of information packages shared between the different types of information packages which is defined by the document “Common Specification for Information Packages”. The current report references this Common Specification and focuses on the structural peculiarities of the AIP format and the implementation as part of the reference implementation E-ARK Web (in short: earkweb). Key objectives of this document are: To define a generic structure of the AIP format in a way that it is suitable for a wide variety of data types, such as document and image collections, archival records, databases or geographical data. To recommend a set of metadata related to the structural and the preservation aspects of the AIP as implemented by the reference implementation (earkweb). To ensure the format is also suitable to store large quantities of data

    The E-ARK Integrated Platform Reference Implementation

    Get PDF
    The report describes a set of software components that have been developed in order to realize the E-ARK Integrated Platform Reference Implementation Prototype for storing, searching, and accessing E-ARK Information Packages on a scalable infrastructure. The E-ARK Integrated Platform Reference Implementation Prototype integrates: (a) an Information Package creation and management system, (b) a repository for content search and access, and (c) a scalable storage and execution environment based on Apache Hadoop. The report focuses on the software components that have been individually developed and deployed on top of the core infrastructure components (Hadoop, Lily, SolR). This complements deliverable D6.1 which describes the set-up and configuration of the repository and indexing frameworks. This report accompanies a number of software development results which have been developed in order to realize the Integrated Platform Reference Implementation Prototype. Besides the individual software components, the report provides an overview of the overall system architecture, the integration approach and utilized interfaces

    SIP-AIP conversion component: AIP specification

    Get PDF
    This report represents both the final version of the AIP format specification, and the documentation of the E-ARK reference implementation which includes the SIP-AIP conversion component

    High Precision Temperature Control of Normal-conducting RF GUN for a High Duty Cycle Free-Electron Laser

    Full text link
    High precision temperature control of the RF GUN is necessary to optimally accelerate thousands of electrons within the injection part of the European X-ray free-electron laser XFEL and the Free Electron Laser FLASH. A difference of the RF GUN temperature from the reference value of only 0.01 K leads to detuning of the cavity and thus limits the performance of the whole facility. Especially in steady-state operation there are some undesired temperature oscillations when using classical standard control techniques like PID control. That is why a model based approach is applied here to design the RF GUN temperature controller for the free-electron lasers. A thermal model of the RF GUN and the cooling facility is derived based on heat balances, considering the heat dissipation of the Low-Level RF power. This results in a nonlinear model of the plant. The parameters are identified by fitting the model to data of temperature, pressure and control signal measurements of the FLASH facility, a pilot test facility for the European XFEL. The derived model is used for controller design. A linear model predictive controller was implemented in MATLAB/Simulink and tuned to stabilize the temperature of the RF GUN in steady-state operation. A test of the controller in simulation shows promising results

    Detailed Pilots Specification

    Get PDF
    The Electronic Archiving Service consists of a series of activities covered by software tools and manual workflow steps. These tools are currently partly in existence, some are being developed by E-ARK project, many more are to be added by developments of the digital preservation community in the future. The role of this report is to identify the most relevant scenarios for the E-ARK Service, define which scenario which level of activity is needed in order to bridge the gap of the currently existing solutions (e.g. integration, software development, interface definition

    E‐ARK Dissemination Information Package (DIP) Draft Specification

    Get PDF
    The primary aim of this report is to present the first version of the E-­‐ARK Dissemination Information Package (DIP) format. In order to do so the report describes the workflows and use cases of archival access services, and ultimately makes use of these these to present a set of requirements which should be followed when designing a DIP format. As access to archival records is largely dependent on the tools and environments used, the secondary aim of the deliverable is to go beyond the DIP format and look closely at the tools needed for preparing and using the DIP
    corecore