From 92e271670ab17920712a1b8caf66399b23093f2b Mon Sep 17 00:00:00 2001 From: reillyowencooper Date: Thu, 22 Aug 2024 11:10:02 -0700 Subject: [PATCH] Fixed typo in README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9ff47d5..7f17de6 100644 --- a/README.md +++ b/README.md @@ -82,7 +82,7 @@ GCF_026212275.2_iyMicDemo2.1a,https://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/026/2 The three columns `genome_accession`, `genome_ftp_path`, and `SRA_run_accession` are all required. The `genome_accession` must match the full accession name that is at the end of the FTP download path for a given assembly input. The FTP path is the full NCBI FTP download path for the entire accession, but not including the specific file to be downloaded, (such as not including GCF_026212275.2_iyMicDemo2.1a_genomic.fna.gz in the download link field) as this is done within the workflow code. The `SRA_run_accession` is just the accession and not the FTP download link. -For every pair of mapping results that you want, you must list them with each `genome_accession` and `SRA_run_accession` pairing. For example the above gives two rows of the same `M. lipitor` genome accession but different SRA run accessions. The workflow will sense duplicate genome accessions in the first column and only download it one time, but the different genome:SRA accession pairing need to be listed like the above to ensure proper mapping pairings. Therefore if you have multiple SRA run accessions to map against the same genome, you can copy columns 1 and 2 but change the SRA run accession in the third column in your samplesheet. +For every pair of mapping results that you want, you must list them with each `genome_accession` and `SRA_run_accession` pairing. For example the above gives two rows of the same `M. demolitor` genome accession but different SRA run accessions. The workflow will sense duplicate genome accessions in the first column and only download it one time, but the different genome:SRA accession pairing need to be listed like the above to ensure proper mapping pairings. Therefore if you have multiple SRA run accessions to map against the same genome, you can copy columns 1 and 2 but change the SRA run accession in the third column in your samplesheet. Now you are ready to launch the workflow: ```