Workflows

What is a Workflow?
11 Workflows visible to you, out of a total of 11

This workflow encodes the top-ranking predicted pathways from the previous workflow into plasmids intended to be expressed in the specified organism. BASIC is used as assembly method.

Type: Galaxy

Creators: None

Submitter: ramiz khaled

This workflow encodes the top-ranking predicted pathways from the previous workflow into plasmids intended to be expressed in the specified organism. Assembly methods are Gibson, Golden or Ligation Chain Reaction.

Type: Galaxy

Creators: None

Submitter: ramiz khaled

Annotation: Evaluating and ranking a set of pathways based on multiple metrics. Given a set of pathways generated by RetroPath2.0, this workflow informs the user as to the theoretically best performing ones based on the four criteria (target product flux, thermodynamic feasibility, pathway length, and enzyme availability).

Type: Galaxy

Creator: BioRetroSynth

Submitter: ramiz khaled

Generating theoretical possible pathways for the production of Lycopene in E.Coli using Retrosynthesis tools

Type: Galaxy

Creator: BioRetroSynth

Submitter: ramiz khaled

No description specified

Type: Galaxy

Creators: None

Submitter: ramiz khaled

No description specified

Type: Galaxy

Creators: None

Submitter: ramiz khaled

Domestication of new parts and cloning simulation

Add new parts to your sequences before the cloning simulation and interact with the database.

input:

  • input: csv file (without header) : The CSV file should contain the constraints line by line in the first column, along with their associated fragments on each line. This data will be passed to the seq_from_DB tool.
  • JSON parameters file (optional) : The JSON file should contain the the parameters used in workflow tools. If this ...

Type: Galaxy

Creators: None

Submitter: ramiz khaled

Cloning simulation workflow for sequences present in DB

Run the GoldenGate cloning simulation for a list of constructs in a CSV file and interact with a database

inputs:

  • Assmbly Plan (without header) : The CSV file should contain the constraints line by line in the first column, along with their associated fragments on each line. This data will be passed to the seq_from_DB tool.
  • JSON parameters file (optional) : The JSON file should contain the the parameters used in workflow ...

Type: Galaxy

Creators: None

Submitter: ramiz khaled

Cloning simulation workflow for sequences present in DB

Run the GoldenGate cloning simulation for a list of constructs in a CSV file and interact with a database

steps:

input: csv file (without header) : The CSV file should contain the constraints line by line in the first column, along with their associated fragments on each line. This data will be passed to the seq_from_DB tool.

workflow_1 Parameter_Maystro

  1. Distribute workflow parameters on the workflow tools
  2. Parameters ...

Type: Galaxy

Creators: None

Submitter: ramiz khaled

Domestication of new parts before cloning simulation

Add new parts to your sequences before the cloning simulation and interact with the database.

steps:

input: csv file (without header) : The CSV file should contain the constraints line by line in the first column, along with their associated fragments on each line. This data will be passed to the seq_from_DB tool.

seq_from_DB

  1. Extract the fragments associated with each constraint from the CSV file.
  2. Check if all fragments are ...

Type: Galaxy

Creators: None

Submitter: ramiz khaled

Powered by
(v.1.17.1)
Copyright © 2008 - 2025 The University of Manchester and HITS gGmbH