In MCNP-BRL particle tracking and boundary crossing mechanisms are performed using BRL-CAD’s ray-tracing algorithm. (The problem geometries and errors in the geometry declarations are identical for both codes.) In this way detailed information was obtained to integrate the error-handling mechanisms, especially for geometry errors and MCNP-like error reporting mechanisms to the GIFT library API. In this set the numerical experiments were conducted for erroneously defined input cards or incorrectly defined geometries. The second set of test problems was used to test and improve the GIFT library API. The results of these studies verified that MCNP-BRL supports the entire standard MCNP features except those listed in “Supported MCNP Features” above. These numerical experiments were conducted to ensure both codes produce identical results or agree with each other within the statistical uncertainties. Problems were constructed to directly test MCNP features, such as source declarations, tally declarations, variance reduction mechanisms, etc., individually or collectively. For each test problem, special attention was given to maintain geometric consistency, to the extent possible/feasible, between MCNP-BRL and MCNP models to enable meaningful systematic comparisons. Set-III: problems to test and further improve the code performance. Set-II: problems to test and improve the GIFT library API, and 3. Set-I: problems to test the functionality of MCNP-BRL compared to the standard MCNP, 2. Three different sets of test problems were designed to comprehensively test MCNP-BRL: 1. However, when/if needed, the MCNP equivalents of these features could be designed and integrated. These features have been deactivated because they are not needed within current projects. In the current version of MCNP-BRL, all of the MCNP features are operational except the following items: (1) mode: e electron transport, (2) surface sources (including read/write), (3) surface tallies, (4) lattices/repeated structures, and (5) transformations. ![]() ![]() An additional input file is also required to provide the database filename, material densities, and region/cell volumes to the code package. In other words the user provides the problem geometry in a BRL-CAD geometry database file and the MCNP problem parameters (material declarations, source and tally definitions, variance reduction parameters, etc.) in an MCNP-BRL input file. The problem is initialized on the BRL-CAD geometry model, and the ray tracing required by Monte Carlo transport is accomplished through the BRL-CAD API. In MCNP-BRL execution the first two sections of the MCNP input (cell and surface declarations) are skipped, and a BRL-CAD geometry file is provided in their place. The BRL-CAD model of this armored vehicle consists of many complicated regions, and this model can be used by MCNP-BRL directly (i.e., without modifications to the BRL-CAD model). ![]() A sample BRL-CAD geometry is depicted in Fig. MGED, which enables users to develop geometries without recourse to an expensive CAD application and (5) it is open source, so it is available freely to all potential MCNP-BRL users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |