Writing station data for each nonlinear run during 4dvar

Report or discuss software problems and other woes

Moderators: arango, robertson

Post Reply
Message
Author
stef
Posts: 196
Joined: Tue Mar 13, 2007 6:38 pm
Location: Independent researcher
Contact:

Writing station data for each nonlinear run during 4dvar

#1 Unread post by stef »

Hi!
I am wondering if station data is supposed to be written for each outer loop?
If so, should it go into the same file, or into different files for each nonlinear run?

I tried with Nouter=1 and there are 2*(ntimes/nSTA + 1) records in the output file,
which made me think they are all written into one single file, and the user is responsible
for splitting it into the corresponding chunks. That would make sense to me.

However, the second half of the records are nan's in my case.

I tried to debug (even though I'm not sure what the intended behaviour is) and saw that:

The Rindex defined in def_station.F:

Code: Select all

        STA(ng)%Rindex=(ntstart(ng)-1)/nSTA(ng)
increases steadily across the two nonlinear runs.

But in the second nonlinear run, the quantities

Code: Select all

        Xpos(i)=SCALARS(ng)%SposX(i)
        Ypos(i)=SCALARS(ng)%SposY(i)
in wrt_station.F aren't set as (I assume) they should be.

The function read_StaPar() is called from inp_par(), which is called in ROMS_initialize() sets
the SposX:

Code: Select all

    SCALARS(ng)%SposX(is(ng))=Xpos
Are these supposed to have a lifetime until the end of the program? Or do they have to be re-initialized
after each nonlinear run?

Thanks for your help!

Post Reply