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