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