This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Need to Generation Glauber Profile Data Has Added Significant Complexity
• DPMJET-II.5 expects the data to be a function of:
− A & Z of projectile
− A & Z of target
− Projectile momentum/nucleon
• If we created data for 2546 projectiles (~301 stable nuclides + ~2245 well-quantified radioactive nuclides) on 301 stable targets = 676,046 combinations ~100 GBytes is full-size ASCII files
generate new data for one momentum only, transfer to DPMJET
N N
Instantiate new GDS objects generate new data (all momenta)
Y
N
Transfer projectile to product vector
DPMJET-II.5 Subroutine DPMEVT
Simulate interaction Transfer information about secondary products to product vector, de-excite nuclear fragments if required and store nuclear de-excitation products
Instantiate new GDS objects & load with data
Instantiate G4DPMJET2_5Model Initialise C++ variables and DPMJET-II.5 common block data Instantiation G4DPMJET2_5Model
Instantiate Glauber DSH object Initialise Glauber DSH variables & clear map of ptr to GDS objects
Define Glauber Data Sets Retrieve ptr to GDSH
Load existing GDS based on projectile – target
Create any new GDS based on projectile – target
Set limits on max # GDS data to be loaded/generated
Instantiate GDS objects & generate new data
Save GDS data to file if required
Unload GDS based on projectile – target
Delete GDS objects
ApplyYourself
DPMJET-II.5 Common blocks accessed through C Struct declarations
Determine projectile and target
Initialise DPMJET-II.5 common block data for interaction
generate new data for one momentum only, transfer to DPMJET
N N
Instantiate new GDS objects generate new data (all momenta)
Y
N
Transfer projectile to product vector
DPMJET-II.5 Subroutine DPMEVT
Simulate interaction Transfer information about secondary products to product vector, de-excite nuclear fragments if required and store nuclear de-excitation products
Instantiate new GDS objects & load with data
Instantiate G4DPMJET2_5Model Initialise C++ variables and DPMJET-II.5 common block data Instantiation G4DPMJET2_5Model
Instantiate Glauber DSH object Initialise Glauber DSH variables & clear map of ptr to GDS objects
Define Glauber Data Sets Retrieve ptr to GDSH
Load existing GDS based on projectile – target
Create any new GDS based on projectile – target
Set limits on max # GDS data to be loaded/generated
Instantiate GDS objects & generate new data
Save GDS data to file if required
Unload GDS based on projectile – target
Delete GDS objects
ApplyYourself
DPMJET-II.5 Common blocks accessed through C Struct declarations
Determine projectile and target
Initialise DPMJET-II.5 common block data for interaction
Review of Existing Sources of Error and Assessment of Approximations to Reduce Demand on No. Data Sets
• There are three sources of error already within the Glauber profile data as used/generated by DPMJET-II.5
− Stochastic errors: generated by MC calculation (up to ~3%)
− MODB interpolation errors i.e. interpolation between different probabilities->impact parameters shown in page 2 (80% of data within error of ~10% for light proj/targets, rising to 90% for others)
− Errors in interpolation between different projectile momenta (90% with 3%)
• There is a better way:
− Only generate and store Glauber profile data as a function of Aprojectile and Atarget (typically <3% error)
− Instead of MODB interpolation, fit impact parameter as a function of integral probability: 200 datapoints -> 10 parameters
• Just completed re-writing of code; need to test/debug
• Currently generating Glauber profiles for 2AP 58 and 2 AT 58
• Also, as part of this process, generating cross-sections for all inelastic interactions and intend to produce updated cross-section class for E>2GeV/nuc
− Necessary since currently using Tripathi, Shen or Kox approximations, and Tripathi only seems to be tested to ~2GeV/nuc
• Taking ~4 CPU-months
• Need to extent to 2 AP 240 and 2 AT 240
• Need for proton-nuclear interactions acknowledged