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 am wanting to show a triplication event between different species in a synteny plot, similar to the figure posted in #642. The gene depth ratio between my two species are 1:3, so I believe that means there has been a triplication event. Also, I believe I can see a triplication event within my plot:
Given this, how can I pinpoint which genes are triplicated and highlight only them in my synteny plot?
# x, y, rotation, ha, va, color, ratio, label
0.5, 0.6, 0, center, top, m, 1, sp1
0.1, 0.2, 0, center, bottom, #fc8d62, .3, sp2
0.5, 0.2, 0, center, bottom, #fc8d62, .3, sp2
0.9, 0.2, 0, center, bottom, #fc8d62, .3, Acicarpha
# edges
e, 0, 1
e, 1, 2
e, 2, 3
I am happy to provide more information, I am just unsure what you would need to help with this.
Thanks,
Erika
The text was updated successfully, but these errors were encountered:
The highlights in #642 were manual highlights. There is no automated way as far as I know.
My recommended path is to identify (e.g. in EXCEL) a region that visually match 3 regions in sp1.sp2.i3.blocks and then look for the same sp1 region in sp1.sp2.anchors.simple.
You can then add the highlight in front of those blocks, as suggested in the wiki.
Hello!
I am wanting to show a triplication event between different species in a synteny plot, similar to the figure posted in #642. The gene depth ratio between my two species are 1:3, so I believe that means there has been a triplication event. Also, I believe I can see a triplication event within my plot:
Given this, how can I pinpoint which genes are triplicated and highlight only them in my synteny plot?
Some code that may be relevant:
Also, I tried to do the blocks and microsynteny, but it did not work out:
blocks.layout:
I am happy to provide more information, I am just unsure what you would need to help with this.
Thanks,
Erika
The text was updated successfully, but these errors were encountered: