# BioBlend

## About

BioBlend is a Python library for interacting with CloudMan and Galaxy‘s API.

BioBlend is supported and tested on:

- Python 2.6, 2.7, 3.3 and 3.4
- Galaxy release_14.02 and later.

Conceptually, it makes it possible to script and automate the process of cloud infrastructure provisioning and scaling via CloudMan, and running of analyses via Galaxy. In reality, it makes it possible to do things like this:

- Create a CloudMan compute cluster, via an API and directly from your local machine:

      from bioblend.cloudman import CloudManConfig
      from bioblend.cloudman import CloudManInstance
      cfg = CloudManConfig('<your cloud access key>', '<your cloud secret key>', 'My CloudMan',  'ami-<ID>', 'm1.small', '<password>')
      cmi = CloudManInstance.launch_instance(cfg)
      cmi.get_status()

- Reconnect to an existing CloudMan instance and manipulate it:

      from bioblend.cloudman import CloudManInstance
      cmi = CloudManInstance("<instance IP>", "<password>")
      cmi.add_nodes(3)
      cluster_status = cmi.get_status()
      cmi.remove_nodes(2)

- Interact with Galaxy via a straightforward API:

      from bioblend.galaxy import GalaxyInstance
      gi = GalaxyInstance('<Galaxy IP>', key='your API key')
      libs = gi.libraries.get_libraries()
      gi.workflows.show_workflow('workflow ID')
      gi.workflows.run_workflow('workflow ID', input_dataset_map)

- Interact with Galaxy via an object-oriented API:

      from bioblend.galaxy.objects import GalaxyInstance
      gi = GalaxyInstance("URL", "API_KEY")
      wf = gi.workflows.list()[0]
      hist = gi.histories.list()[0]
      inputs = hist.get_datasets()[:2]
      input_map = dict(zip(wf.input_labels, inputs))
      params = {"Paste1": {"delimiter": "U"}}
      wf.run(input_map, "wf_output", params=params)

Note

Although this library allows you to blend these two services into a cohesive unit, the library itself can be used with either service irrespective of the other. For example, you can use it to just manipulate CloudMan clusters or to script the interactions with an instance of Galaxy running on your laptop.

## Installation

Stable releases of BioBlend are best installed via `pip` or `easy_install` from PyPI using something like:

    $ pip install bioblend

Alternatively, you may install the most current source code from our Git repository, or fork the project on Github. To install from source, do the following:

    # Clone the repository to a local directory
    $ git clone https://github.com/galaxyproject/bioblend.git
    # Install the library
    $ cd bioblend
    $ python setup.py install

After installing the library, you will be able to simply import it into your Python environment with `import bioblend`. For details on the available functionality, see the API documentation.

BioBlend requires a number of Python libraries. These libraries are installed automatically when BioBlend itself is installed, regardless whether it is installed via PyPi or by running `python setup.py install` command. The current list of required libraries is always available from setup.py in the source code repository.

If you also want to run tests locally, some extra libraries are required. To install them, run:

    $ python setup.py test

## Usage

To get started using BioBlend, install the library as described above. Once the library becomes available on the given system, it can be developed against. The developed scripts do not need to reside in any particular location on the system.

It is probably best to take a look at the example scripts in `docs/examples` source directory and browse the API documentation. Beyond that, it’s up to your creativity :).

## Development

Anyone interested in contributing or tweaking the library is more then welcome to do so. To start, simply fork the Git repository on Github and start playing with it. Then, issue pull requests.

## API Documentation

BioBlend’s API focuses around and matches the services it wraps. Thus, there are two top-level sets of APIs, each corresponding to a separate service and a corresponding step in the automation process. Note that each of the service APIs can be used completely independently of one another.

Effort has been made to keep the structure and naming of those API’s consistent across the library but because they do bridge different services, some discrepancies may exist. Feel free to point those out and/or provide fixes.

For Galaxy, an alternative object-oriented API is also available. This API provides an explicit modeling of server-side Galaxy instances and their relationships, providing higher-level methods to perform operations such as retrieving all datasets for a given history, etc. Note that, at the moment, the oo API is still incomplete, providing access to a more restricted set of Galaxy modules with respect to the standard one.

### CloudMan API

API used to manipulate the instantiated infrastructure. For example, scale the size of the compute cluster, get infrastructure status, get service status.

#### API documentation for interacting with CloudMan

##### CloudManLauncher

##### CloudManInstance

#### Usage documentation

This page describes some sample use cases for CloudMan API and provides examples for these API calls. In addition to this page, there are functional examples of complete scripts in `docs/examples` directory of the BioBlend source code repository.

##### Setting up custom cloud properties

CloudMan supports Amazon, OpenStack, OpenNebula, and Eucalyptus based clouds and BioBlend can be used to programatically manipulate CloudMan on any of those clouds. Once launched, the API calls to CloudMan are the same irrespective of the cloud. In order to launch an instance on a given cloud, cloud properties need to be provided to `CloudManLauncher`. If cloud properties are not specified, `CloudManLauncher` will default to Amazon cloud properties.

If we want to use a different cloud provider, we need to specify additional cloud properties when creating an instance of the `CloudManLauncher` class. For example, if we wanted to create a connection to NeCTAR, Australia’s national research cloud, we would use the following properties:

    from bioblend.util import Bunch
    nectar = Bunch(
        name='NeCTAR',
        cloud_type='openstack',
        bucket_default='cloudman-os',
        region_name='NeCTAR',
        region_endpoint='nova.rc.nectar.org.au',
        ec2_port=8773,
        ec2_conn_path='/services/Cloud',
        cidr_range='115.146.92.0/22',
        is_secure=True,
        s3_host='swift.rc.nectar.org.au',
        s3_port=8888,
        s3_conn_path='/')

Note

These properties are cloud-specific and need to be obtained from a given cloud provider.

##### Launching a new cluster instance

In order to launch a CloudMan cluster on a chosen cloud, we do the following (continuing from the previous example):

    from bioblend.cloudman import CloudManConfig
    from bioblend.cloudman import CloudManInstance
    cmc = CloudManConfig('<your AWS access key', 'your AWS secret key', 'Cluster name',
         'ami-<ID>', 'm1.medium', 'choose_a_password_here', nectar)
    cmi = CloudManInstance.launch_instance(cmc)

Note

If you already have an existing instance of CloudMan, just create an instance of the `CloudManInstance` object directly by calling its constructor and connecting to it (the password you provide must match the password you provided as part of user data when launching this instance). For example:

    cmi = CloudManInstance('http://115.146.92.174', 'your_UD_password')

We now have a `CloudManInstance` object that allows us to manage created CloudMan instance via the API. Once launched, it will take a few minutes for the instance to boot and CloudMan start. To check on the status of the machine, (repeatedly) run the following command:

    >>> cmi.get_machine_status()
    {'error': '',
     'instance_state': u'pending',
     'placement': '',
     'public_ip': ''}
    >>> cmi.get_machine_status()
    {'error': '',
     'instance_state': u'running',
     'placement': u'melbourne-qh2',
     'public_ip': u'115.146.86.29'}

Once the instance is ready, although it may still take a few moments for CloudMan to start, it is possible to start interacting with the application.

Note

The `CloudManInstance` object (e.g., `cmi`) is a local representation of the actual CloudMan instance. As a result, the local object can get out of sync with the remote instance. To update the state of the local object, call the `update` method on the `cmi` object:

    >>> cmi.update()

##### Manipulating an existing cluster

Having a reference to a `CloudManInstance` object, we can manage it via the available CloudManInstance API:

    >>> cmi.initialized
    False
    >>> cmi.initialize('SGE')
    >>> cmi.get_status()
    {u'all_fs': [],
     u'app_status': u'yellow',
     u'autoscaling': {u'as_max': u'N/A',
     u'as_min': u'N/A',
     u'use_autoscaling': False},
     u'cluster_status': u'STARTING',
     u'data_status': u'green',
     u'disk_usage': {u'pct': u'0%', u'total': u'0', u'used': u'0'},
     u'dns': u'#',
     u'instance_status': {u'available': u'0', u'idle': u'0', u'requested': u'0'},
     u'snapshot': {u'progress': u'None', u'status': u'None'}}
    >>> cmi.get_cluster_size()
    1
    >>> cmi.get_nodes()
    [{u'id': u'i-00006016',
      u'instance_type': u'm1.medium',
      u'ld': u'0.0 0.025 0.065',
      u'public_ip': u'115.146.86.29',
      u'time_in_state': u'2268'}]
    >>> cmi.add_nodes(2)
    {u'all_fs': [],
     u'app_status': u'green',
     u'autoscaling': {u'as_max': u'N/A',
      u'as_min': u'N/A',
      u'use_autoscaling': False},
     u'cluster_status': u'READY',
     u'data_status': u'green',
     u'disk_usage': {u'pct': u'0%', u'total': u'0', u'used': u'0'},
     u'dns': u'#',
     u'instance_status': {u'available': u'0', u'idle': u'0', u'requested': u'2'},
     u'snapshot': {u'progress': u'None', u'status': u'None'}}
    >>> cmi.get_cluster_size()
    3

### Galaxy API

API used to manipulate genomic analyses within Galaxy, including data management and workflow execution.

#### API documentation for interacting with Galaxy

##### GalaxyInstance

class `bioblend.galaxy.``GalaxyInstance`(url, key=None, email=None, password=None)

  A base representation of an instance of Galaxy, identified by a URL and a user’s API key.

  After you have created an `GalaxyInstance` object, access various modules via the class fields (see the source for the most up-to-date list): `libraries`, `histories`, `workflows`, `datasets`, and `users` are the minimum set supported. For example, to work with histories, and get a list of all the user’s histories, the following should be done:

      from bioblend import galaxy

      gi = galaxy.GalaxyInstance(url='http://127.0.0.1:8000', key='your_api_key')

      hl = gi.histories.get_histories()

  Parameters:

  - url (str) – A FQDN or IP for a given instance of Galaxy. For example: http://127.0.0.1:8080
  - key (str) – User’s API key for the given instance of Galaxy, obtained from the user preferences. If a key is not supplied, an email address and password must be and key will automatically be created for the user.
  - email (str) – Galaxy e-mail address corresponding to the user. Ignored if key is supplied directly.
  - password (str) – Password of Galaxy account corresponding to the above e-mail address. Ignored if key is supplied directly.

  `__init__`(url, key=None, email=None, password=None)

    A base representation of an instance of Galaxy, identified by a URL and a user’s API key.

    After you have created an `GalaxyInstance` object, access various modules via the class fields (see the source for the most up-to-date list): `libraries`, `histories`, `workflows`, `datasets`, and `users` are the minimum set supported. For example, to work with histories, and get a list of all the user’s histories, the following should be done:

        from bioblend import galaxy

        gi = galaxy.GalaxyInstance(url='http://127.0.0.1:8000', key='your_api_key')

        hl = gi.histories.get_histories()

    Parameters:

    - url (str) – A FQDN or IP for a given instance of Galaxy. For example: http://127.0.0.1:8080
    - key (str) – User’s API key for the given instance of Galaxy, obtained from the user preferences. If a key is not supplied, an email address and password must be and key will automatically be created for the user.
    - email (str) – Galaxy e-mail address corresponding to the user. Ignored if key is supplied directly.
    - password (str) – Password of Galaxy account corresponding to the above e-mail address. Ignored if key is supplied directly.

  `get_retry_delay`
  `max_get_attempts`

##### Config

Contains possible interaction dealing with Galaxy configuration.

class `bioblend.galaxy.config.``ConfigClient`(galaxy_instance)
  `get_config`()

    Get a list of attributes about the Galaxy instance. More attributes will be present if the user is an admin.

    Return type: | list

    Returns:

    A list of attributes. For example:

        {u'allow_library_path_paste': False,
         u'allow_user_creation': True,
         u'allow_user_dataset_purge': True,
         u'allow_user_deletion': False,
         u'enable_unique_workflow_defaults': False,
         u'ftp_upload_dir': u'/SOMEWHERE/galaxy/ftp_dir',
         u'ftp_upload_site': u'galaxy.com',
         u'library_import_dir': u'None',
         u'logo_url': None,
         u'support_url': u'http://wiki.g2.bx.psu.edu/Support',
         u'terms_url': None,
         u'user_library_import_dir': None,
         u'wiki_url': u'http://g2.trac.bx.psu.edu/'}

##### Datasets

Contains possible interactions with the Galaxy Datasets

class `bioblend.galaxy.datasets.``DatasetClient`(galaxy_instance)
  `download_dataset`(dataset_id, file_path=None, use_default_filename=True, wait_for_completion=False, maxwait=12000)

    Downloads the dataset identified by ‘id’.

    Parameters:

    - dataset_id (str) – Encoded dataset ID
    - file_path (str) – If the file_path argument is provided, the dataset will be streamed to disk at that path (Should not contain filename if use_default_name=True). If the file_path argument is not provided, the dataset content is loaded into memory and returned by the method (Memory consumption may be heavy as the entire file will be in memory).
    - use_default_filename (bool) – If the use_default_name parameter is True, the exported file will be saved as file_path/%s, where %s is the dataset name. If use_default_name is False, file_path is assumed to contain the full file path including filename.
    - wait_for_completion (bool) – If wait_for_completion is True, this call will block until the dataset is ready. If the dataset state becomes invalid, a DatasetStateException will be thrown.
    - maxwait (float) – Time (in seconds) to wait for dataset to complete. If the dataset state is not complete within this time, a DatasetTimeoutException will be thrown.

    Return type: | dict
    Returns: | If a file_path argument is not provided, returns a dict containing the file_content. Otherwise returns nothing.

  `show_dataset`(dataset_id, deleted=False, hda_ldda='hda')

    Display information about and/or content of a dataset. This can be a history or a library dataset.

    Parameters:

    - dataset_id (str) – Encoded dataset ID
    - deleted (bool) – Whether to return results for a deleted dataset
    - hda_ldda (str) – Whether to show a history dataset (‘hda’ - the default) or library dataset (‘ldda’).

  `show_stderr`(dataset_id)

    Display stderr output of a dataset.

    Parameters: | dataset_id (str) – Encoded dataset ID

  `show_stdout`(dataset_id)

    Display stdout output of a dataset.

    Parameters: | dataset_id (str) – Encoded dataset ID

exception `bioblend.galaxy.datasets.``DatasetStateException`(value)

exception `bioblend.galaxy.datasets.``DatasetTimeoutException`(value)

##### Datatypes

Contains possible interactions with the Galaxy Datatype

class `bioblend.galaxy.datatypes.``DatatypesClient`(galaxy_instance)
  `get_datatypes`(extension_only=False, upload_only=False)

    Get the list of all installed datatypes.

    Return type: | list

    Returns:

    A list of datatype names. For example:

        [u'snpmatrix',
         u'snptest',
         u'tabular',
         u'taxonomy',
         u'twobit',
         u'txt',
         u'vcf',
         u'wig',
         u'xgmml',
         u'xml']

  `get_sniffers`()

    Get the list of all installed sniffers.

    Return type: | list

    Returns:

    A list of sniffer names. For example:

        [u'galaxy.datatypes.tabular:Vcf',
         u'galaxy.datatypes.binary:TwoBit',
         u'galaxy.datatypes.binary:Bam',
         u'galaxy.datatypes.binary:Sff',
         u'galaxy.datatypes.xml:Phyloxml',
         u'galaxy.datatypes.xml:GenericXml',
         u'galaxy.datatypes.sequence:Maf',
         u'galaxy.datatypes.sequence:Lav',
         u'galaxy.datatypes.sequence:csFasta']

##### Folders

Contains possible interactions with the Galaxy library folders

