| 3 | | == Examples for proposed surface command == |
| | 3 | == New proposed surface command == |
| | 4 | |
| | 5 | I think this new syntax is clearer than what I proposed before (TomG). The first argument is what atoms to use in computing surfaces, and optional keywords handle the rarer uses such as showing a patch of a surface. |
| | 6 | |
| | 7 | To show surfaces for each chain excluding ligands, ions, solvent |
| | 8 | |
| | 9 | surface #1 |
| | 10 | |
| | 11 | To make one surface enclosing all chains excluding ligands, ions, solvent |
| | 12 | |
| | 13 | surface #1 perChain false |
| | 14 | |
| | 15 | To show just the surface patch of chain surfaces near a ligand |
| | 16 | |
| | 17 | surface #1 show ligand za<5 |
| | 18 | |
| | 19 | I think the above 3 examples are the most common uses. Now for some exotic cases. |
| | 20 | |
| | 21 | To surface the chains with each chain surface also enclosing the ligands (in this example ligand is an atom spec) |
| | 22 | |
| | 23 | surface #1 include ligand |
| | 24 | |
| | 25 | To surface just the ligands, one ligand surface per chain. Here we make an exception |
| | 26 | to the rule that ligands, ions and solvent are excluded -- if only ligands, ions and solvent |
| | 27 | are specified. This is a convenience. |
| | 28 | |
| | 29 | surface ligand |
| | 30 | |
| | 31 | To surface several models, one surface per model. Even if per-chain is false it is still per-model. |
| | 32 | |
| | 33 | surface #1,2,3 perChain false |
| | 34 | |
| | 35 | To put one surface around 3 models |
| | 36 | |
| | 37 | surface #1,2,3 perModel false |
| | 38 | |
| | 39 | An alternative to the perChain and perModel options would be to have a split option "split chains|models|none". |
| | 40 | |
| | 41 | |
| | 42 | == Earlier proposed surface command == |