[Eg6_analysis] [Lowq] Meeting tomorrow

Raffaella De Vita devita at jlab.org
Thu Dec 16 19:24:10 EST 2010


Hi Lamiaa,
I have modified the ana and user_ana packages to had the correct 
helicity information to the nutple. You can find the modified code in 
/work/clas/disk4/test_devita/packages . I basically added to variables 
to nt10, called helicity and hel_ofl. To activate this piece of code 
there is a tcl variable named lhelcore that needs to be set to 1 and to 
pass the name of the helicity table file to user_ana. This is done in 
the tcl file you can find in /work/clas/disk4/test_devita/test : it's 
the one I got from you with these two extra lines. The first contains 
the reported helicity information and the second the corrected one. They 
are not just one bit because I'd like to have for now a bit more info 
(basically the sync and quartet signals) to do some debugging. While 
implementing this piece of code, I found in fact something weird in the 
helicity information: the helicity and sync signal that are recoded 
event by event do not change synchronously with the helicity scaler 
which counts the number of helicity states. This changes a few events 
before than the other variables, which is not supposed to happen. I 
talked to Hovanes about it and we may have found the reason for that but 
we will need to do some more debugging to make sure everything is under 
control. Once this is fully understood we should also discuss of the 
best way to store the helicity information in the ntuple to avoid 
wasting disk space and whether we want to add the correct helicity 
information to the bos files too.
Cheers
     Raffaella

