Skip to content

Conversation

@ldemirdj
Copy link
Collaborator

@ldemirdj ldemirdj commented Sep 2, 2025

Assembly review request

  • ToLID: ddHypElod1
  • Species: Hypericum elodes
  • Project: ERGA-BGE
  • Affiliation: Genoscope

@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Sep 2, 2025

Hi @ldemirdj, thanks for sending the EAR of Hypericum elodes.
I added the corresponding tag to the PR and will contact a supervisor and a reviewer ASAP.

@erga-ear-bot erga-ear-bot bot added the ERGA-BGE label Sep 2, 2025
@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Sep 2, 2025

Hi @tbrown91, do you agree to supervise this assembly?
Please reply to this message only with OK to give acknowledge.

@tbrown91
Copy link
Collaborator

tbrown91 commented Sep 3, 2025

ok

@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Sep 3, 2025

*****
EAR Reviewer Selection Process
Date: 2025-09-03 12:45

All Eligible Candidates:

Github ID | Full Name             | Institution | Total Reviews | Last Review | Active | Busy | Calling Score | Adjusted Score
------------------------------------------------------------------------------------------------------------------------------
jesgomez  | Jessica Gomez Garrido | CNAG        | 7             | 2025-08-07  | Y      | N    | 1021          | 1071          

Selected reviewer: Jessica Gomez Garrido (jesgomez)
The decision was based on:
- different institution ('CNAG')
- active ('Y')
- not busy ('N')
- highest adjusted calling score in this particular selection (1071)

@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Sep 3, 2025

Hi @jesgomez, do you agree to review this assembly?
Please reply to this message only with Yes or No by 09-Sep-2025 at 18:45 CET

@jesgomez
Copy link
Collaborator

jesgomez commented Sep 5, 2025

Yes

@erga-ear-bot erga-ear-bot bot requested a review from jesgomez September 5, 2025 10:52
@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Sep 5, 2025

Thanks for agreeing!
I appointed you as the EAR reviewer.
I will track this as one of your Working PRs until you finish this review.
Please check the Wiki if you need to refresh something. (and remember that you must download the EAR PDF to be able to click on the link to the contact map file!)
Contact the PR assignee for any issues.

@tbrown91
Copy link
Collaborator

tbrown91 commented Sep 5, 2025

Hi @ldemirdj

Let's do what we can to make this as good as it can without Hi-C. There are quite a few chromosome-level assemblies from
Hypericum, although with differing numbers of chromosomes. I wonder if a simple mapping between the assemblies could highlight any remaining haplotigs. The duplication rate appears to be quite high, so it would be nice to get rid of some if possible

Hypericum genomes

@auryjm
Copy link
Collaborator

auryjm commented Sep 5, 2025

Hi @tbrown91 and @ldemirdj,

I’m pasting below an exchange we had with the sample ambassador about the Hypericum genome assembly:
"[...] several Hypericum assemblies are already available, with assembly sizes ranging from 338 Mb to 1,541 Mb. This variation might be due to different ploidy levels. Similarly, the number of chromosomes in this genus appears to vary significantly, from 9 to 20 => https://www.ncbi.nlm.nih.gov/datasets/genome/?taxon=55962&assembly_level=2:3
Given these observations, I would expect that the assembly size is correct, potentially due to a different ploidy level similar to that observed in H. androsaemum, H. pulchrum, H. hircinum, and H. hirsutum.[...]"

Please note that, for example, Hypericum perforatum also shows a high rate of duplicated BUSCOs, which may indicate polyploidization events. Be careful when removing suggested allelic contigs or regions, as they might actually correspond to polyploidization events!

Jean-Marc

@diegomics
Copy link
Collaborator

Hi all, I just remember that you may find interesing to try Inspector here since Hi-C data is not available, just a comment :)

@tbrown91
Copy link
Collaborator

tbrown91 commented Sep 5, 2025

Thanks @auryjm

I will give my "philosophical" opinion, and then others can let me know what they think.

If the species is genuinely tetraploid, we should try to either include the contigs from the 2X set of the chromosomes, or reduce it to 1X representation of each chromosome. You will probably have a better idea of whether it is auto-/allo-tetraploid and what is feasible from genomescope and smudgeplots, but looking at the spectra it almost looks like it would better to put back sequences, to account for the missing kmers under what I'm assuming is the homozygous peak.

Are you able to pair the sequences you already have, via something like Dgenies, to get an idea of how many "copies" of the genome are currently included? I note the coverage is also on the lower end for such an assembly, but I would like us to push for as good, or as "complete" as possible.

Before I forget as well, were you able to identify mito and chloroplast sequences? I love OatK for this.

@auryjm
Copy link
Collaborator

auryjm commented Sep 5, 2025

Thank you @tbrown91 ,

I believe it is important to submit a 1n genome, but we cannot exclude the possibility that in the 1n genome all chromosomes are duplicated. If you then look at the 2n genome, you should observe four copies of each region.

For example, Brassica napus contains two genomes, A (B. rapa) and C (B. oleracea). The 1n genome to be submitted is the one composed of 10 A chromosomes and 9 C chromosomes and obvisouly BUSCOs duplicated score is high but this is expected.
It is sometimes not very easy to distinguish between polyploidy and alleles! I remember that for Androsace I did it based on Smudgeplot and SNP detection.

We will have a look, as another plant genome for BGE is in the same situation, except that for that one we do have Hi-C data.

@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Sep 12, 2025

Ping @tbrown91,
One week without any movements on this PR!

4 similar comments
@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Sep 19, 2025

Ping @tbrown91,
One week without any movements on this PR!

@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Sep 27, 2025

Ping @tbrown91,
One week without any movements on this PR!

@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Oct 4, 2025

Ping @tbrown91,
One week without any movements on this PR!

@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Oct 11, 2025

Ping @tbrown91,
One week without any movements on this PR!

@tbrown91
Copy link
Collaborator

Hey @ldemirdj @auryjm did you have another look at this genome and come to any decisions about what sort of genome you would like to submit?

@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Oct 21, 2025

Ping @tbrown91,
One week without any movements on this PR!

1 similar comment
@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Oct 29, 2025

Ping @tbrown91,
One week without any movements on this PR!

@auryjm
Copy link
Collaborator

auryjm commented Oct 30, 2025

Just a quick update: the sample ambassador was able to generate Omni-C data. Maybe we can take a look at their data and see if it can improve the genome assembly.

@tbrown91
Copy link
Collaborator

Thanks @auryjm, sounds good

@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Nov 6, 2025

Ping @tbrown91,
One week without any movements on this PR!

2 similar comments
@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Nov 14, 2025

Ping @tbrown91,
One week without any movements on this PR!

@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Nov 21, 2025

Ping @tbrown91,
One week without any movements on this PR!

@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Dec 3, 2025

Ping @tbrown91,
One week without any movements on this PR!

1 similar comment
@erga-ear-bot
Copy link
Contributor

erga-ear-bot bot commented Dec 10, 2025

Ping @tbrown91,
One week without any movements on this PR!

@erga-ear-bot erga-ear-bot bot added the STALLED label Dec 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants