Re: [Brahms-dev-l] Drift Velocity calibration

Hi Truls and Selemon,

Thanks for the info. The issue is most likely that the T1 drift fibres did not work for those 10's run. The calibration were done
already once, but T1 tracks should point to t2 fibres. This is possible and was done for sets of run, but again I do not recall
how it was done, but invloves changing the 'name' and the distance parameters

Flemming

--------------------------------------------
Flemming Videbaek
Physics Department 
Bldg 510-D
Brookhaven National Laboratory
Upton, NY11973

phone: 631-344-4106
cell:       631-681-1596
fax:        631-344-1334
e-mail: videbaek @ bnl gov
----- Original Message ----- 
From: "Truls Martin Larsen" <trulsml_at_nbi.dk>
To: "Bekele, Selemon" <bekeleku_at_ku.edu>
Cc: <brahms-dev-l_at_lists.bnl.gov>
Sent: Tuesday, February 27, 2007 4:37 AM
Subject: Re: [Brahms-dev-l] Drift Velocity calibration


> Hi Selemon,
> 
> First you need to get the raw data files from HPSS, and convert them
> into root format. This and everything else you do with the scripts in 
> ~bramreco/DataProduction/run05/calibTPC
> 
> Using the script: masterTPCCal.sh to submit jobs...
> (use -s and -j option when you get the files from HPSS (getSequences.C),
> and log onto rcrsuser4)
> 
> --run-list : is a usefull option to write all the run number you want to
> calibrate.
> 
> Run masterTPCCal.sh from some rcas mashine when using
> calibrateFibDrift.C as argument.
> 
> And you are right about the numbers.
> 
> Cheers,
> Truls
> 
> 
> 
> On Mon, 2007-02-26 at 18:10 -0600, Bekele, Selemon wrote:
>> Hi,
>> 
>> 1) I see the following piece of code in the script for drift velocity
>> calibration of T1 and T2. It seems there is some root files to be
>> used as input but it is not clear what the files are and where to find
>> them.
>> 
>> -------------------
>> BrIOModule* inputModule = 
>>     new BrEventIO("inputModule", "Input Module");
>>   inputModule->SetIOMode(BrIOModule::kBrRunFile|
>>                          BrIOModule::kBrReadFile);
>>   for (Int_t j = 0; j < nRuns; j++) 
>>     inputModule->AddFileSet(includeOption->GetValue(), 
>>                             Form("^run%06dseq.*.root$", 
>>                                  runOption->GetValue(j)));
>>   mainModule->AddModule(inputModule);
>> ---------------------
>> 
>> 2) Here is another piece of code that I would like to understand.
>> The suggestion made to me was to use the T2 information to calibrate
>> the T1 drift velocity. What are the values in the arrays below?
>> Is it enough to just use post2 instead of post1 is input, as done below, 
>> to do the calibration. I am also trying to do the TFW2 calibrations in CuCu.
>> It would be helpful if anyone has done this before and comment at least to
>> save time.
>> 
>> --------------------------
>>   Float_t post1[5]   = {5.0, 2.5, 0.0, -2.5, -5.0};
>>   Float_t post2[5]   = {0.0, 2.5, 5.0, -2.5, -5.0};
>>   Float_t t1adc[5] = {400, 400, 400, 350, 600};
>>   Float_t t2adc[5] = {400, 400, 300, 400, 600};
>> 
>>  for(Int_t i = 1; i < 5; i++) {
>>     
>>     t1driftfibmodule->SetFibreAdcCuts(i, 375);
>>     //t1driftfibmodule->SetFibreYPosition(i, post1[i]);
>>     t1driftfibmodule->SetFibreYPosition(i, post2[i]);
>>   }
>> --------------------------
>> 
>> Thanks in advance,
>> 
>> Selemon
>>   
>> 
>> 
>> _______________________________________________
>> Brahms-dev-l mailing list
>> Brahms-dev-l_at_lists.bnl.gov
>> http://lists.bnl.gov/mailman/listinfo/brahms-dev-l
>> 
> 
> _______________________________________________
> Brahms-dev-l mailing list
> Brahms-dev-l_at_lists.bnl.gov
> http://lists.bnl.gov/mailman/listinfo/brahms-dev-l
>
_______________________________________________
Brahms-dev-l mailing list
Brahms-dev-l_at_lists.bnl.gov
http://lists.bnl.gov/mailman/listinfo/brahms-dev-l