Within the full file you can find many options that can be changed which are commented out.

Please refer to the PYTHIA manual to get the full description to see if you will require some of the options that by default I commented out.

Selection of Events

With no pT filtering, file size at the mDST level starts rapidly increasing and exceeding CPU time. thus keep sel Nmax to reasonable numbers. I tested the following without exceeding the standard CPU time of 280000:

===================================

• With a pT cut of 0.7GeV/c:

Accepted events (sel): 2000 . Total Number of generated events (Nmax): 1000000

-Average mDST size is 4MB

-Time to complete 100 submitted jobs (tuesday morning): 30 min.

• No filtering (all events accepted)

sel : 500, Nmax: 501.

-Average mDST size is 8.4MB

-Time to complete 100 jobs (wed morning): 2 hours

Most of the time is spent during the mDST conversion of low mometum tracks Pythia in fact is the fast part of this chain.

If you need large statistics just submit more jobs and then collect the goods. I will ask Damien soon what is the upper limit of CPU time allowed on the machines. I ran some unfiltered jobs with an increased requested cputime (specified in ProdPythia.csh ) to 980000 with no problems. Of course this takes longer time to process. One job took 1 hour and average mDST size was 24MB (2000 events muN)

====================================

// sel Nmax Npri

• MAIN NGEV 1000 1000000 2

//1:nondifractive only, 2:all

• PYTHIA SET MSEL=2

// Select mode (-1 no selection, 2-Filtering (1h))

• FILTER SELECT -1

// high pT thetamax-magnet acceptance, only works with filtering // (-1 no selection, -2 depend on vertex pos)

• FILTER THETAMAX -2

// pT selection, only works with filtering

• FILTER PT1 0.7

-- AstridM - 15 Feb 2010