Project

General

Profile

Port a Pipeline » History » Version 24

Nancy Ouyang, 04/17/2015 04:18 PM

1 7 Tom Clegg
{{>toc}}
2
3 1 Nancy Ouyang
h1. Port a Pipeline
4
5
Like any other tool, Arvados requires time to learn. Thus, we don't encourage using Arvados for initial development of analysis pipelines or exploratory research on small subsets of data, when each quick-and-dirty iteration takes minutes on a single machine. But for any computationally-intense work, Arvados offers a lot of benefits.
6
7 8 Nancy Ouyang
Okay, cool, provenance, reproducibility, easily scaling to gigabytes of data and mucho RAM, evaluating existing pipelines like lobSTR quickly.
8 1 Nancy Ouyang
9 8 Nancy Ouyang
But what about if you want to these benefits when running your own pipelines?
10
In other words, how do you **port a pipeline** to Arvados?
11 1 Nancy Ouyang
12
h2. 1. Quick Way
13
14
First, do you just want to parallelize a single bash script?
15
16 23 Nancy Ouyang
Check if you can use @arv-run@. Take this @arv-run@ example, which searches multiple FASTQ files in parallel, and saves the results to Keep through shell redirection:
17 9 Nancy Ouyang
18
    $ arv-run grep -H -n GCTACCAAGTTT \< *.fa \> output.txt
19 1 Nancy Ouyang
20 24 Nancy Ouyang
Or this example, which runs a shell script:
21
22
    $ echo 'echo hello world' > hello.sh    
23
$ arv-run /bin/sh hello.sh
24
25
(Lost? Check out http://doc.arvados.org/user/topics/arv-run.html)
26
27 1 Nancy Ouyang
h3. 1.1 Install arv-run
28
29
See: http://doc.arvados.org/sdk/python/sdk-python.html and http://doc.arvados.org/user/reference/api-tokens.html, or in short below:
30
<pre>
31
$ sudo apt-get install python-pip python-dev libattr1-dev libfuse-dev pkg-config python-yaml
32
$ sudo pip install --pre arvados-python-client
33
</pre>
34
(Lost? See http://doc.arvados.org/sdk/python/sdk-python.html )
35
36
If you try to use arv run right now, it will complain about some settings your missing. To fix that,
37
38 13 Nancy Ouyang
# Go to http://cloud.curoverse.com
39 1 Nancy Ouyang
# Login with any Google account (you may need to click login a few times if you hit multiple redirects from Google)
40
# Click in the upper right on your account name -> Manage Account
41 15 Nancy Ouyang
... !{height:10em}manage_account.png!:manage_account.png
42 1 Nancy Ouyang
# Optional: While you're here, click "send request for shell access", since that will give you shell access to a VM with all of the Arvados tools pre-installed.
43 14 Nancy Ouyang
1) !{height:10em}send_request.png!:send_request.png 2) !{height:10em}request_sent.png!:request_sent.png 3) !{height:10em}access_granted.png!:access_granted.png 
44 12 Nancy Ouyang
# Copy the lines of text into your terminal, something like
45 1 Nancy Ouyang
<pre>
46
HISTIGNORE=$HISTIGNORE:'export ARVADOS_API_TOKEN=*'
47
export ARVADOS_API_TOKEN=sekritlongthing
48 12 Nancy Ouyang
export ARVADOS_API_HOST=qr1hi.arvadosapi.com
49 1 Nancy Ouyang
unset ARVADOS_API_HOST_INSECURE
50 17 Nancy Ouyang
</pre> ... !{height:5em}terminal_ssh.png!:terminal_ssh.png
51 22 Nancy Ouyang
# If you want this to persist across reboot, add the above lines to @~/.bashrc@ or your @~/.bash_profile@
52 1 Nancy Ouyang
53
(Lost? See http://doc.arvados.org/user/reference/api-tokens.html )
54
55
h3. 1.2 Submit job to Arvados
56
57
First, check: Does your command work locally?
58
59
    $ grep -H -n GCTACCAAGTTT *.fa
60
61
If so, then submit it to arvados using @arv run@
62
63
    $ arv-run grep -H -n GCTACCAAGTTT \< *.fa \> output.txt
64
65 21 Nancy Ouyang
* This bash command stores the results as @output.txt@
66 1 Nancy Ouyang
* Note that due to the particulars of grep, Arvados will report this pipeline as failed if grep does not find anything, and no output will appear on Arvados
67
68 21 Nancy Ouyang
Your dataset is uploaded to Arvados if it wasn't on there already (which may take a while if it's a large dataset), your @grep@ job is submitted to run on the Arvados cluster, and you get the results in a few minutes (stored inside @output.txt@ in Arvados). If you go to Workbench at http://cloud.curoverse.com, you will see the pipeline running. It may take a few minutes for Arvados to spool up a node, provision it, and run your job. The robots are working hard for you, grab a cup of coffee.
69 1 Nancy Ouyang
70
(Lost? See http://doc.arvados.org/user/topics/arv-run.html )
71
72
h3. 1.3 However
73
74 10 Nancy Ouyang
If your pipeline looks more like
75
76 11 Nancy Ouyang
!{width: 50%}https://arvados.org/attachments/download/428/provenance_graph_full.png!:https://arvados.org/attachments/download/428/provenance_graph_full.png
77 10 Nancy Ouyang
78
@arv-run@ is not powerful enough. Here we gooooo.
79 1 Nancy Ouyang
80 20 Nancy Ouyang
(yes, that is a screenshot of an actual pipeline graph auto-generated by Arvados)
81
82 1 Nancy Ouyang
h2. 2. In Short
83
84
**Estimated reading time: 1 hour.**
85
86
You must write a **pipeline template** that describes your pipeline to Arvados.
87
88
h3. 2.1 VM (Virtual Machine) Access
89
90
Note: You'll need the Arvados set of command-line tools to follow along. The easiest way to get started is to get access to a Virtual Machine (VM) with all the tools pre-installed.
91
92 19 Nancy Ouyang
# Go to http://cloud.curoverse.com
93 1 Nancy Ouyang
# Login with google account (you may need to click login a few times, our redirects are not working well)
94 18 Nancy Ouyang
# Click in the upper right on your account name -> Manage Account
95
# Hit the "Request shell access" button under Manage Account in workbench.
96 1 Nancy Ouyang
97
h3. 2.2 Pipeline Template Example
98
99
Here is what a simple pipeline template looks like, where the output of program A is provided as input to program B. We'll explain what it all means shortly, but first, don't worry -- you'll never be creating a pipeline template from scratch. You'll always copy and modify an existing boilerplate one (yes, a template for the pipeline template! :])
100
101
102
    **pipelinetemplate.json**
