docs: rotamers are searched; the Metal path's four kernels; the k_sol box as it is
The "not yet" list named a rotamer search, which the side-chain field does; the Metal path runs four refinement kernels, not only the density gather; the ModelScaling.h comment gave k_sol up to 0.8 where the box stops at 0.6. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HVeDQrPqZ52Tp6rzzZGxf3
This commit is contained in:
1 parent
1584a03b39
commit
d19f0686cb
2 files changed
+7
-6
No files matched your search
@@ -851,10 +851,11 @@ What the refinement does not do yet - each a known gap, not a design choice:
|
||||
density, not by refining each in turn.
|
||||
- **Alternative conformations and occupancies**: existing conformers are refined in place; no occupancy is
|
||||
refined and no conformer is added.
|
||||
- **Rotamer and peptide-flip search**, and **Ramachandran restraints**.
|
||||
- **Peptide-flip search** and **Ramachandran restraints** (side chains are searched over their staggered rotamers
|
||||
by the side-chain field, §15.7).
|
||||
- **Real-space refinement**, and **jelly-body or reference-model restraints**.
|
||||
- **A full Metal (Apple GPU) path**: on macOS the model density is gathered on the GPU and the rest of the
|
||||
refinement runs on the CPU.
|
||||
- **A full Metal (Apple GPU) path**: on macOS the model density, the atom-gradient sums, the solvent mask's
|
||||
shrink and the side-chain field's sums run on the GPU and the rest of the refinement runs on the CPU.
|
||||
- **Validation beyond geometry**: the report gives the bond and angle rmsd, the metal-bond rmsd and the
|
||||
number of clashes, not a MolProbity-style analysis (Ramachandran, rotamer and clashscore statistics).
|
||||
|
||||
|
||||
@@ -24,9 +24,9 @@
|
||||
// Levenberg-Marquardt: nothing there stops k_sol and b_sol reaching values a flat solvent model
|
||||
// is meaningless at (b_sol of 1707 A^2 was measured on this corpus). Here k_sol and b_sol come
|
||||
// from a grid search over the physical ranges, so an unphysical answer cannot be represented.
|
||||
// The box the solvent parameters are searched in. The defaults are the physically reasonable
|
||||
// range reported by Fokine & Urzhumtsev and adopted as phenix's default grid: k_sol in (0.1, 0.8)
|
||||
// and b_sol in (10, 80) A^2, of which phenix searches b_sol 10-80 in steps of 5. A model with high
|
||||
// The box the solvent parameters are searched in: k_sol in (0.10, 0.60) and b_sol in (10, 80) A^2.
|
||||
// The b_sol range is the physically reasonable one reported by Fokine & Urzhumtsev and phenix's
|
||||
// default grid (b_sol 10-80 in steps of 5); their k_sol range reaches 0.8, the box here stops at 0.6. A model with high
|
||||
// atomic B gets a higher b_sol ceiling (SolventBMax).
|
||||
struct ModelScaleBox {
|
||||
double k_lo = 0.10, k_hi = 0.60;
|
||||
|
||||
Reference in new issue
Block a user