Hi Martin, Wow, thanks for the super speedy response!!! Have run a couple of the repeats through BLAST and it seems some match to rRNA. Am also seeing a lot of polyA-tails in there too. I ran all of the reads through seqclean and assumed that this would fix the above. In hindsight, I probably should have been a bit more ruthless. Any advice on how to clean up the dataset a bit more or should I just drop the reads? Be kind, I'm a transcriptome assembling newbie! ;) Thanks in advance! Victoria -----Original Message----- From: mira_talk-bounce@xxxxxxxxxxxxx [mailto:mira_talk-bounce@xxxxxxxxxxxxx] On Behalf Of Martin MOKREJŠ Sent: 25 June 2014 17:02 To: mira_talk@xxxxxxxxxxxxx Subject: [mira_talk] Re: MIRA run failing due to megahubs Hi Victoria, you have to look into the reads listed in *megahubs* file placed in MergedAssembly/MergedAssembly_d_tmp/ subdirectory. Most likely you have too many polyA-tails in your data or rRNA contamination or unremoved adapters/MIDs. Or simple crap like [CA]n repeats causes that (sometimes they are authentic, sometimes not, in either case hard to be useful). Provided it is so few reads, just drop them from your input dataset. Transcriptomic datasets need proper adapter removal and trimming ... see below my signature. ;) Or maybe you get back to me later once you get 40kb long contigs in your assemblies ... :)) Martin Offord, Victoria wrote: > Hi, > > My MIRA run on a parasite transcriptome keeps ending with: > > You have 0.1052271917% of your reads as megahubs. > You have set a maximum allowed ratio of: 0.0000000000 -- Martin Mokrejs, Ph.D. 454 / IonTorrent / Evrogen MINT / Clontech SMART adapter/artifact removal (... too many protocols to name here) http://www.bioinformatics.cz/software/supported-protocols/ -- You have received this mail because you are subscribed to the mira_talk mailing list. For information on how to subscribe or unsubscribe, please visit http://www.chevreux.org/mira_mailinglists.html [RVC Logo - link to RVC Website]<http://www.rvc.ac.uk> [Twitter icon - link to RVC (Official) Twitter] <http://twitter.com/RoyalVetCollege> [Facebook icon - link to RVC (Official) Facebook] <http://www.facebook.com/theRVC> [YouTube icon - link to RVC YouTube] <http://www.youtube.com/user/RoyalVetsLondon?feature=mhee> [Pinterest icon - link to RVC Pinterest] <http://pinterest.com/royalvetcollege/> [Instagram icon - link to RVC Instagram] <http://instagram.com/royalvetcollege> This message, together with any attachments, is intended for the stated addressee(s) only and may contain privileged or confidential information. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Royal Veterinary College (RVC). If you are not the intended recipient, please notify the sender and be advised that you have received this message in error and that any use, dissemination, forwarding, printing, or copying is strictly prohibited. Unless stated expressly in this email, this email does not create, form part of, or vary any contractual or unilateral obligation. Email communication cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, amended, lost, destroyed, incomplete or contain viruses. Therefore, we do not accept liability for any such matters or their consequences. Communication with us by email will be taken as acceptance of the risks inherent in doing so. b��j��yǢ��m�+&j)[yƮ�쨹���r��y�h�����jY&j)b� b��h�)ߢ���*'�xh��,���&ޢ�����r��z�^jǯ�ȭ��i��0��^���Ɗ��h�jf��)��+-�f