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

Need to adapt kmer size values ? #1105

Open
NJeanray opened this issue Dec 15, 2021 · 3 comments
Open

Need to adapt kmer size values ? #1105

NJeanray opened this issue Dec 15, 2021 · 3 comments

Comments

@NJeanray
Copy link

Hello Trinity Team,

I'm currently triying to identify alternative transcripts from RNA-Seq Homo Sapiens samples.
I ran Trinity successfully on each of my samples :

Trinity --seqType fq --left sample_R1.fq.gz --right sample_R2.fq.gz --max_memory 20G --CPU 24 --KMER_SIZE 32 --output /trinity_output/

I performed a check of my assembly quality doing an alignment of my initial reads againt their corresponding assembly, and unfortunately, this not really good :

image

Also, I had a look at the generated de Bruijn graphes and it seems that I get a lot of disconnected nodes. So, I guess this is coming from the length of kmers which are too small. I read that Trinity uses by default a size of 25 and cannot exceed 32.

What would you advice ? The range of my reads lenght is about 36-76 nucleotides (short reads).

What would you do ?

Thanks in advance !

@brianjohnhaas
Copy link
Member

brianjohnhaas commented Dec 15, 2021 via email

@NJeanray
Copy link
Author

Hi Brian,

Excuse-me, I made a mistake writting the command line : I did not set the parameter regarding the kmer size. So I guess Trinity won't give me better results even if I force this parameter to a given value ?

@brianjohnhaas
Copy link
Member

brianjohnhaas commented Dec 15, 2021 via email

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