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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

epresentation of heliostat errors and to incorporate analytical scaling of the im-<br />

ages as the tower height is varied (Reference 5). DELSOL also employs a method<br />

<strong>for</strong> optimizing heliostat densities similar to the Houston approach (Reference 4).<br />

The primary difference in the two codes is in their design/optimization capabili-<br />

ties. The Houston approach considers only one tower height and receiver size at<br />

a time. These variables must be optimized by manually rerunning the Houston<br />

codes until an optimum is located. In contrast, DELSOL automatically optimizes<br />

the tower height and receiver dimension(s), saving considerable user and com-<br />

puter time. (The user is cautioned, however, to provide his own values <strong>for</strong> the<br />

appropriate input variables if his system of interest differs significantly in size or<br />

cost/per<strong>for</strong>mance from the default system description in the code. See Appendix<br />

Am)<br />

DELSOL is a FORTRAN IV code, developed on <strong>Sandia</strong>’s CDC6600 and<br />

CDC7600, and adapted to execute on a CRAY-1. Typical execution times <strong>for</strong><br />

per<strong>for</strong>mance calculations on the CRAY-1 are 45-60 seconds, while design and op-<br />

timization calculations may take 5-300 seconds. Execution times on a VAX 11-<br />

780 will typically be about ten times as long as on the CRAY-1. This manual de-<br />

scribes the status of DELSOL as of January 1986. The code is intended to evolve<br />

with the development of central receiver technology and revised versions of the<br />

code and manual will be released as needed.<br />

LA. Differences from Earlier Versions of DELSOL<br />

Several corrections and additions have been made in DELSOLS which dis-<br />

tinguish it from its predecessors. Known errors which were fixed included cor-<br />

recting the logic <strong>for</strong> scaling flux point positions during the optimization of cavity<br />

receivers, correcting the flux calculation <strong>for</strong> cavity receivers and extending the<br />

calculation to allow general flux maps in front of the aperture, and correcting the<br />

logic when operating from storage and receiver power simultaneously. Also, the<br />

operating parasitic loss calculation was fixed and modified, and numerous typo-<br />

graphical errors in the code and in the outputs were corrected.<br />

At least four major enhancements were added to <strong>DELSOL3</strong>. First, receiver<br />

loss algorithms were modified based on References 6 and 7 to more closely model<br />

experimental and test facility data of receiver losses, including measured losses<br />

at the Solar One facility near Barstow, Cali<strong>for</strong>nia. Next, algorithms <strong>for</strong> non-<br />

operating parasitic losses were added to the code, thus accounting <strong>for</strong> the en-<br />

ergy which is consumed by a power plant at the times when power is not being<br />

<strong>prod</strong>uced. Third, the sizing algorithm <strong>for</strong> a cavity heat absorber area, which de-<br />

termines receiver cost, was modified so that the new area is based on aperture<br />

height rather than on minimum and maximum field dimensions. The previous<br />

algorithm resulted in an extremely large cavity which had very low incident flux<br />

levels on the upper portion of the heat absorber area. This modification assumes<br />

that some internal spillage is acceptable, and is intended to be an empirical model<br />

based on present and past detailed cavity designs.<br />

22

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

Saved successfully!

Ooh no, something went wrong!