2,684
edits
Spot2pdb: Difference between revisions
Jump to navigation
Jump to search
m
→Notes
mNo edit summary |
m (→Notes) |
||
| Line 40: | Line 40: | ||
* the mapping used by <code>dials.rs_mapper</code> uses the (unrefined) frame header values, and possibly assumptions (as implemented in <code>iotbx.detectors</code>) about geometry aspects, like ROTATION_AXIS, not stored in the header. On the other hand, XPARM.XDS may have different assumptions about geometry aspects, and uses the geometry as refined by IDXREF. Ideally, these two mappings should agree. | * the mapping used by <code>dials.rs_mapper</code> uses the (unrefined) frame header values, and possibly assumptions (as implemented in <code>iotbx.detectors</code>) about geometry aspects, like ROTATION_AXIS, not stored in the header. On the other hand, XPARM.XDS may have different assumptions about geometry aspects, and uses the geometry as refined by IDXREF. Ideally, these two mappings should agree. | ||
* Since <code>dials.rs_mapper</code> uses the STARTING_ANGLE information from the frame headers, the mappings can only agree if <code>XDS.INP</code> also has this item. [[generate_XDS.INP]] versions since 0.82 write <code>XDS.INP</code> with STARTING_ANGLE information for most detectors. | * Since <code>dials.rs_mapper</code> uses the STARTING_ANGLE information from the frame headers, the mappings can only agree if <code>XDS.INP</code> also has this item. [[generate_XDS.INP]] versions since 0.82 write <code>XDS.INP</code> with STARTING_ANGLE information for most detectors. | ||
* if no <code>XPARM.XDS</code> exists, spot2pdb uses [ | * if no <code>XPARM.XDS</code> exists, spot2pdb uses [[XDS.INP]] as a source of geometry information. | ||
* <code>coot</code> connects atoms that are close, have residue numbers differing by at most 1, and are in the same chain, with bonds (lines) (Paul Emsley, personal communication). The program makes an attempt to avoid such lines by cycling through chain names; the proper solution would be <code>coot</code>'s ''display objects'' (Paul Emsley, personal communication). | * <code>coot</code> connects atoms that are close, have residue numbers differing by at most 1, and are in the same chain, with bonds (lines) (Paul Emsley, personal communication). The program makes an attempt to avoid such lines by cycling through chain names; the proper solution would be <code>coot</code>'s ''display objects'' (Paul Emsley, personal communication). | ||