Author: Michael R. Crusoe <michael.crusoe@gmail.com>
Description: Update docs to reflect a local install
--- toil.orig/docs/index.rst
+++ toil/docs/index.rst
@@ -31,7 +31,6 @@
    :caption: Getting Started
    :maxdepth: 2
 
-   gettingStarted/install
    gettingStarted/quickStart
 
 .. toctree::
--- toil.orig/docs/gettingStarted/quickStart.rst
+++ toil/docs/gettingStarted/quickStart.rst
@@ -8,22 +8,15 @@
 Running a basic workflow
 ------------------------
 
-A Toil workflow can be run with just three steps:
+A Toil workflow can be run with just two steps:
 
-1. Install Toil (see :ref:`installation-ref`)
-
-2. Copy and paste the following code block into a new file called ``helloWorld.py``:
+1. Copy and paste the following code block into a new file called ``helloWorld.py``:
 
 .. literalinclude:: ../../src/toil/test/docs/scripts/tutorial_helloworld.py
 
-3. Specify the name of the :ref:`job store <jobStoreOverview>` and run the workflow::
-
-       (venv) $ python helloWorld.py file:my-job-store
+2. Specify the name of the :ref:`job store <jobStoreOverview>` and run the workflow::
 
-.. note::
-
-   Don't actually type ``(venv) $`` in at the beginning of each command. This is intended only to remind the user that
-   they should have their :ref:`virtual environment <venvPrep>` running.
+       python helloWorld.py file:my-job-store
 
 Congratulations! You've run your first Toil workflow using the default :ref:`Batch System <batchsysteminterface>`, ``singleMachine``,
 using the ``file`` job store.
@@ -50,13 +43,6 @@
 workflows that are portable across multiple workflow engines and platforms.
 Running CWL workflows using Toil is easy.
 
-#. First ensure that Toil is installed with the
-   ``cwl`` extra (see :ref:`extras`)::
-
-       (venv) $ pip install 'toil[cwl]'
-
-   This installs the ``toil-cwl-runner`` executable.
-
 #. Copy and paste the following code block into ``example.cwl``:
 
    .. code-block:: yaml
@@ -82,11 +68,11 @@
 
 #. To run the workflow simply enter ::
 
-        (venv) $ toil-cwl-runner example.cwl example-job.yaml
+        $ toil-cwl-runner example.cwl example-job.yaml
 
    Your output will be in ``output.txt``::
 