Lamiaa El Fassi wrote:
> Hi Stepan,
>
> For the software, I will leave the two outputs [1] & [3] combined for 
> this cooking too.
> However, I will add the helicity modification when Raffaella is done 
> with it.
>
> As for 1.2 GeV runs, we have two run periods. First from 61216 till 
> 61482 with
> 109 production runs. Second set is from 61931 till 61966 with 25 
> production runs.
> So, a total of 134 runs will be processed. Those run numbers is based 
> on the list
> of good runs study that I did after the pass0_v1 cooking. Some of 
> these runs are
> very long. They contain more than hundred files which means A* and B* 
> extension
> on the raw data. Until now I am processing just the A extension, shall 
> I add the B files
> also to this cooking? I can expect that this cooking will be done in 
> maximum one week
> depends on how much Auger will be busy in this period?
>
> As for the output files, usually I am producing just the SEB NT10 
> ntuple and the BOS
> files when I am cooking to Raphael. But in case some other people 
> might be interested
> to analyse these data, I may produce the full list of output files:
>   - ROOT files: CLASTOOL & H2ROOT root ntuples.
>   - SEB Nt10 ntuple.
>   - BOS files
>   - ANAHIST hbook file
>   - Helicity correction file
>   - LOG files
> I will manage to save the SEB ntuple in the claseg6 work disk and copy 
> all others files to
> the auto-managed work disk but they will be linked to the claseg6 work 
> disk. I will leave the
> IC banks active on those outputs but if there is no objection I may 
> turn off the hodoscope
> banks.
>
> Best regards,
>
> Lamiaa
>
> ************************************************************
> *  Lamiaa El Fassi             email: elfassi at jlab.org 
> <mailto:elfassi at jlab.org>
> *  Research Associate @ Rutgers University
> *  Phone: (757) 269-7011 // Fax: (757) 269-5703
> *  Jefferson Lab., 12000 Jefferson Ave.
> *  Suite# 4, MS 12H3
> *  Newport News, VA. 23606
> ************************************************************
>
>
> On Wed, Dec 15, 2010 at 11:28 PM, Stepan Stepanyan <stepanya at jlab.org 
> <mailto:stepanya at jlab.org>> wrote:
>
>     Hi Lamiaa,
>
>     You can leave changes for DC as they are, no problem.
>     For 1.2 GeV one output [1] will be enough. But if you
>     do not want to touch the code you can leave as it is
>     [1] and [3]. Since this is again mostly for Raphael for
>     the RTPC calibration, we do not want to select events
>     with restriction on a track in RTPC.
>
>     How long the cooking of 1.2 GeV takes, all the files of
>     all good runs.
>
>     Thanks, Stepan
>
>     On 12/15/10 2:46 AM, Lamiaa El Fassi wrote:
>>     Hi Stepan,
>>
>>     Up to now, user_ana codes are up-to-date since we didn't do any
>>     changes since
>>     the previous cooking except the DC initial fit parameters that I
>>     changed to make
>>     them similar to dc3. Shall I leave them like that?
>>     In the previous cooking we decided to combine
>>     - [1] a negatively charged TB track
>>     - [3] a positively charged track with at least 2 neutrals (in any
>>     EC - IC combinations)
>>     in the produced bos file. We turned off the other two outputs:
>>     - [2] a good electron and a positively charged particle (I made a
>>     change)
>>     - [4] at least 1 track in RTPC and at least 2 neutrals in  (any
>>     EC - IC combinations)
>>
>>     I think last cooking choice is okay for the RTPC calibration
>>     since I already used it on
>>     some cooking for Raphael, unless you may want to add the RTPC
>>     track to this
>>     cooking outputs. Please let me know which output configuration
>>     shall we use in this
>>     cooking.
>>
>>     I will wait for the new helicity modification by Raffaella to
>>     implement it into our
>>     cooking packages. She already contacted me to get the tcl file to
>>     run some test
>>     after the helicity modification that she did to her cooking codes
>>     version.
>>
>>     Best regards,
>>
>>     Lamiaa
>>
>>
>>     ************************************************************
>>     *  Lamiaa El Fassi             email: elfassi at jlab.org
>>     <mailto:elfassi at jlab.org>
>>     *  Research Associate @ Rutgers University
>>     *  Phone: (757) 269-7011 // Fax: (757) 269-5703
>>     *  Jefferson Lab., 12000 Jefferson Ave.
>>     *  Suite# 4, MS 12H3
>>     *  Newport News, VA. 23606
>>     ************************************************************
>>
>>
>>     On Tue, Dec 14, 2010 at 9:32 AM, Stepan Stepanyan
>>     <stepanya at jlab.org <mailto:stepanya at jlab.org>> wrote:
>>
>>         Hi Lamiaa,
>>
>>         On the meeting today we decided to not wait for IC calibration
>>         and cook 1.2 GeV for Raphael for RTPC work. What we need to
>>         do is to make sure code is up to date. Raffaella mentioned that
>>         she can add helicity calculations into it within this week. For
>>         1.2 GeV we do not need any output but electron events.
>>         Let's work towards having everything ready for 1.2 GeV cooking,
>>         all of the good runs, by the end of the week. Let me know what
>>         we are missing and what we need to accomplish this goal.
>>
>>         Thanks, Stepan
>>
>>
>>         On 12/13/10 9:49 PM, Lamiaa El Fassi wrote:
>>>         Hi Stepan,
>>>
>>>         Sure we can talk about that whenever you want. Please let me
>>>         know when
>>>         it's convenient for you and I will call you.
>>>
>>>         Best regards,
>>>
>>>         Lamiaa
>>>
>>>         ************************************************************
>>>         *  Lamiaa El Fassi             email: elfassi at jlab.org
>>>         <mailto:elfassi at jlab.org>
>>>         *  Research Associate @ Rutgers University
>>>         *  Phone: (757) 269-7011 // Fax: (757) 269-5703
>>>         *  Jefferson Lab., 12000 Jefferson Ave.
>>>         *  Suite# 4, MS 12H3
>>>         *  Newport News, VA. 23606
>>>         ************************************************************
>>>
>>>
>>>         On Mon, Dec 13, 2010 at 6:23 PM, Stepan Stepanyan
>>>         <stepanya at jlab.org <mailto:stepanya at jlab.org>> wrote:
>>>
>>>             Hi Lamiaa,
>>>
>>>             Thanks for the email. Sorry we did not cross today. I am
>>>             on "vacation" but I come for few meetings.
>>>
>>>             One thing I wanted to talk to you is the preparation of the
>>>             software for the next cooking, including outputs. I guess
>>>             we can do it offline.
>>>
>>>             Have a safe flight.
>>>
>>>             Stepan
>>>
>>>             On 12/13/10 6:10 PM, Lamiaa El Fassi wrote:
>>>>             Hi Stepan,
>>>>
>>>>             I was willing to stop by to talk to you today but I
>>>>             didn't have a chance to do so and it seems you are on
>>>>             vacation. I am leaving tomorrow morning and I am not
>>>>             able to attend the meeting since my flight is on the
>>>>             same meeting time.
>>>>
>>>>             Best regards,
>>>>
>>>>             Lamiaa
>>>>
>>>>             */Sent from my MOTOBLUR™ smartphone on AT&T/*
>>>>
>>>>
>>>>             -----Original message-----
>>>>
>>>>                 *From: *Stepan Stepanyan <stepanya at jlab.org>
>>>>                 <mailto:stepanya at jlab.org>*
>>>>                 To: *eg6_analysis at jlab.org
>>>>                 <mailto:eg6_analysis at jlab.org>, lowq at jlab.org
>>>>                 <mailto:lowq at jlab.org>*
>>>>                 Sent: *Mon, Dec 13, 2010 16:50:34 GMT+00:00*
>>>>                 Subject: *[Lowq] Meeting tomorrow
>>>>
>>>>                 Dear all,
>>>>
>>>>                 We will have eg6 meeting tomorrow Tuesday, December
>>>>                 14, at 9:30am
>>>>                 in room B101.
>>>>                 Agenda items can be found at -
>>>>                 http://clasweb.jlab.org/rungroups/lowq/wiki/index.php/Meeting_on_December_14_at_9:30am
>>>>
>>>>                 Calling instructions can be found at :
>>>>                 http://clasweb.jlab.org/rungroups/lowq/wiki/index.php/Agendas_and_Minutes_of_the_meetings
>>>>
>>>>                 .
>>>>
>>>>
>>>>                 Regards, Stepan
>>>>
>>>>                 _______________________________________________
>>>>                 Lowq mailing list
>>>>                 Lowq at jlab.org <mailto:Lowq at jlab.org>
>>>>                 https://mailman.jlab.org/mailman/listinfo/lowq
>>>>
>>>
>>
>
>
> _______________________________________________
> Eg6_analysis mailing list
> Eg6_analysis at jlab.org
> https://mailman.jlab.org/mailman/listinfo/eg6_analysis
>    



More information about the Eg6_analysis mailing list