Bug #4562
Updated by Ward Vandewege over 9 years ago
These general approaches need to be introduced and explained between http://doc.arvados.org/user/tutorials/intro-crunch.html and http://doc.arvados.org/user/tutorials/running-external-program.html. Executive summary * arv-run makes sense for simple fan-out commands * run-command makes sense when you already have a command line tool installed in a docker image, and you just want to invoke it as part of a compute workflow/pipeline * writing your own crunch script makes sense if you want your code to be in revision control, you want more control of concurrency patterns, you need better performance, or you'd just rather write everything in python. * third option (use run-command to wrap something that lives in your own git tree) isn't very well supported but as a workaround you could copy the run-command stuff into your own git tree. This page should clearly explain the limitations of arv-run and run-command so that users know when to switch between the approaches to run things.