|Message: Re: Understanding format of G4NDL data library||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Like Zach, I also need to understand the format for the G4NDL final state data files so that I can more easily verify my code against MCNP. To verify my code in GEANT4 against MCNP, I want to convert the MCNP data for several isotopes into the G4NDL format. I would then use this data instead of the stock data files so that both codes have the same input distributions/parameters. Any differences in results would then be a product of either my code or the base GEANT4 algorithms (or both).|
The cross section files in the G4NDL libraries are easy to understand and replace, but the final state data is not. The data includes headers, but the main identifiers in these headers may be repeated in a single file with different meanings. For example, a 1 followed by a 5 denotes the prompt neutron energy distribution, and then if repeated before the next major section, it means that the prompt neutron energy distribution is created from the G4NeutronHPEvapSpectrum class. Unfortunately, the minor and major headers seem to be indistinguishable.
To make matters worse, the progress of GEANT4 as it reads through a data file is hard to track in the code since file stream pointer is passed between several classes. Reading the input files starts in the G4NeutronHP______FS files where the blank could be Fission, Elastic, Inelastic or Capture, but it is passed on to several other (sub)classes. Thus, trying to reverse engineer the format from the code is tedious at best. It should be noted that the fission and inelastic final state data is the most complicated, whereas the elastic and capture final state data is relatively simple.
It would help me greatly if someone could provide the documentation to the G4NDL format. Failing that, some tips on the organization of the files and how to read them would be appreciated. Additionally, I agree with Zach that many GEANT4 users would benefit from the documentation of these formats.
M.Sc. Student, Nuclear Engineering