Modeling Disordered Domains
Perhaps inspired by the fierce debate on this BB and elsewhere about how to model disordered side chains, I would like to present the following scenario (my current refinement project): The structure was solved by molecular replacement, is 3.25Å resolution, and ~70% solvent. I have 6 copies of a large complex in the AU (~100kDa per protomer). Only one copy is fully ordered. In the other 5 copies, a entire domain (~25kDa) is largely disordered (some have patchy residual density, but not readily interpretable). Altogether, this means that I am missing ~20% of the total protein in the AU. It seems that how you model this much "missing" material could have a significant effect on the final refined model. This is something we have observed a number of times, so I am wondering if anyone can suggest ways to deal with this aside from just leaving the domains out entirely. In this case, the missing domain is connected by two short hinges that restrict the rotational degrees of freedom considerably (you can think of the missing domains as a door--it can only pivot about the hinge, can't be flipped upside-down or sideways, etc., and is anchored close to the door frame). Additionally, crystal packing and steric constraints restrict the "sweep" of the missing domains to further pinpoint their location. Is it worth trying to model this? My impression from some earlier posts was that most people were content for disordered regions to be modeled as bulk solvent (rather than fiddling with masks to also cover the expected location of protein, etc.), but I wonder if you may actually substantially improve the model when this much protein is disordered. I guess I am imagining something analogous to a rigid body fit to the mean position of the disordered domains and a TLS-like ADP description of the motion (with a very large magnitude to account for the large displacement), but I am open to suggestions. On a final note, regarding those pesky missing side chains: any thoughts on trying to employ a "Ringer"-like approach to model some of these (Fraser, et al., Nature 2009, 462(7273):669-673)? Is this practical (maybe this would add to many additional parameters)? Best, Damian Ekiert
On Mon, Apr 4, 2011 at 11:11 AM, Damian Ekiert
On a final note, regarding those pesky missing side chains: any thoughts on trying to employ a "Ringer"-like approach to model some of these (Fraser, et al., Nature 2009, 462(7273):669-673)? Is this practical (maybe this would add to many additional parameters)?
This is potentially useful for finding and building alternate conformers (something that most programs don't do - the only one I'm aware of is qFit: http://smb.slac.stanford.edu/qFitServer/qFit.jsp). But Ringer still relies on having some interpretable (albeit weak) density for the sidechains, and was designed to look at static rather than dynamic disorder. (A somewhat artificial distinction, but appropriate enough when talking about refinement.) It is also limited to relatively high resolution, usually better than 2.0A, not because of data-to-parameter ratio, but because the maps at lower resolutions just don't have enough detail to detect alternate conformations with any degree of confidence. Regarding missing or patchy domains, Pavel recently added a feature that should at least improve the phases and refinement behavior, but I'll let him describe it since I don't really understand what it does. I do not know of cases where people have found a reasonable way to model these explicitly, other than placing a rigid domain and letting the B-factors go crazy. -Nat
Nat, Thanks for your comments. I guess I was thinking of cases where there was at least some weak density, such that by setting "build_alternates_ringer=True", Phenix would automatically add alternative rotamers and refine the relative occupancies. Regarding my disordered domains, I'm looking forward to hearing from Pavel about this new feature! Best, Damian On Apr 4, 2011, at 11:48 AM, Nathaniel Echols wrote:
On Mon, Apr 4, 2011 at 11:11 AM, Damian Ekiert
wrote: On a final note, regarding those pesky missing side chains: any thoughts on trying to employ a "Ringer"-like approach to model some of these (Fraser, et al., Nature 2009, 462(7273):669-673)? Is this practical (maybe this would add to many additional parameters)?
This is potentially useful for finding and building alternate conformers (something that most programs don't do - the only one I'm aware of is qFit: http://smb.slac.stanford.edu/qFitServer/qFit.jsp). But Ringer still relies on having some interpretable (albeit weak) density for the sidechains, and was designed to look at static rather than dynamic disorder. (A somewhat artificial distinction, but appropriate enough when talking about refinement.) It is also limited to relatively high resolution, usually better than 2.0A, not because of data-to-parameter ratio, but because the maps at lower resolutions just don't have enough detail to detect alternate conformations with any degree of confidence.
Regarding missing or patchy domains, Pavel recently added a feature that should at least improve the phases and refinement behavior, but I'll let him describe it since I don't really understand what it does. I do not know of cases where people have found a reasonable way to model these explicitly, other than placing a rigid domain and letting the B-factors go crazy.
-Nat _______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
Damien, That's pretty much what qFit does--it automatically adds alternate conformations (main-chain and side-chain) at occupancies it computes from a constrained fit to the data. It then uses phenix to further refine coords/adp's/occupancies. Like Nat said--you need better than 2A data. Henry -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Damian Ekiert Sent: Tuesday, April 05, 2011 11:00 AM To: PHENIX user mailing list Subject: Re: [phenixbb] Modeling Disordered Domains Nat, Thanks for your comments. I guess I was thinking of cases where there was at least some weak density, such that by setting "build_alternates_ringer=True", Phenix would automatically add alternative rotamers and refine the relative occupancies. Regarding my disordered domains, I'm looking forward to hearing from Pavel about this new feature! Best, Damian On Apr 4, 2011, at 11:48 AM, Nathaniel Echols wrote:
On Mon, Apr 4, 2011 at 11:11 AM, Damian Ekiert
wrote: On a final note, regarding those pesky missing side chains: any thoughts on trying to employ a "Ringer"-like approach to model some of these (Fraser, et al., Nature 2009, 462(7273):669-673)? Is this practical (maybe this would add to many additional parameters)?
This is potentially useful for finding and building alternate conformers (something that most programs don't do - the only one I'm aware of is qFit: http://smb.slac.stanford.edu/qFitServer/qFit.jsp). But Ringer still relies on having some interpretable (albeit weak) density for the sidechains, and was designed to look at static rather than dynamic disorder. (A somewhat artificial distinction, but appropriate enough when talking about refinement.) It is also limited to relatively high resolution, usually better than 2.0A, not because of data-to-parameter ratio, but because the maps at lower resolutions just don't have enough detail to detect alternate conformations with any degree of confidence.
Regarding missing or patchy domains, Pavel recently added a feature that should at least improve the phases and refinement behavior, but I'll let him describe it since I don't really understand what it does. I do not know of cases where people have found a reasonable way to model these explicitly, other than placing a rigid domain and letting the B-factors go crazy.
-Nat _______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
_______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
Hi Henry, while on the subject.. I remember I promised to let you know but keep forgetting (although most likely you figured this out yourself): phenix.refine can handle any number of alternative conformations (there used to be an artificial limit of 4, but we improved this a while ago). Pavel. On 4/5/11 11:40 AM, van den Bedem, Henry wrote:
Damien,
That's pretty much what qFit does--it automatically adds alternate conformations (main-chain and side-chain) at occupancies it computes from a constrained fit to the data. It then uses phenix to further refine coords/adp's/occupancies. Like Nat said--you need better than 2A data.
Henry
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Damian Ekiert Sent: Tuesday, April 05, 2011 11:00 AM To: PHENIX user mailing list Subject: Re: [phenixbb] Modeling Disordered Domains
Nat,
Thanks for your comments. I guess I was thinking of cases where there was at least some weak density, such that by setting "build_alternates_ringer=True", Phenix would automatically add alternative rotamers and refine the relative occupancies.
Regarding my disordered domains, I'm looking forward to hearing from Pavel about this new feature!
Best,
Damian
On Apr 4, 2011, at 11:48 AM, Nathaniel Echols wrote:
On a final note, regarding those pesky missing side chains: any thoughts on trying to employ a "Ringer"-like approach to model some of these (Fraser, et al., Nature 2009, 462(7273):669-673)? Is this practical (maybe this would add to many additional parameters)? This is potentially useful for finding and building alternate conformers (something that most programs don't do - the only one I'm aware of is qFit: http://smb.slac.stanford.edu/qFitServer/qFit.jsp). But Ringer still relies on having some interpretable (albeit weak) density for the sidechains, and was designed to look at static rather
On Mon, Apr 4, 2011 at 11:11 AM, Damian Ekiert
wrote: than dynamic disorder. (A somewhat artificial distinction, but appropriate enough when talking about refinement.) It is also limited to relatively high resolution, usually better than 2.0A, not because of data-to-parameter ratio, but because the maps at lower resolutions just don't have enough detail to detect alternate conformations with any degree of confidence. Regarding missing or patchy domains, Pavel recently added a feature that should at least improve the phases and refinement behavior, but I'll let him describe it since I don't really understand what it does. I do not know of cases where people have found a reasonable way to model these explicitly, other than placing a rigid domain and letting the B-factors go crazy.
-Nat _______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb _______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
Hi Damian,
In the other 5 copies, a entire domain (~25kDa) is largely disordered (some have patchy residual density, but not readily interpretable). Altogether, this means that I am missing ~20% of the total protein in the AU. It seems that how you model this much "missing" material could have a significant effect on the final refined model. This is something we have observed a number of times, so I am wondering if anyone can suggest ways to deal with this aside from just leaving the domains out entirely.
Regarding missing or patchy domains, Pavel recently added a feature that should at least improve the phases and refinement behavior
this is still ongoing project that Tom and myself are working on. It still need some work and a lot of testing. You can try it now by using "use_statistical_model_for_missing_atoms=true" in phenix.refine (you need the latest version for this), and there is no documentation yet, sorry. Actually, I was looking for a real case where there is a significant amount of model missing. If you send me the data, your best current model and the sequence, I will use it for testing and optimizing/training the algorithms that we are developing right now. For some details see pages #17-19 here: http://cci.lbl.gov/~afonine/afonine.pdf Pavel.
participants (4)
-
Damian Ekiert
-
Nathaniel Echols
-
Pavel Afonine
-
van den Bedem, Henry