[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 19981026: netCDF on T3D/E

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: Re: 19981026: netCDF on T3D/E
Date: Mon, 16 Nov 1998 10:02:43 -0700
> Keywords: 199811051609.JAA13971
> Date: Fri, 13 Nov 1998 11:48:28 -0500
> From: Al Bourgeois <address@hidden>
> Organization: Lockheed Martin
> To: Steve Emmerson <address@hidden>
> Subject: Re: 19981026: netCDF on T3D/E
>
> Hi Steve,
>
> It's been awhile since I've been able to work on this. Here is the
> status: I went back and made sure the environment was set up correctly
> for the T3D, and now the "make test" starts off successfully, but then
> fails (see attached). I suspect this has to do with the following
> warning during the compilation:
>
>
>         cc -c -O -I../libsrc  -DNDEBUG fort-attio.c
>         cc -c -O -I../libsrc  -DNDEBUG fort-control.c
> cc-172 cc_mpp: WARNING File = fort-control.c, Line = 16
>   No code is generated for a superfluous expression.
> cc-172 cc_mpp: WARNING File = fort-control.c, Line = 30
>   No code is generated for a superfluous expression.
>
> TOTAL WARNINGS DETECTED IN fort-control.c: 2
>
> These are the lines:
>
> FCALLSCFUN5(NF_INT, nc__create, NF__CREATE, nf__create,
>             STRING, FINT2CINT, FINT2CSIZET, PCHUNKSIZEHINT, PNCID)
>
> and
>
> FCALLSCFUN4(NF_INT, nc__open, NF__OPEN, nf__open,
>             STRING, FINT2CINT, PCHUNKSIZEHINT, PNCID)
>
>
> Everything else seems normal during compilation. Obviously the netcdf
> library is building, but it doesn't seem to be incomplete.
>
> By the way, my T3D programming environment (PE 1.0) supports only the
> cf77 compiler, but I've tried compiling in PE 2.0 with f90 and the same
> warning occurs. I've compiled on a T3E and everything is ok.
>
> Thanks again for any suggestions.
>
>
> sequoia% make test
>
> Making `test' in directory /work/afl/netCDF/netcdf-3.4/src/libsrc
>
> FORCE: No action was taken.
>         ar cru   libnetcdf.a attr.o  dim.o  error.o  libvers.o  nc.o  ncio.o
 ncx.o  putget.o  string.o  v1hpg.o  v2i.o  var.o
>         : libnetcdf.a
>         cc -o t_nc -O  t_nc.o -L. -lnetcdf
>         ./t_nc
> trying again
> dimrename: IXX
> nc_close ret = 0
>
> reopen id = 274878096704 for filename test.nc
> NC done
> GATTR VAR VATTR
> VATTR
> VATTR
> VATTR
> VATTR
> VATTR
> fill_seq indices         1 2 3  75.000000 != 2.718282
> Done
> got val = 3.250000
> got val = 0.000000
> got val = 2.718282
> got val = 82555
> got val = 97
> got NC_CHAR val = A (0x41)
> got NC_CHAR val = B (0x42)
> got NC_CHAR val = "The red death had long devastated the country."
> got val = A (0x41)
> got val = B (0x42)
> got val = "The red death had long devastated the country."
> got vals = 0.000000 ... 447.000000
> re nc_close ret = 0
>         cmp test.nc test_nc.sav
> *** Success ***
>
> Returning to directory /work/afl/netCDF/netcdf-3.4/src
>
>
> Making `test' in directory /work/afl/netCDF/netcdf-3.4/src/nctest
>
>         cc -o nctest -O  varget.o vargetg.o varput.o varputg.o vardef.o
vartests.o  vputget.o vputgetg.o driver.o cdftests.o dimtests.o rec.o
 atttests.o misctest.o add.o error.o emalloc.o val.o slabs.o -L../libsrc
-lnetcdf
>         ./nctest
> *** Testing nccreate ...        ok ***
> *** Testing ncopen ...          ok ***
> *** Testing ncredef ...         ok ***
> *** Testing ncendef ...         ok ***
> *** Testing ncclose ...         ok ***
> *** Testing ncinquire ...       ok ***
> *** Testing ncsync ...          ok ***
> *** Testing ncabort ...         ok ***
> *** Testing ncdimdef ...        ok ***
> *** Testing ncdimid ...         ok ***
> *** Testing ncdiminq ...        ok ***
> *** Testing ncdimrename ...     ok ***
> *** Testing ncvardef ...        ok ***
> *** Testing ncvarid ...         ok ***
> *** Testing ncvarinq ...        ok ***
> *** Testing ncvarput1 ...       ok ***
> *** Testing ncvarget1 ...       ok ***
> *** Testing ncvarput ...        ok ***
> *** Testing ncvarget ...        ok ***
> *** Testing ncvarputg ...       ok ***
> *** Testing ncvargetg ...       ok ***
> *** Testing ncrecinq ...        ok ***
> *** Testing ncrecput ...        ok ***
> *** Testing ncrecget ...        ok ***
> *** Testing ncvarrename ...     ok ***
> *** Testing ncattput ...        ok ***
> *** Testing ncattinq ...        ok ***
> *** Testing ncattget ...        ok ***
> *** Testing ncattcopy ...       ok ***
> *** Testing ncattname ...       ok ***
> *** Testing ncattrename ...     ok ***
> *** Testing ncattdel ...        ok ***
> *** Testing nctypelen ...       ok ***
>         cmp testfile.nc testfile_nc.sav
>
> Returning to directory /work/afl/netCDF/netcdf-3.4/src
>
>
> Making `test' in directory /work/afl/netCDF/netcdf-3.4/src/nc_test
>
>         cc -o nc_test -O  nc_test.o  error.o  test_get.o  test_put.o
 test_read.o  test_write.o  util.o -L../libsrc -lnetcdf -lm
>         ./nc_test -c
>
>         FAILURE at line 552 of util.c: nc_def_var: String match to name in
use
>         FAILURE at line 552 of util.c: nc_def_var: String match to name in
use
>         FAILURE at line 552 of util.c: nc_def_var: String match to name in
use
>         FAILURE at line 552 of util.c: nc_def_var: String match to name in
use
>         FAILURE at line 552 of util.c: nc_def_var: String match to name in
use
>         FAILURE at line 552 of util.c: nc_def_var: String match to name in
use
>         FAILURE at line 552 of util.c: nc_def_var: String match to name in
use
>         FAILURE at line 552 of util.c: nc_def_var: String match to name in
use ./nc_test
> *** Testing nc_strerror ... ok
> *** Testing nc_open ... ok
> *** Testing nc_close ... ok
> *** Testing nc_inq ...
>         FAILURE at line 223 of test_read.c: nc_inq: wrong number of variables
returned, 112
>         FAILURE at line 249 of test_read.c: nc_inq subset: wrong number of
variables returned, 112
>         ### 2 FAILURES TESTING nc_inq! ###
> *** Testing nc_inq_dimid ... ok
> *** Testing nc_inq_dim ... ok
> *** Testing nc_inq_dimlen ... ok
> *** Testing nc_inq_dimname ... ok
> *** Testing nc_inq_varid ...
>         FAILURE at line 588 of test_read.c: expected 12, got 6
>         FAILURE at line 588 of test_read.c: expected 13, got 7
>         FAILURE at line 588 of test_read.c: expected 14, got 8
>         FAILURE at line 588 of test_read.c: expected 15, got 9
>         FAILURE at line 588 of test_read.c: expected 16, got 10
>         FAILURE at line 588 of test_read.c: expected 17, got 11
>         FAILURE at line 588 of test_read.c: expected 18, got 6
>         FAILURE at line 588 of test_read.c: expected 19, got 7
>         ### 124 FAILURES TESTING nc_inq_varid! ###
> *** Testing nc_inq_var ...
>         FAILURE at line 626 of test_read.c: name expected: cr, got: cr1
>         FAILURE at line 639 of test_read.c: name expected: cr, got: cr1
>         FAILURE at line 649 of test_read.c: ndims expected: 1, got: 2
>         FAILURE at line 654 of test_read.c: unexpected dimid
>         FAILURE at line 626 of test_read.c: name expected: br, got: br2
>         FAILURE at line 639 of test_read.c: name expected: br, got: br2
>         FAILURE at line 649 of test_read.c: ndims expected: 1, got: 2
>         FAILURE at line 654 of test_read.c: unexpected dimid
>         ### 512 FAILURES TESTING nc_inq_var! ###
> *** Testing nc_inq_natts ... ok
> *** Testing nc_inq_ndims ... ok
> *** Testing nc_inq_nvars ...
>         FAILURE at line 397 of test_read.c: nc_inq_nvars: wrong number
returned, 112
>         ### 1 FAILURES TESTING nc_inq_nvars! ###
> *** Testing nc_inq_unlimdim ... ok
> *** Testing nc_inq_vardimid ...
>         FAILURE at line 689 of test_read.c: unexpected dimid
>         FAILURE at line 689 of test_read.c: unexpected dimid
>         FAILURE at line 689 of test_read.c: unexpected dimid
>         FAILURE at line 689 of test_read.c: unexpected dimid
>         FAILURE at line 689 of test_read.c: unexpected dimid
>         FAILURE at line 689 of test_read.c: unexpected dimid
>         FAILURE at line 689 of test_read.c: unexpected dimid
>         FAILURE at line 689 of test_read.c: unexpected dimid
>         ### 115 FAILURES TESTING nc_inq_vardimid! ###
> *** Testing nc_inq_varname ...
>         FAILURE at line 719 of test_read.c: name expected: cr, got: cr1
>         FAILURE at line 719 of test_read.c: name expected: br, got: br2
>         FAILURE at line 719 of test_read.c:
>         FAILURE at line sequoia% 719 of test_read.c: name expected: cr, got:
c13
>         FAILURE at line 719 of test_read.c: name expected: br, got: b14
>         ### 124 FAILURES TESTING nc_inq_varname! ###
> *** Testing nc_inq_varnatts ...
>         FAILURE at line 747 of test_read.c: nc_inq_varnatts: Variable not
found
>         FAILURE at line 747 of test_read.c: nc_inq_varnatts: Variable not
found
>         FAILURE at line 747 of test_read.c: nc_inq_varnatts: Variable not
found
>         FAILURE at line 747 of test_read.c: nc_inq_varnatts: Variable not
found
>         FAILURE at line 747 of test_read.c: nc_inq_varnatts: Variable not
found
>         FAILURE at line 747 of test_read.c: nc_inq_varnatts: Variable not
found
>         FAILURE at line 747 of test_read.c: nc_inq_varnatts: Variable not
found
>         FAILURE at line 747 of test_read.c: nc_inq_varnatts: Variable not
found
>         ### 24 FAILURES TESTING nc_inq_varnatts! ###
> *** Testing nc_inq_varndims ...
>         FAILURE at line 779 of test_read.c: ndims expected: 1, got: 2
>         FAILURE at line 779 of test_read.c: ndims expected: 1, got: 2
>         FAILURE at line 779 of test_read.c: ndims expected: 1, got: 2
>         FAILURE at line 779 of test_read.c: ndims expected: 1, got: 2
>         FAILURE at line 779 of test_read.c: ndims expected: 1, got: 2
>         FAILURE at line 779 of test_read.c: ndims expected: 1, got: 2
>         FAILURE at line 779 of test_read.c: ndims expected: 1, got: 2
>         FAILURE at line 779 of test_read.c: ndims expected: 1, got: 2
>         ### 68 FAILURES TESTING nc_inq_varndims! ###
> *** Testing nc_inq_vartype ...
>         FAILURE at line 807 of test_read.c: nc_inq_vartype: Variable not
found
>         FAILURE at line 807 of test_read.c: nc_inq_vartype: Variable not
found
>         FAILURE at line 807 of test_read.c: nc_inq_vartype: Variable not
found
>         FAILURE at line 807 of test_read.c: nc_inq_vartype: Variable not
found
>         FAILURE at line 807 of test_read.c: nc_inq_vartype: Variable not
found
>         FAILURE at line 807 of test_read.c: nc_inq_vartype: Variable not
found
>         FAILURE at line 807 of test_read.c: nc_inq_vartype: Variable not
found
>         FAILURE at line 807 of test_read.c: nc_inq_vartype: Variable not
found
>         ### 24 FAILURES TESTING nc_inq_vartype! ###


I build netcdf-3.4 on a system here.

(antero) 41 % uname -a
sn4031 antero 10.0.0 and.10 CRAY C90
(antero) 42 % cc -V
Cray Standard C Version 6.0.1.3 11/13/98 10:49:22

from config.log -
CRAY FORTRAN CFT77 6.2.4.0  09/17/97 14:35:05         11/13/98 10:35:42

So, like you, I used cf77. Other than this and dropping the '-F' fortran
option from FFLAGS, I followed the procedure from the INSTALL file.

It works for me. (Don't you hate hearing that? :-)

The failures you are seeing in nc_test look very much to me like the
program nc_test is excuting simultaneously on more than one processor.
'nc_test' is a serial program.

-glenn
Prev by Date: Re: 19981110: Indirect Access in netCDF-4
Next by Date: Re: 19981026: netCDF on T3D/E
Previous by thread: Re: 19981026: netCDF on T3D/E
Next by thread: Re: 19981026: netCDF on T3D/E
Index(es):
- Date
- Thread