Wishlist: Difference between revisions

Jump to navigation Jump to search
926 bytes removed ,  3 July 2019
 
(One intermediate revision by the same user not shown)
Line 12: Line 12:
== Would be nice to have ==
== Would be nice to have ==
* Add the REIDX keyword to XDSCONV. This would enable scaling in a centered spacegroup, and using P1 for the final dataset.
* Add the REIDX keyword to XDSCONV. This would enable scaling in a centered spacegroup, and using P1 for the final dataset.
* Add a SKIP_RANGE keyword similar to SPOT_RANGE which enables skipping multiple ranges of frames from the specified DATA_RANGE. XDS should just ignore those frames as if they were supposed to exist but do not. --[[User:Mnfodje|Mnfodje]] 15:07, 1 November 2010 (UTC). ''Comment: there is EXCLUDE_DATA_RANGE for this purpose''
* Add a SKIP_RANGE keyword similar to SPOT_RANGE which enables skipping multiple ranges of frames from the specified DATA_RANGE. XDS should just ignore those frames as if they were supposed to exist but do not. --[[User:Mnfodje|Mnfodje]] 15:07, 1 November 2010 (UTC). ''Comment: there is EXCLUDE_DATA_RANGE for this purpose. This parameter is used by INIT, COLSPOT, INTEGRATE, but not by CORRECT which means you must re-INTEGRATE. If you want to exclude a data range from an existing XDS_ASCII.HKL, run [[exclude_data_range_from_XDS_ASCII.HKL]].''


* if the first frame of DATA_RANGE cannot be found in CORRECT (because the frames have already been deleted or so), xds should pick up QX, QY, NX, NY from XDS.INP. ''Fixed in the version of Dec 06, 2010''
* if the first frame of DATA_RANGE cannot be found in CORRECT (because the frames have already been deleted or so), xds should pick up QX, QY, NX, NY from XDS.INP. ''Fixed in the version of Dec 06, 2010''


* A breakdown of R<sub>meas</sub> by frame number, as currently only available from [[XDSSTAT]].  
* 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.''
* 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.''
2,652

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.

Navigation menu