class `bioblend.galaxy.folders.``FoldersClient`(galaxy_instance)
  `delete_folder`(folder_id, undelete=False)

    Marks the folder with the given `id` as deleted (or removes the deleted mark if the undelete param is True).

    Parameters:

    - folder_id (str) – the folder’s encoded id, prefixed by ‘F’
    - undelete (bool) – If set to True, the folder will be undeleted (i.e. the deleted mark will be removed)

    Returns: | detailed folder information
    Return type: | dict

  `show_folder`(folder_id)

    Display information about a folder.

    Parameters: | folder_id (str) – the folder’s encoded id, prefixed by ‘F’
    Return type: | dict
    Returns: | dictionary including details of the folder

##### Forms

Contains possible interactions with the Galaxy Forms

class `bioblend.galaxy.forms.``FormsClient`(galaxy_instance)
  `create_form`(form_xml_text)

    Create a new form.

    Parameters: | form_xml_text (str) – Form xml to create a form on galaxy instance
    Return type: | str
    Returns: | Unique url of newly created form with encoded id

  `get_forms`()

    Get the list of all forms.

    Return type: | list

    Returns:

    Displays a collection (list) of forms. For example:

        [{u'id': u'f2db41e1fa331b3e',
          u'model_class': u'FormDefinition',
          u'name': u'First form',
          u'url': u'/api/forms/f2db41e1fa331b3e'},
         {u'id': u'ebfb8f50c6abde6d',
          u'model_class': u'FormDefinition',
          u'name': u'second form',
          u'url': u'/api/forms/ebfb8f50c6abde6d'}]

  `show_form`(form_id)

    Get details of a given form.

    Parameters: | form_id (str) – Encoded form ID
    Return type: | dict

    Returns:

    A description of the given form. For example:

        {u'desc': u'here it is ',
         u'fields': [],
         u'form_definition_current_id': u'f2db41e1fa331b3e',
         u'id': u'f2db41e1fa331b3e',
         u'layout': [],
         u'model_class': u'FormDefinition',
         u'name': u'First form',
         u'url': u'/api/forms/f2db41e1fa331b3e'}

##### FTP files

Contains possible interactions with the Galaxy FTP Files

class `bioblend.galaxy.ftpfiles.``FTPFilesClient`(galaxy_instance)
  `get_ftp_files`(deleted=False)

    Get a list of local files.

    Return type: | list
    Returns: | A list of dicts with details on individual files on FTP

##### Genomes

Contains possible interactions with the Galaxy Histories

class `bioblend.galaxy.genomes.``GenomeClient`(galaxy_instance)
  `get_genomes`()

    Returns a list of installed genomes

  `install_genome`(func='download', source=None, dbkey=None, ncbi_name=None, ensembl_dbkey=None, url_dbkey=None, indexers=None)

    Download and/or index a genome.

    Parameters:

    - dbkey (str) – DB key of the build to download, ignored unless ‘UCSC’ is specified as the source
    - ncbi_name (str) – NCBI’s genome identifier, ignored unless NCBI is specified as the source
    - ensembl_dbkey (str) – Ensembl’s genome identifier, ignored unless Ensembl is specified as the source
    - url_dbkey (str) – DB key to use for this build, ignored unless URL is specified as the source
    - source (str) – Data source for this build. Can be: UCSC, Ensembl, NCBI, URL
    - indexers (list) – POST array of indexers to run after downloading (indexers[] = first, indexers[] = second, ...)
    - func (str) – Allowed values: ‘download’, Download and index; ‘index’, Index only

    Return type: | dict
    Returns: | dict( status: ‘ok’, job: <job ID> ) If error: dict( status: ‘error’, error: <error message> )

  `show_genome`(id, num=None, chrom=None, low=None, high=None)

    Returns information about build <id>

    Parameters:

    - id (str) – Genome build ID to use
    - num (str) – num
    - chrom (str) – chrom
    - low (str) – low
    - high (str) – high

##### Groups

Contains possible interactions with the Galaxy Groups

class `bioblend.galaxy.groups.``GroupsClient`(galaxy_instance)
  `add_group_role`(group_id, role_id)

    Add a role to the given group.

    Parameters:

    - group_id (str) – Encoded group ID
    - role_id (str) – Encoded role ID to add to the group

    Return type: | dict
    Returns: | Added group role’s info

  `add_group_user`(group_id, user_id)

    Add a user to the given group.

    Parameters:

    - group_id (str) – Encoded group ID
    - user_id (str) – Encoded user ID to add to the group

    Return type: | dict
    Returns: | Added group user’s info

  `create_group`(group_name, user_ids=[], role_ids=[])

    Create a new group.

    Parameters:

    - group_name (str) – A name for the new group
    - user_ids (list) – A list of encoded user IDs to add to the new group
    - role_ids (list) – A list of encoded role IDs to add to the new group

    Return type: | list

    Returns:

    A (size 1) list with newly created group details, like:

        [{u'id': u'7c9636938c3e83bf',
          u'model_class': u'Group',
          u'name': u'My Group Name',
          u'url': u'/api/groups/7c9636938c3e83bf'}]

  `delete_group_role`(group_id, role_id)

    Remove a role from the given group.

    Parameters:

    - group_id (str) – Encoded group ID
    - role_id (str) – Encoded role ID to remove from the group

  `delete_group_user`(group_id, user_id)

    Remove a user from the given group.

    Parameters:

    - group_id (str) – Encoded group ID
    - user_id (str) – Encoded user ID to remove from the group

  `get_group_roles`(group_id)

    Get the list of roles associated to the given group.

    Parameters: | group_id (str) – Encoded group ID
    Return type: | list of dicts
    Returns: | List of group roles’ info

  `get_group_users`(group_id)

    Get the list of users associated to the given group.

    Parameters: | group_id (str) – Encoded group ID
    Return type: | list of dicts
    Returns: | List of group users’ info

  `get_groups`()

    Get all (not deleted) groups.

    Return type: | list

    Returns:

    A list of dicts with details on individual groups. For example:

        [ {"name": "Listeria", "url": "/api/groups/33abac023ff186c2",
        "model_class": "Group", "id": "33abac023ff186c2"},
        {"name": "LPN", "url": "/api/groups/73187219cd372cf8",
        "model_class": "Group", "id": "73187219cd372cf8"}
        ]

  `show_group`(group_id)

    Get details of a given group.

    Parameters: | group_id (str) – Encoded group ID
    Return type: | dict

    Returns:

    A description of group For example:

        {"roles_url": "/api/groups/33abac023ff186c2/roles",
        "name": "Listeria", "url": "/api/groups/33abac023ff186c2",
        "users_url": "/api/groups/33abac023ff186c2/users",
        "model_class": "Group", "id": "33abac023ff186c2"}

  `update_group`(group_id, group_name=None, user_ids=[], role_ids=[])

    Update a group.

    Parameters:

    - group_id (str) – Encoded group ID
    - group_name (str) – A new name for the group. If None, the group name is not changed.
    - user_ids (list) – New list of encoded user IDs for the group. It will substitute the previous list of users (with [] if not specified)
    - role_ids (list) – New list of encoded role IDs for the group. It will substitute the previous list of roles (with [] if not specified)

    Return type: | int
    Returns: | status code

##### Histories

Contains possible interactions with the Galaxy Histories

class `bioblend.galaxy.histories.``HistoryClient`(galaxy_instance)
  `create_dataset_collection`(history_id, collection_description)

    Create a new dataset collection

    Parameters:

    - history_id (str) – Encoded history ID
    - collection_description (str) – a description of the dataset collection

  `create_history`(name=None)

    Create a new history, optionally setting the `name`.

    Parameters: | name (str) – Optional name for new history
    Return type: | dict
    Returns: | Dictionary containing information about newly created history

  `create_history_tag`(history_id, tag)

    Create history tag

    Parameters:

    - history_id (str) – Encoded history ID
    - tag (str) – Add tag to history

    Return type: | dict

    Returns:

    A dictionary with information regarding the tag. For example:

        {'model_class':'HistoryTagAssociation', 'user_tname': 'NGS_PE_RUN', 'id': 'f792763bee8d277a', 'user_value': None}

  `delete_dataset`(history_id, dataset_id)

    Mark corresponding dataset as deleted.

    Parameters:

    - history_id (str) – Encoded history ID
    - dataset_id (str) – Encoded dataset ID

  `delete_dataset_collection`(history_id, dataset_collection_id)

    Mark corresponding dataset collection as deleted.

    Parameters:

    - history_id (str) – Encoded history ID
    - dataset_collection_id (str) – Encoded dataset collection ID

  `delete_history`(history_id, purge=False)

    Delete a history.

    Parameters:

    - history_id (str) – Encoded history ID
    - purge (bool) – if `True`, also purge (permanently delete) the history

    Note

    For the purge option to work, the Galaxy instance must have the `allow_user_dataset_purge` option set to `True` in the `config/galaxy.ini` configuration file.

  `download_dataset`(history_id, dataset_id, file_path, use_default_filename=True)

    Download a `dataset_id` from history with `history_id` to a file on the local file system, saving it to `file_path`.

    Refer to `bioblend.galaxy.dataset.DatasetClient.download_dataset()` for the other available parameters.

  `download_history`(history_id, jeha_id, outf, chunk_size=4096)

    Download a history export archive. Use `export_history()` to create an export.

    Parameters:

    - history_id (str) – history ID
    - jeha_id (str) – jeha ID (this should be obtained via `export_history()`)
    - outf (file) – output file object, open for writing in binary mode
    - chunk_size (int) – how many bytes at a time should be read into memory

  `export_history`(history_id, gzip=True, include_hidden=False, include_deleted=False, wait=False)

    Start a job to create an export archive for the given history.

    Parameters:

    - history_id (str) – history ID
    - gzip (bool) – create .tar.gz archive if `True`, else .tar
    - include_hidden (bool) – whether to include hidden datasets in the export
    - include_deleted (bool) – whether to include deleted datasets in the export
    - wait (bool) – if `True`, block until the export is ready; else, return immediately

    Return type: | str
    Returns: | `jeha_id` of the export, or empty if `wait` is `False` and the export is not ready.

  `get_current_history`()

    Deprecated method.

    Just an alias for get_most_recently_used_history().

  `get_histories`(history_id=None, name=None, deleted=False)

    Get all histories or filter the specific one(s) via the provided `name` or `history_id`. Provide only one argument, `name` or `history_id`, but not both.

    If `deleted` is set to `True`, return histories that have been deleted.

    Parameters:

    - history_id (str) – Encoded history ID to filter on
    - name (str) – Name of history to filter on

    Return type: | list
    Returns: | Return a list of history element dicts. If more than one history matches the given `name`, return the list of all the histories with the given name

  `get_most_recently_used_history`()

    Returns the current user’s most recently used history (not deleted).

  `get_status`(history_id)

    Returns the state of this history

    Parameters: | history_id (str) – Encoded history ID
    Return type: | dict
    Returns: | A dict documenting the current state of the history. Has the following keys: ‘state’ = This is the current state of the history, such as ok, error, new etc. ‘state_details’ = Contains individual statistics for various dataset states. ‘percent_complete’ = The overall number of datasets processed to completion.

  `show_dataset`(history_id, dataset_id)

    Get details about a given history dataset.

    Parameters:

    - history_id (str) – Encoded history ID
    - dataset_id (str) – Encoded dataset ID

  `show_dataset_collection`(history_id, dataset_collection_id)

    Get details about a given history dataset collection.

    Parameters:

    - history_id (str) – Encoded history ID
    - dataset_collection_id (str) – Encoded dataset collection ID

  `show_dataset_provenance`(history_id, dataset_id, follow=False)

    Get details related to how dataset was created (`id`, `job_id`, `tool_id`, `stdout`, `stderr`, `parameters`, `inputs`, etc...).

    Parameters:

    - history_id (str) – Encoded history ID
    - dataset_id (str) – Encoded dataset ID
    - follow (bool) – If `follow` is `True`, recursively fetch dataset provenance information for all inputs and their inputs, etc...

  `show_history`(history_id, contents=False, deleted=None, visible=None, details=None, types=None)

    Get details of a given history. By default, just get the history meta information.

    Parameters:

    - history_id (str) – Encoded history ID to filter on
    - contents (bool) – When `True`, the complete list of datasets in the given history.
    - deleted (str) – Used when contents=True, includes deleted datasets in history dataset list
    - visible (str) – Used when contents=True, includes only visible datasets in history dataset list
    - details (str) – Used when contents=True, includes dataset details. Set to ‘all’ for the most information
    - types (str) –

      ???

    Return type: | dict
    Returns: | details of the given history

  `show_matching_datasets`(history_id, name_filter=None)

    Get dataset details for matching datasets within a history.

    Parameters:

    - history_id (str) – Encoded history ID
    - name_filter (str) – Only datasets whose name matches the `name_filter` regular expression will be returned; use plain strings for exact matches and None to match all datasets in the history

  `undelete_history`(history_id)

    Undelete a history

    Parameters: | history_id (str) – Encoded history ID

  `update_dataset`(history_id, dataset_id, **kwds)

    Update history dataset metadata. Some of the attributes that can be modified are documented below.

    Parameters:

    - history_id (str) – Encoded history ID
    - dataset_id (str) – Id of the dataset
    - name (str) – Replace history dataset name with the given string
    - annotation (str) – Replace history dataset annotation with given string
    - deleted (bool) – Mark or unmark history dataset as deleted
    - visible (bool) – Mark or unmark history dataset as visible

    Return type: | int
    Returns: | status code

  `update_dataset_collection`(history_id, dataset_collection_id, **kwds)

    Update history dataset collection metadata. Some of the attributes that can be modified are documented below.

    Parameters:

    - history_id (str) – Encoded history ID
    - dataset_collection_id (str) – Encoded dataset_collection ID
    - name (str) – Replace history dataset collection name with the given string
    - deleted (bool) – Mark or unmark history dataset collection as deleted
    - visible (bool) – Mark or unmark history dataset collection as visible

    Return type: | int
    Returns: | status code

  `update_history`(history_id, name=None, annotation=None, **kwds)

    Update history metadata information. Some of the attributes that can be modified are documented below.

    Parameters:

    - history_id (str) – Encoded history ID
    - name (str) – Replace history name with the given string
    - annotation (str) – Replace history annotation with given string
    - deleted (bool) – Mark or unmark history as deleted
    - published (bool) – Mark or unmark history as published
    - importable (bool) – Mark or unmark history as importable
    - tags (list) – Replace history tags with the given list

    Return type: | int
    Returns: | status code

  `upload_dataset_from_library`(history_id, lib_dataset_id)

    Upload a dataset into the history from a library. Requires the library dataset ID, which can be obtained from the library contents.

    Parameters:

    - history_id (str) – Encoded history ID
    - lib_dataset_id (str) – Encoded library dataset ID

##### Jobs

Contains possible interactions with the Galaxy Jobs

