| ... | ... | @@ -3,7 +3,7 @@ Virtual Research Environments integrate tools and pipelines to enforce a researc |
|
|
|
#### Table of contents
|
|
|
|
* [Why?](#why)
|
|
|
|
* [How it works?](#How-it-works)
|
|
|
|
* [How to bring a new tool?](#how-to-bring-a-new-tool)
|
|
|
|
* [How to bring in a new tool?](#how-to-bring-in-a-new-tool)
|
|
|
|
|
|
|
|
***
|
|
|
|
|
| ... | ... | @@ -41,7 +41,7 @@ There are some steps to follow for achieving the integration of a your applicati |
|
|
|
|
|
|
|
***
|
|
|
|
|
|
|
|
## How to bring a new tool?
|
|
|
|
## How to bring in a new tool?
|
|
|
|
Essentially, VRE will need two elements, (1) your application or workflow wrapped within a **VRE RUNNER**, and (2) **metadata** annotating it (*i.e.* input files requirements, descriptions). The following steps describe how to achieve it.
|
|
|
|
|
|
|
|
- [Step 1](#step-1-pre-define-your-tool-to-build-a-test-set-of-VRE-job-execution-files) Define your tool's input and output files. Build job execution files for testing the RUNNER.
|
| ... | ... | |
