Wishlist: Difference between revisions

Wishlist (view source)

Revision as of 13:41, 4 July 2017

1,148 bytes removed , 4 July 2017

→‎Would be nice to have

Kay

Bureaucrats

2,684

edits

@@ Line 17: / Line 17: @@
 * A breakdown of R<sub>meas</sub> by frame number, as currently only available from [[XDSSTAT]].
-* Templates of XDS.INP currently have
- !EXCLUDE_RESOLUTION_RANGE= 3.93 3.87 !ice-ring at 3.897 Angstrom
- !EXCLUDE_RESOLUTION_RANGE= 3.70 3.64 !ice-ring at 3.669 Angstrom
- !EXCLUDE_RESOLUTION_RANGE= 3.47 3.41 !ice-ring at 3.441 Angstrom
- !EXCLUDE_RESOLUTION_RANGE= 2.70 2.64 !ice-ring at 2.671 Angstrom
- !EXCLUDE_RESOLUTION_RANGE= 2.28 2.22 !ice-ring at 2.249 Angstrom
-This list may/could be completed by
- !EXCLUDE_RESOLUTION_RANGE= 2.102 2.042 !ice-ring at 2.072 Angstrom - should be strong
- !EXCLUDE_RESOLUTION_RANGE= 1.978 1.918 !ice-ring at 1.948 Angstrom - may be weak
- !EXCLUDE_RESOLUTION_RANGE= 1.948 1.888 !ice-ring at 1.918 Angstrom - should be strong
- !EXCLUDE_RESOLUTION_RANGE= 1.913 1.853 !ice-ring at 1.883 Angstrom - may be weak
- !EXCLUDE_RESOLUTION_RANGE= 1.751 1.691 !ice-ring at 1.721 Angstrom - may be weak
-Please note that I did not optimize the widths (in particular the last one should probably be something like 1.741 1.701 or 1.731 1.711), and that the ranges of the 2nd, 3rd and 4th ring overlap (and thus could be combined and narrowed to something like 1.958 1.873).
---[[User:Kay|Kay]] 14:30, 12 November 2007 (CET)
 * INCLUDE_RESOLUTION_RANGE= should be respected by IDXREF because this could be used to prevent ice rings from disturbing the indexing. Drawback: one would have to change INCLUDE_RESOLUTION_RANGE= after running IDXREF.<br />Probably better: EXCLUDE_RESOLUTION_RANGE= should be respected by IDXREF. Drawback: geometrical parameters (in particular the direct beam position) are unrefined when resolution is calculated in IDXREF. ''Solution: Both INCLUDE_RESOLUTION_RANGE and EXCLUDE_RESOLUTION_RANGE are evaluated by IDXREF since version March-30, 2013.''