Thanks for the update, I've started using it in spades for a number of datasets and its great.
In one project, I have a total of around 770 million 100nt-long PE reads across 7 lanes. Unfortunately I am quite limited in computing capacity (only 16Gb RAM - yes I have been critiqued before in other posts to get better specs, but we all have our circumstances
) till we get access to a better one, so as expected an analyses pretty much stopped at the stage of reading the unmapped reads into memory. I currently just want to extend a small number of separate contigs as much as possible, and it would be great to consider all reads at once. 1. I'm just wondering if it is possible to overcome the memory limitation - is the Premium version using a different way to store/access the data?
2. Should I split my inputs into smaller libraries - does sspace free up memory after reading a library before going on to the next (but i think not)?
3. Or should I carry out separate analyses of sspace - but i'm afraid of losing possibilities to extend contigs by not considering all data at once.
Sorry if the questions are naive.
Cheers,
kennels
umper i'm familiar with, it is fixed in the premium version, but i'll fix it in the new basic version too.
Leave a comment: