You are here

Feedback for Loopmodeling module

2 posts / 0 new
Last post
Feedback for Loopmodeling module

Working with Loop-modeling to rebuild some missing loops from crystal structures. I don't see an issues tracking system for Rosetta, so I'm posting a couple of suggestions here:

- The -override flag is required to continue running loopmodel when the out files are already present. Without this the program aborts with no error messages. Is it possible to add in clarification in the log file when this happens? Very difficult to debug for people who are learning.

- The documentation for the frag_files arguments are incomplete. It is only by seeing a working copy that you find "none" should be put in the column corresponding to frag_size 1. Trial and error is okay, but I find this to be strange logic.

Post Situation: 
Tue, 2013-05-14 03:22

Thanks for the suggestions!

The issues tracking system for Rosetta is at

Tue, 2013-05-14 11:12