103
    {
104
    "name": "Tiny Bash Script",
105
      "components": {
106
        "Create Two Files": {
107
          "script": "run-command",
108
          "script_version": "master",
109
          "repository": "nancy",
110
          "script_parameters": {
111
            "command": [
112
              "$(job.srcdir)/crunch_scripts/createtwofiles.sh"
113
            ]
114
          ,
115
          "runtime_constraints": {
116
            "docker_image": "nancy/cgatools-wormtable"
117
        ,
118
        "Merge Files": {
119
          "script": "run-command",
120
          "script_version": "master",
121
          "repository": "nancy",
122
          "script_parameters": {
123
            "command": [
124
              "$(job.srcdir)/crunch_scripts/mergefiles.sh",
125
              "$(input)"
126
            ],
127
            "input": {
128
              "output_of": "Create Two Files"
129
          ,
130
          "runtime_constraints": {
131
            "docker_image": "nancy/cgatools-wormtable"
132
          
133
h2. 3. simple and sweet port-a-pipeline example
134
135
Okay, let's dig into what's going on.
136
137
h3. 3.1 the setup
138
139
We'll port an artificially simple pipeline which involves just two short bash scripts, described as "A" and "B" below:
140
141
**Script A. Create two files**
142
Input: nothing
143
Output: two files (out1.txt and out2.txt)
144
145
**Script B. Merge two files into a single file**
146
Input: output of step A
147
Output: a single file (output.txt)
148
149
Visually, this looks like [!graph image] (ignore the long strings of gibberish in the rectangles for now).
150
151
Here's what we've explained so far in the pipeline template:
152
153
154
    **pipelinetemplate.json**
155
    {
156
    **"name": "Tiny Bash Script",**
157
      "components": {
158
       **"Create Two Files": {**
159
          "script": "run-command",
160
          "script_version": "master",
161
          "repository": "arvados",
162
          "script_parameters": {
163
            "command": [
164
              "$(job.srcdir)/crunch_scripts/ *createtwofiles.sh* "
165
            ]
166
          ,
167
          "runtime_constraints": {
168
            "docker_image": "nancy/cgatools-wormtable"
169
        ,
170
        **"Merge Files": {**
171
          "script": "run-command",
172
          "script_version": "master",
173
          "repository": "arvados",
174
          "script_parameters": {
175
            "command": [
176
              "$(job.srcdir)/crunch_scripts/ *mergefiles.sh* ",
177
              "$(input)"
178
            ],
179
           **"input": {**
180
              **"output_of": "Create Two Files"**
181
          ,
182
          "runtime_constraints": {
183
            "docker_image": "nancy/cgatools-wormtable"
184
185
186
h3. **3.2 arv-what?**
187
188
Before we go further, let's take a quick step back. Arvados consists of two parts
189
190
**Part 1. Keep** - I have all your files in the cloud!
191
192
You can access your files through your browser, using **Workbench**, or using the Arvados command line (CLI) tools (link: http://doc.arvados.org/sdk/cli/index.html ).
193
194
Visually, this looks like
195
[!image 1: workbench]
196
[!image 2: shell session, arv mount]
197
198
**Part 2. Crunch** - I run all your scripts in the cloud!
199
200
Crunch both dispatches jobs and provides version control for your pipelines.
201
202
You describe your workflow to Crunch using **pipeline templates**. Pipeline templates describe a pipeline ("workflow"), the type of inputs each step in the pipeline requires, and . You provide a high-level description of how data flows through the pipeline—for example, the outputs of programs A and B are provided as input to program C—and let Crunch take care of the details of starting the individual programs at the right time with the inputs you specified.
203
204
[!image 2: complex pipeline]
205
206
Once you save a pipeline template in Arvados, you run it by creating a pipeline instance that lists the specific inputs you’d like to use. The pipeline’s final output(s) will be saved in a project you specify.
207
208
Concretely, a pipeline template describes
209
210
* **data inputs** - specified as Keep content addresses
211
* **job scripts** - stored in a Git version control repository and referenced by a commit hash
212
* **parameters** - which, along with the data inputs, can have default values or can be filled in later when the pipeline is actually run
213
* **the execution environment** - stored in Docker images and referenced by Docker image name
214
215
**What is Docker**? Docker allows Arvados to replicate the execution environment your tools need. You install whatever bioinformatics tools (bwa-mem, vcftools, etc.) you are using inside a Docker image, upload it to Arvados, and Arvados will recreate your environment for computers in the cloud.
216
217
**Protip:** Install stable external tools in Docker. Put your own scripts in a Git repository. This is because each docker image is about 500 GB, so each new docker image takes a while to upload (30 minutes) if you are not using Arvados on a local cluster. In the future, we hope to use small diff files describing just the changes made to Docker image instead of the full Docker image. [Last updated 19 Feb 2015]
218
219
h3. 3.3 In More Detail
220
221
Alright, let's put that all together.
222
223
    **pipelinetemplate.json**
224
    {
225
    "name": "Tiny Bash Script",
226
      "components": {
227
        "Create Two Files": {
228
          "script": "run-command",
229
          "script_version": "master",
230
          "repository": "nancy",
231
          "script_parameters": {
232
            "command": [
233
              "$(job.srcdir)/crunch_scripts/createtwofiles.sh" **#[1]**
234
            ]
235
          ,
236
          "runtime_constraints": {
237
            "docker_image": "nancy/cgatools-wormtable"
238
        ,
239
        "Merge Files": {
240
          "script": "run-command",
241
          "script_version": "master",
242
          "repository": "nancy",
243
          "script_parameters": {
244
            "command": [
245
              "$(job.srcdir)/crunch_scripts/mergefiles.sh", **#[2]**
246
              "$(input)"
247
            ],
248
            "input": {
249
              "output_of": "Create Two Files" **#[3]**
250
          ,
251
          "runtime_constraints": {
252
            "docker_image": "nancy/cgatools-wormtable"    
253
    
254
**Explanation**
255
    
256
[1] **$(job.srcdir)** references the git repository "in the cloud". Even though **run-command** is in nancy/crunch_scripts/ and is "magically found" by Arvados, INSIDE run-command you can't reference other files in the same repo as run-command without this magic variable.
257
258
Any output files as a result of this run-command will be automagically stored to keep as an auto-named collection (which you can think of as a folder for now).
259
260
[2] Okay, so how does the next script know where to find the output of the previous job? run-command will keep track of the collections it's created, so we can feed that in as an argument to our next script. In this "command" section under "run-command", you can think of the commas as spaces. Thus, what this line is saying is "run mergefile.sh on the previous input", or
261
262
  $ mergefiles.sh [directory with output of previous command]
263
264
[3] Here we set the variable "input" to point to the directory with the output of the previous command "Create Two Files".
265
266
(Lost? Try the hands-on example in the next section, or read more detailed documentation on the Arvados website: 
267
268
* http://doc.arvados.org/user/tutorials/running-external-program.html
269
* http://doc.arvados.org/user/topics/run-command.html
270
* http://doc.arvados.org/api/schema/PipelineTemplate.html )
271
272
h3. 3.4 All hands on deck!
273
274
Okay, now that we know the rough shape of what's going on, let's get our hands dirty.
275
276 2 Nancy Ouyang
*From your local machine, login to Arvados virtual machine*
277 1 Nancy Ouyang
278 4 Nancy Ouyang
Single step:
279 1 Nancy Ouyang
280 4 Nancy Ouyang
  nrw@ *@nrw-local@* $ ssh nancy@lightning-dev4.shell.arvados
281
282 1 Nancy Ouyang
(Lost? See "SSH access to machine with Arvados commandline tools installed" http://doc.arvados.org/user/getting_started/ssh-access-unix.html )
283
284
**In VM, create pipeline template**
285
286
A few steps:
287
288
  nancy@ *@lightning-dev4.su92l@* :~$ arv create pipeline_template
289
Created object qr1hi-p5p6p-3p6uweo7omeq9e7
290
$ arv edit qr1hi-p5p6p-3p6uweo7omeq9e7 #Create the pipeline template as described above! [[Todo: concrete thing]]
291
292
(Lost? See "Writing a pipeline template" http://doc.arvados.org/user/tutorials/running-external-program.html )
293
294
*In VM, set up git repository with run_command and our scripts*
295
296 2 Nancy Ouyang
A few steps: 
297 1 Nancy Ouyang
298 2 Nancy Ouyang
  $ mkdir @~@/projects
299
$ cd @~@/projects
300
~/projects $ git clone git@git.qr1hi.arvadosapi.com:nancy.git 
301 1 Nancy Ouyang
302 2 Nancy Ouyang
(Lost? Find your own git URL by going to https://workbench.su92l.arvadosapi.com/manage_account )
303 1 Nancy Ouyang
304 2 Nancy Ouyang
    ⤷Copy run_command & its dependencies into this crunch_scripts
305
  $ git clone https://github.com/curoverse/arvados.git 
306 1 Nancy Ouyang
307 2 Nancy Ouyang
(Lost? Visit https://github.com/curoverse/arvados )
308
309
  @  @$ cd ./nancy
310
  *@~/projects/nancy@* $ mkdir crunch_scripts
311
  *@~/projects/nancy@* $ cd crunch_scripts
312
  *@~/projects/nancy/crunch_scripts@* $ cp @~@/projects/arvados/crunch_scripts/run_command . #trailing dot!
313
  ~/projects/nancy/crunch_scripts$ cp ~/projects/arvados/crunch_scripts/crunchutil . #trailing dot!
314
315
  @  @$ cd ~/projects/nancy/crunch_scripts
316
317
  @  @$ vi createtwofiles.sh
318
    ⤷ $cat createtwofiles.sh
319
    #!/bin/bash
320
    echo "Hello " > out1.txt
321
    echo "Arvados!" > out2.txt
322
323
  @  @$ vi mergefiles.sh
324 1 Nancy Ouyang
    ⤷$cat mergefiles.sh
325 5 Nancy Ouyang
      #!/bin/bash *#[1]*
326
      PREVOUTDIR=$1 *#[2]*
327
      echo $TASK_KEEPMOUNT/by_id/$PREVOUTDIR *#[3]*
328 1 Nancy Ouyang
      cat $TASK_KEEPMOUNT/by_id/$PREVOUTDIR/*.txt > output.txt
329
    
330 5 Nancy Ouyang
⤷ *Explanations*
331 6 Nancy Ouyang
*[1]* We use the @#!@ syntax to let bash know what to execute this file with
332 5 Nancy Ouyang
333
  ⤷To find the location of any particular tool, try using **which**
334
    $ which python
335
    /usr/bin/python
336
    $ which bash
337
    /bin/bash
338
    
339
*[2]* [[TODO: $1]] Here we give a human-readable name, @PREVOUTDIR@, to the first argument given to @mergefiles.sh@, which (referring back to the pipeline template) we defined as the directory containing the output of the previous job (which ran @createtwofiles.sh@).
340
    
341
*[3]* Using the environmental variable @TASK_KEEPMOUNT@ allows us to not make assumptions about where **keep** is mounted. @TASK_KEEPMOUNT@ will be replaced by Arvados automatically with the name of the location to which **keep** is mounted on each worker node. (Lost? Visit http://doc.arvados.org/user/tutorials/tutorial-keep-mount.html )
342 1 Nancy Ouyang
    
343 6 Nancy Ouyang
<pre>$ chmod +x createtwofiles.sh mergefiles.sh # make these files executable</pre>
344 1 Nancy Ouyang
345
**Commit changes and push to remote**
346
347 2 Nancy Ouyang
A few steps: 
348 1 Nancy Ouyang
349 2 Nancy Ouyang
  $ git status #check that everything looks ok
350
$ git add *
351
$ git commit -m “hello world-of-arvados scripts!”
352
$ git push
353
354 1 Nancy Ouyang
**Install Docker**
355
356 2 Nancy Ouyang
A few steps: 
357 1 Nancy Ouyang
358 2 Nancy Ouyang
  $ sudo apt-get install docker.io
359
$ sudo groupadd docker
360
$ sudo gpasswd -a $USER docker #in my case, I replace $USER with “nancy”
361
$ sudo service docker restart
362
$ exec su -l $USER   #if you don’t want to login+out or spawn a new shell, this will restart your shell
363
364 1 Nancy Ouyang
**Make docker less sad about running out of space on the VM**
365
366 2 Nancy Ouyang
A few steps:
367
368
  $ sudo mkdir /data/docker
369
$ sudo vi /etc/default/docker
370
@  @⤷$ cat /etc/default/docker
371
      DOCKER_OPTS="--graph='/data/docker'"
372
      export TMPDIR="/data/docker"
373 1 Nancy Ouyang
     
374
**Make Arvados less sad about running out of space on the VM**
375 2 Nancy Ouyang
376
A few steps: 
377
378 1 Nancy Ouyang
    $ sudo mkdir /data/docker-cache
379 3 Nancy Ouyang
$ sudo chown nancy:nancy /data/docker-cache
380
$ ln -s /data/docker-cache docker
381 1 Nancy Ouyang
382
**Create Docker image with Arvados command-line tools and other tools we want**
383 2 Nancy Ouyang
384
A few steps: 
385
386 3 Nancy Ouyang
    $ docker pull arvados/jobs
387 1 Nancy Ouyang
$ docker run -ti arvados/jobs /bin/bash
388 2 Nancy Ouyang
389 4 Nancy Ouyang
Now we are in the docker image.
390 2 Nancy Ouyang
391 1 Nancy Ouyang
    root@4fa648c759f3:/# apt-get update 
392
393 2 Nancy Ouyang
    @  @⤷In the docker image, install external tools that you don't expect to need to update often. 
394 1 Nancy Ouyang
    For instance, we can install the wormtable python tool in this docker image
395 2 Nancy Ouyang
    @  @# apt-get install libdb-dev
396 3 Nancy Ouyang
    @  @# pip install wormtable
397 1 Nancy Ouyang
398
    @  @  ⤷ Note: If you're installing from binaries, you should either
399 6 Nancy Ouyang
        1) Install in existing places where bash looks for programs (e.g. install in /usr/local/bin/cgatools). 
400
        To see where bash looks, inspect the PATH variable.
401 1 Nancy Ouyang
          #echo $PATH
402
          /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
403 6 Nancy Ouyang
        2) If you put them in a custom directory, remember them to reference them as such in your scripts
404
        (e.g. spell out /home/nrw/local/bin/cgatools).
405
        Arvados will not respect modifyng the $PATH variable by using the ~/.bashrc configuration file in the docker image.
406 2 Nancy Ouyang
407 1 Nancy Ouyang
(Lost? See http://doc.arvados.org/user/topics/arv-docker.html )
408
    
409
  root@4fa648c759f3:/# exit
410 2 Nancy Ouyang
411 1 Nancy Ouyang
*Commit Docker image*
412 2 Nancy Ouyang
<pre>
413 6 Nancy Ouyang
$ docker commit 4fa648c759f3 nancy/cgatools-wormtable #Label the image thoughtfully
414
$ #For instance here I used the name of key tools I installed: cgatools & wormtable
415 2 Nancy Ouyang
</pre>
416 1 Nancy Ouyang
417 2 Nancy Ouyang
*Upload Docker image from your VM to Keep*
418
<pre>
419
$ arv keep docker nancy/cgatools-wormtable #this takes a few minutes
420
$ arv keep docker #lists docker images in the cloud, so you can double-check what was uploaded </pre>
421 1 Nancy Ouyang
422
**Run this pipeline!**
423
Go to Workbench and hit **Run**.
424 2 Nancy Ouyang
<pre>$ firefox http://su92l.arvadosapi.com</pre>
425 1 Nancy Ouyang
[!image: workbench with 'tiny bash script']
426
427 2 Nancy Ouyang
*Note: If no worker nodes are already provisioned, your job may take up to 10 minutes to queue up and start.* Behind-the-scenes, Arvados is requesting compute nodes for you and installing your Docker image and otherwise setting up the environment on those nodes. Then Arvados will be ready to run your job. Be patient -- the wait time may seem frustrating for a trivial pipeline like this, but Arvados really excels at handling long and complicated pipelines with built-in data provenance and pipeline reproducibility.
428 1 Nancy Ouyang
429
h3. 3.5 Celebrate
430
431
Whew! Congratulations on porting your first pipeline to Arvados! Check out http://doc.arvados.org/user/topics/crunch-tools-overview.html to learn more about the different ways to port pipelines to Arvados and how to take full advantage of Arvados's features, like restarting pipelines from where they failed instead of from the beginning. 
432
433
h2. 4. Debugging Tips and Pro-Tips
434
435
h3. **4.1 Pro-tips**
436
437
**Keep mounts are read-only right now. [19 March 2015]**
438
Need to 1) make some temporary directories or 2) change directories away from wherever you started out in but still upload the results to keep?
439
440
For 1, Explicitly use the $HOME directory and make the temporary files there
441
For 2, Use present working directory, $(pwd) at the beginning of your script to write down the directory where run-command will look for files to upload to keep.
442
443
Here's an example:
444
<pre>
445
$ cat mergefiles.sh
446
  TMPDIR=$HOME #directory to make temporary files in
447
  OUTDIR=$(pwd) #directory to put output files in
448
  mkdir $TMPDIR
449
  touch $TMPDIR/sometemporaryfile.txt #this file is deleted when the worker node is stopped
450
  touch $OUTDIR/someoutputfile.txt #this file will be uploaded to keep by run-command
451
</pre>
452
453
* make sure you point to the right repository, your own or arvados.
454
* make sure you pin the script versions of your python sdk, docker image, and script version or you will not get reproducibiltiy.
455
* if you have a file you want to use as a crunch script, make sure its in a crunch_scripts directory. otherwise, arvados will not find it. i.e. ~/path/to/git/repo/crunch_scripts/foo.py
456
457
h3. 4.2 Common log errors and reasons for pipelines to fail
458
459
Todo.
460
461
h3. 4.3 Miscellaneous Notes
462
463
Other ways to avoid the read-only keep mount problem is to use task.vwd which uses symlinks from the output directory which is writable to the colelction in keep. If you can change your working directory to the output directory and do all your work there, you'll avoid the keep read only issue.  (lost? see http://doc.arvados.org/user/topics/run-command.html )
464
    
465
When indexing, i.e. tabix, bwa index, etc. The index file tends to be created in the same directory as your fastq file. In order to avoid this, use ^. There is no way to send the index file to another directory. If you figure out a way, please tell me.
466
467
"bash" "-c" could be your friend, it works sometimes, sometimes it doesnt. I don't have a good handle on why this works sometimes.
468
469
if you're trying to iterate over >1 files using the task.foreach, its important to know that run-command uses a m x n method of making groups. I dont think I can explain it right now, but it may not be exactly what you want and you can trip over it. (lost? see http://doc.arvados.org/user/topics/run-command.html )
470
471
When trying to pair up reads, its hard to use run-command. You have to manipulate basename and hope your file names are foo.1 foo.2. base name will treat the group as foo (because you'll regex the groups as foo) and you can glob for foo.1 and foo.2. but if the file names are foo_1 and foo_2, you cant regex search them for foo becuase you'll get both names into a group and you'll be iterating through both of them twice, because of m x n. 
472
    
473
Your scripts need to point to the right place where the file is. Its currently hard to figure out how to grep the file names, you have to do some magic through the collection api.
474
475
h2. 5. Learn More
476
477
To learn more, head over to the Arvados User Guide documentation online: http://doc.arvados.org/user/