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

[netCDF #UUS-259413]: pnetcdf and netcdf

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 #UUS-259413]: pnetcdf and netcdf
  • Date: Wed, 16 Jan 2013 21:13:55 -0700
Russ-
I am getting very confused about pnetcdf support.
This comment of yours
>   2. For netCDF classic format or 64-bit offset format files that use the 
> second nc_create_par() 
>      call above, the parallel I/O uses pnetcdf aka parallel-netcdf, but 
> provides the same API
>      (and thus API parameter types) as in the serial netCDF API.  This 
> restricts it to arrays of
>      primitive types for data, rather than the structured MPI types of data 
> that pnetcdf can also 
>      access, but makes it easier to convert a serial netCDF program to use 
> parallel I/O.
makes me think that pnetcdf code should be in libsrc or as a separate dispatch 
table.
However the current code has all the pnetcdf stuff in libsrc4.
When the --enable-pnetcdf is set for configure, should we treat this like a 
variant
of netcdf-3 or netcdf-4?

=Dennis



Ticket Details
===================
Ticket ID: UUS-259413
Department: Support netCDF
Priority: Normal
Status: Open