Progress on DART code optimization. Page: 3 of 4
This article is part of the collection entitled: Office of Scientific & Technical Information Technical Reports and was provided to Digital Library by the UNT Libraries Government Documents Department.
The following text was automatically extracted from the image on this page using optical character recognition software:
Works done up to date on different goals:
1. Friendly interface:
A friendly input-output interface was created. To design different windows for
user-aid data input, a visual language (Visual Basic*) was used. This way, data was
collected into 5 groups:
1.1. I/O files definition: including complete path (drive, directory, and file) where
will be written the outcome data.
1.2. Data concerning geometric kind and dimension of fuel assembly to be modeled
1.2.1. Plate, rod or tube
1.2.2. Meat and cladding height, width and thickness
1.3. Data concerning material kind of fuel
1.3.1. Oxide, silicide or vhd
1.3.2. Particle size, grain size, fuel volume fraction, cladding volume fraction,
external -as fabricated- and internal porosity
1.4. Data concerning simulation condition
1.4.1. Fission gas to be considered (Xe, Ar or Kr)
1.4.2. Bubble class to calculate its evolution (bulk, dislocation, grain face and
1.4.3. Number of grain radial partition into equal volume shells
1.4.4. Whole simulation time
1.4.5. External pressure
1.4.6. For the each calculation stage, a matrix array containing step numbers,
linear power, border and centerline temperatures, internal pressure and
printout options was made
1.4.7. Calculation of time step
1.5. Command to start DART execution
2. Unified DART version (oxide, silicide, and advanced alloy fuel)
A revision of different DART versions was made. It was possible to merge these
versions into a single program code, around GRASS subroutine. This subroutine
calculates fission gas bubble distributions according to increasing bubble size and bulk,
dislocation, face and edge classes. It constitutes the core of DART program.
Evolutionary processes like recrystallization, U-Al reaction, amorphization, etc; usual
issues of DART versions are programmed in different subroutines. The new unified
version has respected the calling logic of each version. Material and model constants of
DART versions are resident on respective arrays. For the sake of code unification, it
was built a common array made of shared (model and cladding) data, and a separate
matrix made of specific material properties for each kind of fuel.
Progress made on the first point (friendly input interface) allowed the replacement
of original data reading structure. It contributed to clarify the code logic.
Once the code was purified, it was compiled as a dynamic library link (DLL)
subroutine, to allow the visual interface calling to start calculation process. It was
designed a thread (Win32 application) to create, open, dump data and close auxiliary
files. These files contain evaluated (partial) outcome data.
Here’s what’s next.
This article can be searched. Note: Results may vary based on the legibility of text within the document.
Tools / Downloads
Get a copy of this page or view the extracted text.
Citing and Sharing
Basic information for referencing this web page. We also provide extended guidance on usage rights, references, copying or embedding.
Reference the current page of this Article.
Taboada, H.; Rest, J. & Solis, D. Progress on DART code optimization., article, October 2, 2001; Illinois. (digital.library.unt.edu/ark:/67531/metadc724843/m1/3/: accessed July 20, 2018), University of North Texas Libraries, Digital Library, digital.library.unt.edu; crediting UNT Libraries Government Documents Department.