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.
APPENDIX A-INPUT CARDS<br />
The input to DELSOL is accomplished through the use of namelists. Namelists<br />
are a convenient <strong>for</strong>m of input because any <strong>for</strong>mat can be used <strong>for</strong> the input vari-<br />
ables, the variables can be specified in any order and the only variables that need<br />
to be input are those which differ from the default values. However, each namelist<br />
must be input in the order shown in Tables A-1 and A-2, even if no variables in a<br />
namelist are redefined. The namelists are grouped into similar types of variables<br />
(e.g., Namelist HSTAT contains all of the heliostat definition inputs).<br />
There are two types of problems that are run on DELSOL: per<strong>for</strong>mance cal-<br />
culations and design optimization calculations. In a per<strong>for</strong>mance calculation the<br />
user defines a single system and DELSOL calculates the optical per<strong>for</strong>mance <strong>for</strong><br />
that system at a single time or day and/or on an annual basis. In a design opti-<br />
mization calculation the user specifies the heliostat, receiver geometry, and range<br />
of all the optimization variables and DELSOL searches <strong>for</strong> the set of optimization<br />
variables that minimizes the energy cost. In the design search DELSOL analytically<br />
"scales" the results of an initial per<strong>for</strong>mance calculation. These initial per<strong>for</strong>mance<br />
results can be generated in the same computer run as the design optimization or<br />
can be read off a file that was generated during a previous computer run. Finally,<br />
the results of the design optimization can be automatically used as input to a de-<br />
tailed per<strong>for</strong>mance run or can be written on a file <strong>for</strong> subsequent calculations or <strong>for</strong><br />
plotting.<br />
The input cards <strong>for</strong> a per<strong>for</strong>mance calculation are listed in Table A-1. The first<br />
card is a title card. The six namelists that follow specify the system to be analyzed.<br />
If the user wants to read in the coordinates of the heliostats instead of specifying<br />
zones of heliostats, these data cards follow the NLEFF namelist. Finally, the REC<br />
namelist with W=-100 terminates the problem. This arrangement of input cards<br />
should be used <strong>for</strong> either a user specified system or <strong>for</strong> a per<strong>for</strong>mance rerun of a<br />
system previously optimized by DELSOL and stored on a file on Unit 30.<br />
The input cards <strong>for</strong> a design optimization calculation are shown in Table A-2.<br />
The first card is the title card. The next six namelists (BASIC .... NLEFF) define the<br />
initial per<strong>for</strong>mance calculation. The values on these cards fix the zoning, latitude,<br />
insolation model, heliostat design and heliostat focusing/canting strategy to be<br />
used during the optimization. If these values will be used again in another design<br />
optimization calculation, the results should be saved. To do this, set ITAPE=l in<br />
Namelist BASIC and store the local file generated on Unit 10 as a permanent file.<br />
When this initial per<strong>for</strong>mance calculation is to be used in a subsequent design run,<br />
attach a copy of the stored data to DELSOL as a local file on Unit 20, set ITAPE=2<br />
in Namelist BASIC and omit the FIELD, HSTAT, REC, NLFLUX, and NLEFF<br />
namelists that follow the BASIC namelist. The REC, OPT, NLFLUX, NLEFF,<br />
NLCOST, and NLECON namelists define the optimization values. If a detailed<br />
per<strong>for</strong>mance calculation of the optimized design is required, set IRERUN=l in<br />
Namelist OPT and provide the six namelists after the NLECON namelist as shown<br />
in Table A-2. Usually it is not necessary to redefine any variables in these namelists<br />
169