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
For example, when I ran my 3.0GB genome sequence with must and mitetracker, using only 10 and 4 threads respectively, it took 50 hours, but no work was done.
While the classical work will start, after they run with must and mitetracker, the research work will take more and more time with just 4 threads, which is shown in the command line while running.
So, can you come up with some sort of solution to this?
Looking forward to your reply
Sincerely yours
The text was updated successfully, but these errors were encountered:
Der Djangodu,
I was just wrapping these tools mitetracker and must in a pipeline so people can easily use it without having the pain to install them by themselves (as there was few to none manuals), but I didnt develop these tools and I am not their author.
If some tools take long, you might consider not using all of them.
Best, Kevin
For example, when I ran my 3.0GB genome sequence with must and mitetracker, using only 10 and 4 threads respectively, it took 50 hours, but no work was done.
While the classical work will start, after they run with must and mitetracker, the research work will take more and more time with just 4 threads, which is shown in the command line while running.
So, can you come up with some sort of solution to this?
Looking forward to your reply
Sincerely yours
The text was updated successfully, but these errors were encountered: