From d6fa85d3ad9778eba00882965d3a59fc0d8339a1 Mon Sep 17 00:00:00 2001
From: selva <selvaganz1285@gmail.com>
Date: Mon, 17 Oct 2022 14:35:37 +0530
Subject: [PATCH] update working.md
---
docs/source/getting_started/Working.md | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/docs/source/getting_started/Working.md b/docs/source/getting_started/Working.md
index d7f2154..89bd387 100644
--- a/docs/source/getting_started/Working.md
+++ b/docs/source/getting_started/Working.md
@@ -11,10 +11,12 @@ The three commands that are the core of BiTIA's functionality are:
#### 1. Running commands
```bash
-$ bitia run "samtools convert foo.fa#http://example.com/foo.fa"
+$ bitia run "samtools convert <foo.fa|http://example.com/foo.fa>"
```
The above code will:
-- Add the given command `samtools run foo.fa#http://example.com/foo.fa` into a pipeline file.
+- Checks for the input file `foo.fa` in the current working directory
+- Download the input file from given link `http://example.com/foo.fa` and name it as `foo.fa`
+- Add the given command `samtools convert <foo.fa|http://example.com/foo.fa` into a pipeline file.
- Extract the current working directory with the pipeline as a zip file that contains a unique hash and send it to the server `public.bitia.link`
- The BiTIA runner in the server will execute the pipeline by:
- Installing the given command `samtools`
--
GitLab