| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000195 | Rosetta | [All Projects] Input Handling | public | 2013-03-01 12:59 | 2013-03-01 12:59 |
|
| Reporter | smlewis | |
| Assigned To | | |
| Priority | low | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | |
| Platform | | OS | | OS Version | |
| Product Version | | |
| Fixed in Version | | |
|
| Summary | 0000195: Feature Request: CartesianMoveMap |
| Description | So, there's a cartesian coordinate minimizer (as opposed to the internal coordinate minimizer), but it still reads from the internal coordinate MoveMap to determine mobility.
How about a CartesianMoveMap that lets you list which _atoms_ are / are not mobile? This lets you do crazy stuff like loop minimization without a loop fold tree, just say "don't move the nonloop atoms, please"! |
| Additional Information | So, how to implement? Inside MoveMap (no)? Child of MoveMap (no)? Sibling to MoveMap under a new parent class (maybe)? Not at all (maybe?) |
| Tags | No tags attached. |
|
| Application(s) Affected | cartesian minimization |
| Command Line Used | cartesian minimization |
| Developer Options | Feature Request |
| Fixed in SVN Version | |
|
| Attached Files | |
|
Relationships 
Relationships