Skip to content

updated wording of no-raw-sequences.rst #1827

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 6, 2016
Merged

updated wording of no-raw-sequences.rst #1827

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b1b82e2
updated wording of no-raw-sequences.rst
colinbrislawn May 5, 2016
71810c0
Update no-raw-sequences.rst
colinbrislawn May 5, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions qiita_pet/support_files/doc/source/tutorials/no-raw-sequences.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,8 +78,10 @@ files and that they do not have any barcode or primer information. This file typ
normally is what you can download from `Illumina's BaseSpace <https://basespace.illumina.com/home/index>`__.


The current system allows users to upload this kind of files. The only requirement is
that the prep template should have the uploaded sequence file(s) name in the
The current system allows users to upload these files and the standard protocol
differs in two small ways. The first is that the ``barcode`` field will be
omitted. The second is that the Preparation information file should have the
uploaded sequence file(s) name in the
run_prefix field. This should be an exact match without extension (fastq or
fastq.gz). For example, if your uploaded file is named sample1_L001_R1.fastq.gz
you will need to have sample1_L001_R1 as the run_prefix.
Expand Down