Re: Range check error

["David Bradley" <bradley@xxxxxxxxxxxxxxx>]

Holger,
	Most often, a range check error comes from an array within the TRNSYS
Fortran source code going out of bounds. If you're using Digital or
Compaq's developer studio, the best way to locate the problem is inside the
developer studio, place a breakpoint early in the code (before the problem
occurrs) run to there and then select Debug Menu: Exceptions and set all
the exceptions listed to "stop always" instead of "stop if not handled."
Then remove your breakpoint and let the simulation go. When the problem
array is hit, the debugger will point you to it. 

	Please let me know if you ever run across one of these in the standard
types, I'd be happy to take a look at them and see if I can solve the problem.

	As for components getting listed twice, I've never seen the problem. If
you have an example of a deck in which it happens, please send it my way so
that I can locate the problem.

Cheers,
David

At 16:20 5/8/00 +1000, you wrote:
>I seem to come across "Range check errors" all the time. What exactly
>are they and how can they be fixed?
>Another problem which might be related is sometimes a component gets
>listed in the deck twice (reactor1... reactor2) even though it has only
>be included once...
>Thanks for your help in advance,
>
>Holger
> 
---------------------------------------------------------------
David BRADLEY
1500 Engineering Drive		ph: +1 608 263 1589
Madison, WI				fax: +1 608 262 8464
53706 
URL: http://sel.me.wisc.edu/trnsys
---------------------------------------------------------------