Difference between revisions of "SoLID Software idea"
From Hall A Wiki
(→simulation: Simulation output, and local copy of Trajectories and replayability) |
|||
| Line 9: | Line 9: | ||
* Based on initial discussions on simulation I have added a summary of simulation requirements [https://hallaweb.jlab.org/wiki/images/e/e5/Solid_simulation_req.pdf Solid Simulation Req.] (Rakitha Beminiwattha) | * Based on initial discussions on simulation I have added a summary of simulation requirements [https://hallaweb.jlab.org/wiki/images/e/e5/Solid_simulation_req.pdf Solid Simulation Req.] (Rakitha Beminiwattha) | ||
* [https://hallaweb.jlab.org/wiki/images/a/a0/Simulation_output.pdf Simulation output] Initial ideas on data for output trees (Rich Holmes) | * [https://hallaweb.jlab.org/wiki/images/a/a0/Simulation_output.pdf Simulation output] Initial ideas on data for output trees (Rich Holmes) | ||
| + | * some thoughts from Zhiwen Zhao | ||
| + | ** For the output tree format, I think we definitely need a tree or a bank contain the event info. But the critical thing is that each sub-detector should be able to define it easily and freely. They can have very different truth info and digitization and the requirement can be different at different stage of study. | ||
| + | ** For background mixing, the challenge is that different background have very different rates. For example, we can have photon from pion0 more than an order larger than pion+. Producing a file with enough photons from pion0 may have too little pion+ to do study with meaningful statistics. If we increase number of events by an order, we have enough pion+, but wasting a lot computing time on pion0. The things goes to extreme when combine low energy Em background with hadron background. Therefore, running geant4 with all physics turned on only gives huge amount of low energy EM background, but little hadron background. So far, what we did is to run all background separately, then record background rate at entrance of detectors. Then do a separate simulation again for the detector with background thrown onto it accordingly. This maybe ok for single detector study, but is not good for combined detector and DAQ study. We need to think of a solution from the top. | ||
= reconstruction = | = reconstruction = | ||
Revision as of 14:12, 31 March 2015
SoLID software idea page
feel free to record any thing you want to share
general
simulation
- Trajectories and replayability (Rich Holmes)
- Based on initial discussions on simulation I have added a summary of simulation requirements Solid Simulation Req. (Rakitha Beminiwattha)
- Simulation output Initial ideas on data for output trees (Rich Holmes)
- some thoughts from Zhiwen Zhao
- For the output tree format, I think we definitely need a tree or a bank contain the event info. But the critical thing is that each sub-detector should be able to define it easily and freely. They can have very different truth info and digitization and the requirement can be different at different stage of study.
- For background mixing, the challenge is that different background have very different rates. For example, we can have photon from pion0 more than an order larger than pion+. Producing a file with enough photons from pion0 may have too little pion+ to do study with meaningful statistics. If we increase number of events by an order, we have enough pion+, but wasting a lot computing time on pion0. The things goes to extreme when combine low energy Em background with hadron background. Therefore, running geant4 with all physics turned on only gives huge amount of low energy EM background, but little hadron background. So far, what we did is to run all background separately, then record background rate at entrance of detectors. Then do a separate simulation again for the detector with background thrown onto it accordingly. This maybe ok for single detector study, but is not good for combined detector and DAQ study. We need to think of a solution from the top.
