Skip to content
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.

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

Are Illumina reads still supported? #17

Open
osowiecki opened this issue Feb 19, 2020 · 7 comments
Open

Are Illumina reads still supported? #17

osowiecki opened this issue Feb 19, 2020 · 7 comments

Comments

@osowiecki
Copy link

osowiecki commented Feb 19, 2020

What about mate-pair illumina reads?
How do polish my pacbio restults?

@osowiecki osowiecki changed the title Are PacBio reads still supported? Are Illumina reads still supported? Feb 19, 2020
@rvaser
Copy link
Collaborator

rvaser commented Feb 19, 2020

Hello,
Illumina reads for polishing (as in Ra) are not supported for now, as the underlying mapper has not yet been tested for mapping Illumina reads to the assembly. You can always use minimap2 + racon as a separate step after Raven assembly.

Best regards,
Robert

@osowiecki
Copy link
Author

Assuming I want to do exactly that, probably based on that thread
isovic/racon#146
Should I set polishing rounds to 0 in raven or will it only help my pacbio assembly to keep "-p" value on default "2"?

@rvaser
Copy link
Collaborator

rvaser commented Feb 19, 2020

Use raven in default mode (so two iterations of PacBio polishing) and then follow the instructions for Illumina polishing as in the thread you listed :)

@osowiecki
Copy link
Author

Thank you. I'm using quality trimmed illumina reads paired end + mate pairs.
Do you think using make pair reads with large insert sizes (smushed together with PE reads) are useful for polishing? How will racon treat reads with 11k insert size?

@rvaser
Copy link
Collaborator

rvaser commented Feb 19, 2020

Currently racon does not use the insert information, it treats both reads of a pair as single end reads. Thus I think nothing will happen if you merge together the PE and MP reads.

@osowiecki
Copy link
Author

osowiecki commented Feb 19, 2020

That clears things up.

As for the racon input. Does it really matter if R1 and R2 reads are put right next to each other in the shuffled fasta file?
The proposed "shuffle_pairs_fastq.py" produces reads with /11 as their name. Shouldn't pairs be named /1 and /2 or it doesn't really matter?

FCC4U5HACXX:1:1101:6258:2807#ACTTGAAT/11
ACGCGCTTCCCGGGAATGATCCCATGAAAAGGCGTCGCGCCTGCCCGGACCGTGGACAGATCGATCCGCAGGAGCCCGAGGGTCTCGGCGTAGATGAT
FCC4U5HACXX:1:1101:6449:2827#ACTTGAAT/11
GTTAGGCTGCCTCCAGTAAGACCCGCTAAAACGCACTGTCCGGTAAATATAGCGGATGCTATGCTCTTCTATGCCTCCAGCAACAACCGGTAAAACGT

[EDIT]

it treats both reads of a pair as single end reads
This is my answer, right?

@rvaser
Copy link
Collaborator

rvaser commented Feb 19, 2020

It does not matter, you can shuffle them as you like. All reads just need to have unique identifiers up to the first space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants