05.08.2013 Views

ORNL-4191 - the Molten Salt Energy Technologies Web Site

ORNL-4191 - the Molten Salt Energy Technologies Web Site

ORNL-4191 - the Molten Salt Energy Technologies Web Site

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

- ~~<br />

20<br />

-~<br />

~~<br />

REACTIVITY<br />

POWER<br />

<strong>ORNL</strong>- DWG 67- 9191<br />

-<br />

16 18 20 22 24 26 28 3C 1 3 S 7 9<br />

JULY, 1967 nus, 1967<br />

residual reactivity occurred during <strong>the</strong> first<br />

several weeks of run 11. Detailed analysis of <strong>the</strong><br />

individual terms revealed two sources of error.<br />

One was a gradual downward drift in <strong>the</strong> temperature<br />

indicated by two of <strong>the</strong> four <strong>the</strong>rmocouples<br />

used to calculate <strong>the</strong> average reactor outlet temperature.<br />

These two <strong>the</strong>rmocouples were eliminated<br />

and replaced by one o<strong>the</strong>r that had not<br />

drifted. The second error was caused by loss of<br />

significance in <strong>the</strong> calculation of <strong>the</strong> 14'Sm concentration.<br />

In <strong>the</strong> program, only <strong>the</strong> change in<br />

samarium concentration is computed, and that<br />

change is added to <strong>the</strong> last value to obtain <strong>the</strong><br />

current value. As <strong>the</strong> I4'Sm concentration approached<br />

85% of its equilibrium value, <strong>the</strong> incremental<br />

concentration change computed for <strong>the</strong> 5-<br />

miri time step between routine reactivity balances<br />

was outside <strong>the</strong> five-decimal-digit precision of <strong>the</strong><br />

computer. As a result, <strong>the</strong>se increinents were<br />

lost when <strong>the</strong> concentration was updated. To<br />

avoid using doubl e-precision arithmetic, <strong>the</strong> program<br />

was modified to only update <strong>the</strong> 14'Srn and<br />

<strong>the</strong> 'Sm concentrations every 4 hr while <strong>the</strong><br />

reactor is at steady po~~i. Summary calculations<br />

made off line were used to verify <strong>the</strong> adequacy<br />

of this change.<br />

Fig. 1.6. Residual Reactivity During MSRE Run 12.<br />

When <strong>the</strong>se corrections were introduced on<br />

March 1'7, <strong>the</strong> apparent downward drift in reactivity<br />

disappeared. At <strong>the</strong> same time, minor<br />

changes were made in some of <strong>the</strong> '35Xe stripping<br />

parameters to make <strong>the</strong> calculated steady-state<br />

xenon poisoning agree more closely with <strong>the</strong> observed<br />

value.<br />

O<strong>the</strong>r small reactivity variations were observed<br />

in run 11, for example, from March 29 to April 9.<br />

These changes are directly related to changes in<br />

<strong>the</strong> helium overpressure on <strong>the</strong> fuel loop; a 1-psi<br />

pressure increase leads to a reversible reactivity<br />

decrease of slightly less than 0.01% 6k/k. The<br />

mechanism through which pressure and reactivity<br />

are coupled has not yet been established. The<br />

direct reactivity effect of <strong>the</strong> change in circulating<br />

voids caused by a change in absolute pressure<br />

is at least a factor of 10 smaller than <strong>the</strong> observed<br />

effect of pressure on reactivity. The time constant<br />

of <strong>the</strong> pressure-reactivity effect is relatively<br />

long, suggesting a possible connection through <strong>the</strong><br />

xenon poisoning.<br />

Fuel additions were made for <strong>the</strong> first time in<br />

run 11 with <strong>the</strong> reactor at full power. Nine capsules<br />

containing a total of 761 g of 235U were<br />

added between April 18 and 21. The reactivity-

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

Saved successfully!

Ooh no, something went wrong!