You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting the trinity_kmer_length option in the config file leads to this error from trinity: ERROR, don't recognize parameter: --KMER_SIZE
Based on this, I believe that --KMER_SIZE should be changed to --__KMER_SIZE on line 1093 of tracer_func.py.
When running Trinity standalone instead of Tracer, using --__KMER_SIZE instead of --KMER_SIZE works.
Thank you!
The text was updated successfully, but these errors were encountered:
Yes, this has obviously been changed in an update to Trinity. You can either:
1. Install the last version of Trinity that accepted the old argument
or
2. Edit the tracer code so that it passes the new argument to the current version of Trinity.
Cheers,
Mike
On 25 Sep 2020, at 21:46, HumzaHemani ***@***.***> wrote:
Hi,
Setting the trinity_kmer_length option in the config file leads to this error from trinity:
ERROR, don't recognize parameter: --KMER_SIZE
Based on this, I believe that --KMER_SIZE should be changed to --__KMER_SIZE on line 1093 of tracer_func.py.
When running Trinity standalone instead of Tracer, using --__KMER_SIZE instead of --KMER_SIZE works.
Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Hi,
Setting the trinity_kmer_length option in the config file leads to this error from trinity:
ERROR, don't recognize parameter: --KMER_SIZE
Based on this, I believe that
--KMER_SIZE
should be changed to--__KMER_SIZE
on line 1093 of tracer_func.py.When running Trinity standalone instead of Tracer, using --__KMER_SIZE instead of --KMER_SIZE works.
Thank you!
The text was updated successfully, but these errors were encountered: