|
|
Line 174: |
Line 174: |
| <div class="bevel tr"></div> | | <div class="bevel tr"></div> |
| <div class="content"> | | <div class="content"> |
− | <h3> Matching Step</h3> | + | <h4> Matching Step</h4> |
| <div class="contentline"> | | <div class="contentline"> |
| <div class="third"> | | <div class="third"> |
Line 186: |
Line 186: |
| <article> | | <article> |
| The meaning of the matching step is to match the amino acids which constrains to the ligand, following specific constrains which ensure that the result is sensible and feasible. For this, ROSETTA analyzes the structural formula of the non- canonical amino acid and offers the possible hydrogen binding partners. </br> | | The meaning of the matching step is to match the amino acids which constrains to the ligand, following specific constrains which ensure that the result is sensible and feasible. For this, ROSETTA analyzes the structural formula of the non- canonical amino acid and offers the possible hydrogen binding partners. </br> |
− | Matching step inputs </br> | + | <b>Matching step inputs</b> </br> |
| For the matching step, the following input-files are needed: | | For the matching step, the following input-files are needed: |
| <ul> | | <ul> |
Line 219: |
Line 219: |
| </article> | | </article> |
| | | |
− | <h4>Matching step outputs</h4> </br> | + | <b>Matching step outputs</b> </br> |
| | | |
| <div class="contentline"> | | <div class="contentline"> |
Line 246: |
Line 246: |
| <div class="bevel tr"></div> | | <div class="bevel tr"></div> |
| <div class="content"> | | <div class="content"> |
− | <h3> Design Step</h3> | + | <h4> Design Step</h4> |
| <div class="article"> | | <div class="article"> |
| The design step applies an algorithm such that the binding pocket and the near environment are mutated and the remaining scaffold is repacked. Additionally, a badness-of-fit score is generated which indicates how well the mutation fits the amino acid. For every file from the matching step, a model with a score and a “.pdb-file” will be generated, specifying where the sequence can be located, and the 3D-structure can be analyzed. Notably, the amino acid structure can be extracted separately. | | The design step applies an algorithm such that the binding pocket and the near environment are mutated and the remaining scaffold is repacked. Additionally, a badness-of-fit score is generated which indicates how well the mutation fits the amino acid. For every file from the matching step, a model with a score and a “.pdb-file” will be generated, specifying where the sequence can be located, and the 3D-structure can be analyzed. Notably, the amino acid structure can be extracted separately. |
Line 267: |
Line 267: |
| To optimize the structure we used applied an iterative optimization algorithm. This algorithm mutates all residues from the backbone, which are not part of the catalytic center, to alanine, and a small energy function refraction will place the ligand in an optimal position to the backbone. </br> | | To optimize the structure we used applied an iterative optimization algorithm. This algorithm mutates all residues from the backbone, which are not part of the catalytic center, to alanine, and a small energy function refraction will place the ligand in an optimal position to the backbone. </br> |
| For this approach, bb_min and chi_min allow for backbone flexibility and the rotation of the torsions. An alternative for this minimization step is the Monte Carlo rigid body ligand sampling. For further information on this method, we refer to the ROSETTA documentation (https://www.rosettacommons.org/manuals/archive/rosetta3.5_user_guide/d6/dbc/enzyme_design.html). </br> | | For this approach, bb_min and chi_min allow for backbone flexibility and the rotation of the torsions. An alternative for this minimization step is the Monte Carlo rigid body ligand sampling. For further information on this method, we refer to the ROSETTA documentation (https://www.rosettacommons.org/manuals/archive/rosetta3.5_user_guide/d6/dbc/enzyme_design.html). </br> |
− | <h4>Design step inputs </h4></br> | + | <b>Design step inputs </b></br> |
| The following input files are relevant for the design procedure: | | The following input files are relevant for the design procedure: |
| <ul> | | <ul> |
Line 285: |
Line 285: |
| </div> | | </div> |
| <div class="third double"> | | <div class="third double"> |
− | <h4>Design step outputs </h4></br> | + | <b>Design step outputs </b></br> |
| The output for the design step is a “.pdb”-file containing the mutated scaffold and a “.score”-file. | | The output for the design step is a “.pdb”-file containing the mutated scaffold and a “.score”-file. |
| For every PDB-file, a line in the score-file is generated, so it is easy to evaluate the given structure. | | For every PDB-file, a line in the score-file is generated, so it is easy to evaluate the given structure. |