Choosing a workflow =================== .. The workflow status table and README accordion sections rely on raw HTML/JavaScript to fetch and render live status from the GitLab API. Those sections will be empty or broken in non-HTML output formats (PDF, LaTeX, man pages) and require internet access to display. Which workflow fits your needs? ------------------------------- RAFT workflows are designed for different analysis goals, so the best choice depends on the biological question you are trying to answer. For example, **LENS** is designed for tumor antigen discovery from short-read data, while **Gene-Fusions** is designed for fusion detection. Review the workflow table below to compare available workflows and their current status. Which workflow profile fits your needs? --------------------------------------- Each workflow provides a ``standard`` profile by default. This profile is intended to provide a balanced starting point for typical analyses. Some workflows also offer additional profiles. For example, an ``exhaustive`` profile may run a broader set of tools, while a ``fast`` profile may prioritize turnaround time over breadth. Review the workflow details below to see which profiles are currently available for each workflow. Customizing the workflow configuration -------------------------------------- RAFT allows users to fully customize the workflow to their liking. Specifically, users can modify: - Which tools are run - Which version of tools are run - Parameters passed to tools - References used throughout the workflow Users can introduce these modifications through the `web-based user interface `_ when running RAFT. .. figure:: _static/config-generator.png :alt: RAFT workflow configuration interface The RAFT workflow configuration interface. Available workflows -------------------- .. raw:: html
Loading workflows from GitLab...
Workflow details ---------------- .. raw:: html