<div dir="ltr"><div>Dear Carson:<br><br></div>Thanks again for all your previous help. I am still trying to identify pseudo genes. For me, I have two goals to identify pseudo genes. <br>(1) Check which predicted protein coding genes are in fact pseudo genes (especially I want to check genes belong to gene families, which are found under expansion in our analyzed geome). <br>(2) Identify pseudo genes in the intergentic regions. <br>But the link "<a href="http://shiulab.plantbiology.msu.edu/index.php/Protocol:Pseudogene">http://shiulab.plantbiology.msu.edu/index.php/Protocol:Pseudogene</a>" only describe Identification of pseudo genes in the intergentic regions. I wonder whether I can simple follow the pipeline and run it on the whole genome, so I can achieve my two goals above. Or do I need to do some adjustment of the pipeline?<br><br><div>At beginning, I though the pipeline is only useful to identify pseudo genes in the intergentic regions, but in the following paper, they mentioned the pipeline was applied to the whole genome. So I think maybe I can also do this, but not sure whether I can simply run the same pipeline in the following link on whole genome ("<a href="http://shiulab.plantbiology.msu.edu/index.php/Protocol:Pseudogene">http://shiulab.plantbiology.msu.edu/index.php/Protocol:Pseudogene</a>"). <br></div><div><br>In the paper "MAKER-P: A Tool Kit for the Rapid Creation,Management, and Quality Control of Plant Genome Annotations". It saids "If the analysis pipeline is applied to the whole genome, 2.5% and 0.6% of currently annotated proteincoding genes are identified as pseudogenes due to the presence of misidentified stops and frame shifts, respectively, indicating that the false-positive rate of our pipeline is 3.1%."</div><div><br></div><div>Many thanks for your help.</div><div><br></div><div>Best</div><div>Quanwei<br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-08-01 9:32 GMT-04:00 Quanwei Zhang <span dir="ltr"><<a href="mailto:qwzhang0601@gmail.com" target="_blank">qwzhang0601@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi Carson:<br><br>I took a look at the description
about the pipe line of pseudogene identification. In my understanding it
will use the annotated (predicted by Maker2) protein coding genes as
input (i.e., query sequences), search in the intergenic spaces (so
annotated genes will not be checked) and find the regions where show
certain level of similarity to the annotated genes.<br><br></div>If my
understanding is correct, I think it is not what I want to do get. Based
on the annotated coding genes from Maker2, we found some genes are
under expansion in the new species. We want to check and make sure all
the gene copies in the expanded gene family really function (to make
sure they are not pseudogenes).<br><br></div>Do you think the pseudogene
identification pipe line of Maker2 can be helpful for my goal? Or do
you have any suggestions on this?<br><br></div><div>Many thanks<br><br></div>Best<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888">Quanwei</font></span></div><div class="gmail_extra"><br><div class="gmail_quote"><span class="">2017-07-31 19:54 GMT-04:00 Carson Holt <span dir="ltr"><<a href="mailto:carsonhh@gmail.com" target="_blank">carsonhh@gmail.com</a>></span>:<br></span><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">The MAKER-P fork was merged back into standard MAKER with version 2.29 (roughly 3 years ago - a separate download no longer exists). This is because MAKER-P’s functionality is almost entirely in accessory scripts and written protocols. The …/maker/bin/maker called by both MAKER2 and MAKER-P is actually the same script. So no need to rerun, because if you are using version 2.29 or later, you already ran it.<br><div><br></div><div>Pseudogene calling is therefore handled by accessory scripts and protocols you can find here —> <a href="http://shiulab.plantbiology.msu.edu/wiki/index.php/Protocol:Pseudogene" target="_blank">http://shiulab.plantbiology<wbr>.msu.edu/wiki/index.php/<wbr>Protocol:Pseudogene</a></div><div><br></div><div>The other MAKER-P protocols can be found here —> <a href="http://www.yandell-lab.org/software/maker-p.html" target="_blank">http://www.yandell-lab.org/<wbr>software/maker-p.html</a> </div><div><br></div><div>--Carson</div><div><br></div><div><br></div><div><br><div><blockquote type="cite"><div><div class="m_-7328894762670251025h5"><div>On Jul 31, 2017, at 5:02 PM, Quanwei Zhang <<a href="mailto:qwzhang0601@gmail.com" target="_blank">qwzhang0601@gmail.com</a>> wrote:</div><br class="m_-7328894762670251025m_-6056823154815264704Apple-interchange-newline"></div></div><div><div><div class="m_-7328894762670251025h5"><div dir="ltr"><div><div><div><div><div><div>Hello:<br><br></div>We used Maker2 to annotate a new rodent genome. By using the annotated genes we did gene family expansion analysis, and found several gene families under expansion in the new rodent genome. But we want to check whether some annotated genes are Pseudogenes, which lead to the expansion. Do you have any suggestions on this?<br><br></div>We found the Maker-P can annotate Pseudogene, but we are not sure whether it is worth to repeat our annotation with Maker-P. Besides, we are not sure whether the default parameters of Maker-P are good for a rodent species. What's more, in my understanding the Maker-P will identify Pseudogenes in the intergenic spaces (which I think the annotated coding genes will be not be tested and checked).<br><br></div>Do you have any suggestions to solve our problem? We do not want to identify Pseudogene on the genome wide, but only want to check those genes showing expansion (to make sure all those gene copies really function).<br><br></div>Many thanks<br><br></div>Best<br></div>Quanwei<br><div><div><div><div><br></div></div></div></div></div></div></div>
______________________________<wbr>_________________<br>maker-devel mailing list<br><a href="mailto:maker-devel@box290.bluehost.com" target="_blank">maker-devel@box290.bluehost.co<wbr>m</a><br><a href="http://box290.bluehost.com/mailman/listinfo/maker-devel_yandell-lab.org" target="_blank">http://box290.bluehost.com/mai<wbr>lman/listinfo/maker-devel_yand<wbr>ell-lab.org</a><br></div></blockquote></div><br></div></div></blockquote></div></div></div><br></div>
</blockquote></div><br></div>