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 ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
To directly specify such a field, the following variables must be defined: (1) RAD-<br />
MIN, RADMAX, NRAD, NAZM, INORTH, and AMAXN, to set up the zoning;<br />
and (2) NRADMN, NRADMX, DENSIT, AZMSEP, and FLAND, to character-<br />
ize the field zone by zone. In addition, <strong>for</strong> a per<strong>for</strong>mance calculation on a system<br />
optimized by DELSOL (where the results were saved on a file by specifying IO-<br />
TAPE=l in namelist OPT), all of the above variables can be read from the file<br />
by specifying ITAPE=3. In this case, IUSERF=2 will be the code default, and<br />
should not be set by the user to any other value.<br />
For the Lth azimuthal zone (L=l, NAZM) as numbered in Figure 11-4, all ra-<br />
dial zones are occupied from the minimum radial zone number, NRADMN(L),<br />
through the maximum radial zone number, NRADMX(L). If no zones are oc-<br />
cupied in the Lth azimuthal zone, then NRADMN(L)=NRADMX(L)=O. The<br />
radial/azimuthal zone boundaries may not exactly match the boundaries of the<br />
user’s field. The FLAND array can be used to trim the DELSOL zoning. If there<br />
is a land constraint, FLAND will be calculated automatically by DELSOL. In the<br />
absence of a land constraint, the user may specify FLAND. For the (K,L) zone,<br />
FLAND(K,L) is the fraction of the land area in the (K,L) zone that is occupied<br />
by the heliostat field. If the whole zone is occupied, FLAND(K,L)=l.O; if half the<br />
zone is occupied, FLAND(K,L)=0.5, etc. Field averaged per<strong>for</strong>mance is calcu-<br />
lated and reported using this option. This option cannot be used <strong>for</strong> any initial<br />
per<strong>for</strong>mance run which will be used later <strong>for</strong> a field buildup (optimization) run.<br />
d) IUSERF-3<br />
This option allows the user to specify the x and y (east and north) coordi-<br />
nates of the base of every heliostat relative to the tower base. For the per<strong>for</strong>-<br />
mance at a single time (IPROB=2, namelist BASIC), an asymmetrical heliostat<br />
field can be used. However, in order to calculate daily or annual per<strong>for</strong>mances the<br />
field must be symmetric about the N-S axis.<br />
A special convention is used to group and number the heliostats. The he-<br />
liostats are grouped into “rows” as illustrated in Figure 11-7. In a field that sur-<br />
rounds the receiver the rows will usually be completely or partially filled circles.<br />
In a north-only field the rows will be arcs or lines. The rows do not intersect.<br />
The rows are numbered starting with the row nearest the tower and proceeding<br />
outward. Within each row the heliostats are numbered starting with the heliostat<br />
on the N/S line or just east of the N/S line. The numbering increases in a clock-<br />
wise manner around the tower. Note that <strong>for</strong> a line or arc of heliostats (see row<br />
4 in Figure 11-7) the number starts in the middle, proceeds to the eastern edge,<br />
goes to the western edge and then heads to the middle again. The code considers<br />
the shading and blocking by only those heliostats within f two rows of the row in<br />
which the heliostat of interest is located.<br />
For any of the options described above, the number of zones and hence the<br />
accuracy increases as NRAD and NAZM increase. The tradeoff is that computing<br />
time and cost will also increase. The variation in execution time is approximately<br />
linear with the number of zones, while the increase in accuracy with the number<br />
35