2,684
edits
Wishlist: Difference between revisions
→Bugs
(→Bugs) |
(→Bugs) |
||
| 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 | * 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 separatey for each resolution-truncated dataset. --[[User:Kay|Kay]] 18:21, 25 June 2011 (CEST)'' | ||
== Would be nice to have == | == Would be nice to have == | ||