2,684
edits
Wishlist: Difference between revisions
Jump to navigation
Jump to search
→Would be nice to have
| Line 27: | Line 27: | ||
* 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. <br /> Probably best: a new keyword for this purpose. <br /> For a workaround, see [[Ice_rings]]. <br /> Based on discussion with Clemens Vonrhein --[[User:Kay|Kay]] 12:16, 16 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. <br /> Probably best: a new keyword for this purpose. <br /> For a workaround, see [[Ice_rings]]. <br /> Based on discussion with Clemens Vonrhein --[[User:Kay|Kay]] 12:16, 16 November 2007 (CET) | ||
* a keyword | * a keyword REJECT_ALIEN= with a default of 20. This would be the cutoff for automatic rejection of "aliens". See [[Optimization#Wilson%20outliers%20(aliens)]]--[[User:Kay|Kay]] 10:29, 27 November 2007 (CET). '' This was implemented in January 2010.'' | ||
* Automated Direct Beam Position Recognition from Direct Beam Shots: The [[Features that are not officially documented|undocumented]] DIRB option should be announced and extended. I would suggest the following: a new input keyword "NAME_OF_DIRB_FRAME=" instead of interactive input is used to specifiy the direct beam shot frame. As a default "NAME_OF_DIRB_FRAME=" should use frame 0 of the current Name_Template_of_data_frames selection. Avoiding interactive input would facilitate automated script based processing and avoid the use of erroneous direct beam position from headers or manual input.--[[User:Tmaier|Tmaier]] 13:24, 13 December 2007 (CET) | * Automated Direct Beam Position Recognition from Direct Beam Shots: The [[Features that are not officially documented|undocumented]] DIRB option should be announced and extended. I would suggest the following: a new input keyword "NAME_OF_DIRB_FRAME=" instead of interactive input is used to specifiy the direct beam shot frame. As a default "NAME_OF_DIRB_FRAME=" should use frame 0 of the current Name_Template_of_data_frames selection. Avoiding interactive input would facilitate automated script based processing and avoid the use of erroneous direct beam position from headers or manual input.--[[User:Tmaier|Tmaier]] 13:24, 13 December 2007 (CET) | ||
* Option to write out FRAME.PCK for visual control for every nth image, e.g. controlled by a keyword "FRAMEPCK_EVERY_NTH=" with default FRAMEPCK_EVERY_NTH=0 i.e. single FRAME_NTH.PCK as in current version, the option FRAMEPCK_EVERY_NTH=B i.e. writing one FRAME_NTH.PCK per batch in INTEGRATE, and the option to provide an integer number n to get FRAME_NTH.PCK for every nth original image.--[[User:Tmaier|Tmaier]] 13:37, 13 December 2007 (CET) | * Option to write out FRAME.PCK for visual control for every nth image, e.g. controlled by a keyword "FRAMEPCK_EVERY_NTH=" with default FRAMEPCK_EVERY_NTH=0 i.e. single FRAME_NTH.PCK as in current version, the option FRAMEPCK_EVERY_NTH=B i.e. writing one FRAME_NTH.PCK per batch in INTEGRATE, and the option to provide an integer number n to get FRAME_NTH.PCK for every nth original image.--[[User:Tmaier|Tmaier]] 13:37, 13 December 2007 (CET) | ||