<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello Lamiaa,<br>
<br>
Seems to me everything is well planned. I think any run we have<br>
with production settings of RTPC (HV and gas) that do not have <br>
any obvious problem we should cook.<br>
Personally I do not have preference for CLASTOOL ntuples, if it <br>
is not too much trouble for you I would prefer to generate them.<br>
<br>
Thanks, Stepan <br>
<br>
On 3/14/13 5:31 PM, Lamiaa El Fassi wrote:
<blockquote
cite="mid:CADOiO9rQ7TqMx6SoiLprJSYj4BXDDEQjeq19UW+Ux7Du7pQYZA@mail.gmail.com"
type="cite">Hi All,<br>
<div class="gmail_quote">
<br>
As a readiness of our next Pass1_v1 cooking, I would like to
check with you some information before start processing the
data. <br>
Like Pass1_v0, I will first process the 1.2 GeV data. Its
run-list is attached. I have split this list into two to
separate the special <br>
1H runs from others. I am thinking to process the Hydrogen data
afterwards to store it in Silo under the 1.2 GeV directory, like
<br>
/mss/clas/eg6/production/pass1_v1/1p2gev/1H. In such case, it
will be easy to jcache it if it's needed for any study. Do you
think <br>
it's worthy to do that?<br>
All other data sets will be stored in Silo under directories
tagged with the associated beam energy. I am attaching also the
list <br>
of different dataset runs, which I previously used.<br>
<br>
In addition, please have a look to the attached tcl file and let
me know if any modification is needed. As usual, all calibration
banks <br>
are turned off, even the RTPC ones (TPC and TPCC). If you have
any new preferences, I will be happy to change it! <br>
<br>
In this cooking, I am willing to produce the regular output
files listed below:<br>
1. SEB ntuples,<br>
2. HROOT ntuples,<br>
3. CLASTOOL ntuples, ! Not sure if it is still
required!<br>
4. BOS files<br>
5. ANAHIST files<br>
6. Helicity correction text files,<br>
7. LOG files<br>
<br>
Due to the size of our 1.2 GeV data set, I can save its HROOT
(Anahist/LOG for debugging) files in our permanent volatile
disk. <br>
Hence, it will be easy to access and analyze the new processed
data afterwards. However, this feature may not be possible for <br>
the other data sets (at least for the 6 GeV data!)<br>
<br>
Last but not least, the new processed data will be monitored in
our CSQL web-page under a new table/bullet "Pass1_v1". The
latter <br>
will be quite similar to the latest 1.2 GeV test table <a
moz-do-not-send="true"
href="http://www.jlab.org/Hall-B/secure/eg6/cooking/online_sql/monitor.html">epass1_v11</a>.<br>
<br>
Please feel free to send me any comments or suggestions
concerning the proposed cooking plan and tools.<br>
<br>
Best regards,<br>
<br>
Lamiaa<br>
<br clear="all">
<div>************************************************************<br>
* Lamiaa El Fassi email: <a
moz-do-not-send="true" href="mailto:lamiaa11@fnal.gov">lamiaa11@fnal.gov</a><br>
* Research Associate @ Rutgers University <br>
* Phone: <a moz-do-not-send="true"
href="tel:%28630%29%20840-4861">(630) 840-4861</a>
<br>
* Fermilab, Aspen East #105 <br>
* Batavia, IL. 60510<br>
************************************************************</div>
<br>
<br>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Eg6_analysis mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Eg6_analysis@jlab.org">Eg6_analysis@jlab.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/eg6_analysis">https://mailman.jlab.org/mailman/listinfo/eg6_analysis</a></pre>
</blockquote>
</body>
</html>