Multiple Badness in Multiple time-stamps in instantaneous output

[rgknox]

The ED2IN text describing how to write multiple time-stamps per file is so wrong... and... then when I figure it out, it so doesn't work.

We supposedly have functionality that allows multiple time instances of model output per instantaneous output files. I cannot get it working for my runs. The text in the ED2IN says that OUTFAST AND OUTSTATE have a time unit, but it doesn't, it should be an integer stating a number of counts per file. It also says that FRQFAST is the time between files, but it totally isn't, it acts as the time between time-stamps.

Can anyone re-produce this problem or get it to work?

For instance, if I want hourly instantaneous output sent to daily files, this is what one would interperate from the ED2IN descriptions:

IFOUTPUT = 3
UNITFAST = 0
OUTFAST = 24
FRQFAST = 86400

it does not work, as you can see I am left with a single time in the file:

h5dump -d FMEAN_CAN_CO2_PY oxi_v4_pi_test-I-2001-12-02-000000-g01.h5
HDF5 "oxi_v4_pi_test-I-2001-12-02-000000-g01.h5" {
DATASET "FMEAN_CAN_CO2_PY" {
DATATYPE H5T_IEEE_F32LE
DATASPACE SIMPLE { ( 1 ) / ( 1 ) }
DATA {
(0): 320.785
}
}
}

So I tried this,

IFOUTPUT = 3
UNITFAST = 0
OUTFAST = -1
FRQFAST = 3600

and now it allocates 24 time-stamps, but only fills the first one....

h5dump -d FMEAN_CAN_CO2_PY oxi_v4_pi_test-I-2001-12-02-000000-g01.h5
HDF5 "oxi_v4_pi_test-I-2001-12-02-000000-g01.h5" {
DATASET "FMEAN_CAN_CO2_PY" {
DATATYPE H5T_IEEE_F32LE
DATASPACE SIMPLE { ( 24, 1 ) / ( 24, 1 ) }
DATA {
(0,0): 320.374,
(1,0): 0,
(2,0): 0,
(3,0): 0,
(4,0): 0,
(5,0): 0,
(6,0): 0,
(7,0): 0,
(8,0): 0,
(9,0): 0,
(10,0): 0,
(11,0): 0,
(12,0): 0,
(13,0): 0,
(14,0): 0,
(15,0): 0,
(16,0): 0,
(17,0): 0,
(18,0): 0,
(19,0): 0,
(20,0): 0,
(21,0): 0,
(22,0): 0,
(23,0): 0
}
}
}