Details
-
Type:
Bug
-
Status: To-Do (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:2
-
Epic Link:
Description
I've found a bug in IGB 10.1.0 that relates to the addition of custom genomes to IGB.
What I found is that, while viewing a custom genome in IGB, attempting to add a subsequent custom genome to IGB adds that second genome to the chromosome list of the custom genome that was being viewed. Expected behavior is that the second custom genome would be added to the Species drop-down menu as a separate genome. This may be an issue with how IGB differentiates genomes based on the value populated in the Genome Version field because the two custom genomes I added had the same value for Genome Version (S_SPECIES_MMM_YYYY).
This issue is appearing in 9.1.8 and beyond, though note that I did not test earlier releases.
To reproduce the issue as I found it, do the following:
- Open IGB 9.1.8
- Click the "Open genome from file." (double helix) button along the top of IGB
- Click "Browse..."
- Select "GIC31_complete.fna", then click "Open"
- In the Genus field, type "Samplegic31"
- Click "OK"
- Drag and drop "GIC31_complete_proteins.gff" into IGB
- Click "Load Data"
- Click "Load Sequence"
- Observe the Chromosome list on the right side of IGB and notice one listing (strain_GIC31_complete_genome)
- Click the "Open genome from file." (double helix) button along the top of IGB
- Click "Browse..."
- Select "gsD_SM51.fna", then click "Open"
- In the Genus field, type "Samplesm51"
- Click "OK"
- Observe the Chromosome list on the right side of IGB and notice that same listing from earlier, plus 25 new scaffolds
- Click the Species drop-down menu in the top-right of IGB
- Observe only one custom genome where there should be two (Samplegic31 SPECIES)
Attachments
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link | IGBF-1765 [ 17855 ] |
Attachment | Screenshot 2024-09-18 at 14.23.00.png [ 18510 ] |
Summary | Adding custom genome while viewing another custom genome adds that new genome as a chromosome | Investigate: Unexpected behavior when adding subsequent custom genomes |