Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Displaying PDB assembly predictions, EPPIC disjoint assemblies and invalid assemblies #54

Closed
gcapitani opened this issue Jul 29, 2015 · 2 comments

Comments

@gcapitani
Copy link
Contributor

In order to clearly display PDB assembly predictions it seems that an additional column in the assembly panel would be a good solution to tag the EPPIC assembly that corresponds to the PDB prediction.
A special case occurs when the PDB prediction is an invalid assembly, in that case EPPIC will output that assembly as the last row and it is important to clearly show users that it is invalid. A simple way is to use the thumbnail field, which is anyway empty in those cases. There one could display a .png with the text "TOPOLOGICALLY INVALID".
The same approach could be employed to clearly tag disjoint assemblies: see e.g. the case of 1jap, where currently the same cartoon icon corresponds to both A,I and AI stoichiometries. An assembly like A,I should not have a graphical representation, but just a "DISJOINT ASSEMBLY" text in the thumbnail field.

@sbliven
Copy link
Member

sbliven commented Sep 25, 2015

If we add a schematic thumbnail, that would make it clear which chains are interacting.

Alternately, what if we translate the subassemblies so that there is a visible gap between them? This could be either done by choosing a different lattice point (consistent with 3D), or just by composing multiple images for the thumbnail.

@josemduarte
Copy link
Contributor

This is several issues in one, I've now split it into its subcomponents: #100 #101 #102

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants