Difference between revisions of "Radphi MonteCarlo"

From UConn PAN
Jump to navigation Jump to search
Line 1: Line 1:
 
'''To generate Radphi Monte Carlo events steps below are followed:'''
 
'''To generate Radphi Monte Carlo events steps below are followed:'''
 
*Edit the decay.dat[http://zeus.phys.uconn.edu/~mokaya/decayt.dat] file and specify the reaction of interest and number of events to generate.
 
*Edit the decay.dat[http://zeus.phys.uconn.edu/~mokaya/decayt.dat] file and specify the reaction of interest and number of events to generate.
*Run mcwrap[http://zeus.phys.uconn.edu/~mokaya/mcwrap] and specify output name.
+
*Run mcwrap[http://zeus.phys.uconn.edu/~mokaya/mcwrap], mcwrap requires [http://zeus.phys.uconn.edu/~mokaya/cebaf.geom]to run, and specify output name.
 
*Output file generated with output_name.itape(omega.itape).
 
*Output file generated with output_name.itape(omega.itape).
 
*Move this file to the folder Gradphi.
 
*Move this file to the folder Gradphi.

Revision as of 20:05, 9 June 2014

To generate Radphi Monte Carlo events steps below are followed:

  • Edit the decay.dat[1] file and specify the reaction of interest and number of events to generate.
  • Run mcwrap[2], mcwrap requires [3]to run, and specify output name.
  • Output file generated with output_name.itape(omega.itape).
  • Move this file to the folder Gradphi.
  • Edit events.in and control.in files and the run gradphi.x.

Resources needed to generate 100000000 events.

  • The calculation below is based on 300,000 omega events that were generated using mcwrap and reconstructed using gradphi software on gluey.
  • To reconstruct 300,000 events it took 6840 seconds .
Number generated(millions) CPU time per event (s) Output file size (MB) Total time in days
100 0.0216 59000 25