-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
calculate the LTR insertion time by EDTA #271
Comments
Hello @tinyfallen, This is a good suggestion. I will add -u in the next release. Shujun |
Hi Shujun, Like @tinyfallen having this flag in EDTA would be fantastic - cant wait for the next release :) Many thanks Chris |
HI Chris, Thank you for reminding me. Yes, this is on my to-do list and I will try to get it done soon. Best, |
Thanks Shujun,
Looking forward to the update in due course. In the meantime Is there a possibility of using one of the EDTA intermediate files to pop into LTR-retriever or would I be best just running the LTR-retriever pipeline independantly?
Kind Regards
Chris
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Shujun Ou ***@***.***>
Sent: Thursday, June 16, 2022 6:28:52 PM
To: oushujun/EDTA ***@***.***>
Cc: Winefield, Christopher ***@***.***>; Comment ***@***.***>
Subject: Re: [oushujun/EDTA] calculate the LTR insertion time by EDTA (Issue #271)
Caution: This email originated from outside our organisation. Do not click links or open attachments unless you recognize the sender and know the content is safe.
HI Chris,
Thank you for reminding me. Yes, this is on my to-do list and I will try to get it done soon.
Best,
Shujun
—
Reply to this email directly, view it on GitHub<#271 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABYMLSXQJUVLGM5QYJAPGEDVPLCR5ANCNFSM5XJYQKSQ>.
You are receiving this because you commented.Message ID: ***@***.***>
________________________________
"The contents of this e-mail (including any attachments) may be confidential and/or subject to copyright. Any unauthorised use, distribution, or copying of the contents is expressly prohibited. If you have received this e-mail in error, please advise the sender by return e-mail or telephone and then delete this e-mail together with all attachments from your system."
|
Hi Chris, You can run EDTA_raw.pl with the Shujun |
This parameter ( |
Hi Shujun,
Many thanks for that addition - I will let you know how it goes in due course.
Kind Regards
Chris
Chris Winefield
Associate Professor in Plant Genomics and Molecular Biology
Department of Wine Food and Molecular Biosciences
Faculty of Agriculture and Life Sciences
RFH, room 062
Engineering Drive
P O Box 85084
Lincoln University
Lincoln 7647
Christchurch
New Zealand
p +64 3 4230630 | m +64 021 0238 4476
e ***@***.*** | w www.lincoln.ac.nz<http://www.lincoln.ac.nz/>
Lincoln University, Te Whare Wānaka o Aoraki
New Zealand's Specialist Land-Based University
[cid:62da8c21-dff1-49b8-ab4d-200c5815e2a2]
The NZ Plant <http://www.mobilekiwi.org/>
Transposon <http://www.mobilekiwi.org/>
Team<http://www.mobilekiwi.org/>
…________________________________
From: Shujun Ou ***@***.***>
Sent: 23 June 2022 12:23 PM
To: oushujun/EDTA ***@***.***>
Cc: Winefield, Christopher ***@***.***>; Comment ***@***.***>
Subject: Re: [oushujun/EDTA] calculate the LTR insertion time by EDTA (Issue #271)
Caution: This email originated from outside our organisation. Do not click links or open attachments unless you recognize the sender and know the content is safe.
This parameter (--u) is added to the latest repo and release. Please allow a couple of days to reflect on the conda recepie. Please let me know if you have more questions.
—
Reply to this email directly, view it on GitHub<#271 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABYMLSVWWNI3VPU3ZVXAYUDVQOVA3ANCNFSM5XJYQKSQ>.
You are receiving this because you commented.Message ID: ***@***.***>
________________________________
"The contents of this e-mail (including any attachments) may be confidential and/or subject to copyright. Any unauthorised use, distribution, or copying of the contents is expressly prohibited. If you have received this e-mail in error, please advise the sender by return e-mail or telephone and then delete this e-mail together with all attachments from your system."
|
Dear teacher, That's so fantastic! Actually, I do have met some problems about the classification of TEs recently. I found almost half of the final library labelled Unknown which seemed to come from the RepeatModeler steps. So I separately fed the lib to TEsorter and deepTE to perform classification, in which some sequence's classification may be contradictory with each other or the original result of EDTA. Following comes my questions:
Maybe I should open a new issue to consult the questions, or you could just give me some brief suggestions, thanks! Best~ |
Dear teacher, I saw the discussion in issue98 and found the genome.mod.EDTA.TEanno.split.gff3, thus I could conduct analysis using this file to exclude overlaps. Descriptions in detail about the outputs could be added into wiki or README if you would like to. And I still have the interest to know how it accomplished and whether it is necessary to further classify the unknowns. Wish to see a more powerful and comprehensive EDTA! Thanks for your excellent work! |
Hi @tinyfallen, Thank you for your suggestions. I have added the following Q&As to the wiki: https://github.com/oushujun/EDTA/wiki/Making-sense-of-EDTA-usage-and-outputs---Q&A For unknown TEs, it's always recommended to classify them as much and accurately as possible, but this is challenging. You may use TEsorter, deepTE, or others to do so, and use Best, |
Many thanks dear teacher! Best~ |
Hi dear developer,
The LTR_retriever accepts the -u parameter for LTR insertion time calculation while the EDTA not. The user have to recalculate by themselves. For my own, I'm afraid I may make mistakes in the calculation steps. So could you please do a favor to add the -u parameter to EDTA in the next update?
Thanks a lot !
The text was updated successfully, but these errors were encountered: