Hi guys, for some reason I keep getting negative BRBRs when I use may
correction factors. I feel that this is due to either there being
something wrong with my VVF, correction factors or both. To remedy this I
setup two new analyses, one using Concezio's latest tag and another using
Wolfgang's. Failing this, I guess my correction factors would probably be
the problem.
Cheers, C.C.
On Mon, 11 Sep 2006, Concezio Bozzi wrote:
> Yes, if corr_BDFHweights_ip050.txt has been obtained on a dataset where D**
> have been reweighted to 0.551406. If not, you need to take out "-dssRatio
> 0.551496"
> Ciao, Concezio.
>
> CHUKWUDI KWEKU CLARKE wrote:
>> Hi Concezio and Antonio, for the stand point of trying to submit jobs for
>> the all weighting scenario, is the following th correct way to submit my
>> jobs;
>> subVirFit.pl -que xlong -opt 1 -b -d -FF=1 -rew 12 -wF
>> sysWd/HFAGCombWin06_3d_0.txt -cm CM2 -debug -Sun -novarfit -small -tmodel
>> -notunbinmes=3 -fixSBratio corr_BDFHweights_ip050.txt -countmc -minintpur
>> 0.50 -dssRatio 0.551496 -flag corr_BDFHW_ip050_dss
>> for IP cut = 0.5 and using my .txt file, corr_BDFHweights_ip050.txt?
>> Cheers, C.C.
>>
>> On Mon, 11 Sep 2006, Concezio Bozzi wrote:
>>
>>> The VVF command I used in July to determine the D** fraction to be used in
>>> mx unfolded fits is
>>>
>>> ./subVirFit.pl -que kanga -cm CM2 -debug -novarfit -small -tmodel
>>> -notunbinmes=3 -rew 12 -wF sysWd/HFAGCombWin06_3d_0.txt -opt 1 -fitdss 1
>>> -flag fitdss1_nounf_nofixcount -countmc
>>>
>>> -opt 1 sets the 3-parameter fit, -fitdss 1 is used to set the other
>>> component equal to D**lnu decays.
>>>
>>> Concezio.
>>>
>
>
|