I am trying to model (not design) a protein in an alternate state, where a phenylalanine is burried in the native state, and solvent exposed in the one I am modeling.
I would like to use a constraint, or some or other method, that specifies the solvent accessibility of that PHE, while running a relax or remodel application. I would prefer to not use a list of nearest-neighbor distance constraints, since there are quite a few of them, the residues and distances vary depending on the exposure of the PHE, and it is the identity and distances of the nearest neighbors that I am trying to figure out based on the exposure of the PHE.
Any suggestions would be greatly appreciated!
I know you said remodel/relax application and not script, but the SASA selection is available in scripting.
The bad news is that there are few cascading effects to deal with:
The <Layer> elements go within <RESIDUE_SELECTORS> element. In the <MoveMap> of <FastRelax> (or similar mover) there is written that you can add <ResidueSelector>. This in my hands is not true. No idea why the documentation says you can, but you get a "Error: Element 'ResidueSelector': This element is not expected. Expected is one of ( Jump, Chain, Span )." if you do. So you have to use a movemap factory, which can.
So you have to add:
<MoveMapFactory name="moove" bb="0" chi="0">
<Backbone residue_selector="layerz" />
<Chi residue_selector="layerz" />
Which is called by <FastRelax name="chillax" repeats="1" movemap_factory="moove" cartesian="1" />.
Also, cartesian="1" is needed or the constraint gets ignored. But to get cartesian mode to work you have to add -beta_nov16_cart to your run.
$ROSETTAPATH/source/bin/rosetta_scripts.static.macosclangrelease -s something.pdb -parser:protocol yourscript.xml -beta_nov16_cart
Sorry to double post but I remembered that I had a snippets of code that could something similar to what you asked* and then I re-read the question and realised you know a priori what the phenylalanine is....
Rosetta Relax has an option `-in:file:movemap`, where you can specify explicitly which residues you want to move both backbone (bb) or sidechain (chi). A movemap is also an element in Rosetta scripts and in Pyrosetta. The movemap file will have to be made external and not in Rosetta.
Note that the values are in pose numbering and not PDB and using the 23A kind of notation does not work IIRC.
Pyrosetta has a really nice function called pdb2pose that does these conversion for you. Here is a chunk of code as an example (same thing as using the application).
*) Not that it matters but the code I was going to post was a python script using pymol that I quickly adapted: