Hi Phil,Thanks for your email. I did get it to work with the options you
suggested .
i.e
Toggle ON "Override automatic definition of runs to mark discontinuities in
data
Toggle ON Define Runs
Toggle OFF Use run 1 as reference run.
Setup runs as follows ( intended to exclude batches 200 to 400
You are right: this is a bug I should fix sometime
Assigning two runs should work though
You should not assign a reference run, and you shouldn't need to
reassign the datasets
Best wishes
Phil
On 14 Mar 2008, at 21:45, hari jayaram wrote:
Hi.
I did try that beforehand when I tried exclud
Hi.
I did try that beforehand when I tried excluding a "range" of batches with
the ccp4i gui
But I got an error
Scala: *** Gap in "time" (rotation) ***
Sorry...both versions of the protocol for handling a bad internal wedge are
giving me either a "gap in rotation" error or a "Run 2 has no
In ccp4i Scala task, click to open the "Excluded data" panel, click on
"Exclude selected batches"
There you can define one or more ranges of batches or lists to exclude
If you just want to exclude the last part you can define a range eg
301 to 999
You don't need to explicitly define runs
Hi.
Based on your explanation it looks like you want to remove your "RUN 1
REFERENCE" and "EXCLUDE BATCH 400 TO 500" lines from your script. You might
also want to try without the NAME lines on the off chance that the harvesting
stuff is causing the problems.
My best guess is that the "RUN 1
