Commits

yev ishere committed 5018625

Edited online

Comments (0)

Files changed (1)

     shell:  'somecommand {input} {output}'
 ```
 
-Like with GNU Make, in Snakemake you first specify targets in terms of a pseudo rule, and then how they are created via one or more steps of subsequent rule applications. Rules can be generalized via wildcards (here `{dataset}`). Everything is propagated top-down, i.e. here Snakemake determines that for the file `"plots/dataset1.pdf"` the rule plot has to be applied with wildcard `{dataset} = dataset1` to the file `raw/dataset1.csv`. How the files are created is specified either with a shell command or python code. Further, Snakemake can interface with R to specify R code inside rules. Also see the [FAQ](FAQ) to get an impression of the basic idea behind Snakemake.
+Like with GNU Make, in Snakemake you first specify targets in terms of a pseudo rule, and then how they are created via one or more steps of subsequent rule applications. Rules can be generalized via wildcards (here `{dataset}`). Everything is propagated top-down, i.e. here Snakemake determines that for the file `"plots/dataset1.pdf"` the rule plot has to be applied with wildcard `{dataset} = dataset1` to the file `raw/dataset1.csv`. How the files are created is specified either with a shell command or python code. Further, Snakemake can interface with R to specify R code inside rules. Also see the [FAQ](FAQ) to get an impression of the basic idea behind Snakemake. Also there is a [Getting Started with Snakemake and Qsub] Getting Started Guide.
 
 # Usage #
 We provide a [Documentation](Documentation), a [Tutorial](Tutorial) for a particular bioinformatics application a [FAQ](FAQ) and further [Examples](Examples). If you have further questions, please feel free to join our new [Forums](http://groups.google.com/group/Snakemake).
 * **6 June 2012:** Maintenance release 1.1.3 of snakemake. On top of various bug fixes, the algorithm to determine if a rule needs to be run now correctly ignores intermediate files in certain cases. Further, when an error occurs upon parallel execution, all currently running jobs are finished properly before snakemake exits.
 * **15 May 2012:** Release 1.1.2 of snakemake. Instead of using only plain strings, input files can now also be defined as functions or lambda expressions that return a string given the wildcards as an argument. Fixed hangups in parallel execution of a lot of jobs.
 * **15 Apr 2012:** Maintenance release 1.0.2 of snakemake. Improved temporary file handling and error handling when running snakemake on clusters.
-* **9 Apr 2012:** The first stable release (1.0.1) of snakemake.
+* **9 Apr 2012:** The first stable release (1.0.1) of snakemake.