5
edits
Wishlist: Difference between revisions
→Bugs
(→Bugs) |
|||
| Line 9: | Line 9: | ||
* FRAME.cbf does not have distance and wavelength information, as well as direct beam position - would be good to have those for adxv usage. | * FRAME.cbf does not have distance and wavelength information, as well as direct beam position - would be good to have those for adxv usage. | ||
* When scaling multiple datasets with multiple OUTPUT entries within the same XSCALE.INP file, the reported statistics within XSCALE.LP does respect the corresponding INCLUDE_RESOLUTION_RANGE= keyword entries. --[[User:Mnfodje|Mnfodje]] June 24, 2011 <br> ''Comment: XSCALE finds the highest high-resolution cutoff of all output datasets, and prints out statistics for all datasets up to this resolution. Depending on the user-input values of INCLUDE_RESOLUTION_RANGE= , this may lead to tables that e.g. have 0 reflections in the high-resolution bin(s). This does not affect the data that are output; the only number (I think) that is wrong in those tables is the value for the total completeness. The workaround to get that value obviously is running XSCALE separately for each resolution-truncated dataset. --[[User:Kay|Kay]] 18:21, 25 June 2011 (CEST)'' | * When scaling multiple datasets with multiple OUTPUT entries within the same XSCALE.INP file, the reported statistics within XSCALE.LP does respect the corresponding INCLUDE_RESOLUTION_RANGE= keyword entries. --[[User:Mnfodje|Mnfodje]] June 24, 2011 <br> ''Comment: XSCALE finds the highest high-resolution cutoff of all output datasets, and prints out statistics for all datasets up to this resolution. Depending on the user-input values of INCLUDE_RESOLUTION_RANGE= , this may lead to tables that e.g. have 0 reflections in the high-resolution bin(s). This does not affect the data that are output; the only number (I think) that is wrong in those tables is the value for the total completeness. The workaround to get that value obviously is running XSCALE separately for each resolution-truncated dataset. --[[User:Kay|Kay]] 18:21, 25 June 2011 (CEST)'' | ||
* In previous versions of XDS, you could integrate a partial dataset which contains only frames 1-2,46-47,90-91 by specifying a DATA_RANGE=1 91. Although this complained about missing images, it still worked and we used this for screening by collecting only those frames and naming the images accordingly. Starting with the Dec 2011 version, this no longer works and the integration step stops with the error message ''!!!ERROR!!! CANNOT OPEN OR READ FILE bin2_XX.tmp''. Checking the directory, I can see that the file bin2_XX.tmp exists. After some testing, I can confirm that this happens if all the images within any single integration batch are missing. If the number of images missing is equal to or greater than DELPHI/OSCILLATION_RANGE, the error appears. The number of the bin file seems to correspond to the batch number and it does not matter where in the dataset the images are missing from. As a result it is no longer possible to process partial datasets for screening, or to exclude a section of bad frames in the dataset which is larger than DELPHI/OSCILLATION_RANGE. --[[User:mnfodje|mnfodje]] Feb 2, 2012 | |||
== Would be nice to have == | == Would be nice to have == | ||