Re: [Brahms-dev-l] Making ltr files

Hello.  As I said in the earlier mail, HPSS will go down on the next 
Monday (until possibly Friday).  This means that you can not submit any 
ltr jobs from late evening of this Sunday to the end of the next week. 
Make sure to plan around this HPSS outage.

Hiro

Bekele, Selemon wrote:

>Hi brahms,
>
>      I want to get started making ltr files. It would be great if
>someone from Europe can help out with this to run continueosly when
>it is night time here in the US. 
>
> Truels, would you be able to help with this?
> If not, would anyone be able to help with this? 
>
>Here is the plan if someone volunteers to help out:
>--------------------------
>Data disks to be used
>
>data10,data11,data12,data13,data14,data17,data18
> 
>########## Important #############
>Make sure that the line
>
>set datadir=/brahms/dataXX/
>
>is updated and the shell script "updateScripts.sh" is run
>before submitting jobs so that the output would go to the
>specified data directory
>
>I will use 
>   data10,data11,data12
>
>and the other person would use
>   data13,data14,data17,data18
>
>###################################
>----------------------------
>I will submit jobs for runs
>
>12224 - 12198
>
>Someone from Europe will submit
>
>12199 - 13612 
>----------------------------
>
>Thanks in advance,
>
>Selemon,
>
>#####################################################################
>Below is some instructions from Hiro about making ltr/gtr/dst files
>
>To anybody who wants to analyze ltr/gtr/dst in the official way, here is 
>the steps.  (By the way, there was no pp in run01)  (NOTE:  Please 
>change production version.  See the stop no 10. )
>
>For ltr.
>1.  logon to a rcas machine as bramreco
>2.  change directory to DataProduction directory by "cd DataProduction"
>3.  create an appropriate directory.  For example, for pp runs in RUN 02 
>at sqrt(s_NN) =200 GeV, you would do "mkdir -p run02/pp/200/ltr"
> (NOTE:  make sure to follow the format.  The first one is run period.  
>The second one is specie.  And, the third one is energy.  And the last 
>one is type of data that you want to create.
>4.  change to that directory
>5.  copy the updateScript.sh from other production runs (for example, 
>from run03/pp/200/ltr/updateScript.sh)
>6.  Copy/create the bratmain script for your (ltr) job.  (NOTE:  Your 
>old script may/may not work.)
>7.  Change the content of the script (updateScript.sh) accordingly.  Pay 
>particular attention to "set" statement.  For example, your homedir 
>should be "/brahms/u/bramreco/DataProduction/run02/pp/200/ltr" in the 
>above example.  "configscript" should be what you just made in step 6.  
>The "datadir" is output directory.  You can find the use of our data 
>disk by DataFileUsage.perl.  "basedir" should be 
>"/brahms/u/bramreco/DataProduction/scripts/ltr".
>8.  run updateScript.sh   This will copy all necessary files from the 
>repository and change the content accordingly to your updateScript.sh
>9.  If you are remaking the production runs after substantial change in 
>brat, it is highly adviserable (and sometimes required) to make a new 
>production version. You can view and create production version  at 
>http://brahms-web.brahms.bnl.gov/daq-cgi-bin/EnterNewProduction.pl
>10.  The change the production version number in submitLtr.perl script 
>according to new production version number.
>11.  Now, you are ready to submit your job.  Log on the rcrsuser4 
>machine instead of rcas.  Then, you submit jobs by "./submitLtr.perl -u 
>yourusername firstRunNo lastRunNo" at the directory you just created.
>12.  You can monitor the progress by crs_status and crs_panel
>
>Hiro
>_______________________________________________
>Brahms-dev-l mailing list
>Brahms-dev-l@lists.bnl.gov
>http://lists.bnl.gov/mailman/listinfo/brahms-dev-l
>  
>

_______________________________________________
Brahms-dev-l mailing list
Brahms-dev-l@lists.bnl.gov
http://lists.bnl.gov/mailman/listinfo/brahms-dev-l