Am 15.10.2015 um 16:43 schrieb Riccardo (Jack) Lucchetti:
On Thu, 15 Oct 2015, Sven Schreiber wrote:
> It seems (not proven yet, just tentatively) the small number is coming
> from the cdf() function.
Well, no -- it turns out that it has nothing to do with any functions
and numerics (though it's also nice to have that sorted out along the way).
It's apparently a problem of dataset handling, but it's kind of strange:
On my local copy of the workfile the relevant value of the obs is
0.870609. After transferring the full 350KB gdt file to the server this
value somehow becomes the problematic 4.90325e-310! All the other values
are fine (it seems).
I thought it was file corruption, but the issue is reproducible after
transferring and overwriting on the server several times. However, the
problem goes away when I export the specific series to a new gdt file
which holds only that series. After the transfer to the server, the
value 0.870609 shows up like it should in the small datafile.
The problem also disappears when I save the full dataset to a new
binary-format .gdtb file. However, it doesn't help to save the full
dataset in a new file, but in the standard gdt format.
Ok, so I know how to work around this problem, but I'm curious what
Allin will investigate in this respect!
thanks,
sven