1 / 17

An Overview of ICAT

Damian Flannery EDNP 2009 UK ICAT. An Overview of ICAT. Damian Flannery The Problem(s) ICAT. Large Data Volumes High Throughput Proliferation of data formats Multiple Data Analysis Step Increasing complexity of data Data Access requirements (Sharing and Restriction)

ulema
Download Presentation

An Overview of ICAT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Damian FlanneryEDNP 2009 UKICAT An Overview of ICAT

  2. Damian FlanneryThe Problem(s)ICAT • Large Data Volumes • High Throughput • Proliferation of data formats • Multiple Data Analysis Step • Increasing complexity of data • Data Access requirements (Sharing and Restriction) • Versioning of data formats and associated software • Distributed Computation (accessed offline from research chain) • Common names and units for temperature, pressure etc. • Changing / differing metadata requirements • International users / federation of data from facilities • Relating to Proposals and Publications • Ontologies • Provenance (Creation, Ownership, History) • Governments want return on investment

  3. Damian FlanneryWhat is ICAT?ICAT • What is ICAT ? • ICAT is a database (with a well defined API) that provides a uniform interface to experimental data and a mechanism to link all aspects of research from proposal through to publication. • Access data anywhere via the web • Annotate your data • Search for data in a meaningful way e.g. taxonomy, Sample, temperature, pressure etc • Share data with colleagues • Access data via your own programs (C++, Fortran, Java etc.) via the ICAT API • Identify potential collaborations • Utilise integrated e-Science High-Performance Computing and Visualisation resources • Link to data from your publications • Etc. Example ISIS Proposal H2-(zeolite) vibrational frequencies vs polarising potential of cations B-lactoglobulin protein interfacial structure GEM – High intensity, high resolution neutron diffractometer Proposals Once awarded beamtime at ISIS, an entry will be created in ICAT that describes your proposed experiment. Experiment Data collected from your experiment will be indexed by ICAT (with additional experimental conditions) and made available to your experimental team Publication Using ICAT you will also be able to associate publications to your experiment and even reference data from your publications. Analysed Data You will have the capability to upload any desired analysed data and associate it with your experiments.

  4. Damian FlanneryOverviewICAT User Database System Single Sign On Data Storage/ Delivery System Proposal System Publication System ICAT API e-Science Services RDBMS Software Repository Web Services API Command Line Tools Fortran C++ Java Glassfish / JBOSS

  5. Damian FlanneryFederationICAT User Database System User Database System User Database System Single Sign On Single Sign On Single Sign On Data Storage/ Delivery System Data Storage/ Delivery System Data Storage/ Delivery System Proposal System Proposal System Proposal System Publication System Publication System Publication System ICAT API ICAT API ICAT API ANSTO SNS ISIS e-Science Services e-Science Services e-Science Services RDBMS RDBMS RDBMS Software Repository Software Repository Software Repository Web Services API Web Services API Web Services API Data Portal

  6. Damian FlanneryData ModelICAT • CCLRC Scientific Metadata Model • Brian Matthews • Shoaib Sufi Topic Publication Keyword Authorisation Investigation Investigator Dataset Sample Sample Parameter Datafile Dataset Parameter Parameter Related Datafile Datafile Parameter

  7. Damian FlanneryICAT APIICAT • Service Oriented Architecture • Services exposed as Web Services • User required to authenticate in order to obtain Session Token • Token is used in all subsequent API calls to for authorisation • The API is modular in order to fit the needs of the facilities • Plugin own user database • Plugin data delivery system • Clustering capability • Chracteristics • Platform independent [Java] • Application Server independent [EJB3] • Language independent [Web Services] • Database Independent (Almost!) [JPL] • Internals • Services are unit tested using JUNIT • Services are stress tested using JMETER • Services are logged at every interaction point using LOG4J

  8. Damian FlanneryICAT API ContinuedICAT

  9. Damian FlanneryData PortalICAT

  10. Damian FlannerySecurityICAT • Role based permissions • [Super] • Admin • Create • Delete • Update • Download • Read • Data Policy • 3 year embargo on data (+1 if requested) • Commercial data is never made public • Instrument Scientists can access all data from their beamline • Calibration data is public • Any data that involves IPR (e.g. Analysed data) is private for perpetuity unless explicitly shared by user • Secure Sockets Layer (SSL) • Limited lifetime security token

  11. Damian FlanneryInstallation / DevelopmentICAT Installation • Any O/S • Oracle 10G/11G • Java 6 Update 6 • Apache Ant v1.7+ • Glassfish v2 UR2 • Installed & Configured Cog Kit • Unzip download bundle • Update properties files e.g. database details • Run Ant commands Technologies Used • Java • NetBeans 6.5 • Glassfish • Ant • JUnit • JMeter • Log4J • EJB3 • JPA • JAX-WS • JAXB • Oracle (10G / 11G) • Subversion Development

  12. Damian FlanneryISIS IntegrationICAT • At ISIS • Volume of data ~4TB • ~3M datafiles (22 instruments, 330/hour) • 6.7GB metadata, 33M rows • MyProxy / fed id for authentication • Data.ISIS for data delivery • Trigger • NXIngest • RawIngest

  13. Damian FlanneryDevelopersICAT

  14. Damian FlanneryFuture DevelopmentsICAT • Release Data Portal to ISIS users • Move XML Ingest into asynchonous Message Driven Bean • Rule-based policy implementation • Expand and improve the supplied interface • Proposal System integration • Publication System integration • Adherence to open standards e.g. OAI-PMH • Integration with computational & visualisation services • DOIs • Digital Rights Management • Consequence • Database independence • Look at issue/tickets & forum!

  15. Damian FlannerySummaryICAT • Open Source • Searchability and more • Attempt to solve problems as outlined earlier in this talk • Built with the following software characteristics • Scalability • Maintainability • Reliability • Availability • Extensibility • Performance • Manageability • Security • Standardised interface for integration • We want to drive this forward in collaboration with other facilities

  16. Damian FlanneryAcknowledgementsICAT • ISIS • Robert McGreevy, Kenneth Shankland, Tom Griffin, Stuart Ansell • Freddie Akeroyd, Chris Moreton-Smith, Matt Clarke, Kevin Knowles, Steven King, Adrian Hillier, Alex Hannon, Rob Dalgleish • e-Science • Laurent Lerusse, Glen Drinkwater, Shoaib Sufi, Kerstin Kleese Van Dam, Rik Tyer, Phil Couch • Shoaib Sufi, Brian Matthews • Gordon Brown, Kier Hawker, Carmine Coiffe • Roger Downing

  17. Damian FlanneryQuestionsICAT http://www.icatproject.org

More Related