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.

Only one design point and one annual average loss calculation is done during<br />

system optimization, and the results are used <strong>for</strong> all systems examined.<br />

I V. A - 9. Atmospheric Att e nuation-The atmospheric attenuation is exactly re-<br />

calculated <strong>for</strong> every tower height and receiver examined during system optimiza-<br />

tion.<br />

1V.A-4. Tower Shadow Scaling-DELSOL accounts <strong>for</strong> the tower shadow as<br />

described in Section 1II.E-2. The tower shadow as calculated or specified in an<br />

initial per<strong>for</strong>mance run is scaled with tbwer height during optimization. That is,<br />

the last specified tower shadow (TOWL, TOWD in Namelist REC) is scaled by<br />

the ratio of the current tower height to the tower height specified in the initial<br />

per<strong>for</strong>mance run. Thus, it is suggested that TOWL and TOWD be specified in<br />

the initial per<strong>for</strong>mance run to match the tower dimensions, and then that these<br />

variables not be changed during optimization input.<br />

I V.A-5. Receiver Losses-Receiver design point losses are calculated using the<br />

algorithms described in Section 1II.G-3, depending on the receiver dimensions of<br />

each system examined during system optimization. It is assumed, as <strong>for</strong> a final<br />

per<strong>for</strong>mance calculation, that receiver losses represented as an efficiency do not<br />

vary with time of day or year, so annual receiver efficiencies are the same as de-<br />

sign point efficiencies.<br />

1V.A-6. Other Component Losses-Components downstream from the receiver<br />

have simple loss calculations, as described in Section III.G, and so these losses are<br />

calculated as described in that Section. These losses are assumed to be time inde-<br />

pendent, so annual efficiencies are the same as design point efficiencies. However,<br />

the turbine annual efficiency is assumed to equal its off-design point ef-<br />

ficiency, as represented by the value ETAREF x FEFF (Namelist NLEFF). This<br />

worst case assumption is made because the code does not know during optimiza-<br />

tion the amount of time the turbine will actually have enough power to run at its<br />

rated capacity. The actual annual efficiency, and there<strong>for</strong>e the amount of annual<br />

energy, will always be higher than this assumption would indicate. This assump-<br />

tion could and usually does cause the largest difference in predicted annual energy<br />

(levelized energy cost) between an optimization calculation and the comparable<br />

final per<strong>for</strong>mance calculation on the same system. Since the final per<strong>for</strong>mance<br />

calculation is more exact, its annual energy prediction and levelized energy cost<br />

values should be used if a discrepancy exists with system optimization predic-<br />

t ions.<br />

The turbine annual efficiency assumption is not a very good assumption <strong>for</strong><br />

systems which have reasonable quantities of storage to supplement power from<br />

the field, since <strong>for</strong> those cases storage will be used to operate the turbine at full<br />

power. The assumption was originally made based on water-steam systems. Al-<br />

though the assumption affects the actual energy and cost values calculated during<br />

optimization, the comparison determining which system is better should only be<br />

slightly affected, and so the assumption is acceptable <strong>for</strong> this purpose.<br />

98<br />

I

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

Saved successfully!

Ooh no, something went wrong!