forked from RosettaCommons/rosetta
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1928 from RosettaCommons/Cyrus/mergetarget
From Steven Lewis: This is mostly small features I did in in the summer/fall of 2016 and never got around to testing and PRing until just now. Features: * smlewis/fix_README - improving the front README, based on a better understanding of our forking policy, thanks to @aleaverfay @kwikwag * smlewis/FT_clangstatic_fix - fix a clangstatic bug @roccomoretti pointed out (it was a copy paste error) * smlewis/cyrus/ss_printer_for_commons - fixes to the HELIX/SHEET printer so that the records are ordered properly in large/multichain structures where the numbering restarts per chain. This integration test (secondary_structure_output) will change, as it now has a long enough input to have triggered this bug. smlewis/cyrus/LoopLengthChange_restype: LoopLengthChange takes a residue type char for what to insert/ Resolves RC issue RosettaCommons/main#1700. Adds integration test. smlewis/cyrus/actccm_atompair_bounded - AddConstraintsToCurrentConformationMover constraint choice improvements. Adds integration test. This code already had an integration test testing different aspects of the Mover; I made a second test so that it multithreads more efficiently. Old repository SHA1: d610dbcac7de639bb5b5bd832f24a111e2e5cc83 Co-authored-by: Steven Lewis <[email protected]>
- Loading branch information
1 parent
20351e3
commit c3d6219
Showing
34 changed files
with
784 additions
and
129 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -137,8 +137,8 @@ struct HELIXInformation { | |
// http://www.wwpdb.org/documentation/file-format-content/format23/sect5.html | ||
/// @author Steven Lewis [email protected] | ||
struct SHEETInformation { | ||
core::Size sheetID; //numeric ID (which # helix is this?). if > 999 bad things happen here (output field is only 3 chars) | ||
std::string sheet_name; //arbitrary unique ID; copy of sheetID as a string | ||
core::Size strand_num = 1; //nominally the strand number within the sheet, but we are recording each STRAND as its own sheet | ||
std::string sheetID; //arbitrary unique ID; copy of sheetID as a string | ||
core::Size num_strands = 1; //nominally these are SHEET records but we are only doing STRANDs | ||
std::string name3_1; //name3 of start residue | ||
char chainID1; //chain of start residue | ||
|
@@ -247,15 +247,15 @@ public: // Accessors ///////////////////////////////////////////////////////// | |
|
||
// PDB Secondary Structure Section //////////////////////////////////////// | ||
/// @brief Access map for storing HELIX records. | ||
/// @details key is 6-character resID of 1st residue in helix, from ResidueInformation::resid(). These records should be essentially correct, unlike the SHEET records. NOTE that they are NOT read from the PDB by PoseFromStructFileRepConverter, only generated FROM the pose in PoseToStructFileRepConverter. | ||
std::map< std::string, HELIXInformation > const & HELIXInformations() const { return HELIXInformations_; } | ||
std::map< std::string, HELIXInformation > & HELIXInformations() { return HELIXInformations_; } | ||
/// @details These records should be essentially correct, unlike the SHEET records. NOTE that they are NOT read from the PDB by PoseFromStructFileRepConverter, only generated FROM the pose in PoseToStructFileRepConverter. | ||
utility::vector1< HELIXInformation > const & HELIXInformations() const { return HELIXInformations_; } | ||
utility::vector1< HELIXInformation > & HELIXInformations() { return HELIXInformations_; } | ||
|
||
// PDB Secondary Structure Section //////////////////////////////////////// | ||
/// @brief Access map for storing SHEET records. | ||
/// @details key is 6-character resID of 1st residue in strand, from ResidueInformation::resid(). These records are cheating on the PDB rules and just storing individual strands as 1-strand sheets. NOTE that they are NOT read from the PDB by PoseFromStructFileRepConverter, only generated FROM the pose in PoseToStructFileRepConverter. | ||
std::map< std::string, SHEETInformation > const & SHEETInformations() const { return SHEETInformations_; } | ||
std::map< std::string, SHEETInformation > & SHEETInformations() { return SHEETInformations_; } | ||
/// @details These records are cheating on the PDB rules and just storing individual strands as 1-strand sheets. NOTE that they are NOT read from the PDB by PoseFromStructFileRepConverter, only generated FROM the pose in PoseToStructFileRepConverter. | ||
utility::vector1< SHEETInformation > const & SHEETInformations() const { return SHEETInformations_; } | ||
utility::vector1< SHEETInformation > & SHEETInformations() { return SHEETInformations_; } | ||
|
||
// PDB Connectivity Annotation Section //////////////////////////////////// | ||
/// @brief Access map for storing SSBOND records. | ||
|
@@ -365,8 +365,8 @@ private: | |
std::map< std::string, utility::vector1< std::string > > heterogen_synonyms_; // key is hetID | ||
std::map< std::string, std::string > heterogen_formulae_; // key is hetID | ||
std::map< std::string, std::pair< std::string, std::string > > residue_type_base_names_; // key is 6-char. resID | ||
std::map< std::string, HELIXInformation > HELIXInformations_; // key is 6-char resID from ResidueInformation::resid | ||
std::map< std::string, SHEETInformation > SHEETInformations_; // key is 6-char resID from ResidueInformation::resid | ||
utility::vector1< HELIXInformation > HELIXInformations_; | ||
utility::vector1< SHEETInformation > SHEETInformations_; | ||
std::map< std::string, utility::vector1< SSBondInformation > > ssbond_map_; // key is 6-character resID | ||
std::map< std::string, utility::vector1< LinkInformation > > link_map_; // key is 6-character resID | ||
std::map< std::string, CisPeptideInformation > cispep_map_; // key is 6-character resID | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.