fixed BUSCO part to run on GCP

Author: aolveraNIH

GoogleCloud/Submodule_2_annotation_only.ipynb

@@ -278,7 +278,7 @@
    "outputs": [],
    "source": [
     "! mkdir -p <Your-Output-Directory-annotation-only>\n",
-    "! gsutil cp -r s3://<YOUR-BUCKET-NAME>/<Your-Output-Directory-annotation-only>/ ./<Your-Output-Directory-annotation-only>"
+    "! gsutil -m cp -r s3://<YOUR-BUCKET-NAME>/<Your-Output-Directory-annotation-only>/ <Your-Output-Directory-annotation-only>"
    ]
   },
   {
@@ -288,24 +288,15 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "! ls -l ./<Your-Output-Directory-annotation-only>"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "a96e29ed",
-   "metadata": {},
-   "source": [
-    "----\n",
-    "# Andrea, please update this part"
+    "! ls -l <Your-Output-Directory-annotation-only>"
    ]
   },
   {
    "cell_type": "markdown",
    "id": "f3255502-270c-4ebb-9f72-141c4fab5c0f",
    "metadata": {},
    "source": [
-    "Let's take a look at the `RUN_INFO.txt` file to see what the parameters and programs associated with our analysis were."
+    "Let's take a look at the `params.json` file to see what the parameters and programs associated with our analysis were. This json file will have the date you ran the pipeline as well a pipeline identifier. Update the code below to look at the `params.json` file."
    ]
   },
   {
@@ -315,15 +306,7 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "! cat ./<Your-Output-Directory-annotation-only>/output/RUN_INFO.txt"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "9c86c829",
-   "metadata": {},
-   "source": [
-    "---"
+    "! cat ./<Your-Output-Directory-annotation-only>/pipeline_info/params_<Date-identifier>.json"
    ]
   },
   {
@@ -342,7 +325,7 @@
     ">\n",
     ">Container systems ([Docker](https://www.docker.com/) and [Singularity](https://sylabs.io/singularity/) are the two most well-known examples) address this by installing and encapsulating the program and all of its necessary supporting components in an image. Each program is then executed in the context of its container image, which is activated just long enough to run its program.\n",
     ">\n",
-    ">Because of the way that we have run the TransPi workflow in the previous, our system will already have several container images installed. We can now work directly with these images."
+    ">Because of the way that we have run the denovotranscript workflow previously, our system will already have several container images installed. We can now work directly with these images."
    ]
   },
   {
@@ -439,9 +422,9 @@
    "outputs": [],
    "source": [
     "! docker run -it --rm --volume /home:/home quay.io/biocontainers/busco:5.4.3--pyhdfd78af_0 busco \\\n",
-    "-i /home/ec2-user/SageMaker/Transcriptome-Assembly-Refinement-and-Applications/GoogleCloud/resources/trans/Oncorhynchus_mykiss_GGBN01.1.fa \\\n",
+    "-i /home/jupyter/resources/trans/Oncorhynchus_mykiss_GGBN01.1.fa \\\n",
     "-l vertebrata_odb10 -o GGBN01_busco_vertebrata \\\n",
-    "--out_path /home/ec2-user/SageMaker/Transcriptome-Assembly-Refinement-and-Applications/GoogleCloud/buscoOutput -m tran -c $THREADS"
+    "--out_path ./buscoOutput -m tran -c $THREADS"
    ]
   },
   {