| ... | @@ -153,12 +153,15 @@ After approval, the tool will be accessible on the web application in *test mode |
... | @@ -153,12 +153,15 @@ After approval, the tool will be accessible on the web application in *test mode |
|
|
<br/>
|
|
<br/>
|
|
|
|
|
|
|
|
#### STEP 4: Test and debug the new tool from the VRE
|
|
#### STEP 4: Test and debug the new tool from the VRE
|
|
|
|
As Tool developer, you'll be able to run your tool from the VRE as any other tool, although some extra information will be available for you to easy monitoring and debugging:
|
|
|
|
- Extra Job information: access to the complete metadata of jobs, including identifiers, full paths, submitted command lines and access to the configuration JSONs
|
|
|
|
- Tool Panel Administration: right to enable/disable your tool, together with some statistics on the runs carried out at the VRE
|
|
|
|
|
|
|
|
<br/>
|
|
<br/>
|
|
|
|
|
|
|
|
#### STEP 5: Prepare a custom report viewer for each execution
|
|
#### STEP 5: Prepare a custom report viewer for each execution
|
|
|
|
|
|
|
|
<br/>
|
|
If any of the visualizers is not display your results in the appropriated way, you can create a dynamics HTML page that is going to be framed within the platform in the `Run Folder > View Results` tab, at the workspace
|
|
|
|
|
|
|
|
#### STEP 6: Provide documentation for the new tool
|
|
#### STEP 6: Provide documentation for the new tool
|
|
|
|
|
|
| ... | | ... | |
