A User's Manual for DELSOL3 - prod.sandia.gov - Sandia National ...

directly to the optimization calculations. The next Namelist read after the BA-
SIC Namelist in this case is the REC Namelist that begins the optimization group
of Namelists.
V1.A-5. Optimized System File (Unit $0)-This file is an unformatted file,
written during optimization and read during a final performance run, which con-
tains the description of an optimized design. The user must specify IOTAPE=l
(Namelist OPT) to request that this file be written, and this file must be written
if the user plans to do a final performance calculation on the optimized system.
Once the Unit 30 file is written, the code can either go directly into a final per-
formance calculation if IRERUN=l is specified (Namelist OPT) or execution can
be terminated before doing a performance calculation if IRERUN=O. This latter
option allows the user to save the optimized design file for either a later perfor-
mance calculation, multiple flux map calculations, or as input to a user provided
plotting program.
The options for saving and rerunning optimized systems are illustrated in Fig-
ures VI-1 and VI-2. As seen in the lower part of Figure VI-1, when DELSOL has
finished optimizing a system the optimum design(s) are written to the Unit 30
file. The user should take appropriate action to save the Unit 30 file. To read
the optimized system for a performance calculation, the user attaches a copy of
the Unit 30 file to the program and specifies ITAPE=3 on Namelist BASIC. Re-
member that if IRERUN=l (Namelist OPT) DELSOL does not stop after system
optimization is complete, but immediately starts a new performance calculation
using the optimized system.
The information stored on the Unit 30 file describing the optimum system
becomes the default values for a final performance calculation when that file is
read by specifying ITAPE=3. Specifically, the following are stored on the Unit
file:
site (latitude, weather, insolation, etc.)
field (number and type of zones, heliostat layout)
heliostat (dimensions , reflectivity, canting, focusing)
receiver (type and dimensions)
tower height
flux points (only if flux was calculated during optimization)
The user, therefore, does not have to define these variables. Generally, when re-
running a system in a performance calculation the only variables that the user
redefines are: (1) type of problem (e.g., single time, single day, annual perfor-
mance); (2) flux calculation if different from optimization (more flux points or
different flux surfaces may be examined); or (3) heliostat aim strategies or the
146
30