You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a situation I'm not sure how to interpret. I have a big gap in synteny for one contig (circled in red).
Wanting to see what genes are in that gap region of Gt-23d, I dug into the syntenicBlock_coordinates file to figure out where the gap started and then looked at the corresponding synHits file to see what genes were there. However, I was a bit confused to see that the genes continued to blast to contiguous genes in the other genome and that were in the same orthogroup, and yet were being assigned to a different blkID per gene. Here's an extract of the synHits as it crosses the start of the gap (onwards from blkID Gt23d_vs_Gt8d: 390):
I guess I'm either misunderstanding the output files or missing some idiosyncrasy in how GENESPACE defines synteny, but I was wondering why the plot ends up with a gap when to my eyes it looks like there are syntenic genes across the region.
I did notice that there seems to be a funny numerical sorting thing happening across rows in the synHits file e.g. going from 4_2017 to 4_202 before back to 4_2025, is that contributing to breaking up the blkIDs?
Firstly, thanks for your fantastic tool!
I have a situation I'm not sure how to interpret. I have a big gap in synteny for one contig (circled in red).
Wanting to see what genes are in that gap region of Gt-23d, I dug into the syntenicBlock_coordinates file to figure out where the gap started and then looked at the corresponding synHits file to see what genes were there. However, I was a bit confused to see that the genes continued to blast to contiguous genes in the other genome and that were in the same orthogroup, and yet were being assigned to a different blkID per gene. Here's an extract of the synHits as it crosses the start of the gap (onwards from blkID Gt23d_vs_Gt8d: 390):
I guess I'm either misunderstanding the output files or missing some idiosyncrasy in how GENESPACE defines synteny, but I was wondering why the plot ends up with a gap when to my eyes it looks like there are syntenic genes across the region.
I did notice that there seems to be a funny numerical sorting thing happening across rows in the synHits file e.g. going from 4_2017 to 4_202 before back to 4_2025, is that contributing to breaking up the blkIDs?
I've attached some full files in case that helps.
Thanks!
syntenicBlock_coordinates.csv
Gt23d_pangenes.txt
Gt23d_vs_Gt8d.synHits.txt
The text was updated successfully, but these errors were encountered: