[buster-discuss] test flag number in BUSTER

[Keitaro Yamashita]

Dear Claus,

> you need a newer BUSTER ;-) ... until then try the 'indirect method':
>
> % refine ... BusterExtraKwds="FREFLG=1" ...
>
> to use the reflection with a flag value of '1' as test-set.
>
> Does that work for you?

Thank you for your instruction. It worked!

CRD files have two lines which include FREFLG=, and the latter ones
reflect the input value.
I confirmed the resultant R-factors differ.

By the way, when will the new BUSTER be available?


Cheers,

Keitaro

2011/4/1 Claus Flensburg <claus at globalphasing.com>:
> Dear Keitaro,
>
> On Fri, Apr 01, 2011 at 12:42:52AM +0900, Keitaro Yamashita wrote:
> ...
>> Claus wrote:
>> > by default '0' is used. You can double-check that by inspecting
>> > the value of the FREFLG keyword in one of the CRD files eg.
>> > % grep FREFLG ./run00/01-BUSTER/Cycle-1/CRD
>> > KEYWORD    FREFLG=0 USESIG BLKBLR=50 MXLCYC=1 MSKRAD=400
>>
>> Checking CRD file, I confirmed test set flag number was correctly chosen.
>>
>> But I always found FREFLG=0 in CRD file though I specified
>> BusterFreeFlagValue= in command line argument.
>> Moreover, trying all flag values, I got the same R/R-free factors.
>>
>> Could you tell me what to check?
>
> you need a newer BUSTER ;-) ... until then try the 'indirect method':
>
> % refine ... BusterExtraKwds="FREFLG=1" ...
>
> to use the reflection with a flag value of '1' as test-set.
>
> Does that work for you?
>
>
> Regards,
>
> ClAuS
>