science/cdf 3.9.1 DragonFly

Device independent view of the CDF data model

System: DragonFly
Repository: DPorts
Maintainer: [email protected] (as in FreeBSD)
License: NASA-G
Categories: science
Package size: 1193.6 KiB, 14576.9 KiB installed

Description

Common Data Format (CDF) is a conceptual data abstraction for storing multi-dimensional data sets. The basic component of CDF is a software programming interface that is a device independent view of the CDF data model. The application developer is insulated from the actual physical file format for reasons of conceptual simplicity, device independence, and future expandability. CDF files created on any given platform can be transported to any other platform on to which CDF is ported and used with any CDF tools or layered applications. A more detailed introduction to CDF can be found in the CDF User's Guide.

A comparison between CDF, netCDF, HDF and HDF5 is available at <http://cdf.gsfc.nasa.gov/html/FAQ.html>.

In the other systems

System

Port

Version

DragonFly

science/cdf

3.9.1

FreeBSD

science/cdf

3.9.1_1

Install

Binary package:

pkg install cdf3

From DPorts:

cd /usr/dports/science/cdf && make install clean

Dependencies

Run dependencies 2

Required by 1

graphics/opendx

Configuration

No options to configure.

Service scripts: none

Message after installing

A set of script files named `definitions.<shell-type>' should now
exist in the `bin' directory.
`<shell-type>' specifies the type of shell (command interpreter)
for which the script file was written: `C' (C-shell style), `K'
(Korn shell style),  or `B' (Bourne shell style).  They are script
files that a user would execute to set up the environment variables
and aliases (where supported) necessary to use CDF.
A user would then execute the appropriate script file to define
aliases for the toolkit programs and environment variables for
the locations of the include files, CDF library, etc.

For the Korn, BASH, and POSIX shells, the following command
would be used:

       . /usr/local/bin/definitions.K

For the Bourne shell, the following command would be used:

       . /usr/local/bin/definitions.B

For the C and `tcsh' shells, the following command would be
used:

       source /usr/local/bin/definitions.C

Because aliases are not available when using the Bourne shell,
the toolkit programs must be invoked by specifying the actual
name of the executable file.  The script file `definitions.B'
describes how to do this.