FAQ: Difference between revisions
(New page: These are answers to questions that were asked concerning XDS, on the occasion of the webinar on Feb 25, 2010. Some answers were given during the webinar; these are not repeated here. Q:...) |
(post-webinar) |
||
| Line 1: | Line 1: | ||
These are answers to questions that were asked concerning XDS, on the occasion of the webinar on Feb 25, 2010. Some answers were given during the webinar; these are not repeated here. | These are answers to questions that were asked concerning XDS, on the occasion of the webinar on Feb 25, 2010. Some answers were given during the webinar; these are not repeated here. | ||
---- | |||
Q: Is there a way to automatically set the high resolution limit based on an I/sigma cutoff? | Q: Is there a way to automatically set the high resolution limit based on an I/sigma cutoff? | ||
| Line 6: | Line 7: | ||
A: no. | A: no. | ||
---- | |||
Q: How does one define the beam stop shadow? Is it possible to develop a simple method, e.g. the ignore circle and ignore rectangle of HKL2000? | Q: How does one define the beam stop shadow? Is it possible to develop a simple method, e.g. the ignore circle and ignore rectangle of HKL2000? | ||
| Line 11: | Line 13: | ||
A: VALUE_RANGE_FOR_TRUSTED_DETECTOR_PIXELS= and UNTRUSTED_RECTANGLE= are the primary means. UNTRUSTED_CIRCLE may be implemented soon. | A: VALUE_RANGE_FOR_TRUSTED_DETECTOR_PIXELS= and UNTRUSTED_RECTANGLE= are the primary means. UNTRUSTED_CIRCLE may be implemented soon. | ||
---- | |||
Q: Can one apply the corrections in CORRECT without deleting outliers (i.e. waiting for a later program e.g. SCALA to do outlier rejection). | Q: Can one apply the corrections in CORRECT without deleting outliers (i.e. waiting for a later program e.g. SCALA to do outlier rejection). | ||
| Line 16: | Line 19: | ||
A: you may set WFAC1 to 100 (default is 1) | A: you may set WFAC1 to 100 (default is 1) | ||
---- | |||
Q: What is LATTICE-CHARACTER in CORRECT.LP ? | Q: What is LATTICE-CHARACTER in CORRECT.LP ? | ||
| Line 33: | Line 36: | ||
A: the error should be less than half the minimum spot separation. XDS does optimize the beam position. | A: the error should be less than half the minimum spot separation. XDS does optimize the beam position. | ||
---- | ---- | ||
Q: I can not find generate_XDS.INP in XDSwiki page | Q: I can not find generate_XDS.INP in XDSwiki page | ||
| Line 43: | Line 43: | ||
A: try http://strucbio.biologie.uni-konstanz.de/xdswiki/index.php/Generate_XDS.INP | A: try http://strucbio.biologie.uni-konstanz.de/xdswiki/index.php/Generate_XDS.INP | ||
---- | ---- | ||
| Line 49: | Line 48: | ||
A: try http://www.mpimf-heidelberg.mpg.de/~kabsch/xds/html_doc/xds_prepare.html | A: try http://www.mpimf-heidelberg.mpg.de/~kabsch/xds/html_doc/xds_prepare.html | ||
---- | ---- | ||
| Line 69: | Line 67: | ||
A: Using XDS-Viewer: along the x direction, you find the "integration batches" (last frames on the right). Along the y direction, the resolution ranges. The shades of gray correspond to numbers - move the mouse across them. The numbers are scalefactors multiplied with 1000. | A: Using XDS-Viewer: along the x direction, you find the "integration batches" (last frames on the right). Along the y direction, the resolution ranges. The shades of gray correspond to numbers - move the mouse across them. The numbers are scalefactors multiplied with 1000. | ||
---- | |||
Q: What about overlapping reflections in XDS? | Q: What about overlapping reflections in XDS? | ||
| Line 79: | Line 79: | ||
A: yes, because the programs implement different ideas. | A: yes, because the programs implement different ideas. | ||
---- | ---- | ||
Q: Is there a way to automatically set the high resolution limit based on and I/sigma cutoff? | Q: Is there a way to automatically set the high resolution limit based on and I/sigma cutoff? | ||
| Line 88: | Line 86: | ||
A: no. | A: no. | ||
---- | |||
What about very low resolution data, 5 to 10 A range with the rather high mosaicity of few degrees? Any experience with processing of such data with the XDS? | |||
A: yes, I have lots of experience with bad data. It should be possible to process these data. You may want to specify | |||
BEAM_DIVERGENCE= BEAM_DIVERGENCE_E.S.D.= | |||
REFLECTING_RANGE= REFLECTING_RANGE_E.S.D.= | |||
in XDS.INP, and to use REFINE(INTEGRATE)= | |||
---- | ---- | ||
Q: You said that the XDS deals with high mosaicity. How high mosaicity is still manageable? | |||
A: I don't have exact numbers. Maybe up to ten degrees? | |||
---- | |||
Q: Could you give recommendation for MAD data processing, to get best anomalous?? | |||
How to process the 3 data sets with the same orientation matrix, should we use | |||
reference datataset? | |||
A: First question: see XDSwiki. Second question: yes. | |||
---- | |||
Q: It would be nice to have a Table with Rfactors for each Image to identify xtal damage. | |||
I meant Table with Ractor over Image in CORRECT.LP | |||
A: XDSSTAT produces this table. | |||
---- | |||
Q: Is it possible to exclude images inside the frame range from integration? | |||
A: just remove them from the directory, or change their name. Or create a directory with symlinks only to those file you want XDS to use. | |||
---- | |||
Q: how to identify whether the data processed had a good anomalous signal? | |||
A: look at anomalous correlation: if it is > 90% at low resolution it is definitely good. | |||
---- | |||
Q: All my crystals are split, and HKL200 has a hard time indexing the unit cell using sequential | |||
frames. However, iMOSFLM does a really good job indexing using orthagonal frames. Can XDS | frames. However, iMOSFLM does a really good job indexing using orthagonal frames. Can XDS | ||
index the unit cell using orthagonal frames? | index the unit cell using orthagonal frames? | ||
A: yes. You can define several SPOT_RANGE= keyword/parameter pairs, e.g. SPOT_RANGE=1 1 SPOT_RANGE=90 90 . | |||
---- | |||
Q: What is the best way to create mtz files? With the Xscale/xdsconv I often obtain intensity values that are marked *** stars - probably overshooting a formatting limit. | |||
A: do you mean the *** stars appear in the output of mtzdump? That would be a problem of mtzdump only, and irrelevant for the use of the MTZ file. The XDS/XSCALE/XDSCONV route should not produce these stars (the proper Fortran formats are used throughout). | |||
---- | |||
Q: How does one check you've got the ice-rings excluded correctly ? (ie Is there a visual way of | |||
checking?) | checking?) | ||
A: look at the Wilson plot. | |||
---- | |||
Q: The background range is defined as first 5 degrees by default. Is this an assumption that the background (used in Integrate?) remains consistent over the entire dataset valid? The spots over the entire dataset still have background corrected based on first 5 degrees? | |||
A: No. The INIT step uses the first 5 degrees (by default) for a number of purposes (check out the files written by INIT !). BKGINIT.cbf is essentially used only for scaling purposes; the ''real'' background calculation just requires the frame which has the reflections whose background. | |||
background | |||
Revision as of 00:01, 28 February 2010
These are answers to questions that were asked concerning XDS, on the occasion of the webinar on Feb 25, 2010. Some answers were given during the webinar; these are not repeated here.
Q: Is there a way to automatically set the high resolution limit based on an I/sigma cutoff?
A: no.
Q: How does one define the beam stop shadow? Is it possible to develop a simple method, e.g. the ignore circle and ignore rectangle of HKL2000?
A: VALUE_RANGE_FOR_TRUSTED_DETECTOR_PIXELS= and UNTRUSTED_RECTANGLE= are the primary means. UNTRUSTED_CIRCLE may be implemented soon.
Q: Can one apply the corrections in CORRECT without deleting outliers (i.e. waiting for a later program e.g. SCALA to do outlier rejection).
A: you may set WFAC1 to 100 (default is 1)
Q: What is LATTICE-CHARACTER in CORRECT.LP ?
A: the definitive answer is at 9.2.5. Lattice characters in International Tables A.
Q: any comments on compatibility with Pilatus detector?
A: fully compatible & well tested
Q: How accurate need to be the ORGX, ORGY? Can XDS optimize the beam position?
A: the error should be less than half the minimum spot separation. XDS does optimize the beam position.
Q: I can not find generate_XDS.INP in XDSwiki page
A: try http://strucbio.biologie.uni-konstanz.de/xdswiki/index.php/Generate_XDS.INP
Q: the url for detector templates on slide 6 denied my visits
A: try http://www.mpimf-heidelberg.mpg.de/~kabsch/xds/html_doc/xds_prepare.html
Q: can I use xdisp (part of denzo) to find out the beamstop position and use it for xds?
A: unfortunately, the conventions of the different data reduction programs are not the same, but there is always a simple transformation between them, like x' = y; y' = x or some such. You can easily find that out for yourself.
Q: for anomalous dataset, if there is radiation damage, how do I find out where to best cut off the frames for processing?
A: there are no hard rules. One possibility is to look at the anomalous correlation printed in CORRECT.LP for subsets of the data. If those numbers drop after frame X, you should probably not use frames after X.
Q: How do you interpret the DECAY.cbf file?
A: Using XDS-Viewer: along the x direction, you find the "integration batches" (last frames on the right). Along the y direction, the resolution ranges. The shades of gray correspond to numbers - move the mouse across them. The numbers are scalefactors multiplied with 1000.
Q: What about overlapping reflections in XDS?
A: If I understand your question correctly: reflections that occur on the same position of the detector, and on the same frame, are not deconvoluted by XDS (there are programs which may be able to do this but I have not used them so far, and cannot comment on them). Reflections that are either spatially (x,y) or rotationally (in phi) separated are not a problem, they are treated very adequately by XDS (read about the pixel-labelling method!)
Q: if one compares data integrated with the different programs (XDS, mosflm, hkl2000...): is there any difference in the final quality of the data set?
A: yes, because the programs implement different ideas.
Q: Is there a way to automatically set the high resolution limit based on and I/sigma cutoff?
A: no.
What about very low resolution data, 5 to 10 A range with the rather high mosaicity of few degrees? Any experience with processing of such data with the XDS?
A: yes, I have lots of experience with bad data. It should be possible to process these data. You may want to specify BEAM_DIVERGENCE= BEAM_DIVERGENCE_E.S.D.= REFLECTING_RANGE= REFLECTING_RANGE_E.S.D.= in XDS.INP, and to use REFINE(INTEGRATE)=
Q: You said that the XDS deals with high mosaicity. How high mosaicity is still manageable?
A: I don't have exact numbers. Maybe up to ten degrees?
Q: Could you give recommendation for MAD data processing, to get best anomalous?? How to process the 3 data sets with the same orientation matrix, should we use reference datataset?
A: First question: see XDSwiki. Second question: yes.
Q: It would be nice to have a Table with Rfactors for each Image to identify xtal damage. I meant Table with Ractor over Image in CORRECT.LP
A: XDSSTAT produces this table.
Q: Is it possible to exclude images inside the frame range from integration?
A: just remove them from the directory, or change their name. Or create a directory with symlinks only to those file you want XDS to use.
Q: how to identify whether the data processed had a good anomalous signal?
A: look at anomalous correlation: if it is > 90% at low resolution it is definitely good.
Q: All my crystals are split, and HKL200 has a hard time indexing the unit cell using sequential frames. However, iMOSFLM does a really good job indexing using orthagonal frames. Can XDS index the unit cell using orthagonal frames?
A: yes. You can define several SPOT_RANGE= keyword/parameter pairs, e.g. SPOT_RANGE=1 1 SPOT_RANGE=90 90 .
Q: What is the best way to create mtz files? With the Xscale/xdsconv I often obtain intensity values that are marked *** stars - probably overshooting a formatting limit.
A: do you mean the *** stars appear in the output of mtzdump? That would be a problem of mtzdump only, and irrelevant for the use of the MTZ file. The XDS/XSCALE/XDSCONV route should not produce these stars (the proper Fortran formats are used throughout).
Q: How does one check you've got the ice-rings excluded correctly ? (ie Is there a visual way of checking?)
A: look at the Wilson plot.
Q: The background range is defined as first 5 degrees by default. Is this an assumption that the background (used in Integrate?) remains consistent over the entire dataset valid? The spots over the entire dataset still have background corrected based on first 5 degrees?
A: No. The INIT step uses the first 5 degrees (by default) for a number of purposes (check out the files written by INIT !). BKGINIT.cbf is essentially used only for scaling purposes; the real background calculation just requires the frame which has the reflections whose background.