[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #HPS-623090]: Re: [netcdfgroup] files with compound types not portable?

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [netCDF #HPS-623090]: Re: [netcdfgroup] files with compound types not portable?
  • Date: Wed, 22 Apr 2009 14:58:29 -0600
"Jeff Whitaker" <address@hidden> writes:

> New Client Reply: Re: [netcdfgroup] files with compound types not portable?
>
> Unidata netCDF Support wrote:
>> Hi Jeff,
>>
>> We actually think we've figured out the problem and we're testing a 
>> fix this afternoon.  If our diagnosis is correct, everything is
>> written OK, it's only that the structure offsets that ncdump uses
>> when reading are off.  This only occurs in generic programs such as
>> ncdump, which don't have a native structure into which to read the 
>> compound value.  But the fix would be in the netCDF-4 library to make
>> sure the member offsets are properly adjusted before returning from
>> the nc_inq_compound_field() function that ncdump relies on to figure
>> out where in the void* data it has read it finds the member values.

Unfortunately my easy fix did not work. So I am studying the
problem...

But I still believe it is in the reading, not the writing of the file.

Thanks,

Ed

-- 
Ed Hartnett  -- address@hidden



Ticket Details
===================
Ticket ID: HPS-623090
Department: Support netCDF
Priority: Normal
Status: Open