0000090: No mechanism to convert centroid silent files to fullatom (particularly for fixbb, which should do this)

Notes
(0000086) rmoretti (Attentive Developer) 2012-08-29 09:59	I think if you have centroid input, you should get a centroid pose. I believe certain protocols depend on this for silent files, so making the silent file reader always give back fullatom poses with junk sidechains would not work well. (That said, looking at a flag like -in:file:fullatom and acting based on it might be acceptable.) I'd say that if the PDB inputter always converts a centroid input into a fullatom pose with junk sidechains, that's the bug. The input machinery should leave things as they are, and perhaps there should be a utility function that protocols can call to force fullatom poses, if they want to automagically mock centroid input as fullatom. (Or have the user specify something like -in:file:fullatom if they want to use centroid silent/PDB files.)

(0000087) smlewis (Administrator) 2012-08-29 10:21	The PDB reader (not PDBJobInputter) can read centroid as fullatom as a consequence of its necessary fuzzy matching of residue types. If it sees a valid name3 and valid backbone atoms, it will ignore the CEN atoms and make a fullatom pose. (it minimally packs them by default so the sidechains aren't total junk). Of course, if centroid options are active (I guess in:file:centroid) it doesn't do that and coughs up a centroid pose instead. I guess you can argue that it's a bug that the PDB reader can noisily convert centroid to fullatom without a specific flag requesting that...but I don't know how that bug-or-feature could be decoupled from the absolutely-a-feature ability to read in PDBs with sidechains that are incomplete in some fashion. in:file:fullatom and in:file:centroid are hopelessly vague in that sometimes they mean "I HAVE a centroid/fullatom and am warning you" and sometimes mean "I want centroid/fullatom, ignore the nonbackbone atoms of what I give you". The least-effect bandaid is to throw a SwitchResidueTypeSetMover into fixbb's stack to force fullatom at all times. The widest fix might be to put switches into most of the input machinery to ensure that the pose they return is the type of pose the user wants (preferably specified by some new nonvague flags); while this is possible I think it's pretty unrealistic. I'll take a stab at option 1.

Issue History
Date Modified	Username	Field	Change
2012-08-29 08:38	smlewis	New Issue
2012-08-29 09:59	rmoretti	Note Added: 0000086
2012-08-29 10:21	smlewis	Note Added: 0000087
2012-08-29 10:21	smlewis	Assigned To	=> smlewis
2012-08-29 10:21	smlewis	Status	new => assigned

Relationships