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.

Sign up for GitHub

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

Jump to bottom

rethink how rotations are handled internally #41

Open
aloctavodia opened this issue Nov 28, 2017 · 0 comments
Open

rethink how rotations are handled internally #41

aloctavodia opened this issue Nov 28, 2017 · 0 comments

Comments

@aloctavodia
Copy link
Contributor

aloctavodia commented Nov 28, 2017 •
edited
Loading

The current method for rotating the coordinates seems a little bit naive, but probably it is OK for protein, but seems complicated for glycans. Should we use a tree-based-algorithm? should we forget for a sec about glycans and see how far we can move with proteins and only then revisit this issue?
@aloctavodia aloctavodia changed the title rethink how rotation are handled internally rethink how rotations are handled internally Nov 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aloctavodia