|
- Timestamp:
-
Jan 17, 2008, 10:16:11 PM (17 years ago)
- Author:
-
gallmei
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v176
|
v177
|
|
2 | 2 | |
3 | 3 | = GiBUU = |
4 | | The '''GiBUU project''' is aiming to provide an unified transport framework for |
| 4 | The '''GiBUU project''' is aiming to provide an unified transport framework in the MeV and GeV energy regimes for |
| 5 | * '''elementary reactions on nuclei''', as e.g. |
| 6 | * '''electron''' + A, |
| 7 | * '''photon''' + A, |
| 8 | * '''neutrino''' + A , |
| 9 | * '''hadron''' + A (especially '''pion''' + A) |
5 | 10 | |
6 | | * '''electron''', |
7 | | * '''photon''', |
8 | | * '''neutrino''', |
9 | | * and '''hadron''' (especially '''pion''') induced reactions on nuclei, |
10 | 11 | * and for '''heavy-ion collisions'''. |
11 | 12 | |
12 | 13 | For those reactions, the flow of particles is modelled within a Boltzmann-Uehling-Uhlenbeck (BUU) framework. |
13 | | The relevant degrees of freedom are mesons and baryons which propagate in mean fields and scatter according to cross sections which are tuned to the energy range of 10 MeV to more than 10 GeV. |
| 14 | The relevant degrees of freedom are '''mesons''' and '''baryons''', which propagate in mean fields and scatter according to cross sections which are tuned to the energy range of 10 MeV to more than 10 GeV. |
14 | 15 | |
15 | | The new numerical implementation, named '''GiBUU''', is written in modular [http://www.kcl.ac.uk/kis/support/cit/fortran Fortran2003] and based upon a [http://subversion.tigris.org/ Subversion] version control system, which allows for a concise control over the full development phase of the code. |
| 16 | The new numerical implementation, named '''GiBUU''' (standing for '''Gießen''' and '''BUU'''), is written in modular [http://www.kcl.ac.uk/kis/support/cit/fortran Fortran2003] and based upon a [http://subversion.tigris.org/ Subversion] version control system, which allows for a concise control over the full development phase of the code. |
16 | 17 | |
17 | | The [wiki:GiBUU_Code_history history of the code] is rather long and reports about several main development steps. The present inititiative accomplished a total rewrite of the source code in a present-day computing language. The main goals of this effort were ''modularization'' to allow for a more transparent multi-user development process, a strict ''reduction of global variables'' for a more transparent debugging procedure, an ''improved control over the development phase'' such that modifications can be backtracked and a ''unified standard version''. In the past, every member of the team had its own version of the code whereas in the present situation all members are programming in parallel on one single code. The technical overhead which comes with this is compensated by the benefit of a'' faster distribution of improvements and innovations'' and their ''enhanced sustainability''. |
| 18 | The [wiki:GiBUU_Code_history history of the code] is rather long and reports about several main development steps. The present initiative accomplished a total rewrite of the source code in a present-day computing language. The main goals of this effort were ''modularization'' to allow for a more transparent multi-user development process, a strict ''reduction of global variables'' for a more transparent debugging procedure, an ''improved control over the development phase'' such that modifications can be backtracked and a ''unified standard version''. |
| 19 | Therefore every member of the team works on the same single code version, albeit different temporal branches may coexist. Possible technical overhead is compensated by the benefit of a ''faster distribution of improvements and innovations'' and their ''enhanced sustainability''. |
18 | 20 | |
19 | 21 | GiBUU is being developed at the [http://theorie.physik.uni-giessen.de Institut für Theoretische Physik] of the [http://www.uni-giessen.de Justus-Liebig-Universität Giessen]. |
|