class `bioblend.galaxy.jobs.``JobsClient`(galaxy_instance)
  `get_jobs`()

    Get the list of jobs of the current user.

    Return type: | list

    Returns:

    list of dictionaries containing summary job information. For example:

        [{u'create_time': u'2014-03-01T16:16:48.640550',
          u'exit_code': 0,
          u'id': u'ebfb8f50c6abde6d',
          u'model_class': u'Job',
          u'state': u'ok',
          u'tool_id': u'fasta2tab',
          u'update_time': u'2014-03-01T16:16:50.657399'},
         {u'create_time': u'2014-03-01T16:05:34.851246',
          u'exit_code': 0,
          u'id': u'1cd8e2f6b131e891',
          u'model_class': u'Job',
          u'state': u'ok',
          u'tool_id': u'upload1',
          u'update_time': u'2014-03-01T16:05:39.558458'}]

  `get_state`(job_id)

    Display the current state for a given job of the current user.

    Parameters: | job_id (str) – job ID
    Return type: | str
    Returns: | state of the given job among the following values: new, queued, running, waiting, ok. If the state cannot be retrieved, an empty string is returned.

    New in version 0.5.3.

  `search_jobs`(job_info)

    Return jobs for the current user based payload content.

    Parameters: | job_info (dict) – dictionary containing description of the requested job. This is in the same format as a request to POST /api/tools would take to initiate a job
    Return type: | list
    Returns: | list of dictionaries containing summary job information of the jobs that match the requested job run

    This method is designed to scan the list of previously run jobs and find records of jobs that had the exact some input parameters and datasets. This can be used to minimize the amount of repeated work, and simply recycle the old results.

  `show_job`(job_id, full_details=False)

    Get details of a given job of the current user.

    Parameters:

    - job_id (str) – job ID
    - full_details (bool) – when `True`, the complete list of details for the given job.

    Return type: | dict

    Returns:

    A description of the given job. For example:

        {u'create_time': u'2014-03-01T16:17:29.828624',
         u'exit_code': 0,
         u'id': u'a799d38679e985db',
         u'inputs': {u'input': {u'id': u'ebfb8f50c6abde6d',
           u'src': u'hda'}},
         u'model_class': u'Job',
         u'outputs': {u'output': {u'id': u'a799d38679e985db',
           u'src': u'hda'}},
         u'params': {u'chromInfo': u'"/opt/galaxy-central/tool-data/shared/ucsc/chrom/?.len"',
           u'dbkey': u'"?"',
           u'seq_col': u'"2"',
           u'title_col': u'["1"]'},
         u'state': u'ok',
         u'tool_id': u'tab2fasta',
         u'update_time': u'2014-03-01T16:17:31.930728'}

##### Libraries

Contains possible interactions with the Galaxy Data Libraries

class `bioblend.galaxy.libraries.``LibraryClient`(galaxy_instance)
  `copy_from_dataset`(library_id, dataset_id, folder_id=None, message='')

    Copy a Galaxy dataset into a library.

    Parameters:

    - library_id (str) – id of the library where to place the uploaded file
    - dataset_id (str) – id of the dataset to copy from
    - folder_id (str) – id of the folder where to place the uploaded files. If not provided, the root folder will be used
    - message (str) – message for copying action

  `create_folder`(library_id, folder_name, description=None, base_folder_id=None)

    Create a folder in a library.

    Parameters:

    - library_id (str) – library id to use
    - folder_name (str) – name of the new folder in the data library
    - description (str) – description of the new folder in the data library
    - base_folder_id (str) – id of the folder where to create the new folder. If not provided, the root folder will be used

  `create_library`(name, description=None, synopsis=None)

    Create a data library with the properties defined in the arguments. Return a list of JSON dicts, looking like so:

        :type name: str
        :param name: Name of the new data library

    Parameters:

    - description (str) – Optional data library description
    - synopsis (str) – Optional data library synopsis

    Return type: | dict

    Returns:

    details of the created library:
    {“id”: “f740ab636b360a70”,

      “name”: “Library from bioblend”, “url”: “/api/libraries/f740ab636b360a70”}

  `delete_library`(library_id)

    Delete a data library.

    Parameters: | library_id (str) – Encoded data library ID identifying the library to be deleted

    Warning

    Deleting a data library is irreversible - all of the data from the library will be permanently deleted.

  `delete_library_dataset`(library_id, dataset_id, purged=False)

    Delete a library dataset in a data library.

    Parameters:

    - library_id (str) – library id where dataset is found in
    - dataset_id (str) – id of the dataset to be deleted
    - purged (bool) – Indicate that the dataset should be purged (permanently deleted)

    Return type: | dict

    Returns:

    A dictionary containing the dataset id and whether the dataset has been deleted For example:

        {u'deleted': True, u'id': u'60e680a037f41974'}

  `get_folders`(library_id, folder_id=None, name=None)

    Get all the folders or filter specific one(s) via the provided `name` or `folder_id` in data library with id `library_id`. Provide only one argument: `name` or `folder_id`, but not both.

    Parameters:

    - folder_id (str) – filter for folder by folder id
    - name (str) – filter for folder by name. For `name` specify the full path of the folder starting from the library’s root folder, e.g. `/subfolder/subsubfolder`.

    Return type: | list
    Returns: | list of dicts each containing basic information about a folder.

  `get_libraries`(library_id=None, name=None, deleted=False)

    Get all the libraries or filter for specific one(s) via the provided name or ID. Provide only one argument: `name` or `library_id`, but not both.

    Parameters:

    - library_id (str) – filter for library by library id
    - name (str) – If `name` is set and multiple names match the given name, all the libraries matching the argument will be returned.
    - deleted (bool) – If set to `True`, return libraries that have been deleted.

    Return type: | list
    Returns: | list of dicts each containing basic information about a library.

  `get_library_permissions`(library_id)

    Get the permessions for a library.

    Parameters: | library_id (str) – id of the library
    Return type: | dict
    Returns: | dictionary with all applicable permissions’ values

  `set_library_permissions`(library_id, access_in=None, modify_in=None, add_in=None, manage_in=None)

    Set the permissions for a library. Note: it will override all security for this library even if you leave out a permission type.

    Parameters:

    - library_id (str) – id of the library
    - access_in (list) – list of role ids
    - modify_in (list) – list of role ids
    - add_in (list) – list of role ids
    - manage_in (list) – list of role ids

  `show_dataset`(library_id, dataset_id)

    Get details about a given library dataset. The required `library_id` can be obtained from the datasets’s library content details.

    Parameters:

    - library_id (str) – library id where dataset is found in
    - dataset_id (str) – id of the dataset to be inspected

    Return type: | dict
    Returns: | A dictionary containing information about the dataset in the library

  `show_folder`(library_id, folder_id)

    Get details about a given folder. The required `folder_id` can be obtained from the folder’s library content details.

    Parameters:

    - library_id (str) – library id to inspect folders in
    - folder_id (str) – id of the folder to be inspected

  `show_library`(library_id, contents=False)

    Get information about a library.

    Parameters:

    - library_id (str) – filter for library by library id
    - contents (bool) – True if want to get contents of the library (rather than just the library details).

    Return type: | dict
    Returns: | details of the given library

  `upload_file_contents`(library_id, pasted_content, folder_id=None, file_type='auto', dbkey='?')

    Upload pasted_content to a data library as a new file.

    Parameters:

    - library_id (str) – id of the library where to place the uploaded file
    - pasted_content (str) – Content to upload into the library
    - folder_id (str) – id of the folder where to place the uploaded file. If not provided, the root folder will be used
    - file_type (str) – Galaxy file format name
    - dbkey (str) – Dbkey

  `upload_file_from_local_path`(library_id, file_local_path, folder_id=None, file_type='auto', dbkey='?')

    Read local file contents from file_local_path and upload data to a library.

    Parameters:

    - library_id (str) – id of the library where to place the uploaded file
    - file_local_path (str) – path of local file to upload
    - folder_id (str) – id of the folder where to place the uploaded file. If not provided, the root folder will be used
    - file_type (str) – Galaxy file format name
    - dbkey (str) – Dbkey

  `upload_file_from_server`(library_id, server_dir, folder_id=None, file_type='auto', dbkey='?', link_data_only=None, roles='')

    Upload all files in the specified subdirectory of the Galaxy library import directory to a library.

    Note

    For this method to work, the Galaxy instance must have the `library_import_dir` option configured in the `config/galaxy.ini` configuration file.

    Parameters:

    - library_id (str) – id of the library where to place the uploaded file
    - server_dir (str) – relative path of the subdirectory of `library_import_dir` to upload. All and only the files (i.e. no subdirectories) contained in the specified directory will be uploaded.
    - folder_id (str) – id of the folder where to place the uploaded files. If not provided, the root folder will be used
    - file_type (str) – Galaxy file format name
    - dbkey (str) – Dbkey
    - link_data_only (str) – either ‘copy_files’ (default) or ‘link_to_files’. Setting to ‘link_to_files’ symlinks instead of copying the files
    - roles (str) –

      ???

  `upload_file_from_url`(library_id, file_url, folder_id=None, file_type='auto', dbkey='?')

    Upload a file to a library from a URL.

    Parameters:

    - library_id (str) – id of the library where to place the uploaded file
    - file_url (str) – URL of the file to upload
    - folder_id (str) – id of the folder where to place the uploaded file. If not provided, the root folder will be used
    - file_type (str) – Galaxy file format name
    - dbkey (str) – Dbkey

  `upload_from_galaxy_filesystem`(library_id, filesystem_paths, folder_id=None, file_type='auto', dbkey='?', link_data_only=None, roles='')

    Upload a set of files already present on the filesystem of the Galaxy server to a library.

    Note

    For this method to work, the Galaxy instance must have the `allow_library_path_paste` option set to `True` in the `config/galaxy.ini` configuration file.

    Parameters:

    - library_id (str) – id of the library where to place the uploaded file
    - filesystem_paths (str) – file paths on the Galaxy server to upload to the library, one file per line
    - folder_id (str) – id of the folder where to place the uploaded files. If not provided, the root folder will be used
    - file_type (str) – Galaxy file format name
    - dbkey (str) – Dbkey
    - link_data_only (str) – either ‘copy_files’ (default) or ‘link_to_files’. Setting to ‘link_to_files’ symlinks instead of copying the files
    - roles (str) –

      ???

##### Quotas

Contains possible interactions with the Galaxy Quota

class `bioblend.galaxy.quotas.``QuotaClient`(galaxy_instance)
  `get_quotas`(deleted=False)

    Get a list of quotas

    Parameters: | deleted (bool) – Only return quota(s) that have been deleted
    Return type: | list

    Returns:

    A list of dicts with details on individual quotas. For example:

        [{   u'id': u'0604c8a56abe9a50',
        u'model_class': u'Quota',
        u'name': u'test ',
        u'url': u'/api/quotas/0604c8a56abe9a50'},
        {   u'id': u'1ee267091d0190af',
        u'model_class': u'Quota',
        u'name': u'workshop',
        u'url': u'/api/quotas/1ee267091d0190af'}]

  `show_quota`(quota_id, deleted=False)

    Display information on a quota

    Parameters:

    - quota_id (str) – Encoded quota ID
    - deleted (bool) – Search for quota in list of ones already marked as deleted

    Return type: | dict

    Returns:

    A description of quota For example:

        {   u'bytes': 107374182400,
        u'default': [],
        u'description': u'just testing',
        u'display_amount': u'100.0 GB',
        u'groups': [],
        u'id': u'0604c8a56abe9a50',
        u'model_class': u'Quota',
        u'name': u'test ',
        u'operation': u'=',
        u'users': []}

##### Roles

Contains possible interactions with the Galaxy Roles

class `bioblend.galaxy.roles.``RolesClient`(galaxy_instance)
  `get_roles`()

    Displays a collection (list) of roles.

    Return type: | list

    Returns:

    A list of dicts with details on individual roles. For example:

        [ {"id": "f2db41e1fa331b3e",
        "model_class": "Role",
        "name": "Foo",
        "url": "/api/roles/f2db41e1fa331b3e"},
        {"id": "f597429621d6eb2b",
        "model_class": "Role",
        "name": "Bar",
        "url": "/api/roles/f597429621d6eb2b"}
        ]

  `show_role`(role_id)

    Display information on a single role

    Parameters: | role_id (str) – Encoded role ID
    Return type: | dict

    Returns:

    A description of role For example:

        {"description": "Private Role for Foo",
        "id": "f2db41e1fa331b3e",
        "model_class": "Role",
        "name": "Foo",
        "type": "private",
        "url": "/api/roles/f2db41e1fa331b3e"}

##### Tools

Contains possible interaction dealing with Galaxy tools.

class `bioblend.galaxy.tools.``ToolClient`(galaxy_instance)
  `get_tool_panel`()

    Get a list of available tool elements in Galaxy’s configured toolbox.

    Return type: | list
    Returns: | List containing tools (if not in sections) or tool sections with nested tool descriptions.

    See also

    bioblend.galaxy.toolshed.get_repositories()

  `get_tools`(tool_id=None, name=None, trackster=None)

    Get all tools or filter the specific one(s) via the provided `name` or `tool_id`. Provide only one argument, `name` or `tool_id`, but not both.

    If `name` is set and multiple names match the given name, all the tools matching the argument will be returned.

    Parameters:

    - tool_id (str) – id of the requested tool
    - name (str) – name of the requested tool(s)
    - trackster (bool) – if True, only tools that are compatible with Trackster are returned

    Return type: | list
    Returns: | List of tool descriptions.

    See also

    bioblend.galaxy.toolshed.get_repositories()

  `paste_content`(content, history_id, **kwds)

    Upload a string to a new dataset in the history specified by `history_id`.

    Parameters:

    - content (str) – content of the new dataset to upload or a list of URLs (one per line) to upload
    - history_id (str) – id of the history where to upload the content

    See `upload_file()` for the optional parameters (except file_name).

  `put_url`(content, history_id, **kwds)

    Upload a string to a new dataset in the history specified by `history_id`.

    Parameters:

    - content (str) – content of the new dataset to upload or a list of URLs (one per line) to upload
    - history_id (str) – id of the history where to upload the content

    See `upload_file()` for the optional parameters (except file_name).

  `run_tool`(history_id, tool_id, tool_inputs)

    Runs tool specified by `tool_id` in history indicated by `history_id` with inputs from `dict` `tool_inputs`.

    Parameters:

    - history_id (str) – encoded ID of the history in which to run the tool
    - tool_id (str) – ID of the tool to be run
    - tool_inputs (dict) – dictionary of input datasets and parameters for the tool (see below)

    The `tool_inputs` dict should contain input datasets and parameters in the (largely undocumented) format used by the Galaxy API. Some examples can be found in https://bitbucket.org/galaxy/galaxy-central/src/tip/test/api/test_tools.py .

  `show_tool`(tool_id, io_details=False, link_details=False)

    Get details of a given tool.

    Parameters:

    - tool_id (str) – id of the requested tool
    - io_details (bool) – if True, get also input and output details
    - link_details (bool) – if True, get also link details

  `upload_file`(path, history_id, **keywords)

    Upload the file specified by `path` to the history specified by `history_id`.

    Parameters:

    - path (str) – path of the file to upload
    - history_id (str) – id of the history where to upload the file
    - file_name (str) – (optional) name of the new history dataset
    - file_type (str) – Galaxy datatype for the new dataset, default is auto
    - dbkey (str) – (optional) genome dbkey
    - to_posix_lines (bool) – if True, convert universal line endings to POSIX line endings. Default is True. Set to False if you upload a gzip, bz2 or zip archive containing a binary file
    - space_to_tab (bool) – whether to convert spaces to tabs. Default is False. Applicable only if to_posix_lines is True

  `upload_from_ftp`(path, history_id, **keywords)

    Upload the file specified by `path` from the user’s FTP directory to the history specified by `history_id`.

    Parameters:

    - path (str) – path of the file in the user’s FTP directory
    - history_id (str) – id of the history where to upload the file

    See `upload_file()` for the optional parameters.

##### Tool data tables

Contains possible interactions with the Galaxy Tool data tables

class `bioblend.galaxy.tool_data.``ToolDataClient`(galaxy_instance)
  `delete_data_table`(data_table_id, values)

    Delete an item from a data table.

    Parameters:

    - data_table_id (str) – ID of the data table
    - values (str) – a “|” separated list of column contents, there must be a value for all the columns of the data table

  `get_data_tables`()

    Get the list of all data tables.

    Return type: | list

    Returns:

    A list of dicts with details on individual data tables. For example:

        [{"model_class": "TabularToolDataTable", "name": "fasta_indexes"},
         {"model_class": "TabularToolDataTable", "name": "bwa_indexes"}]

  `show_data_table`(data_table_id)

    Get details of a given data table.

    Parameters: | data_table_id (str) – ID of the data table
    Return type: | dict

    Returns:

    A description of the given data table and its content. For example:

        {"columns": ["value", "dbkey", "name", "path"],
         "fields": [["test id",
           "test",
           "test name",
           "/opt/galaxy-dist/tool-data/test/seq/test id.fa"]],
         "model_class": "TabularToolDataTable",
         "name": "all_fasta"}

