[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[netCDF #GBB-400841]: NCVGT: : Start+count exceeds dimension bound
- To: thin_runner@xxxxxxxxx
- Subject: [netCDF #GBB-400841]: NCVGT: : Start+count exceeds dimension bound
- From: "Unidata netCDF Support" <support-netcdf@xxxxxxxxxxxxxxxx>
- Date: Mon, 03 Mar 2008 13:44:08 -0700
- Delivered-to: support-netcdf@unidata.ucar.edu by laraine.unidata.ucar.edu (Postfix) with ESMTP id D7FF5CB188; Mon, 3 Mar 2008 13:44:08 -0700 (MST) id A6616D5116; Mon, 3 Mar 2008 13:44:08 -0700 (MST)
Steve,
Now that I see the ncdump output, the row-major CDL declaration
float ht(record, z, y, x) ;
would correspond to a column-major Fortran declaration with the dimensions
reversed:
ALLOCATE ( ht ( x , y , z3+1 ) )
and consistent start and count vectors:
start = (/ 1 , 1 , 1 , 1 /)
count = (/ x , y , z , 1 /)
We have a worked out example here of the output from ncdump of an example
file, and Fortran 90 programs for writing and reading the 4D variable:
http://www.unidata.ucar.edu/software/netcdf/examples/programs/pres_temp_4D.cdl
http://www.unidata.ucar.edu/software/netcdf/examples/programs/pres_temp_4D_wr.f90
http://www.unidata.ucar.edu/software/netcdf/examples/programs/pres_temp_4D_rd.f90
If it's not clear that the row-major and column-major dimension orders are just
reversed, maybe the example above will help.
--Russ
Russ Rew UCAR Unidata Program
russ@xxxxxxxxxxxxxxxx http://www.unidata.ucar.edu
Ticket Details
===================
Ticket ID: GBB-400841
Department: Support netCDF
Priority: Normal
Status: Closed