<p dir="ltr">Thank you all for your responses.</p>
<p dir="ltr">Regards,<br>
/SB</p>
<br><div class="gmail_quote"><div dir="ltr">On Mon, 8 May 2017, 18:50 Jiang, Ning, <<a href="mailto:jiangn@msu.edu">jiangn@msu.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div id="m_8536000270490088673divtagdefaultwrapper" style="color:rgb(0,0,0);font-family:Calibri,Arial,Helvetica,sans-serif,'EmojiFont','Apple Color Emoji','Segoe UI Emoji',NotoColorEmoji,'Segoe UI Symbol','Android Emoji',EmojiSymbols;font-size:12pt" dir="ltr">
<p>Hi Salim,</p>
<p><br>
</p>
<p>I am sorry to learn about the issues. it depends on the quality of your genome assembly for how many intact LTR elements you would get; however, 16 seems too low to me.
</p>
<p><br>
</p>
<p>The inner and LTR sequence file should NOT be empty. Some times the issue could be due to that the initial sequence name is long and complicated. If that's the case for your sequences, you might want to simplify your sequence name (only including letters
and numbers) and try again. </p>
<p><br>
</p>
<p>We are working on an automatic pipeline for LTR collection, if everything goes smoothly, it should be available in two to three months.
</p>
<p><br>
</p>
<p>Best wishes,</p>
<p><br>
</p>
<p>Ning <br>
</p>
<div style="color:rgb(0,0,0)">
<div>
<hr style="width:98%;display:inline-block">
<div id="m_8536000270490088673x_divRplyFwdMsg" dir="ltr"><font color="#000000" face="Calibri, sans-serif" style="font-size:11pt"><b>From:</b> Campbell, Michael <<a href="mailto:mcampbel@cshl.edu" target="_blank">mcampbel@cshl.edu</a>><br>
<b>Sent:</b> Sunday, May 7, 2017 9:24 PM<br>
<b>To:</b> Carson Holt<br>
<b>Cc:</b> Salim Bougouffa; <a href="mailto:maker-devel@yandell-lab.org" target="_blank">maker-devel@yandell-lab.org</a> List; Jiang, Ning<br>
<b>Subject:</b> Re: [maker-devel] advanced repeat masking library constructions & rna-seq assembly choices</font>
<div> </div>
</div>
</div></div></div></div><div dir="ltr"><div id="m_8536000270490088673divtagdefaultwrapper" style="color:rgb(0,0,0);font-family:Calibri,Arial,Helvetica,sans-serif,'EmojiFont','Apple Color Emoji','Segoe UI Emoji',NotoColorEmoji,'Segoe UI Symbol','Android Emoji',EmojiSymbols;font-size:12pt" dir="ltr"><div style="color:rgb(0,0,0)">
<font size="2"><span style="font-size:10pt">
<div class="m_8536000270490088673PlainText">Hi SB,<br>
<br>
I’ve added Ning Jaing to this email. She has put great effort into updating this protocol recently and will be able to address your questions better than I can.<br>
<br>
Ning, would you mind helping out with this?<br>
<br>
Thanks,<br>
Mike<br>
<br>
On May 7, 2017, at 9:17 PM, Carson Holt <<a href="mailto:carsonhh@gmail.com" target="_blank">carsonhh@gmail.com</a><mailto:<a href="mailto:carsonhh@gmail.com" target="_blank">carsonhh@gmail.com</a>>> wrote:<br>
<br>
Michael can you answer the second question (Michael wrote the protocol, so I CC’d him).<br>
<br>
With respect to the first question. Expression level is not necessarily relevant to the annotation process (so no MAKER does not look at read coverage). Instead we use the transcript assemblies to identify introns via splice aware alignment (yes it is the introns
and not the exons we care about). Trinity has a nice option called jaccard_clip which avoids false merging of neighboring transcripts (mostly occurs in fungi where UTR can overlap). Merging of transcripts will cause extra introns to be assigned as hints as
well as potential overextension of UTR during final polishing steps. The jaccard_clip option is the main reason we recommend Trinity. If Stringtie has a similar option, then it can be used as well.<br>
<br>
Thanks,<br>
Carson<br>
<br>
<br>
<br>
On May 4, 2017, at 12:37 AM, Salim Bougouffa <<a href="mailto:mjfi2sb3@gmail.com" target="_blank">mjfi2sb3@gmail.com</a><mailto:<a href="mailto:mjfi2sb3@gmail.com" target="_blank">mjfi2sb3@gmail.com</a>>> wrote:<br>
<br>
Hi,<br>
<br>
I am attempting to annotate a plant genome. I have a couple of questions:<br>
<br>
1) RNA-seq assembly<br>
a) I assembled my RNA-seq data using Trinity and StringTie. The two produce drastically different numbers. When I compare the two assemblies for each sample using TransRate, StringTie produces a higher score. for most of the assemblies. I see in all of the
threads that you recommend Trinity but doesn't trinity produce way too many transcripts (even after chucking out the "bad" ones using transrate).<br>
b) During hint creation in MAKER, does it take into account that different transcripts have different read coverage (expression levels). I guess my question is should I filter transcripts that have a small read coverage.<br>
<br>
2) Repeat Masking<br>
I am following the advanced repeat library construction tutorial (<a id="m_8536000270490088673LPlnk685979" href="http://weatherby.genetics.utah.edu/MAKER/wiki/index.php/Repeat_Library_Construction-Advanced" target="_blank">http://weatherby.genetics.utah.edu/MAKER/wiki/index.php/Repeat_Library_Construction-Advanced</a>).
The initial steps find 15 sequences for the LTR and 159 for MITE. But, when I get to the perl DIR_CRL/CRL_Step4.pl step, both output files (Inner_Seq_For_BLAST.fasta, lLTRs_Seq_For_BLAST.fasta) are empty.<br>
<br>
a) are these numbers normal because I was expecting a lot more than 16 for the LTR?<br>
b) I don't get any errors when I run CRL_Step4.pl yet no output. What's going on?!<br>
<br>
Many thanks,<br>
/SB<br>
--<br>
<br>
____________________________<br>
Sent from Inbox Mobile<br>
<br>
_______________________________________________<br>
maker-devel mailing list<br>
<a href="mailto:maker-devel@box290.bluehost.com" target="_blank">maker-devel@box290.bluehost.com</a><mailto:<a href="mailto:maker-devel@box290.bluehost.com" target="_blank">maker-devel@box290.bluehost.com</a>><br>
<a id="m_8536000270490088673LPlnk166035" href="http://box290.bluehost.com/mailman/listinfo/maker-devel_yandell-lab.org" target="_blank">http://box290.bluehost.com/mailman/listinfo/maker-devel_yandell-lab.org</a><br>
<br>
_______________________________________________<br>
maker-devel mailing list<br>
<a href="mailto:maker-devel@box290.bluehost.com" target="_blank">maker-devel@box290.bluehost.com</a><mailto:<a href="mailto:maker-devel@box290.bluehost.com" target="_blank">maker-devel@box290.bluehost.com</a>><br>
<a id="m_8536000270490088673LPlnk147503" href="http://box290.bluehost.com/mailman/listinfo/maker-devel_yandell-lab.org" target="_blank">http://box290.bluehost.com/mailman/listinfo/maker-devel_yandell-lab.org</a><br>
<br>
</div>
</span></font></div></div></div></blockquote></div>