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 @


From EGIWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Overview For users For resource providers Infrastructure status Site-specific configuration Architecture

Federated Cloud Communities menu: Home Production use cases Under development use cases Closed use cases High level tools use cases

General Information

  • Status: Preparatory
  • Start Date: 08/10/2014
  • End Date: -
  • contact: Nuno Ferreira /, Diego Scardaci /
  • External contact: Jacques.van-Helden /

Short Description

RSAT (Regulatory Sequence Analysis Tools) offers a series of tools dedicated to the detection of regulatory signals in non-coding sequences. The only input required is a list of genes of interest (e.g. a family of co-regulated genes). From this information, you can retrieve the upstream sequences over a desired distance, discover putative regulatory signals, search the matching positions for these signals in your original dataset or in whole genomes, and display the results graphically in the form of a feature map. Each tool is presented as a form to fill. For each form, a manual page provides detailed information about the parameters. RSAT usally processes data-sets extracted by the Ensembl databases

Use Case

A VM image embedding RSAT is already available. As a first test we would like to deploy one instance of this VM on the EGI Federated Cloud.

Requirements to run the RSAT VM:

  • 1 Core
  • 2 GB of RAM
  • 12 GB of storage

RSAT Data-sets can be huge, first tests will be done with a couple of genomes (about 4 GB). Later we will test RSAT with bigger data-sets.

Additional Files

RSAT web site: