{"_id":"5b0e13ffc4664e0003c75ab6","project":"5b0e13ffc4664e0003c75a66","version":{"_id":"5b0e13ffc4664e0003c75a67","project":"5b0e13ffc4664e0003c75a66","__v":4,"createdAt":"2015-09-17T16:58:03.490Z","releaseDate":"2015-09-17T16:58:03.490Z","categories":["5b0e13ffc4664e0003c75a68","5b0e13ffc4664e0003c75a69","5b0e13ffc4664e0003c75a6a","5b0e13ffc4664e0003c75a6b","5b0e13ffc4664e0003c75a6c","5b0e13ffc4664e0003c75a6d","5b0e13ffc4664e0003c75a6e","5b0e13ffc4664e0003c75a6f","5b0e13ffc4664e0003c75a70","5b0e13ffc4664e0003c75a71","5b0e13ffc4664e0003c75a72","5b0e13ffc4664e0003c75a73","5b0e13ffc4664e0003c75a74","5b0e13ffc4664e0003c75a75","5b0e13ffc4664e0003c75a76","5b0e13ffc4664e0003c75a77","5b0e13ffc4664e0003c75a89","5b0e13ffc4664e0003c75a8a","5b0e13ffc4664e0003c75a9d","5b0e13ffc4664e0003c75a9e","5b0e13ffc4664e0003c75a9f","5b0e13ffc4664e0003c75aa0","5b0e13ffc4664e0003c75aa1","5b0e13ffc4664e0003c75aa2","5b0e13ffc4664e0003c75aa3","5b0e13ffc4664e0003c75aa4","5b0e13ffc4664e0003c75aa5","5b0e13ffc4664e0003c75aa6","5b0e13ffc4664e0003c75aa7","5b0e13ffc4664e0003c75aa8","5b0e13ffc4664e0003c75aa9","5b0e13ffc4664e0003c75aaa","5b0e13ffc4664e0003c75aab","5b0e13ffc4664e0003c75aac","5b0e13ffc4664e0003c75aad","5b0e13ffc4664e0003c75aae","5b0e13ffc4664e0003c75aaf","5b0e13ffc4664e0003c75ab2","5bb3374f4306ad0003eb18e7","5bbf3c5373e72a000318362b","5bc065567d1cb0000384c649","5cbf19a5f9181f0033fbb968"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"5b0e13ffc4664e0003c75a70","project":"5b0e13ffc4664e0003c75a66","__v":0,"version":"5b0e13ffc4664e0003c75a67","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-17T17:33:29.016Z","from_sync":false,"order":23,"slug":"run-an-analysis","title":"RUN AN ANALYSIS"},"user":"5613e4f8fdd08f2b00437620","__v":0,"parentDoc":null,"githubsync":"","metadata":{"title":"","description":"","image":[]},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-12-20T12:10:38.314Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"##Overview\n\nExecute apps on the Platform to perform analyses. Each app execution is called a **task**. Each task is associated with a set of input files and chosen settings for the tool(s) in the app.\n\nOn this page, learn about the different types of tasks as well as the configurable components of a task.\n\nConversely, see the step-by-step instructions for [running a task](doc:run-a-task).\n\n##About tasks\n\nA **task** is an execution of an app. Each task is associated with a set of input files and parameter settings. There are two types of tasks on the Platform:\n\n  * **Single task:** A single task represents one execution of a workflow or tool in your project. \n  * **Batch task:** Batch tasks comprise of several child tasks and are used to run the same workflow or tool multiple times with varying inputs in parallel executions. Learn more about [batch tasks](doc:about-batch-analysis).\n\nWhile you set up a task, it is in a draft state and is labelled **DRAFT**. Each **DRAFT** task is saved in the **Tasks** tab for you to set up and run whenever convenient.\n\nLearn how to [create a **DRAFT** task](doc:run-a-task#section-1-create-draft-task) as part of running an analysis.\n\n##Configure your task\n\nBelow, learn about the configurable components of your task: [inputs](doc:about-analyses#section-inputs) and [app settings](doc:about-analyses#section-app-settings).\n\n###Inputs\n\nInput files are the data on which you execute your analysis. \n\nNote that before you configure your task, input must have already been added to your project. You can [add files to a project](docs:copy-files-using-the-visual-interface) from the **Public Files Repository**, from **another project**, or by [uploading them directly to your project](doc:upload-to-the-f4c). \n\nLearn about specific types of input files below. Or, learn how to [select input files](doc:run-a-task#section-2-select-input-files) as part of running your analysis.\n\n####Reference files\n\nA reference file is a specific type of input. The DataSTAGE powered by Seven Bridges maintains the latest and the most frequently used reference genomes and annotation files in its **Public Reference Files** repository, so you won't have to upload your own reference files each time.\n\n####Suggested files\n\nTo help you get started with your analyses, some of the public workflows in the **Public apps** gallery have suggested reference files. This feature allows you to easily add the necessary reference files to help your workflow run properly.\n\nA **Suggested files** pop-up will prompt you to add the suggested files when setting up your draft task. \n\nIf you already have all the suggested reference files in your project, they will pre-populate your draft task page. If any of your workflow's suggested files are not in your project, a **Suggested files** pop-up will prompt you to copy the missing files to your project. You can:\n\n  * Populate your task with the suggested files by clicking **Copy**.\n  * Ignore the suggested files by clicking **Don’t copy**. The pop-up is permanently dismissed and you can choose your own reference files.\n  * Postpone your decision by closing the **Suggested files** pop-up. The pop-up will appear again the next time you access this draft task. \n\n###App settings\n\nThe **Define App Settings** tab on the draft task page allows you to [set the exposed parameters](doc:run-a-task#section--3-define-app-settings) for every tool in your app.\n\nOnly parameters marked to be exposed at runtime can be edited, but you can view all tool parameters. The View Parameters dropdown list allows you to:\n* **Show all** - Displays all editable and non-editable parameters.\n* **Show editable** - Displays editable parameters in view mode.\n* **Show non-default** - Displays parameters whose values have been modified compared to the default ones.\n\nLearn how to [define app settings](doc:run-a-task#section-3-define-app-settings) as part of running your analysis.\n\n##Resources\n* [Run a task](doc:run-a-task) \n* [About batch analyses](doc:about-batch-analyses)\n* [About task execution](doc:about-task-execution) \n* [About controlling task execution](doc:about-controlling-task-execution)","excerpt":"","slug":"about-analyses","type":"basic","title":"About analyses"}
##Overview Execute apps on the Platform to perform analyses. Each app execution is called a **task**. Each task is associated with a set of input files and chosen settings for the tool(s) in the app. On this page, learn about the different types of tasks as well as the configurable components of a task. Conversely, see the step-by-step instructions for [running a task](doc:run-a-task). ##About tasks A **task** is an execution of an app. Each task is associated with a set of input files and parameter settings. There are two types of tasks on the Platform: * **Single task:** A single task represents one execution of a workflow or tool in your project. * **Batch task:** Batch tasks comprise of several child tasks and are used to run the same workflow or tool multiple times with varying inputs in parallel executions. Learn more about [batch tasks](doc:about-batch-analysis). While you set up a task, it is in a draft state and is labelled **DRAFT**. Each **DRAFT** task is saved in the **Tasks** tab for you to set up and run whenever convenient. Learn how to [create a **DRAFT** task](doc:run-a-task#section-1-create-draft-task) as part of running an analysis. ##Configure your task Below, learn about the configurable components of your task: [inputs](doc:about-analyses#section-inputs) and [app settings](doc:about-analyses#section-app-settings). ###Inputs Input files are the data on which you execute your analysis. Note that before you configure your task, input must have already been added to your project. You can [add files to a project](docs:copy-files-using-the-visual-interface) from the **Public Files Repository**, from **another project**, or by [uploading them directly to your project](doc:upload-to-the-f4c). Learn about specific types of input files below. Or, learn how to [select input files](doc:run-a-task#section-2-select-input-files) as part of running your analysis. ####Reference files A reference file is a specific type of input. The DataSTAGE powered by Seven Bridges maintains the latest and the most frequently used reference genomes and annotation files in its **Public Reference Files** repository, so you won't have to upload your own reference files each time. ####Suggested files To help you get started with your analyses, some of the public workflows in the **Public apps** gallery have suggested reference files. This feature allows you to easily add the necessary reference files to help your workflow run properly. A **Suggested files** pop-up will prompt you to add the suggested files when setting up your draft task. If you already have all the suggested reference files in your project, they will pre-populate your draft task page. If any of your workflow's suggested files are not in your project, a **Suggested files** pop-up will prompt you to copy the missing files to your project. You can: * Populate your task with the suggested files by clicking **Copy**. * Ignore the suggested files by clicking **Don’t copy**. The pop-up is permanently dismissed and you can choose your own reference files. * Postpone your decision by closing the **Suggested files** pop-up. The pop-up will appear again the next time you access this draft task. ###App settings The **Define App Settings** tab on the draft task page allows you to [set the exposed parameters](doc:run-a-task#section--3-define-app-settings) for every tool in your app. Only parameters marked to be exposed at runtime can be edited, but you can view all tool parameters. The View Parameters dropdown list allows you to: * **Show all** - Displays all editable and non-editable parameters. * **Show editable** - Displays editable parameters in view mode. * **Show non-default** - Displays parameters whose values have been modified compared to the default ones. Learn how to [define app settings](doc:run-a-task#section-3-define-app-settings) as part of running your analysis. ##Resources * [Run a task](doc:run-a-task) * [About batch analyses](doc:about-batch-analyses) * [About task execution](doc:about-task-execution) * [About controlling task execution](doc:about-controlling-task-execution)