Changes between Initial Version and Version 1 of Ticket #835


Ignore:
Timestamp:
01/09/20 21:54:50 (5 years ago)
Author:
arango
Comment:

Yes, indeed. Great catch! The issue here is that the time-averaged output NetCDF files (when AVERAGES or DIAGNOSTICS_* are activated) are delayed in its creation until the fields are accumulated and ready to write out if the parameters NDEFAVG or NDEFDIA are greater than zero (multi-file option).

It is tricky, but the solution is very simple. The AVG(ng)%load or DIA(ng)%load are reset to zero for such cases in read_phypar.F. By default, their values are initialized to one during initialization in load_s1d. It is weird that the compiler didn't pick-up the out-of-bounds errors during my original testing.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #835

    • Property ResolutionFixed
    • Property Status newclosed
    • Property Summary trouble in outputTrouble in time-averaged output NetCDF files
  • Ticket #835 – Description

    initial v1  
    1 If you run the standard upwelling case with NTIMES = 18, NAVG = 9, NDEFAVG = 9,
     1If you run the standard upwelling case with '''NTIMES = 18''', N'''AVG = 9''', '''NDEFAVG = 9''',
    22it blows up:
    33
     
    2020278             IF (iic(ng).eq.ntstart(ng)) THEN
    2121}}}
    22 is never true, so AVG(ng)%load starts at 1, goes to 2, then 3. When Fcount is 3, it goes out of bounds with AVG(ng)%Nrec is dimensioned size 2.
     22is never true, so '''AVG(ng)%load''' starts at 1, goes to 2, then 3. When '''Fcount''' is 3, it goes out of bounds with '''AVG(ng)%Nrec''' is dimensioned size 2.
    2323
    2424It was working before: src:ticket:825, trunk@982