Dear Charles,BLEND assumes data to be continuous sweeps, i.e. they should not
include gaps. A valid data set,for example, could go from image 1 to image 100;
an invalid one from 1 to 20 and, say, 22 to 100 - forsome reason image 21 has
gone missing.
This can be annoying, I know, and, indeed, a future version of BLEND will
eliminate this feature.
A typical case where datasets include gaps is when they are collected with the
inverse beamstrategy. In this case one should use programs like rebatch
(keyword REJECT) on two identicalcopies of each dataset and eliminate in turn
one wedge from them.
There could be other reasons why files are rejected, but I need to look at one
of your datasets to get moredetails.
J
Dr James Foadi PhD
Membrane Protein Laboratory
Diamond Light Source Ltd.
Diamond House
Harwell Science and Innovation Campus
Didcot
Oxfordshire
OX11 0DE
United Kingdom
office email: james.fo...@diamond.ac.uk
alternative email: j.fo...@imperial.ac.uk
personal web page: http://www.jfoadi.me.uk
On Thursday, 19 March 2015, 16:01, CPMAS Chen cpmas...@gmail.com wrote:
Dear All,
when I use BLEND to analyze XDS-POINTLESS processed mtz files, some are
reported as invalid datasets. Do you guys have some suggestions on what could
be wrong with the datasets?
I processed these datasets in the same way, XDS and then POINTLESS. I am
looking the detail of the processing. Meanwhile, I would like to know what
others could make these datasets invalid as judged by BLEND.
I have tried to use the XDS_ASCII.HKL, the same invalid datasets.
Thanks!
Charles
--
***Charles ChenResearch
AssociateUniversity of Pittsburgh School of MedicineDepartment of
Anesthesiology**