-        (venv) $ cat output.txt
+        $ cat output.txt
         Hello world!
 
 To learn more about CWL, see the `CWL User Guide`_ (from where this example was
@@ -104,13 +90,6 @@
 The `Workflow Description Language`_ (WDL) is another emerging language for writing workflows that are portable across multiple workflow engines and platforms.
 Running WDL workflows using Toil is still in alpha, and currently experimental.  Toil currently supports basic workflow syntax (see :ref:`wdl` for more details and examples).  Here we go over running a basic WDL helloworld workflow.
 
-#. First ensure that Toil is installed with the
-   ``wdl`` extra (see :ref:`extras`)::
-
-        (venv) $ pip install 'toil[wdl]'
-
-   This installs the ``toil-wdl-runner`` executable.
-
 #. Copy and paste the following code block into ``wdl-helloworld.wdl``::
 
         workflow write_simple_file {
@@ -130,11 +109,11 @@
 
 #. To run the workflow simply enter ::
 
-        (venv) $ toil-wdl-runner wdl-helloworld.wdl wdl-helloworld.json
+        $ toil-wdl-runner wdl-helloworld.wdl wdl-helloworld.json
 
    Your output will be in ``wdl-helloworld-output.txt``::
 
-        (venv) $ cat wdl-helloworld-output.txt
+        $ cat wdl-helloworld-output.txt
         Hello world!
 
 To learn more about WDL, see the main `WDL website`_ .
@@ -161,7 +140,7 @@
 
 #. Run it with the default settings::
 
-      (venv) $ python sort.py file:jobStore
+      $ python sort.py file:jobStore
 
    The workflow created a file called ``sortedFile.txt`` in your current directory.
    Have a look at it and notice that it contains a whole lot of sorted lines!
@@ -178,7 +157,7 @@
 
 3. Run with custom options::
 
-      (venv) $ python sort.py file:jobStore --numLines=5000 --lineLength=10 --overwriteOutput=True --workDir=/tmp/
+      $ python sort.py file:jobStore --numLines=5000 --lineLength=10 --overwriteOutput=True --workDir=/tmp/
 
    Here we see that we can add our own options to a Toil script. As noted above, the first two
    options, ``--numLines`` and ``--lineLength``, determine the number of lines and how many characters are in each line.
@@ -293,7 +272,7 @@
 with the ``--logLevel`` flag. For example, to only log ``CRITICAL`` level
 messages to the screen::
 
-   (venv) $ python sort.py file:jobStore --logLevel=critical --overwriteOutput=True
+   $ python sort.py file:jobStore --logLevel=critical --overwriteOutput=True
 
 This hides most of the information we get from the Toil run. For more detail,
 we can run the pipeline with ``--logLevel=debug`` to see a comprehensive
@@ -317,7 +296,7 @@
 
 When we run the pipeline, Toil will show a detailed failure log with a traceback::
 
-   (venv) $ python sort.py file:jobStore
+   $ python sort.py file:jobStore
    ...
    ---TOIL WORKER OUTPUT LOG---
    ...
@@ -339,11 +318,11 @@
 failure, the job store is preserved so that the workflow can be restarted,
 starting from the previously failed jobs. We can restart the pipeline by running ::
 
-   (venv) $ python sort.py file:jobStore --restart --overwriteOutput=True
+   $ python sort.py file:jobStore --restart --overwriteOutput=True
 
 We can also change the number of times Toil will attempt to retry a failed job::
 
-   (venv) $ python sort.py file:jobStore --retryCount 2 --restart --overwriteOutput=True
+   $ python sort.py file:jobStore --retryCount 2 --restart --overwriteOutput=True
 
 You'll now see Toil attempt to rerun the failed job until it runs out of tries.
 ``--retryCount`` is useful for non-systemic errors, like downloading a file that
@@ -354,7 +333,7 @@
 
 ::
 
-    (venv) $ python sort.py file:jobStore --restart --overwriteOutput=True
+    $ python sort.py file:jobStore --restart --overwriteOutput=True
 
 The pipeline will run successfully, and the job store will be removed on the
 pipeline's completion.
@@ -380,19 +359,19 @@
 
 #. Launch a cluster in AWS using the :ref:`launchCluster` command::
 
-        (venv) $ toil launch-cluster <cluster-name> --keyPairName <AWS-key-pair-name> --leaderNodeType t2.medium --zone us-west-2a
+        $ toil launch-cluster <cluster-name> --keyPairName <AWS-key-pair-name> --leaderNodeType t2.medium --zone us-west-2a
 
    The arguments ``keyPairName``, ``leaderNodeType``, and ``zone`` are required to launch a cluster.
 
 #. Copy ``helloWorld.py`` to the ``/tmp`` directory on the leader node using the :ref:`rsyncCluster` command::
 
-        (venv) $ toil rsync-cluster --zone us-west-2a <cluster-name> helloWorld.py :/tmp
+        $ toil rsync-cluster --zone us-west-2a <cluster-name> helloWorld.py :/tmp
 
    Note that the command requires defining the file to copy as well as the target location on the cluster leader node.
 
 #. Login to the cluster leader node using the :ref:`sshCluster` command::
 
-        (venv) $ toil ssh-cluster --zone us-west-2a <cluster-name>
+        $ toil ssh-cluster --zone us-west-2a <cluster-name>
 
    Note that this command will log you in as the ``root`` user.
 
@@ -413,7 +392,7 @@
 
 #. Use the :ref:`destroyCluster` command to destroy the cluster::
 
-        (venv) $ toil destroy-cluster --zone us-west-2a <cluster-name>
+        $ toil destroy-cluster --zone us-west-2a <cluster-name>
 
    Note that this command will destroy the cluster leader
    node and any resources created to run the job, including the S3 bucket.
@@ -431,17 +410,17 @@
 
 #. First launch a node in AWS using the :ref:`launchCluster` command::
 
-      (venv) $ toil launch-cluster <cluster-name> --keyPairName <AWS-key-pair-name> --leaderNodeType t2.medium --zone us-west-2a
+      $ toil launch-cluster <cluster-name> --keyPairName <AWS-key-pair-name> --leaderNodeType t2.medium --zone us-west-2a
 
 #. Copy ``example.cwl`` and ``example-job.yaml`` from the :ref:`CWL example <cwlquickstart>` to the node using
    the :ref:`rsyncCluster` command::
 
-      (venv) $ toil rsync-cluster --zone us-west-2a <cluster-name> example.cwl :/tmp
-      (venv) $ toil rsync-cluster --zone us-west-2a <cluster-name> example-job.yaml :/tmp
+      $ toil rsync-cluster --zone us-west-2a <cluster-name> example.cwl :/tmp
+      $ toil rsync-cluster --zone us-west-2a <cluster-name> example-job.yaml :/tmp
 
 #. SSH into the cluster's leader node using the :ref:`sshCluster` utility::
 
-      (venv) $ toil ssh-cluster --zone us-west-2a <cluster-name>
+      $ toil ssh-cluster --zone us-west-2a <cluster-name>
 
 #. Once on the leader node, it's a good idea to update and install the following::
 
@@ -458,7 +437,7 @@
 
 #. Now run the CWL workflow::
 
-      (venv) $ toil-cwl-runner --provisioner aws --jobStore aws:us-west-2a:any-name /tmp/example.cwl /tmp/example-job.yaml
+      $ toil-cwl-runner --provisioner aws --jobStore aws:us-west-2a:any-name /tmp/example.cwl /tmp/example-job.yaml
 
    ..  tip::
 
@@ -468,7 +447,7 @@
 
 #. Finally, log out of the leader node and from your local computer, destroy the cluster::
 
-      (venv) $ toil destroy-cluster --zone us-west-2a <cluster-name>
+      $ toil destroy-cluster --zone us-west-2a <cluster-name>
 
 
 .. _awscactus:
@@ -508,7 +487,7 @@
 
 #. Launch a leader node using the :ref:`launchCluster` command::
 
-        (venv) $ toil launch-cluster <cluster-name> --provisioner <aws, gce> --keyPairName <key-pair-name> --leaderNodeType <type> --zone <zone>
+        $ toil launch-cluster <cluster-name> --provisioner <aws, gce> --keyPairName <key-pair-name> --leaderNodeType <type> --zone <zone>
 
 
    .. note::
@@ -518,11 +497,11 @@
         When using AWS, setting the environment variable eliminates having to specify the ``--zone`` option
         for each command. This will be supported for GCE in the future. ::
 
-            (venv) $ export TOIL_AWS_ZONE=us-west-2c
+            $ export TOIL_AWS_ZONE=us-west-2c
 
 #. Create appropriate directory for uploading files::
 
-        (venv) $ toil ssh-cluster --provisioner <aws, gce> <cluster-name>
+        $ toil ssh-cluster --provisioner <aws, gce> <cluster-name>
         $ mkdir /root/cact_ex
         $ exit
 
@@ -531,18 +510,18 @@
    `here <https://github.com/ComparativeGenomicsToolkit/cactus#seqfile-the-input-file>`__), organisms' genome sequence
    files in FASTA format, and configuration files (e.g. blockTrim1.xml, if desired), up to the leader node::
 
-      (venv) $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> pestis-short-aws-seqFile.txt :/root/cact_ex
-      (venv) $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> GCF_000169655.1_ASM16965v1_genomic.fna :/root/cact_ex
-      (venv) $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> GCF_000006645.1_ASM664v1_genomic.fna :/root/cact_ex
-      (venv) $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> GCF_000182485.1_ASM18248v1_genomic.fna :/root/cact_ex
-      (venv) $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> GCF_000013805.1_ASM1380v1_genomic.fna :/root/cact_ex
-      (venv) $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> setup_leaderNode.sh :/root/cact_ex
-      (venv) $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> blockTrim1.xml :/root/cact_ex
-      (venv) $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> blockTrim3.xml :/root/cact_ex
+      $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> pestis-short-aws-seqFile.txt :/root/cact_ex
+      $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> GCF_000169655.1_ASM16965v1_genomic.fna :/root/cact_ex
+      $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> GCF_000006645.1_ASM664v1_genomic.fna :/root/cact_ex
+      $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> GCF_000182485.1_ASM18248v1_genomic.fna :/root/cact_ex
+      $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> GCF_000013805.1_ASM1380v1_genomic.fna :/root/cact_ex
+      $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> setup_leaderNode.sh :/root/cact_ex
+      $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> blockTrim1.xml :/root/cact_ex
+      $ toil rsync-cluster --provisioner <aws, gce> <cluster-name> blockTrim3.xml :/root/cact_ex
 
 #. Log in to the leader node::
 
-        (venv) $ toil ssh-cluster --provisioner <aws, gce> <cluster-name>
+        $ toil ssh-cluster --provisioner <aws, gce> <cluster-name>
 
 #. Set up the environment of the leader node to run Cactus::
 
@@ -588,8 +567,8 @@
 
 #. Download the resulted output to local machine::
 
-        (venv) $ toil rsync-cluster --provisioner <aws, gce> <cluster-name>  :/root/cact_ex/pestis_output3.hal <path-of-folder-on-local-machine>
+        $ toil rsync-cluster --provisioner <aws, gce> <cluster-name>  :/root/cact_ex/pestis_output3.hal <path-of-folder-on-local-machine>
 
 #. Destroy the cluster::
 
-        (venv) $ toil destroy-cluster --provisioner <aws, gce> <cluster-name>
+        $ toil destroy-cluster --provisioner <aws, gce> <cluster-name>
