Re: [FLASH-USERS] Initial condition

Having extra variables should not cause this behavior, and the integer
indices of the variables in the array storing this information are
somewhat arbitrarily decided by the setup script. They should work fine as
long as they are consistent throughout the code.

Could it be that you want to call eos3d in non-default mode. In most cases
Flash assumes that dens and ei are input and temp and pres are output. If
you need it to be different, you will have to change the mode in the eos3d
call.

If that is not the problem, could you please send us your Modules file,
and init_block routine so we can take a look at it.

Anshu

On Sun, 23 Jul 2006, Stefan Hirche wrote:

> Hi,
> my problem is as follows.
> I initialize all variables in init_block, but the output is not like my
> initialisation. So I looked into the code and in init_from_scratch init_block
> gets called. But in the subroutine that is called afterwards, eos3d, one of
> the variables is allready wrong.
>
> So I tested this behaviour and I discovered, that xn got the value of the
> temperature (every 8 cells, it keeps the right value). So something with the
> variables in the memory is wrong.
> I checked the numbers in the database, in both routines (eos3d and init_block)
> itemp is 3 and xn (inuc_begin) is 19. I don't know if the difference of 16
> is important...
>
> The behaviour might be caused by the fact that I have created some additional
> variables, but they are not used in init_block and the total number of
> variables is not close to 48.
>
> Maybe someone has an idea what to do or what to test next...
>
> Thanks, Stefan
>
Received on Tue Jul 25 10:40:12 2006