Conversation
|
Hi @CaroB-M, thanks for sending the EAR of Lyristes plebejus. |
|
ok |
|
|
Hi @DomAbsolon, do you agree to review this assembly? |
|
@DomAbsolon Time is out! I will look for the next reviewer on the list :) |
|
|
Hi @gitcruz, do you agree to review this assembly? |
|
Yes
El vie, 16 ene 2026, 22:22, erga-ear-bot[bot] ***@***.***>
escribió:
… *erga-ear-bot[bot]* left a comment (ERGA-consortium/EARs#318)
<#318 (comment)>
Hi @gitcruz <https://github.com/gitcruz>, do you agree to review this
assembly?
Please reply to this message only with *Yes* or *No* by 23-Jan-2026 at
02:20 CET
—
Reply to this email directly, view it on GitHub
<#318 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB34KVK74AW4WAGFVOOTNHL4HFJAZAVCNFSM6AAAAACRMXN7CCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONRRHA2TIOBTGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Thanks for agreeing! |
|
Ping @tbrown91, |
|
Hi @CaroB-M This is looking really nice for a big genome. The only obvious thing I would change is: The X chromosome is a little more difficult. I can see for example what looks like missing sequence at ~154Mb and 179Mb. I don't think these are retained haplotypic sequences. |
|
Hi @CaroB-M, I finally took crack on it. Excellent big genome. As @tbrown91 my only worries concern the X chromosome. Personally, I find hard to order and orient all the "blocks" in this chromosome and I am missing the telomere extension (did you try to generate it?). WRT Tom's comment about the haplotigs, I was looking at the coverage in those regions. It's actually very high, rather than half coverage: so for me either are real tandem duplicates or they come from the Y chromosome...could that be the case? Coming back to the whole X, I would group the regions that contact more clearly and have similar coverage together and tag the rest as unloc...as I said, no clue on the orientation:
Please let me know what you think. Minor comment: the TAPAs plot is from the rpecurated assembly right? reading the notes I understood that the reviewed assembly was contaminated. Question: Is "Context" a contaminant removal tool or a strategy? If it is a tool, could you post the link here? Thanks. |
|
Another thought after the morning coffee: why don't you produce a map for just the X chromosome? This will drop the resolution from 68K/texel to 10-15K/texel for a 1Gb chromosome. With more resolution meaybe we could tease out haplotigs from tandem repeats and be more sure of the orientation zooming in the boundaries of the different sections. I know that we are bit short of time because of the deadlines but if you still have the bams it should be relatively quick using PretextMap and the FilterInclude option: https://github.com/sanger-tol/PretextMap?tab=readme-ov-file#new-option-version-01 What do you two think? Cheers, |
|
Hello @gitcruz |
|
Thanks @CaroB-M Hope you get the mappings done fast so we can look at the X in more detail. The rest of the assembly, looks excellent to me. Best, |
|
Hi @gitcruz |
|
Hi @CaroB-M I finally have a look at the map. It does not look that bad but I'd like you to add the coverage extension. Do you still have the bam of Hifi mapped against the whole assembly? It will really help to distinguish some false duplications Thanks |
|
@CaroB-M are you able to get the coverage track on this map? It's really difficult to tell real duplication/repeat arrays from potential retained haplotypes. I do appreciate the work done and think it is looking much better |
|
Hello @tbrown91 and @gitcruz , I have added the coverage track to the map. You can use the same link to download it |
|
I actually think that most of them are artifacts of the contigging
(specially those appearing in adjacent contigs). Often the show coverage
peaks around them and If I'm right is due to the fact that they share the
same secondary alignments. My interpretation is that they have
been contigged twice. Also there are some contigs with a repeat structure
that contacts strongly in more than one place ***@***.***,605-387,516) that I
think should be unplaced.
I'd like to prune the map a bit and share a savestate with you two. Please
give me some time, I'll try to share a savestate asap.
Cheers.
…On Thu, 12 Feb 2026 at 15:59, Tom Brown ***@***.***> wrote:
*tbrown91* left a comment (ERGA-consortium/EARs#318)
<#318 (comment)>
Thanks @CaroB-M <https://github.com/CaroB-M> Given this, I am leaning
towards believing that most of these duplications/repeats are genuine.
@gitcruz <https://github.com/gitcruz> see what you think
—
Reply to this email directly, view it on GitHub
<#318 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB34KVN4BNOJ3B7Q3PQ2SWT4LSINDAVCNFSM6AAAAACRMXN7CCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQOJRGQ2TANJWGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hello again, I have been trying to clean up a bit the map, but whenever I try to break a contig PretextViewAI v1.0.5 crashes. I triead to clear the cache and started all over, but same problem. It seems to be an issue with single large chromosomes' maps...Tyler had lot of problems with wpGesJame1 too. Anyway, you can have a look at savestate_3, just moved that contig as unloc, and after that the map looks good to me there. As that contig contacts other repeat, I doubt it really fits in. My following edit was intended to be this one, I think the sequence after gap@123,013Kb is a FalseDuplicate that was contigged twice:
IMO these are repeat structures that have been alternatively assembled in different contigs, and should be removed. If you @CaroB-M want to try, let me know if PretextView works for you and which version you use. Otherwise, If we are uncapable to clean it from "FalseDuplicates" I'll aprove it as at least the overall order seems more or less right. Anyway let me know what you guys think. Cheers, |
|
Hello @gitcruz |
|
oops sorry, i put them in the wrong folder. Could you try here and let me know if it works? |
|
Hello @gitcruz |
|
Hi @CaroB-M
Hold your horses, no need to regenerate a new EAR. Just produce the new
fasta and upload it to ENA.
I think that there are many false dups in this chromosome, but we cannot
remove them with PretextViewAI 1.0.5 I'll follow up with this issue in
github.
So I will approve immediately, and If @tbrown91
can merge it that would be lovely.
Great job @CaroB-M sorry for delaying this so much. Just thought we could
improve the X chromosome a bit.
Have a nice weekend
Fernando
…On Fri, 13 Feb 2026 at 11:10, CaroB-M ***@***.***> wrote:
*CaroB-M* left a comment (ERGA-consortium/EARs#318)
<#318 (comment)>
Hello @gitcruz <https://github.com/gitcruz>
I have downloaded your savestate 👍 and I have the same issue with
PretextView
I will transfer your change to the complete map and regenerate a new EAR
Best
—
Reply to this email directly, view it on GitHub
<#318 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB34KVLM4YAAJTKAW7SMGID4LWPI5AVCNFSM6AAAAACRMXN7CCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQOJWGI3DENZWHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Thanks @gitcruz for the review. Congrats on the assembly @CaroB-M! After @tbrown91 confirmation, you can start with the assembly submission to save time. |
|
Thanks @gitcruz |
|
Thanks both |



Assembly review request