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

Fwd: UNLIMITED long long



I'm forwarding this example message to see if there's a way to drive it into eSupport to make it behave as if the user sent it to address@hidden.

--Russ

---------- Forwarded message ----------
From: <address@hidden>
Date: Tue, Jul 29, 2014 at 2:37 PM
Subject: UNLIMITED long long
To: address@hidden


I have gcc code that I've been using for a long time that creates a file like this:
netcdf ki_040_b_ha {
dimensions:
    lon = 646 ;
    lat = 720 ;
    grid_lon = 2581 ;
    grid_lat = 2879 ;
    time = 1441 ;
    index = UNLIMITED ; // (190827214 currently)
variables:
    int start(lat, lon) ;
        start:long_name = "Starting Index" ;
        start:_FillValue = -1 ;
        start:missing_value = -1 ;
    int end(lat, lon) ;
        end:long_name = "Ending Index" ;
        end:_FillValue = -1 ;
        end:missing_value = -1 ;
    int start_time(lat, lon) ;
        start_time:long_name = "Time of Starting Index" ;
        start_time:_FillValue = -1 ;
        start_time:missing_value = -1 ;
    double lon(lon) ;
        lon:long_name = "longitude" ;
        lon:units = "degrees_east" ;
        lon:point_spacing = "even" ;
    double lat(lat) ;
        lat:long_name = "latitude" ;
        lat:units = "degrees_north" ;
        lat:point_spacing = "uneven" ;
    float grid_lon(grid_lon) ;
        grid_lon:long_name = "Grid Longitude" ;
        grid_lon:units = "degrees_east" ;
        grid_lon:point_spacing = "even" ;
    float grid_lat(grid_lat) ;
        grid_lat:long_name = "Grid Latitude" ;
        grid_lat:units = "degrees_north" ;
        grid_lat:point_spacing = "uneven" ;
    float bathymetry(grid_lat, grid_lon) ;
        bathymetry:long_name = "Grid Bathymetry" ;
        bathymetry:standard_name = "depth" ;
        bathymetry:units = "meters" ;
        bathymetry:missing_value = -1.e+34f ;
        bathymetry:_FillValue = -1.e+34f ;
    float deformation(grid_lat, grid_lon) ;
        deformation:long_name = "Grid Deformation" ;
        deformation:units = "meters" ;
        deformation:missing_value = -1.e+34f ;
        deformation:_FillValue = -1.e+34f ;
    float max_height(lat, lon) ;
        max_height:long_name = "Maximum Wave Amplitude" ;
        max_height:units = "cm" ;
        max_height:missing_value = -1.e+34f ;
        max_height:_FillValue = -1.e+34f ;
    float travel_time(lat, lon) ;
        travel_time:long_name = "Travel Time" ;
        travel_time:units = "hours" ;
        travel_time:_FillValue = -1.e+34f ;
        travel_time:missing_value = -1.e+34f ;
    double time(time) ;
        time:units = "seconds" ;
    byte ha(index) ;
        ha:units = "cm" ;
        ha:long_name = "Wave Amplitude" ;
Â...

and now I have files with longer variables UNLIMITED = 3832812000. I've updated the code to netcdf4 from classic and converted INTs to LONG LONGs(NC_INT64) and the code runs with the shorter files but with the longer ones I get a Segmentation fault. Do you have any suggestions on where I can look for the problem? Can I have a 1D array w/ UNLIMITED = 3832812000 values? Or arrays with longlong values?
Thank you for your time. ÂJean
Â___________________________________________________________
 Jean Newman               Tel: 206-526-6531
 NOAA Center for Tsunami Research
 NOAA/PMEL/OERD2 - UW/JISAO       ÂFAX: 206-526-6485
 7600 Sand Point Way NE, Bldg. 3  Âaddress@hidden
 Seattle, WA 98115-6349             address@hidden
Â_________________________. URL: http://nctr.pmel.noaa.gov/
            Â(__________________________________



--
Russ Rew
UCAR Unidata Program


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.