Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

FedCloudBSIM2

From EGIWiki
Revision as of 17:38, 15 December 2014 by Scardaci (talk | contribs)
Jump to navigation Jump to search

General Information

  • Status: Assessed
  • Start Date: 17-03-2014
  • End Date:
  • EGI.eu contact: Nuno Ferreira / nuno.ferreira@egi.eu ; Diego Scardaci / diego.scardaci@egi.eu
  • External contact: Bruno Victor / bruno.victor@bsimsquare.com ; Carlos Simões / carlos.simoes@bsimsquare.com

Short Description

BSIM2 is a spin-off company founded in 2011 as the result of scientific work carried out at the University of Coimbra, in collaboration with the University of Leeds. For five years, the promoters assembled a suite of computational algorithms and workflows to conduct large-scale screenings and identify new amyloid inhibitors. The first product of the company’s portfolio is directed against a rare and fatal neurodegenerative disease.

BSIM2 is interested to to test the capabilities of the EGI Federated Cloud with some proof of concepts. At this stage, BSIM2 doesn't want to use the EGI Federated Cloud resources for commercial purposes but only to explore what EGI can provide and offer to understand if it could be useful for them in the future (e.g. when the pay-per-use model will be available). All the simulations that will be executed on the EGI FedCloud resources will use old or dummy data as input.

Use Case

Requirements

  • Molecular Dynamics simulations
    • cores: 24-28
    • RAM per CPU core: 512 MB
    • Inbound/Outbound during execution: no
    • Licensed software: no
    • Graphical interface: no
    • Operating System: Linux (Red Hat-­based)
    • Other requirements: SSH for access and Rsync for data transfer
  • Chemoinformatics applications/workflows
    • cores:
    • RAM per CPU core:
    • Inbound/Outbound during execution:
    • Licensed software:
    • Graphical interface:
    • Operating System:
    • Other requirements:
  • Third-­‐party, licensed, Linux applications
    • cores:
    • RAM per CPU core:
    • Inbound/Outbound during execution:
    • Licensed software:
    • Graphical interface:
    • Operating System:
    • Other requirements:
  • Third-­‐party, licensed, Windows applications
    • cores:
    • RAM per CPU core:
    • Inbound/Outbound during execution:
    • Licensed software:
    • Graphical interface:
    • Operating System:
    • Other requirements:

Additional Files