##### ToolShed

Interaction with a Galaxy Tool Shed

class `bioblend.galaxy.toolshed.``ToolShedClient`(galaxy_instance)
  `get_repositories`()

    Get the list of all installed Tool Shed repositories on this Galaxy instance.

    Return type: | list

    Returns:

    a list of dictionaries containing information about repositories present in the Tool Shed. For example:

        [{u'changeset_revision': u'4afe13ac23b6',
          u'deleted': False,
          u'dist_to_shed': False,
          u'error_message': u'',
          u'name': u'velvet_toolsuite',
          u'owner': u'edward-kirton',
          u'status': u'Installed'}]

    Changed in version 0.4.1: Changed method name from `get_tools` to `get_repositories` to better align with the Tool Shed concepts

    See also

    bioblend.galaxy.tools.get_tool_panel()

  `install_repository_revision`(tool_shed_url, name, owner, changeset_revision, install_tool_dependencies=False, install_repository_dependencies=False, tool_panel_section_id=None, new_tool_panel_section_label=None)

    Install a specified repository revision from a specified Tool Shed into this Galaxy instance. This example demonstrates installation of a repository that contains valid tools, loading them into a section of the Galaxy tool panel or creating a new tool panel section. You can choose if tool dependencies or repository dependencies should be installed, use `install_tool_dependencies` or `install_repository_dependencies`.

    Installing the repository into an existing tool panel section requires the tool panel config file (e.g., tool_conf.xml, shed_tool_conf.xml, etc) to contain the given tool panel section:

    > <section id=”from_test_tool_shed” name=”From Test Tool Shed” version=”“> </section>

    Parameters:

    - tool_shed_url (str) – URL of the Tool Shed from which the repository should be installed from (e.g., `http://testtoolshed.g2.bx.psu.edu`)
    - name (str) – The name of the repository that should be installed
    - owner (str) – The name of the repository owner
    - changeset_revision (str) – The revision of the repository to be installed
    - install_tool_dependencies (bool) – Whether or not to automatically handle tool dependencies (see http://wiki.galaxyproject.org/AToolOrASuitePerRepository for more details)
    - install_repository_dependencies (bool) – Whether or not to automatically handle repository dependencies (see http://wiki.galaxyproject.org/DefiningRepositoryDependencies for more details)
    - tool_panel_section_id (str) – The ID of the Galaxy tool panel section where the tool should be insterted under. Note that you should specify either this parameter or the `new_tool_panel_section_label`. If both are specified, this one will take precedence.
    - new_tool_panel_section_label (str) – The name of a Galaxy tool panel section that should be created and the repository installed into.

  `show_repository`(toolShed_id)

    Get details of a given Tool Shed repository as it is installed on this Galaxy instance.

    Parameters: | toolShed_id (str) – Encoded toolShed ID
    Return type: | dict

    Returns:

    Information about the tool For example:

        {u'changeset_revision': u'b17455fb6222',
         u'ctx_rev': u'8',
         u'owner': u'aaron',
         u'status': u'Installed',
         u'url': u'/api/tool_shed_repositories/82de4a4c7135b20a'}

    Changed in version 0.4.1: Changed method name from `show_tool` to `show_repository` to better align with the Tool Shed concepts

##### Users

Contains possible interaction dealing with Galaxy users.

These methods must be executed by a registered Galaxy admin user.

class `bioblend.galaxy.users.``UserClient`(galaxy_instance)
  `create_local_user`(username, user_email, password)

    Create a new Galaxy user.

    Note

    For this method to work, the Galaxy instance must have the `allow_user_creation` option set to `True` and `use_remote_user` option set to `False` in the `config/galaxy.ini` configuration file.

    Parameters:

    - username (str) – Username of user to be created
    - user_email (str) – Email of user to be created
    - password (str) – password of user to be created

    Return type: | dict
    Returns: | dictionary containing information about the created user

  `create_remote_user`(user_email)

    Create a new Galaxy remote user.

    Note

    For this method to work, the Galaxy instance must have the `allow_user_creation` and `use_remote_user` options set to `True` in the `config/galaxy.ini` configuration file. Also note that setting `use_remote_user` will require an upstream authentication proxy server; however, if you do not have one, access to Galaxy via a browser will not be possible.

    Parameters: | user_email (str) – Email of user to be created
    Return type: | dict
    Returns: | dictionary containing information about the created user

  `create_user`(user_email)

    Deprecated method.

    Just an alias for create_remote_user().

  `create_user_apikey`(user_id)

    Create a new api key for a user

    Parameters: | user_id (str) – Encoded user ID
    Return type: | str
    Returns: | The api key for the user

  `get_current_user`()

    Returns the user id associated with this Galaxy connection

    Return type: | dict
    Returns: | dictionary containing information about the current user

  `get_users`(deleted=False)

    Get a list of all registered users. If `deleted` is set to `True`, get a list of deleted users.

    Return type: | list

    Returns:

    A list of dicts with user details. For example:

        [{u'email': u'a_user@example.com',
          u'id': u'dda47097d9189f15',
          u'url': u'/api/users/dda47097d9189f15'}]

  `show_user`(user_id, deleted=False)

    Display information about a user. If `deleted` is set to `True`, display information about a deleted user.

    Parameters:

    - user_id (str) – User ID to inspect
    - deleted (bool) – Whether to return results for a deleted user

    Return type: | dict
    Returns: | dictionary containing information about the user

##### Visual

Contains possible interactions with the Galaxy visualization

class `bioblend.galaxy.visual.``VisualClient`(galaxy_instance)
  `get_visualizations`()

    Get the list of all visualizations.

    Return type: | list

    Returns:

    A list of dicts with details on individual visualizations. For example:

        [{u'dbkey': u'eschColi_K12',
          u'id': u'df1c7c96fc427c2d',
          u'title': u'AVTest1',
          u'type': u'trackster',
          u'url': u'/api/visualizations/df1c7c96fc427c2d'},
         {u'dbkey': u'mm9',
          u'id': u'a669f50f8bf55b02',
          u'title': u'Bam to Bigwig',
          u'type': u'trackster',
          u'url': u'/api/visualizations/a669f50f8bf55b02'}]

  `show_visualization`(visual_id)

    Get details of a given visualization.

    Parameters: | visual_id (str) – Encoded visualization ID
    Return type: | dict

    Returns:

    A description of the given visualization. For example:

        {u'annotation': None,
         u'dbkey': u'mm9',
         u'id': u'18df9134ea75e49c',
         u'latest_revision': {  ... },
         u'model_class': u'Visualization',
         u'revisions': [u'aa90649bb3ec7dcb', u'20622bc6249c0c71'],
         u'slug': u'visualization-for-grant-1',
         u'title': u'Visualization For Grant',
         u'type': u'trackster',
         u'url': u'/u/azaron/v/visualization-for-grant-1',
         u'user_id': u'21e4aed91386ca8b'}

##### Workflows

Contains possible interactions with the Galaxy Workflows

class `bioblend.galaxy.workflows.``WorkflowClient`(galaxy_instance)
  `cancel_invocation`(workflow_id, invocation_id)

    Cancel the scheduling of a workflow.

    Parameters:

    - workflow_id (str) – Encoded workflow ID
    - invocation_id (str) – Encoded workflow invocation ID

  `delete_workflow`(workflow_id)

    Delete a workflow identified by workflow_id.

    Parameters: | workflow_id (str) – Encoded workflow ID

    Warning

    Deleting a workflow is irreversible - all workflow data will be permanently deleted.

  `export_workflow_json`(workflow_id)

    Exports a workflow

    Parameters: | workflow_id (str) – Encoded workflow ID
    Return type: | dict
    Returns: | Dict representing the workflow requested

  `export_workflow_to_local_path`(workflow_id, file_local_path, use_default_filename=True)

    Exports a workflow in json format to a given local path.

    Parameters:

    - workflow_id (str) – Encoded workflow ID
    - file_local_path (str) – Local path to which the exported file will be saved. (Should not contain filename if use_default_name=True)
    - use_default_filename (bool) – If the use_default_name parameter is True, the exported file will be saved as file_local_path/Galaxy-Workflow-%s.ga, where %s is the workflow name. If use_default_name is False, file_local_path is assumed to contain the full file path including filename.

  `get_invocations`(workflow_id)

    Get a list containing all the workflow invocations corresponding to the specified workflow.

    Parameters: | workflow_id (str) – Encoded workflow ID
    Return type: | list

    Returns:

    A list of workflow invocations. For example:

        [{u'update_time': u'2015-10-31T22:00:22',
          u'uuid': u'c8aa2b1c-801a-11e5-a9e5-8ca98228593c',
          u'history_id': u'2f94e8ae9edff68a',
          u'workflow_id': u'03501d7626bd192f',
          u'state': u'new',
          u'model_class': u'WorkflowInvocation',
          u'id': u'df7a1f0c02a5b08e'}
        ]

  `get_workflow_inputs`(workflow_id, label)

    Get a list of workflow input IDs that match the given label. If no input matches the given label, an empty list is returned.

    Parameters:

    - workflow_id (str) – Encoded workflow ID
    - label (str) – label to filter workflow inputs on

    Return type: | list
    Returns: | list of workflow inputs matching the label query

  `get_workflows`(workflow_id=None, name=None, published=False)

    Get all workflows or filter the specific one(s) via the provided `name` or `workflow_id`. Provide only one argument, `name` or `workflow_id`, but not both.

    Parameters:

    - workflow_id (str) – Encoded workflow ID (incompatible with `name`)
    - name (str) – Filter by name of workflow (incompatible with `workflow_id`). If multiple names match the given name, all the workflows matching the argument will be returned.
    - published (bool) – if `True`, return also published workflows

    Return type: | list

    Returns:

    A list of workflow dicts. For example:

        [{u'id': u'92c56938c2f9b315',
          u'name': u'Simple',
          u'url': u'/api/workflows/92c56938c2f9b315'}]

  `import_shared_workflow`(workflow_id)

    Imports a new workflow from the shared published workflows.

    Parameters: | workflow_id (str) – Encoded workflow ID
    Return type: | dict

    Returns:

    A description of the workflow. For example:

        {u'id': u'ee0e2b4b696d9092',
         u'model_class': u'StoredWorkflow',
         u'name': u'Super workflow that solves everything!',
         u'published': False,
         u'tags': [],
         u'url': u'/api/workflows/ee0e2b4b696d9092'}

  `import_workflow_from_local_path`(file_local_path)

    Imports a new workflow given the path to a file containing a previously exported workflow.

    Parameters: | file_local_path (str) – File to upload to the server for new workflow

  `import_workflow_json`(workflow_json)

    Imports a new workflow given a json representation of a previously exported workflow.

    Parameters: | workflow_json (str) – JSON string representing the workflow to be imported

  `invoke_workflow`(workflow_id, inputs=None, params=None, history_id=None, history_name=None, import_inputs_to_history=False, replacement_params=None, allow_tool_state_corrections=None)

    Invoke the workflow identified by `workflow_id`. This will cause a workflow to be scheduled and return an object describing the workflow invocation.

    Parameters:

    - workflow_id (str) – Encoded workflow ID
    - inputs (dict) –

      A mapping of workflow inputs to datasets and dataset collections. The datasets source can be a LibraryDatasetDatasetAssociation (`ldda`), LibraryDataset (`ld`), HistoryDatasetAssociation (`hda`), or HistoryDatasetCollectionAssociation (`hdca`).

      The map must be in the following format: `{'<input_index>': {'id': <encoded dataset ID>, 'src': '[ldda, ld, hda, hdca]'}}` (e.g. `{'2': {'id': '29beef4fadeed09f', 'src': 'hda'}}`)

      This map may also be indexed by the UUIDs of the workflow steps, as indicated by the `uuid` property of steps returned from the Galaxy API.

    - params (str or dict) – A mapping of tool parameters that are non-datasets parameters. The map must be in the following format: `{'blastn': {'param': 'evalue', 'value': '1e-06'}}`
    - history_id (str) – The encoded history ID where to store the workflow output. Alternatively, `history_name` may be specified to create a new history.
    - history_name (str) – Create a new history with the given name to store the workflow output. If both `history_id` and `history_name` are provided, `history_name` is ignored. If neither is specified, a new ‘Unnamed history’ is created.
    - import_inputs_to_history (bool) – If `True`, used workflow inputs will be imported into the history. If `False`, only workflow outputs will be visible in the given history.
    - allow_tool_state_corrections (bool) – If True, allow Galaxy to fill in missing tool state when running workflows. This may be useful for workflows using tools that have changed over time or for workflows built outside of Galaxy with only a subset of inputs defined.
    - replacement_params (dict) – pattern-based replacements for post-job actions (see below)

    Return type: | dict

    Returns:

    A dict containing the workflow invocation describing the scheduling of the workflow. For example:

        {u'inputs': {u'0': {u'src': u'hda', u'id': u'a7db2fac67043c7e', u'uuid': u'7932ffe0-2340-4952-8857-dbaa50f1f46a'}},
         u'update_time': u'2015-10-31T22:00:26',
         u'uuid': u'c8aa2b1c-801a-11e5-a9e5-8ca98228593c',
         u'history_id': u'2f94e8ae9edff68a',
         u'workflow_id': u'03501d7626bd192f',
         u'state': u'ready',
         u'steps': [{u'workflow_step_uuid': u'b81250fd-3278-4e6a-b269-56a1f01ef485',
                     u'update_time': u'2015-10-31T22:00:26',
                     u'job_id': None,
                     u'state': None,
                     u'workflow_step_label': None,
                     u'order_index': 0,
                     u'action': None,
                     u'model_class': u'WorkflowInvocationStep',
                     u'workflow_step_id': u'cbbbf59e8f08c98c',
                     u'id': u'd413a19dec13d11e'},
                    {u'workflow_step_uuid': u'e62440b8-e911-408b-b124-e05435d3125e',
                     u'update_time': u'2015-10-31T22:00:26',
                     u'job_id': u'e89067bb68bee7a0',
                     u'state': u'new',
                     u'workflow_step_label':None,
                     u'order_index': 1,
                     u'action': None,
                     u'model_class': u'WorkflowInvocationStep',
                     u'workflow_step_id': u'964b37715ec9bd22',
                     u'id': u'2f94e8ae9edff68a'},
                   ],
         u'model_class': u'WorkflowInvocation',
         u'id': u'df7a1f0c02a5b08e'
        }

    The `replacement_params` dict should map parameter names in post-job actions (PJAs) to their runtime values. For instance, if the final step has a PJA like the following:

        {u'RenameDatasetActionout_file1': {
         u'action_arguments': {u'newname': u'${output}'},
         u'action_type': u'RenameDatasetAction',
         u'output_name': u'out_file1'}}

    then the following renames the output dataset to ‘foo’:

        replacement_params = {'output': 'foo'}

    see also this email thread.

    Warning

    Historically, the `run_workflow` method consumed a `dataset_map` data structure that was indexed by unencoded workflow step IDs. These IDs would not be stable across Galaxy instances. The new `inputs` property is instead indexed by either the `order_index` property which is stable across workflow imports or the step UUID which is also stable.

  `run_invocation_step_action`(workflow_id, invocation_id, step_id, action)

    Execute an action for an active workflow invocation step. The nature of this action and what is expected will vary based on the the type of workflow step (the only currently valid action is True/False for pause steps).

    Parameters:

    - workflow_id (str) – Encoded workflow ID
    - invocation_id (str) – Encoded workflow invocation ID
    - step_id (str) – Encoded workflow invocation step ID
    - action (object) – Action to use when updating state, semantics depends on step type.

  `run_workflow`(workflow_id, dataset_map=None, params=None, history_id=None, history_name=None, import_inputs_to_history=False, replacement_params=None)

    Run the workflow identified by `workflow_id`. This method is deprecated please use `invoke_workflow` instead.

    Parameters:

    - workflow_id (str) – Encoded workflow ID
    - dataset_map (str or dict) – A mapping of workflow inputs to datasets. The datasets source can be a LibraryDatasetDatasetAssociation (`ldda`), LibraryDataset (`ld`), or HistoryDatasetAssociation (`hda`). The map must be in the following format: `{'<input>': {'id': <encoded dataset ID>, 'src': '[ldda, ld, hda]'}}` (e.g. `{'23': {'id': '29beef4fadeed09f', 'src': 'ld'}}`)
    - params (str or dict) – A mapping of tool parameters that are non-datasets parameters. The map must be in the following format: `{'blastn': {'param': 'evalue', 'value': '1e-06'}}`
    - history_id (str) – The encoded history ID where to store the workflow output. Alternatively, `history_name` may be specified to create a new history.
    - history_name (str) – Create a new history with the given name to store the workflow output. If both `history_id` and `history_name` are provided, `history_name` is ignored. If neither is specified, a new ‘Unnamed history’ is created.
    - import_inputs_to_history (bool) – If `True`, used workflow inputs will be imported into the history. If `False`, only workflow outputs will be visible in the given history.
    - replacement_params (dict) – pattern-based replacements for post-job actions (see below)

    Return type: | dict

    Returns:

    A dict containing the history ID where the outputs are placed as well as output dataset IDs. For example:

        {u'history': u'64177123325c9cfd',
         u'outputs': [u'aa4d3084af404259']}

    The `replacement_params` dict should map parameter names in post-job actions (PJAs) to their runtime values. For instance, if the final step has a PJA like the following:

        {u'RenameDatasetActionout_file1': {
         u'action_arguments': {u'newname': u'${output}'},
         u'action_type': u'RenameDatasetAction',
         u'output_name': u'out_file1'}}

    then the following renames the output dataset to ‘foo’:

        replacement_params = {'output': 'foo'}

    see also this email thread.

    Warning

    This method is deprecated, please use `invoke_workflow` instead. `run_workflow` will wait for the whole workflow to be scheduled before returning and will not scale to large workflows as a result. `invoke_workflow` also features improved default behavior for dataset input handling.

  `show_invocation`(workflow_id, invocation_id)

    Get a workflow invocation object representing the scheduling of a workflow. This object may be sparse at first (missing inputs and invocation steps) and will become more populated as the workflow is actually scheduled.

    Parameters:

    - workflow_id (str) – Encoded workflow ID
    - invocation_id (str) – Encoded workflow invocation ID

    Return type: | dict

    Returns:

    The workflow invocation. For example:

        {u'inputs': {u'0': {u'src': u'hda', u'id': u'a7db2fac67043c7e', u'uuid': u'7932ffe0-2340-4952-8857-dbaa50f1f46a'}},
         u'update_time': u'2015-10-31T22:00:26',
         u'uuid': u'c8aa2b1c-801a-11e5-a9e5-8ca98228593c',
         u'history_id': u'2f94e8ae9edff68a',
         u'workflow_id': u'03501d7626bd192f',
         u'state': u'ready',
         u'steps': [{u'workflow_step_uuid': u'b81250fd-3278-4e6a-b269-56a1f01ef485',
                     u'update_time': u'2015-10-31T22:00:26',
                     u'job_id': None,
                     u'state': None,
                     u'workflow_step_label': None,
                     u'order_index': 0,
                     u'action': None,
                     u'model_class': u'WorkflowInvocationStep',
                     u'workflow_step_id': u'cbbbf59e8f08c98c',
                     u'id': u'd413a19dec13d11e'},
                    {u'workflow_step_uuid': u'e62440b8-e911-408b-b124-e05435d3125e',
                     u'update_time': u'2015-10-31T22:00:26',
                     u'job_id': u'e89067bb68bee7a0',
                     u'state': u'new',
                     u'workflow_step_label':None,
                     u'order_index': 1,
                     u'action': None,
                     u'model_class': u'WorkflowInvocationStep',
                     u'workflow_step_id': u'964b37715ec9bd22',
                     u'id': u'2f94e8ae9edff68a'},
                   ],
         u'model_class': u'WorkflowInvocation',
         u'id': u'df7a1f0c02a5b08e'
        }

  `show_invocation_step`(workflow_id, invocation_id, step_id)

    See the details of a particular workflow invocation step.

    Parameters:

    - workflow_id (str) – Encoded workflow ID
    - invocation_id (str) – Encoded workflow invocation ID
    - step_id (str) – Encoded workflow invocation step ID

    Return type: | dict

    Returns:

    The workflow invocation step. For example:

        {u'workflow_step_uuid': u'4060554c-1dd5-4287-9040-8b4f281cf9dc',
         u'update_time': u'2015-10-31T22:11:14',
         u'job_id': None,
         u'state': None,
         u'workflow_step_label': None,
         u'order_index': 2,
         u'action': None,
         u'model_class': u'WorkflowInvocationStep',
         u'workflow_step_id': u'52e496b945151ee8',
         u'id': u'63cd3858d057a6d1'}

  `show_workflow`(workflow_id)

    Display information needed to run a workflow

    Parameters: | workflow_id (str) – Encoded workflow ID
    Return type: | dict

    Returns:

    A description of the workflow and its inputs as a JSON object. For example:

        {u'id': u'92c56938c2f9b315',
         u'inputs': {u'23': {u'label': u'Input Dataset', u'value': u''}},
         u'name': u'Simple',
         u'url': u'/api/workflows/92c56938c2f9b315'}

#### Object-oriented Galaxy API

class `bioblend.galaxy.objects.galaxy_instance.``GalaxyInstance`(url, api_key=None, email=None, password=None)

  A representation of an instance of Galaxy, identified by a URL and a user’s API key.

  Parameters:

  - url (str) – a FQDN or IP for a given instance of Galaxy. For example: `http://127.0.0.1:8080`
  - api_key (str) – user’s API key for the given instance of Galaxy, obtained from the Galaxy web UI.

  This is actually a factory class which instantiates the entity-specific clients.

  Example: get a list of all histories for a user with API key ‘foo’:

      from bioblend.galaxy.objects import *
      gi = GalaxyInstance('http://127.0.0.1:8080', 'foo')
      histories = gi.histories.list()

  `histories`

    Client module for Galaxy histories.

  `jobs`

    Client module for Galaxy jobs.

  `libraries`

    Client module for Galaxy libraries.

  `tools`

    Client module for Galaxy tools.

  `workflows`

    Client module for Galaxy workflows.

##### Client

Clients for interacting with specific Galaxy entity types.

Classes in this module should not be instantiated directly, but used via their handles in `GalaxyInstance`.

class `bioblend.galaxy.objects.client.``ObjClient`(obj_gi)
  `get_previews`(**kwargs)

    Get a list of object previews.

    Previews entity summaries provided by REST collection URIs, e.g. `http://host:port/api/libraries`. Being the most lightweight objects associated to the various entities, these are the ones that should be used to retrieve their basic info.

    Return type: | list
    Returns: | a list of object previews

  `list`(**kwargs)

    Get a list of objects.

    This method first gets the entity summaries, then gets the complete description for each entity with an additional GET call, so may be slow.

    Return type: | list
    Returns: | a list of objects

class `bioblend.galaxy.objects.client.``ObjDatasetContainerClient`(obj_gi)

class `bioblend.galaxy.objects.client.``ObjHistoryClient`(obj_gi)

  Interacts with Galaxy histories.

  `create`(name=None)

    Create a new Galaxy history, optionally setting its name.

    Return type: | `History`
    Returns: | the history just created

  `delete`(id_=None, name=None, purge=False)

    Delete the history with the given id or name.

    Note that the same name can map to multiple histories.

    Parameters: | purge (bool) – if `True`, also purge (permanently delete) the history

    Note

    For the purge option to work, the Galaxy instance must have the `allow_user_dataset_purge` option set to `True` in the `config/galaxy.ini` configuration file.

  `get`(id_)

    Retrieve the history corresponding to the given id.

    Return type: | `History`
    Returns: | the history corresponding to `id_`

  `get_previews`(name=None, deleted=False)
  `list`(name=None, deleted=False)

    Get histories owned by the user of this Galaxy instance.

    Parameters:

    - name (str) – return only histories with this name
    - deleted (bool) – if `True`, return histories that have been deleted

    Return type: | list of `History`

class `bioblend.galaxy.objects.client.``ObjJobClient`(obj_gi)

  Interacts with Galaxy jobs.

  `get`(id_, full_details=False)

    Retrieve the job corresponding to the given id.

    Parameters: | full_details (bool) – if `True`, return the complete list of details for the given job.
    Return type: | `Job`
    Returns: | the job corresponding to `id_`

  `get_previews`()
  `list`()

    Get the list of jobs of the current user.

    Return type: | list of `Job`

class `bioblend.galaxy.objects.client.``ObjLibraryClient`(obj_gi)

  Interacts with Galaxy libraries.

  `create`(name, description=None, synopsis=None)

    Create a data library with the properties defined in the arguments.

    Return type: | `Library`
    Returns: | the library just created

  `delete`(id_=None, name=None)

    Delete the library with the given id or name.

    Note that the same name can map to multiple libraries.

    Warning

    Deleting a data library is irreversible - all of the data from the library will be permanently deleted.

  `get`(id_)

    Retrieve the data library corresponding to the given id.

    Return type: | `Library`
    Returns: | the library corresponding to `id_`

  `get_previews`(name=None, deleted=False)
  `list`(name=None, deleted=False)

    Get libraries owned by the user of this Galaxy instance.

    Parameters:

    - name (str) – return only libraries with this name
    - deleted (bool) – if `True`, return libraries that have been deleted

    Return type: | list of `Library`

class `bioblend.galaxy.objects.client.``ObjToolClient`(obj_gi)

  Interacts with Galaxy tools.

  `get`(id_, io_details=False, link_details=False)

    Retrieve the tool corresponding to the given id.

    Parameters:

    - io_details (bool) – if True, get also input and output details
    - link_details (bool) – if True, get also link details

    Return type: | `Tool`
    Returns: | the tool corresponding to `id_`

  `get_previews`(name=None, trackster=None)

    Get the list of tools installed on the Galaxy instance.

    Parameters:

    - name (str) – return only tools with this name
    - trackster (bool) – if True, only tools that are compatible with Trackster are returned

    Return type: | list of `Tool`

  `list`(name=None, trackster=None)

    Get the list of tools installed on the Galaxy instance.

    Parameters:

    - name (str) – return only tools with this name
    - trackster (bool) – if True, only tools that are compatible with Trackster are returned

    Return type: | list of `Tool`

class `bioblend.galaxy.objects.client.``ObjWorkflowClient`(obj_gi)

  Interacts with Galaxy workflows.

  `delete`(id_=None, name=None)

    Delete the workflow with the given id or name.

    Note that the same name can map to multiple workflows.

    Warning

    Deleting a workflow is irreversible - all of the data from the workflow will be permanently deleted.

  `get`(id_)

    Retrieve the workflow corresponding to the given id.

    Return type: | `Workflow`
    Returns: | the workflow corresponding to `id_`

  `get_previews`(name=None, published=False)
  `import_new`(src)

    Imports a new workflow into Galaxy.

    Parameters: | src (dict or str) – deserialized (dictionary) or serialized (str) JSON dump of the workflow (this is normally obtained by exporting a workflow from Galaxy).
    Return type: | `Workflow`
    Returns: | the workflow just imported

  `import_shared`(id_)

    Imports a shared workflow to the user’s space.

    Parameters: | id (str) – workflow id
    Return type: | `Workflow`
    Returns: | the workflow just imported

  `list`(name=None, published=False)

    Get workflows owned by the user of this Galaxy instance.

    Parameters:

    - name (str) – return only workflows with this name
    - published (bool) – if `True`, return also published workflows

    Return type: | list of `Workflow`

##### Wrappers

A basic object-oriented interface for Galaxy entities.

class `bioblend.galaxy.objects.wrappers.``Wrapper`(wrapped, parent=None, gi=None)

  Abstract base class for Galaxy entity wrappers.

  Wrapper instances wrap deserialized JSON dictionaries such as the ones obtained by the Galaxy web API, converting key-based access to attribute-based access (e.g., `library['name'] -> library.name`).

  Dict keys that are converted to attributes are listed in the `BASE_ATTRS` class variable: this is the ‘stable’ interface. Note that the wrapped dictionary is accessible via the `wrapped` attribute.

  Parameters:

  - wrapped (dict) – JSON-serializable dictionary
  - parent (`Wrapper`) – the parent of this wrapper
  - gi (`GalaxyInstance`) – the GalaxyInstance through which we can access this wrapper

  `BASE_ATTRS` = ('id', 'name')
  `clone`()

    Return an independent copy of this wrapper.

  classmethod `from_json`(jdef)

    Build a new wrapper from a JSON dump.

  `gi_module`

    The GalaxyInstance module that deals with objects of this type.

  `is_mapped`

    `True` if this wrapper is mapped to an actual Galaxy entity.

  `parent`

    The parent of this wrapper.

  `to_json`()

    Return a JSON dump of this wrapper.

  `touch`()

    Mark this wrapper as having been modified since its creation.

  `unmap`()

    Disconnect this wrapper from Galaxy.

class `bioblend.galaxy.objects.wrappers.``Step`(step_dict, parent)

  Abstract base class for workflow steps.

  Steps are the main building blocks of a Galaxy workflow. A step can be: an input (type ‘data_collection_input` or ‘data_input`), a computational tool (type ‘tool`) or a pause (type ‘pause`).

  `BASE_ATTRS` = ('id', 'name', 'input_steps', 'tool_id', 'tool_inputs', 'tool_version', 'type')
  `gi_module`

class `bioblend.galaxy.objects.wrappers.``Workflow`(wf_dict, gi=None)

  Workflows represent ordered sequences of computations on Galaxy.

  A workflow defines a sequence of steps that produce one or more results from an input dataset.

  `BASE_ATTRS` = ('id', 'name', 'deleted', 'inputs', 'published', 'steps', 'tags')
  `POLLING_INTERVAL` = 10
  `convert_input_map`(input_map)

    Convert `input_map` to the format required by the Galaxy web API.

    Parameters: | input_map (dict) – a mapping from input labels to datasets
    Return type: | dict
    Returns: | a mapping from input slot ids to dataset ids in the format required by the Galaxy web API.

  `data_collection_input_ids`

    Return the list of data collection input steps for this workflow.

  `data_input_ids`

    Return the list of data input steps for this workflow.

  `delete`()

    Delete this workflow.

    Warning

    Deleting a workflow is irreversible - all of the data from the workflow will be permanently deleted.

  `export`()

    Export a re-importable representation of the workflow.

    Return type: | dict
    Returns: | a JSON-serializable dump of the workflow

  `gi_module`
  `input_labels`

    Return the labels of this workflow’s input steps.

  `is_runnable`

    Return True if the workflow can be run on Galaxy.

    A workflow is considered runnable on a Galaxy instance if all of the tools it uses are installed in that instance.

  `preview`()
  `run`(input_map=None, history='', params=None, import_inputs=False, replacement_params=None, wait=False, polling_interval=10, break_on_error=True)

    Run the workflow in the current Galaxy instance.

    Parameters:

    - input_map (dict) – a mapping from workflow input labels to datasets, e.g.: `dict(zip(workflow.input_labels, library.get_datasets()))`
    - history (`History` or str) – either a valid history object (results will be stored there) or a string (a new history will be created with the given name).
    - params (`Mapping`) – parameter settings for workflow steps (see below)
    - import_inputs (bool) – If `True`, workflow inputs will be imported into the history; if `False`, only workflow outputs will be visible in the history.
    - replacement_params (`Mapping`) – pattern-based replacements for post-job actions (see the docs for `run_workflow()`)
    - wait (bool) – whether to wait while the returned datasets are in a pending state
    - polling_interval (float) – polling interval in seconds
    - break_on_error (bool) – whether to break as soon as at least one of the returned datasets is in the ‘error’ state

    Return type: | tuple
    Returns: | list of output datasets, output history

    The `params` dict should be structured as follows:

        PARAMS = {STEP_ID: PARAM_DICT, ...}
        PARAM_DICT = {NAME: VALUE, ...}

    For backwards compatibility, the following (deprecated) format is also supported:

        PARAMS = {TOOL_ID: PARAM_DICT, ...}

    in which case PARAM_DICT affects all steps with the given tool id. If both by-tool-id and by-step-id specifications are used, the latter takes precedence.

    Finally (again, for backwards compatibility), PARAM_DICT can also be specified as:

        PARAM_DICT = {'param': NAME, 'value': VALUE}

    Note that this format allows only one parameter to be set per step.

    Example: set ‘a’ to 1 for the third workflow step:

        params = {workflow.steps[2].id: {'a': 1}}

    Warning

    This is a blocking operation that can take a very long time. If `wait` is set to `False`, the method will return as soon as the workflow has been scheduled, otherwise it will wait until the workflow has been run. With a large number of steps, however, the delay may not be negligible even in the former case (e.g. minutes for 100 steps).

  `sorted_step_ids`()

    Return a topological sort of the workflow’s DAG.

  `tool_ids`

    Return the list of tool steps for this workflow.

class `bioblend.galaxy.objects.wrappers.``ContentInfo`(info_dict, gi=None)

  Instances of this class wrap dictionaries obtained by getting `/api/{histories,libraries}/<ID>/contents` from Galaxy.

  `BASE_ATTRS` = ('id', 'name', 'type')

class `bioblend.galaxy.objects.wrappers.``LibraryContentInfo`(info_dict, gi=None)

  Instances of this class wrap dictionaries obtained by getting `/api/libraries/<ID>/contents` from Galaxy.

  `gi_module`

class `bioblend.galaxy.objects.wrappers.``HistoryContentInfo`(info_dict, gi=None)

  Instances of this class wrap dictionaries obtained by getting `/api/histories/<ID>/contents` from Galaxy.

  `BASE_ATTRS` = ('id', 'name', 'type', 'deleted', 'state', 'visible')
  `gi_module`

class `bioblend.galaxy.objects.wrappers.``DatasetContainer`(c_dict, content_infos=None, gi=None)

  Abstract base class for dataset containers (histories and libraries).

  Parameters: | content_infos (list of `ContentInfo`) – info objects for the container’s contents

  `BASE_ATTRS` = ('id', 'name', 'deleted')
  `dataset_ids`

    Return the ids of the contained datasets.

  `get_dataset`(ds_id)

    Retrieve the dataset corresponding to the given id.

    Parameters: | ds_id (str) – dataset id
    Return type: | `HistoryDatasetAssociation` or `LibraryDataset`
    Returns: | the dataset corresponding to `ds_id`

  `get_datasets`(name=None)

    Get all datasets contained inside this dataset container.

    Parameters: | name (str) – return only datasets with this name
    Return type: | list of `HistoryDatasetAssociation` or list of `LibraryDataset`
    Returns: | datasets with the given name contained inside this container

    Note

    when filtering library datasets by name, specify their full paths starting from the library’s root folder, e.g., `/seqdata/reads.fastq`. Full paths are available through the `content_infos` attribute of `Library` objects.

  `preview`()
  `refresh`()

    Re-fetch the attributes pertaining to this object.

    Returns: self

class `bioblend.galaxy.objects.wrappers.``History`(hist_dict, content_infos=None, gi=None)

  Maps to a Galaxy history.

  `API_MODULE` = 'histories'
  `BASE_ATTRS` = ('id', 'name', 'deleted', 'annotation', 'state', 'state_ids', 'state_details', 'tags')
  `CONTENT_INFO_TYPE`

    alias of `HistoryContentInfo`

  `DS_TYPE`

    alias of `HistoryDatasetAssociation`

  `delete`(purge=False)

    Delete this history.

    Parameters: | purge (bool) – if `True`, also purge (permanently delete) the history

    Note

    For the purge option to work, the Galaxy instance must have the `allow_user_dataset_purge` option set to `True` in the `config/galaxy.ini` configuration file.

  `download`(jeha_id, outf, chunk_size=4096)

    Download an export archive for this history. Use `export()` to create an export and get the required `jeha_id`. See `download_history()` for parameter and return value info.

  `export`(gzip=True, include_hidden=False, include_deleted=False, wait=False)

    Start a job to create an export archive for this history. See `export_history()` for parameter and return value info.

  `gi_module`
  `import_dataset`(lds)

    Import a dataset into the history from a library.

    Parameters: | lds (`LibraryDataset`) – the library dataset to import
    Return type: | `HistoryDatasetAssociation`
    Returns: | the imported history dataset

  `paste_content`(content, **kwargs)

    Upload a string to a new dataset in this history.

    Parameters: | content (str) – content of the new dataset to upload

    See `upload_file()` for the optional parameters (except file_name).

    Return type: | `HistoryDatasetAssociation`
    Returns: | the uploaded dataset

  `update`(name=None, annotation=None, **kwds)

    Update history metadata information. Some of the attributes that can be modified are documented below.

    Parameters:

    - name (str) – Replace history name with the given string
    - annotation (str) – Replace history annotation with the given string
    - deleted (bool) – Mark or unmark history as deleted
    - published (bool) – Mark or unmark history as published
    - importable (bool) – Mark or unmark history as importable
    - tags (list) – Replace history tags with the given list

  `upload_dataset`(path, **kwargs)

    Upload the file specified by `path` to this history.

    Parameters: | path (str) – path of the file to upload

    See `upload_file()` for the optional parameters.

    Return type: | `HistoryDatasetAssociation`
    Returns: | the uploaded dataset

  `upload_file`(path, **kwargs)

    Upload the file specified by `path` to this history.

    Parameters: | path (str) – path of the file to upload

    See `upload_file()` for the optional parameters.

    Return type: | `HistoryDatasetAssociation`
    Returns: | the uploaded dataset

  `upload_from_ftp`(path, **kwargs)

    Upload the file specified by `path` from the user’s FTP directory to this history.

    Parameters: | path (str) – path of the file in the user’s FTP directory

    See `upload_file()` for the optional parameters.

    Return type: | `HistoryDatasetAssociation`
    Returns: | the uploaded dataset

class `bioblend.galaxy.objects.wrappers.``Library`(lib_dict, content_infos=None, gi=None)

  Maps to a Galaxy library.

  `API_MODULE` = 'libraries'
  `BASE_ATTRS` = ('id', 'name', 'deleted', 'description', 'synopsis')
  `CONTENT_INFO_TYPE`

    alias of `LibraryContentInfo`

  `DS_TYPE`

    alias of `LibraryDataset`

  `copy_from_dataset`(hda, folder=None, message='')

    Copy a history dataset into this library.

    Parameters: | hda (`HistoryDatasetAssociation`) – history dataset to copy into the library

    See `upload_data()` for info on other params.

  `create_folder`(name, description=None, base_folder=None)

    Create a folder in this library.

    Parameters:

    - name (str) – folder name
    - description (str) – optional folder description
    - base_folder (`Folder`) – parent folder, or `None` to create in the root folder

    Return type: | `Folder`
    Returns: | the folder just created

  `delete`()

    Delete this library.

  `folder_ids`

    Return the ids of the contained folders.

  `get_folder`(f_id)

    Retrieve the folder corresponding to the given id.

    Return type: | `Folder`
    Returns: | the folder corresponding to `f_id`

  `gi_module`
  `root_folder`

    The root folder of this library.

    Return type: | `Folder`
    Returns: | the root folder of this library

  `upload_data`(data, folder=None, **kwargs)

    Upload data to this library.

    Parameters:

    - data (str) – dataset contents
    - folder (`Folder`) – a folder object, or `None` to upload to the root folder

    Return type: | `LibraryDataset`
    Returns: | the dataset object that represents the uploaded content

    Optional keyword arguments: `file_type`, `dbkey`.

  `upload_from_galaxy_fs`(paths, folder=None, link_data_only=None, **kwargs)

    Upload data to this library from filesystem paths on the server.

    Note

    For this method to work, the Galaxy instance must have the `allow_library_path_paste` option set to `True` in the `config/galaxy.ini` configuration file.

    Parameters:

    - paths (str or `Iterable` of str) – server-side file paths from which data should be read
    - link_data_only (str) – either ‘copy_files’ (default) or ‘link_to_files’. Setting to ‘link_to_files’ symlinks instead of copying the files

    Return type: | list of `LibraryDataset`
    Returns: | the dataset objects that represent the uploaded content

    See `upload_data()` for info on other params.

  `upload_from_local`(path, folder=None, **kwargs)

    Upload data to this library from a local file.

    Parameters: | path (str) – local file path from which data should be read

    See `upload_data()` for info on other params.

  `upload_from_url`(url, folder=None, **kwargs)

    Upload data to this library from the given URL.

    Parameters: | url (str) – URL from which data should be read

    See `upload_data()` for info on other params.

class `bioblend.galaxy.objects.wrappers.``Folder`(f_dict, container, gi=None)

  Maps to a folder in a Galaxy library.

  `BASE_ATTRS` = ('id', 'name', 'description', 'deleted', 'item_count')
  `container_id`

    Deprecated property.

    Id of the folder container. Use `container.id` instead.

  `gi_module`
  `parent`

    The parent folder of this folder. The parent of the root folder is `None`.

    Return type: | `Folder`
    Returns: | the parent of this folder

  `refresh`()

    Re-fetch the attributes pertaining to this object.

    Returns: self

class `bioblend.galaxy.objects.wrappers.``Dataset`(ds_dict, container, gi=None)

  Abstract base class for Galaxy datasets.

  `BASE_ATTRS` = ('id', 'name', 'data_type', 'file_name', 'file_size', 'state', 'deleted', 'file_ext')
  `POLLING_INTERVAL` = 1
  `container_id`

    Deprecated property.

    Id of the dataset container. Use `container.id` instead.

  `download`(file_object, chunk_size=4096)

    Open dataset for reading and save its contents to `file_object`.

    Parameters: | file_object (file) – output file object

    See `get_stream()` for info on other params.

  `get_contents`(chunk_size=4096)

    Open dataset for reading and return its full contents.

    See `get_stream()` for param info.

  `get_stream`(chunk_size=4096)

    Open dataset for reading and return an iterator over its contents.

    Parameters: | chunk_size (int) – read this amount of bytes at a time

    Warning

    Due to a change in the Galaxy API endpoint, this method does not work on `LibraryDataset` instances with Galaxy `release_2014.06.02`. Methods that delegate work to this one are also affected: `peek()`, `download()` and `get_contents()`.

  `peek`(chunk_size=4096)

    Open dataset for reading and return the first chunk.

    See `get_stream()` for param info.

  `refresh`()

    Re-fetch the attributes pertaining to this object.

    Returns: self

  `wait`(polling_interval=1, break_on_error=True)

    Wait for this dataset to come out of the pending states.

    Parameters:

    - polling_interval (float) – polling interval in seconds
    - break_on_error (bool) – if `True`, raise a RuntimeError exception if the dataset ends in the ‘error’ state.

    Warning

    This is a blocking operation that can take a very long time. Also, note that this method does not return anything; however, this dataset is refreshed (possibly multiple times) during the execution.

class `bioblend.galaxy.objects.wrappers.``HistoryDatasetAssociation`(ds_dict, container, gi=None)

  Maps to a Galaxy `HistoryDatasetAssociation`.

  `BASE_ATTRS` = ('id', 'name', 'data_type', 'file_name', 'file_size', 'state', 'deleted', 'file_ext', 'tags', 'visible')
  `SRC` = 'hda'
  `delete`()

    Delete this dataset.

  `gi_module`

class `bioblend.galaxy.objects.wrappers.``LibraryDatasetDatasetAssociation`(ds_dict, container, gi=None)

  Maps to a Galaxy `LibraryDatasetDatasetAssociation`.

  `SRC` = 'ldda'

class `bioblend.galaxy.objects.wrappers.``LibraryDataset`(ds_dict, container, gi=None)

  Maps to a Galaxy `LibraryDataset`.

  `SRC` = 'ld'
  `delete`(purged=False)

    Delete this library dataset.

    Parameters: | purged (bool) – if `True`, also purge (permanently delete) the dataset

class `bioblend.galaxy.objects.wrappers.``Tool`(t_dict, gi=None)

  Maps to a Galaxy tool.

  `BASE_ATTRS` = ('id', 'name', 'version')
  `POLLING_INTERVAL` = 10
  `gi_module`
  `run`(inputs, history, wait=False, polling_interval=10)

    Execute this tool in the given history with inputs from dict `inputs`.

    Parameters:

    - inputs (dict) – dictionary of input datasets and parameters for the tool (see below)
    - history (`History`) – the history where to execute the tool
    - wait (bool) – whether to wait while the returned datasets are in a pending state
    - polling_interval (float) – polling interval in seconds

    Return type: | list of `HistoryDatasetAssociation`
    Returns: | list of output datasets

    The `inputs` dict should contain input datasets and parameters in the (largely undocumented) format used by the Galaxy API. Some examples can be found in Galaxy’s API test suite. The value of an input dataset can also be a `Dataset` object, which will be automatically converted to the needed format.

class `bioblend.galaxy.objects.wrappers.``Job`(j_dict, gi=None)

  Maps to a Galaxy job.

  `BASE_ATTRS` = ('id', 'state')
  `gi_module`

class `bioblend.galaxy.objects.wrappers.``Preview`(pw_dict, gi=None)

  Abstract base class for Galaxy entity ‘previews’.

  Classes derived from this one model the short summaries returned by global getters such as `/api/libraries`.

  `BASE_ATTRS` = ('id', 'name', 'deleted')

class `bioblend.galaxy.objects.wrappers.``LibraryPreview`(pw_dict, gi=None)

  Models Galaxy library ‘previews’.

  Instances of this class wrap dictionaries obtained by getting `/api/libraries` from Galaxy.

  `gi_module`

class `bioblend.galaxy.objects.wrappers.``HistoryPreview`(pw_dict, gi=None)

  Models Galaxy history ‘previews’.

  Instances of this class wrap dictionaries obtained by getting `/api/histories` from Galaxy.

  `BASE_ATTRS` = ('id', 'name', 'deleted', 'tags')
  `gi_module`

class `bioblend.galaxy.objects.wrappers.``WorkflowPreview`(pw_dict, gi=None)

  Models Galaxy workflow ‘previews’.

  Instances of this class wrap dictionaries obtained by getting `/api/workflows` from Galaxy.

  `BASE_ATTRS` = ('id', 'name', 'deleted', 'published', 'tags')
  `gi_module`

#### Usage documentation

This page describes some sample use cases for the Galaxy API and provides examples for these API calls. In addition to this page, there are functional examples of complete scripts in the `docs/examples` directory of the BioBlend source code repository.

##### Connect to a Galaxy server

To connect to a running Galaxy server, you will need an account on that Galaxy instance and an API key for the account. Instructions on getting an API key can be found at http://wiki.galaxyproject.org/Learn/API .

To open a connection call:

    from bioblend.galaxy import GalaxyInstance

    gi = GalaxyInstance(url='http://example.galaxy.url', key='your-API-key')

We now have a `GalaxyInstance` object which allows us to interact with the Galaxy server under our account, and access our data. If the account is a Galaxy admin account we also will be able to use this connection to carry out admin actions.

##### View Histories and Datasets

Methods for accessing histories and datasets are grouped under `GalaxyInstance.histories.*` and `GalaxyInstance.datasets.*` respectively.

To get information on the Histories currently in your account, call:

    >>> gi.histories.get_histories()
    [{u'id': u'f3c2b0f3ecac9f02',
      u'name': u'RNAseq_DGE_BASIC_Prep',
      u'url': u'/api/histories/f3c2b0f3ecac9f02'},
     {u'id': u'8a91dcf1866a80c2',
      u'name': u'June demo',
      u'url': u'/api/histories/8a91dcf1866a80c2'}]

This returns a list of dictionaries containing basic metadata, including the id and name of each History. In this case, we have two existing Histories in our account, ‘RNAseq_DGE_BASIC_Prep’ and ‘June demo’. To get more detailed information about a History we can pass its id to the `show_history` method:

    >>> gi.histories.show_history('f3c2b0f3ecac9f02', contents=False)
    {u'annotation': u'',
     u'contents_url': u'/api/histories/f3c2b0f3ecac9f02/contents',
     u'id': u'f3c2b0f3ecac9f02',
     u'name': u'RNAseq_DGE_BASIC_Prep',
     u'nice_size': u'93.5 MB',
     u'state': u'ok',
     u'state_details': {u'discarded': 0,
          u'empty': 0,
          u'error': 0,
          u'failed_metadata': 0,
          u'new': 0,
          u'ok': 7,
          u'paused': 0,
          u'queued': 0,
          u'running': 0,
          u'setting_metadata': 0,
          u'upload': 0 },
     u'state_ids': {u'discarded': [],
          u'empty': [],
          u'error': [],
          u'failed_metadata': [],
          u'new': [],
          u'ok': [u'd6842fb08a76e351',
                  u'10a4b652da44e82a',
                  u'81c601a2549966a0',
                  u'a154f05e3bcee26b',
                  u'1352fe19ddce0400',
                  u'06d549c52d753e53',
                  u'9ec54455d6279cc7'],
          u'paused': [],
          u'queued': [],
          u'running': [],
          u'setting_metadata': [],
          u'upload': []
          }
      }

This gives us a dictionary containing the History’s metadata. With `contents=False` (the default), we only get a list of ids of the datasets contained within the History; with `contents=True` we would get metadata on each dataset. We can also directly access more detailed information on a particular dataset by passing its id to the `show_dataset` method:

    >>> gi.datasets.show_dataset('10a4b652da44e82a')
    {u'data_type': u'fastqsanger',
     u'deleted': False,
     u'file_size': 16527060,
     u'genome_build': u'dm3',
     u'id': 17499,
     u'metadata_data_lines': None,
     u'metadata_dbkey': u'dm3',
     u'metadata_sequences': None,
     u'misc_blurb': u'15.8 MB',
     u'misc_info': u'Noneuploaded fastqsanger file',
     u'model_class': u'HistoryDatasetAssociation',
     u'name': u'C1_R2_1.chr4.fq',
     u'purged': False,
     u'state': u'ok',
     u'visible': True}

##### Uploading Datasets to a History

To upload a local file to a Galaxy server, you can run the `upload_file` method, supplying the path to a local file:

    >>> gi.tools.upload_file('test.txt', 'f3c2b0f3ecac9f02')
    {u'implicit_collections': [],
     u'jobs': [{u'create_time': u'2015-07-28T17:52:39.756488',
                u'exit_code': None,
                u'id': u'9752b387803d3e1e',
                u'model_class': u'Job',
                u'state': u'new',
                u'tool_id': u'upload1',
                u'update_time': u'2015-07-28T17:52:39.987509'}],
     u'output_collections': [],
     u'outputs': [{u'create_time': u'2015-07-28T17:52:39.331176',
                   u'data_type': u'galaxy.datatypes.data.Text',
                   u'deleted': False,
                   u'file_ext': u'auto',
                   u'file_size': 0,
                   u'genome_build': u'?',
                   u'hda_ldda': u'hda',
                   u'hid': 16,
                   u'history_content_type': u'dataset',
                   u'history_id': u'f3c2b0f3ecac9f02',
                   u'id': u'59c76a119581e190',
                   u'metadata_data_lines': None,
                   u'metadata_dbkey': u'?',
                   u'misc_blurb': None,
                   u'misc_info': None,
                   u'model_class': u'HistoryDatasetAssociation',
                   u'name': u'test.txt',
                   u'output_name': u'output0',
                   u'peek': u'<table cellspacing="0" cellpadding="3"></table>',
                   u'purged': False,
                   u'state': u'queued',
                   u'tags': [],
                   u'update_time': u'2015-07-28T17:52:39.611887',
                   u'uuid': u'ff0ee99b-7542-4125-802d-7a193f388e7e',
                   u'visible': True}]}

If files are greater than 2GB in size, they will need to be uploaded via FTP. Importing files from the user’s FTP folder can be done via running the upload tool again:

    >>> gi.tools.upload_from_ftp('test.txt', 'f3c2b0f3ecac9f02')
    {u'implicit_collections': [],
     u'jobs': [{u'create_time': u'2015-07-28T17:57:43.704394',
                u'exit_code': None,
                u'id': u'82b264d8c3d11790',
                u'model_class': u'Job',
                u'state': u'new',
                u'tool_id': u'upload1',
                u'update_time': u'2015-07-28T17:57:43.910958'}],
     u'output_collections': [],
     u'outputs': [{u'create_time': u'2015-07-28T17:57:43.209041',
                   u'data_type': u'galaxy.datatypes.data.Text',
                   u'deleted': False,
                   u'file_ext': u'auto',
                   u'file_size': 0,
                   u'genome_build': u'?',
                   u'hda_ldda': u'hda',
                   u'hid': 17,
                   u'history_content_type': u'dataset',
                   u'history_id': u'f3c2b0f3ecac9f02',
                   u'id': u'a676e8f07209a3be',
                   u'metadata_data_lines': None,
                   u'metadata_dbkey': u'?',
                   u'misc_blurb': None,
                   u'misc_info': None,
                   u'model_class': u'HistoryDatasetAssociation',
                   u'name': u'test.txt',
                   u'output_name': u'output0',
                   u'peek': u'<table cellspacing="0" cellpadding="3"></table>',
                   u'purged': False,
                   u'state': u'queued',
                   u'tags': [],
                   u'update_time': u'2015-07-28T17:57:43.544407',
                   u'uuid': u'2cbe8f0a-4019-47c4-87e2-005ce35b8449',
                   u'visible': True}]}

##### View Data Libraries

Methods for accessing Data Libraries are grouped under `GalaxyInstance.libraries.*`. Most Data Library methods are available to all users, but as only administrators can create new Data Libraries within Galaxy, the `create_folder` and `create_library` methods can only be called using an API key belonging to an admin account.

We can view the Data Libraries available to our account using:

    >>> gi.libraries.get_libraries()
    [{u'id': u'8e6f930d00d123ea',
      u'name': u'RNA-seq workshop data',
      u'url': u'/api/libraries/8e6f930d00d123ea'},
     {u'id': u'f740ab636b360a70',
      u'name': u'1000 genomes',
      u'url': u'/api/libraries/f740ab636b360a70'}]

This gives a list of metadata dictionaries with basic information on each library. We can get more information on a particular Data Library by passing its id to the `show_library` method:

    >>> gi.libraries.show_library('8e6f930d00d123ea')
    {u'contents_url': u'/api/libraries/8e6f930d00d123ea/contents',
     u'description': u'RNA-Seq workshop data',
     u'name': u'RNA-Seq',
     u'synopsis': u'Data for the RNA-Seq tutorial'}

##### Upload files to a Data Library

We can get files into Data Libraries in several ways: by uploading from our local machine, by retrieving from a URL, by passing the new file content directly into the method, or by importing a file from the filesystem on the Galaxy server.

For instance, to upload a file from our machine we might call:

    >>> gi.libraries.upload_file_from_local_path('8e6f930d00d123ea', '/local/path/to/mydata.fastq', file_type='fastqsanger')

Note that we have provided the id of the destination Data Library, and in this case we have specified the type that Galaxy should assign to the new dataset. The default value for `file_type` is ‘auto’, in which case Galaxy will attempt to guess the dataset type.

##### View Workflows

Methods for accessing workflows are grouped under `GalaxyInstance.workflows.*`.

To get information on the Workflows currently in your account, use:

    >>> gi.workflows.get_workflows()
    [{u'id': u'e8b85ad72aefca86',
      u'name': u"TopHat + cufflinks part 1",
      u'url': u'/api/workflows/e8b85ad72aefca86'},
     {u'id': u'b0631c44aa74526d',
      u'name': u'CuffDiff',
      u'url': u'/api/workflows/b0631c44aa74526d'}]

This returns a list of metadata dictionaries. We can get the details of a particular Workflow, including its steps, by passing its id to the `show_workflow` method:

    >>> gi.workflows.show_workflow('e8b85ad72aefca86')
    {u'id': u'e8b85ad72aefca86',
     u'inputs':
        {u'252':
           {u'label': u'Input RNA-seq fastq',
            u'value': u''
            }
         },
     u'name': u"TopHat + cufflinks part 1",
     u'steps':
        {u'250':
           {u'id': 250,
            u'input_steps':
               {u'input1':
                  {u'source_step': 252,
                   u'step_output': u'output'
                   }
               },
            u'tool_id': u'tophat',
            u'type': u'tool'
            },
         u'251':
            {u'id': 251,
             u'input_steps':
                {u'input':
                   {u'source_step': 250,
                    u'step_output': u'accepted_hits'
                    }
                },
             u'tool_id': u'cufflinks',
             u'type': u'tool'
             },
         u'252':
            {u'id': 252,
             u'input_steps': {},
             u'tool_id': None,
             u'type': u'data_input'
             }
         },
     u'url': u'/api/workflows/e8b85ad72aefca86'
     }

##### Export or import a Workflow

Workflows can be exported from or imported into Galaxy as JSON. This makes it possible to archive Workflows, or to move them between Galaxy instances.

To export a workflow, we can call:

    >>> workflow_string = gi.workflows.export_workflow_json('e8b85ad72aefca86')

This gives us a (rather long) string with a JSON-encoded representation of the Workflow. We can import this string as a new Workflow with:

    >>> gi.workflows.import_workflow_json(workflow_string)
    {u'id': u'c0bacafdfe211f9a',
     u'name': u'TopHat + cufflinks part 1 (imported from API)',
     u'url': u'/api/workflows/c0bacafdfe211f9a'}

This call returns a dictionary containing basic metadata on the new Workflow object. Since in this case we have imported the JSON string into the original Galaxy instance, we now have a duplicate of the original Workflow in our account:

    >>> gi.workflows.get_workflows()
    [{u'id': u'c0bacafdfe211f9a',
      u'name': u'TopHat + cufflinks part 1 (imported from API)',
      u'url': u'/api/workflows/c0bacafdfe211f9a'},
     {u'id': u'e8b85ad72aefca86',
      u'name': u"TopHat + cufflinks part 1",
      u'url': u'/api/workflows/e8b85ad72aefca86'},
     {u'id': u'b0631c44aa74526d',
      u'name': u'CuffDiff',
      u'url': u'/api/workflows/b0631c44aa74526d'}]

Instead of using JSON strings directly, Workflows can be exported to or imported from files on the local disk using the `export_workflow_to_local_path` and `import_workflow_from_local_path` methods. See the API reference for details.

Note

If we export a Workflow from one Galaxy instance and import it into another, Galaxy will only run it without modification if it has the same versions of the tool wrappers installed. This is to ensure reproducibility. Otherwise, we will need to manually update the Workflow to use the new tool versions.

##### Run a Workflow

To run a Workflow, we need to tell Galaxy which datasets to use for which workflow inputs. We can use datasets from Histories or Data Libraries.

Examine the Workflow above. We can see that it takes only one input file. That is:

    >>> wf = gi.workflows.show_workflow('e8b85ad72aefca86')
    >>> wf['inputs']
    {u'252':
        {u'label':
            u'Input RNA-seq fastq',
            u'value': u''
        }
    }

There is one input, labelled ‘Input RNA-seq fastq’. This input is passed to the Tophat tool and should be a fastq file. We will use the dataset we examined above, under View Histories and Datasets, which had name ‘C1_R2_1.chr4.fq’ and id ‘10a4b652da44e82a’.

To specify the inputs, we build a data map and pass this to the `run_workflow` method. This data map is a nested dictionary object which maps inputs to datasets. We call:

    >>> datamap = dict()
    >>> datamap['252'] = { 'src':'hda', 'id':'10a4b652da44e82a' }
    >>> gi.workflows.run_workflow('e8b85ad72aefca86', datamap, history_name='New output history')
    {u'history': u'0a7b7992a7cabaec',
     u'outputs': [u'33be8ad9917d9207',
                  u'fbee1c2dc793c114',
                  u'85866441984f9e28',
                  u'1c51aa78d3742386',
                  u'a68e8770e52d03b4',
                  u'c54baf809e3036ac',
                  u'ba0db8ce6cd1fe8f',
                  u'c019e4cf08b2ac94'
                  ]
    }

In this case the only input id is ‘252’ and the corresponding dataset id is ‘10a4b652da44e82a’. We have specified the dataset source to be ‘hda’ (HistoryDatasetAssociation) since the dataset is stored in a History. See the API reference for allowed dataset specifications. We have also requested that a new History be created and used to store the results of the run, by setting `history_name='New output history'`.

The `run_workflow` call submits all the jobs which need to be run to the Galaxy workflow engine, with the appropriate dependencies so that they will run in order. The call returns immediately, so we can continue to submit new jobs while waiting for this workflow to execute. `run_workflow` returns the id of the output History and of the datasets that will be created as a result of this run. Note that these dataset ids are valid immediately, so we can specify these datasets as inputs to new jobs even before the files have been created, and the new jobs will be added to the queue with the appropriate dependencies.

If we view the output History immediately after calling `run_workflow`, we will see something like:

    >>> gi.histories.show_history('0a7b7992a7cabaec')
    {u'annotation': u'',
     u'contents_url': u'/api/histories/0a7b7992a7cabaec/contents',
     u'id': u'0a7b7992a7cabaec',
     u'name': u'New output history',
     u'nice_size': u'0 bytes',
     u'state': u'queued',
     u'state_details': {u'discarded': 0,
         u'empty': 0,
         u'error': 0,
         u'failed_metadata': 0,
         u'new': 0,
         u'ok': 0,
         u'paused': 0,
         u'queued': 8,
         u'running': 0,
         u'setting_metadata': 0,
         u'upload': 0},
     u'state_ids': {u'discarded': [],
         u'empty': [],
         u'error': [],
         u'failed_metadata': [],
         u'new': [],
         u'ok': [],
         u'paused': [],
         u'queued': [u'33be8ad9917d9207',
                     u'fbee1c2dc793c114',
                     u'85866441984f9e28',
                     u'1c51aa78d3742386',
                     u'a68e8770e52d03b4',
                     u'c54baf809e3036ac',
                     u'ba0db8ce6cd1fe8f',
                     u'c019e4cf08b2ac94'],
         u'running': [],
         u'setting_metadata': [],
         u'upload': []
        }
    }

In this case, because the submitted jobs have not had time to run, the output History contains 8 datasets in the ‘queued’ state and has a total size of 0 bytes. If we make this call again later we should instead see completed output files.

##### View Users

Methods for managing users are grouped under `GalaxyInstance.users.*`. User management is only available to Galaxy administrators, that is, the API key used to connect to Galaxy must be that of an admin account.

To get a list of users, call:

    >>> gi.users.get_users()
    [{u'email': u'userA@unimelb.edu.au',
      u'id': u'975a9ce09b49502a',
      u'quota_percent': None,
      u'url': u'/api/users/975a9ce09b49502a'},
     {u'email': u'userB@student.unimelb.edu.au',
      u'id': u'0193a95acf427d2c',
      u'quota_percent': None,
      u'url': u'/api/users/0193a95acf427d2c'}]

### Toolshed API

API used to interact with the Galaxy Toolshed, including repository management.

#### API documentation for interacting with the Galaxy Toolshed

##### ToolShedInstance

class `bioblend.toolshed.``ToolShedInstance`(url, key='', email=None, password=None)

  A base representation of an instance of ToolShed, identified by a URL and a user’s API key.

  After you have created an `ToolShed` object, access various modules via the class fields (see the source for the most up-to-date list): `repositories` are the minimum set supported. For example, to work with a repositories, and get a list of all the public repositories, the following should be done:

      from bioblend import toolshed

      ts = toolshed.ToolShedInstance(url='http://testtoolshed.g2.bx.psu.edu')

      rl = ts.repositories.get_repositories()

      tools = ts.tools.search_tools('fastq')

  Parameters:

  - url (str) – A FQDN or IP for a given instance of ToolShed. For example: http://testtoolshed.g2.bx.psu.edu
  - key (str) – If required, user’s API key for the given instance of ToolShed, obtained from the user preferences.

  `__init__`(url, key='', email=None, password=None)

    A base representation of an instance of ToolShed, identified by a URL and a user’s API key.

    After you have created an `ToolShed` object, access various modules via the class fields (see the source for the most up-to-date list): `repositories` are the minimum set supported. For example, to work with a repositories, and get a list of all the public repositories, the following should be done:

        from bioblend import toolshed

        ts = toolshed.ToolShedInstance(url='http://testtoolshed.g2.bx.psu.edu')

        rl = ts.repositories.get_repositories()

        tools = ts.tools.search_tools('fastq')

    Parameters:

    - url (str) – A FQDN or IP for a given instance of ToolShed. For example: http://testtoolshed.g2.bx.psu.edu
    - key (str) – If required, user’s API key for the given instance of ToolShed, obtained from the user preferences.

##### Repositories

Interaction with a Tool Shed instance repositories

class `bioblend.toolshed.repositories.``ToolShedClient`(toolshed_instance)
  `create_repository`(name, synopsis, description=None, type='unrestricted', remote_repository_url=None, homepage_url=None, category_ids=None)

    Create a new repository in a Tool Shed

    Parameters:

    - name (str) – Name of the repository
    - synopsis (str) – Synopsis of the repository
    - description (str) – Optional description of the repository
    - type (str) – type of the repository. One of “unrestricted”, “repository_suite_definition”, or “tool_dependency_definition”
    - remote_repository_url (str) – Remote URL (e.g. github/bitbucket repository)
    - homepage_url (str) – Upstream’s homepage for the project.
    - category_ids (list) – List of encoded category IDs

    Return type: | dict

    Returns:

    a dictionary containing information about the new repository. For example:

        {
            "deleted": false,
            "deprecated": false,
            "description": "new_synopsis",
            "homepage_url": "https://github.com/galaxyproject/",
            "id": "8cf91205f2f737f4",
            "long_description": "this is some repository",
            "model_class": "Repository",
            "name": "new_repo_17",
            "owner": "qqqqqq",
            "private": false,
            "remote_repository_url": "https://github.com/galaxyproject/tools-devteam",
            "times_downloaded": 0,
            "type": "unrestricted",
            "user_id": "adb5f5c93f827949"
        }

  `get_categories`()

    Returns a list of dictionaries that contain descriptions of the repository categories found on the given Tool Shed instance.

    Return type: | list

    Returns:

    A list of dictionaries containing information about repository categories present in the Tool Shed. For example:

        [{u'deleted': False,
          u'description': u'Tools for manipulating data',
          u'id': u'175812cd7caaf439',
          u'model_class': u'Category',
          u'name': u'Text Manipulation',
          u'url': u'/api/categories/175812cd7caaf439'},]

    New in version 0.5.2.

  `get_ordered_installable_revisions`(name, owner)

    Returns the ordered list of changeset revision hash strings that are associated with installable revisions. As in the changelog, the list is ordered oldest to newest.

    Parameters:

    - name (str) – the name of the repository
    - owner (str) – the owner of the repository

    Return type: | list
    Returns: | List of changeset revision hash string from oldest to newest

  `get_repositories`()

    Get a list of all the repositories in a Galaxy Tool Shed

    Return type: | list

    Returns:

    Returns a list of dictionaries containing information about repositories present in the Tool Shed. For example:

        [{u'times_downloaded': 0, u'user_id': u'5cefd48bc04af6d4',
        u'description': u'Order Contigs', u'deleted': False,
        u'deprecated': False, u'private': False,
        u'url': u'/api/repositories/287bd69f724b99ce',
        u'owner': u'billybob', u'id': u'287bd69f724b99ce',
        u'name': u'best_tool_ever'}]

    Changed in version 0.4.1: Changed method name from `get_tools` to `get_repositories` to better align with the Tool Shed concepts

  `get_repository_revision_install_info`(name, owner, changeset_revision)

    Return a list of dictionaries of metadata about a certain changeset revision for a single tool.

    Parameters:

    - name (str) – the name of the repository
    - owner (str) – the owner of the repository
    - changeset_revision (str) – the changset_revision of the RepositoryMetadata object associated with the repository

    Return type: | List of dictionaries

    Returns:

    Returns a list of the following dictionaries:
      - a dictionary defining the repository
      - a dictionary defining the repository revision (RepositoryMetadata)
      - a dictionary including the additional information required to install the repository

    For example:

        [{u'times_downloaded': 269, u'user_id': u'1de29d50c3c44272', u'description': u'Galaxy Freebayes Bayesian genetic variant detector tool', u'deleted': False, u'deprecated': False, u'private': False, u'long_description': u'Galaxy Freebayes Bayesian genetic variant detector tool originally included in the Galaxy code distribution but migrated to the tool shed.', u'url': u'/api/repositories/491b7a3fddf9366f', u'owner': u'devteam', u'id': u'491b7a3fddf9366f', u'name': u'freebayes'},
        {u'repository_id': u'491b7a3fddf9366f', u'has_repository_dependencies': False, u'includes_tools_for_display_in_tool_panel': True, u'url': u'/api/repository_revisions/504be8aaa652c154', u'malicious': False, u'includes_workflows': False, u'downloadable': True, u'includes_tools': True, u'changeset_revision': u'd291dc763c4c', u'id': u'504be8aaa652c154', u'includes_tool_dependencies': True, u'includes_datatypes': False}, {u'freebayes': [u'Galaxy Freebayes Bayesian genetic variant detector tool', u'http://takadonet@toolshed.g2.bx.psu.edu/repos/devteam/freebayes', u'd291dc763c4c', u'9', u'devteam', {},
        {u'freebayes/0.9.6_9608597d12e127c847ae03aa03440ab63992fedf': {u'repository_name': u'freebayes', u'name': u'freebayes', u'readme': u'FreeBayes requires g++ and the standard C and C++ development libraries. Additionally, cmake is required for building the BamTools API.', u'version': u'0.9.6_9608597d12e127c847ae03aa03440ab63992fedf', u'repository_owner': u'devteam', u'changeset_revision': u'd291dc763c4c', u'type': u'package'}, u'samtools/0.1.18': {u'repository_name': u'freebayes', u'name': u'samtools', u'readme': u'Compiling SAMtools requires the ncurses and zlib development libraries.', u'version': u'0.1.18', u'repository_owner': u'devteam', u'changeset_revision': u'd291dc763c4c', u'type': u'package'}}]}]

  `repository_revisions`(downloadable=None, malicious=None, tools_functionally_correct=None, missing_test_components=None, do_not_test=None, includes_tools=None, test_install_error=None, skip_tool_test=None)

    Returns a (possibly filtered) list of dictionaries that include information about all repository revisions. The following parameters can be used to filter the list.

    Parameters:

    - downloadable (Boolean) – Can the tool be downloaded
    - malicious (Boolean) –
    - tools_functionally_correct (Boolean) –
    - missing_test_components (Boolean) –
    - do_not_test (Boolean) –
    - includes_tools (Boolean) –
    - test_install_error (Boolean) –
    - skip_tool_test (Boolean) –

    Return type: | List of dictionaries

    Returns:

    Returns a (possibly filtered) list of dictionaries that include information about all repository revisions. For example:

        [{u'repository_id': u'78f2604ff5e65707', u'has_repository_dependencies': False, u'includes_tools_for_display_in_tool_panel': True, u'url': u'/api/repository_revisions/92250afff777a169', u'malicious': False, u'includes_workflows': False, u'downloadable': True, u'includes_tools': True, u'changeset_revision': u'6e26c5a48e9a', u'id': u'92250afff777a169', u'includes_tool_dependencies': False, u'includes_datatypes': False},
        {u'repository_id': u'f9662009da7bfce0', u'has_repository_dependencies': False, u'includes_tools_for_display_in_tool_panel': True, u'url': u'/api/repository_revisions/d3823c748ae2205d', u'malicious': False, u'includes_workflows': False, u'downloadable': True, u'includes_tools': True, u'changeset_revision': u'15a54fa11ad7', u'id': u'd3823c748ae2205d', u'includes_tool_dependencies': False, u'includes_datatypes': False}]

  `search_repositories`(q, page=1, page_size=10)

    Search for repositories in a Galaxy Tool Shed

    Parameters:

    - q (str) – query string for searching purposes
    - page (int) – page requested
    - page_size (int) – page size requested

    Return type: | dict

    Returns:

    dictionary containing search hits as well as metadata for the search example: { u’hits’: [

    > > {

    > >   u’matched_terms’: [], u’repository’:

    > >   > {

    > >   >   u’approved’: u’no’, u’description’: u’Convert export file to fastq’, u’full_last_updated’: u‘2015-01-18 09:48 AM’, u’homepage_url’: None, u’id’: u’bdfa208f0cf6504e’, u’last_updated’: u’less than a year’, u’long_description’: u’This is a simple too to convert Solexas Export files to FASTQ files. The tool installation needs to add a new Export file type, the new class is included in the README file as a patch.’, u’name’: u’export_to_fastq’, u’remote_repository_url’: None, u’repo_owner_username’: u’louise’, u’times_downloaded’: 164

    > >   > },

    > >   u’score’: 4.92

    > > },

    > {

    >   > u’matched_terms’: [], u’repository’:

    >   > > {

    >   > >   u’approved’: u’no’, u’description’: u’Convert BAM file to fastq’, u’full_last_updated’: u‘2015-04-07 11:57 AM’, u’homepage_url’: None, u’id’: u‘175812cd7caaf439’, u’last_updated’: u’less than a month’, u’long_description’: u’Use Picards SamToFastq to convert a BAM file to fastq. Useful for storing reads as BAM in Galaxy and converting to fastq when needed for analysis.’, u’name’: u’bam_to_fastq’, u’remote_repository_url’: None, u’repo_owner_username’: u’brad-chapman’, u’times_downloaded’: 138

    >   > > },

    >   > u’score’: 4.14

    >   }

    ], u’hostname’: u’https://testtoolshed.g2.bx.psu.edu/‘, u’page’: u‘1’, u’page_size’: u‘2’, u’total_results’: u‘64’ }

  `show_repository`(toolShed_id)

    Display information of a repository from Tool Shed

    Parameters: | toolShed_id (str) – Encoded toolShed ID
    Return type: | dictionary

    Returns:

    Information about the tool For example:

        {{u'times_downloaded': 0, u'user_id': u'5cefd48bc04af6d4',
        u'description': u'Order Contigs', u'deleted': False,
        u'deprecated': False, u'private': False,
        u'url': u'/api/repositories/287bd69f724b99ce',
        u'owner': u'billybob', u'id': u'287bd69f724b99ce',
        u'name': u'best_tool_ever'}

    Changed in version 0.4.1: Changed method name from `show_tool` to `show_repository` to better align with the Tool Shed concepts

  `show_repository_revision`(metadata_id)

    Returns a dictionary that includes information about a specified repository revision.

    Parameters: | metadata_id (str) – Encoded repository metadata ID
    Return type: | dictionary

    Returns:

    Returns a dictionary that includes information about a specified repository revision. For example:

        {u'repository_id': u'491b7a3fddf9366f',
         u'has_repository_dependencies': False,
         u'includes_tools_for_display_in_tool_panel': True,
         u'test_install_error': False,
         u'url': u'/api/repository_revisions/504be8aaa652c154',
         u'malicious': False,
         u'includes_workflows': False,
         u'id': u'504be8aaa652c154',
         u'do_not_test': False,
         u'downloadable': True,
         u'includes_tools': True,
         u'tool_test_results': {u'missing_test_components': [],,
         u'includes_datatypes': False}

  `update_repository`(id, tar_ball_path, commit_message=None)

    Update the contents of a tool shed repository with specified tar ball.

    Parameters:

    - id (str) – Encoded repository ID
    - tar_ball_path (str) – Path to file containing tar ball to upload.
    - commit_message (str) – Commit message used for underlying mercurial repository backing tool shed repository.

    Return type: | dict

    Returns:

    Returns a dictionary that includes repository content warnings. Most valid uploads will result in no such warning and an exception will be raised generally if there are problems.

    For example a successful upload will look like:

        {u'content_alert': u'', u'message': u''}

    New in version 0.5.2.

## Configuration

BioBlend allows library-wide configuration to be set in external files. These configuration files can be used to specify access keys, for example.

### Configuration documents for BioBlend

#### BioBlend

class `bioblend.``NullHandler`(level=0)

  Initializes the instance - basically setting the formatter to None and the filter list to empty.

  `emit`(record)

`bioblend.``get_version`()

  Returns a string with the current version of the library (e.g., “0.2.0”)

`bioblend.``init_logging`()

  Initialize BioBlend’s logging from a configuration file.

`bioblend.``set_file_logger`(name, filepath, level=20, format_string=None)

`bioblend.``set_stream_logger`(name, level=10, format_string=None)

#### Config

class `bioblend.config.``Config`(path=None, fp=None, do_load=True)

  BioBlend allows library-wide configuration to be set in external files. These configuration files can be used to specify access keys, for example. By default we use two locations for the BioBlend configurations:

  - System wide: `/etc/bioblend.cfg`
  - Individual user: `~/.bioblend` (which works on both Windows and Unix)
  `get`(section, name, default=None)
  `get_value`(section, name, default=None)
  `getbool`(section, name, default=False)
  `getfloat`(section, name, default=0.0)
  `getint`(section, name, default=0)

## Testing

If you’d like to do more than just a mock test, you’ll want to point BioBlend to an instance of Galaxy. Do so by exporting the following two variables:

    $ export BIOBLEND_GALAXY_URL=http://127.0.0.1:8080
    $ export BIOBLEND_GALAXY_API_KEY=<API key>

The unit tests, stored in the `tests` folder, can be run using nose. From the project root:

    $ nosetests

## Getting help

If you’ve run into issues, found a bug, or can’t seem to find an answer to your question regarding the use and functionality of BioBlend, please use Github Issues page to ask your question.

## Related documentation

Links to other documentation and libraries relevant to this library:

> - Galaxy API documentation
> - Blend4j: Galaxy API wrapper for Java
> - clj-blend: Galaxy API wrapper for Clojure

## Indices and tables

- Index
- Module Index
- Search Page