01.03.2013 Views

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 ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

large enough fraction of total capital cost so that total capital cost decreases by<br />

a greater amount than annual decreases due to optimization, the levelized energy<br />

cost will decrease. However, <strong>for</strong> designs in which field costs are not as significant,<br />

the annual energy might decrease more than total capital cost (as a percentage),<br />

and thus LEC could increase due to heliostat density optimization at a constant<br />

design point power. In either case, if the user plots energy cost vs. annual energy,<br />

then improvement with heliostat spacing optimization can be seen.<br />

In practice the difference in the energy costs between optimizing <strong>for</strong> a given<br />

annual energy vs. optimizing <strong>for</strong> a given design point are small (< 1%). The dif-<br />

ference disappears (i.e., optimizing <strong>for</strong> annual energy acts like optimizing <strong>for</strong> de-<br />

sign point) if the non-field costs are relatively small or if the energy cost is not<br />

changing with annual energy. Why doesn’t DELSOL offer the option of finding<br />

the system optimized to <strong>prod</strong>uce a given design point power? Because it is much<br />

more complicated and the small improvements are generally not significant.<br />

The user should at least consider having the code do heliostat optimization.<br />

However, if after optimization levelized energy costs are higher than be<strong>for</strong>e, then<br />

density optimization will not help the user and should not be used <strong>for</strong> that prob-<br />

lem.<br />

1V.C. Variables With Wlich DElLSOL Optimizes<br />

DELSOL can vary certain design variables during optimization to per<strong>for</strong>m a<br />

search <strong>for</strong> the combination of variables that minimizes the levelized energy cost<br />

(LEC). The design variables or parameters which can be varied during a single<br />

DELSOL run are listed in Qble IV-1. The design parameters that are held con-<br />

stant during a single optimization search are listed in Table IV-2. This second<br />

set of variables can be “optimized” by per<strong>for</strong>ming several DELSOL optimization<br />

runs, each run having different values <strong>for</strong> these variables.<br />

DELSOL can per<strong>for</strong>m optimizations <strong>for</strong> systems with certain restraints.<br />

These restraints are a limitation on peak incident flux allowed on the receiver,<br />

and a restriction on the land available <strong>for</strong> the heliostat field. In this case, an op-<br />

timum system design must have a combination of system design variables which<br />

<strong>prod</strong>uces the lowest LEC and which also meets the flux and/or land constraints.<br />

Note that the computer time required <strong>for</strong> optimization will depend on the<br />

size of the matrix over which optimization is being per<strong>for</strong>med. For instance, if<br />

the user allows a choice of 5 values each <strong>for</strong> tower height and receiver dimensions,<br />

then up to 5 x 5 x 5 (125) calculations will be done during optimization; but if a<br />

choice of 10 values each is allowed, then up to 10 x 10 x 10 (1000) calculations<br />

will be done. Thus the user is cautioned to choose the range of optimizations<br />

carefully so as to minimize computation time.<br />

If the values of NUMTHT, NUMREC, or NUMHTW are set to 1 (allowing no<br />

variation in tower height or receiver dimensions), then the values which are used<br />

103

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!