This script is useful when converting an application-defined Mover (in its original use case, coupled_moves) into a protocols library Mover. Application-defined options have to move to options_rosetta.py to do this. The script takes lines of code that are sed-able or awk-able from the .cc file and outputs python to copy into options_rosetta.py. What the input ought to look like is present as input_sample. I did the conversion semi-manually for the one use case, so I don't have that first command line handy, sorry!
A technical note: I wrote this in its own non-GitHub git repository on an airplane. I merged it into Cyrus' rosetta-tools and am now PRing to RosettaCommons tools. It does introduce a second "root" into the repository (a commit with no parents) - I assume that is not a problem; it hasn't been in other repositories I've done this to. Here's how you do that, BTW. http://stackoverflow.com/questions/1683531/how-to-import-existing-git-repository-into-another
This script is useful when converting an application-defined Mover (in its original use case, coupled_moves) into a protocols library Mover. Application-defined options have to move to options_rosetta.py to do this. The script takes lines of code that are sed-able or awk-able from the .cc file and outputs python to copy into options_rosetta.py. What the input ought to look like is present as input_sample. I did the conversion semi-manually for the one use case, so I don't have that first command line handy, sorry!
A technical note: I wrote this in its own non-GitHub git repository on an airplane. I merged it into Cyrus' rosetta-tools and am now PRing to RosettaCommons tools. It does introduce a second "root" into the repository (a commit with no parents) - I assume that is not a problem; it hasn't been in other repositories I've done this to. Here's how you do that, BTW. http://stackoverflow.com/questions/1683531/how-to-import-existing-git-repository-into-another