2,652
edits
Wishlist: Difference between revisions
no edit summary
(→Bugs) |
No edit summary |
||
| Line 8: | Line 8: | ||
* The ISa printed out by XSCALE does not take a, b (as determined by CORRECT) into account. ''Fixed in the version of Dec 06, 2010'' | * The ISa printed out by XSCALE does not take a, b (as determined by CORRECT) into account. ''Fixed in the version of Dec 06, 2010'' | ||
* 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 | * 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)'' | ||
== Would be nice to have == | == Would be nice to have == | ||
* 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: the workaround is to just rename the frames that you wish to skip; the Unix "rename" commmand is very handy for this, e.g. "rename peak bad_peak peak_1_2*.cbf" would rename frames 200 to 299. Ignore the error messages from INTEGRATE about frames that it didn't find; there are no adverse effects. --[[User:Kay|Kay]] 12:38, 7 November 2010 (UTC) | * 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: the workaround is to just rename the frames that you wish to skip; the Unix "rename" commmand is very handy for this, e.g. "rename peak bad_peak peak_1_2*.cbf" would rename frames 200 to 299. Ignore the error messages from INTEGRATE about frames that it didn't find; there are no adverse effects. --[[User:Kay|Kay]] 12:38, 7 November 2010 (UTC) | ||
* if the first frame of DATA_RANGE cannot be found in CORRECT (because the frames have already been deleted or so), | * 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]]. This would be useful in order to identify bad frames. --[[User:Kay|Kay]] 14:00, 12 November 2007 (CET) | * A breakdown of R<sub>meas</sub> by frame number, as currently only available from [[XDSSTAT]]. This would be useful in order to identify bad frames. --[[User:Kay|Kay]] 14:00, 12 November 2007 (CET) | ||