[Thread Prev][Thread Next][Index]

Re: problem in regridig of data



Hi Yogesh,
I am confused about one thing in your message. Where do the
lines come from at the end of your message:

File name is ./default.spk
File name is /pool/ia64/ferret/v5.70/ppl/default.spk

The file default.spk is a color palette file, defining the colors used
in shade and fill plots. Is there a problem accessing these files? Can you make other plots, like

yes? shade/palette=default x[x=1:10:1] + y[y=1:10:1]

Otherwise, I think that with this large number of points the calculation
might just be taking a long time, and not actually hanging. The gridding
function takes each input scattered point and calculates its contribution
to each output gridded cell. It skips the main computation for scattered
points that are outside the cutoff area, but it still does that distance check
for each scattered point and each grid cell (actually if it's too far away
in the first dimension it doesn't check the distance in the second dimension).

You can test this by timing a few intermediate problems, such as
npts =1000, 5000, 10000, 50000. Also, here is a slightly different way to
define the mask from the number of observations


let npts = 1000
let xpts = lon_1D[i=1:`npts`]
let ypts = lon_1D[i=1:`npts`]
let cpts = co2_1D[i=1:`npts`]

let mask = IF obs_count GE 10 ! There is an implied ELSE missing data

let co2_point = mask* scat2gridgauss_xy(xpts,ypts,cpts,\
x[gx=gcom],y[gy=gcom],($radius),($radius),($cutoff),($cutoff))\

shade co2_point


Another question: where do the lines come from at the end of your message:

File name is ./default.spk
File name is /pool/ia64/ferret/v5.70/ppl/default.spk

The file default.spk is a color palette files.
Ansley

Yogesh K. Tiwari wrote:

Hello Ferret Users,

I caaled a script in ferret which counts the number of observations and then regrids the data

The problem is if I shade the data or try to save it ,it gets hanged for hours and hours.

Some times few data works and sometime another file contains same of data dosen't works.

Currently the file which I am using and got hanged has 40 mb data size.

If any person can help me, if the ferret hangs without giving any error then what may be the problem and how we can decide the check points.

I called script like that :

*********************************

yes? set data ecmwf_co2_jan2003.nc !

File name is ./ecmwf_co2_jan2003.nc

yes? set data tm3airs_new_January_2003.nc

File name is ./tm3airs_new_January_2003.nc

yes?sh dat
currently SET data sets:
1> ./ecmwf_co2_jan2003.nc
name I J K L
LON 1:360 ... ... ...
LAT 1:180 ... ... ...
CO2_T 1:360 1:180 ... ...


2> ./tm3airs_new_January_2003.nc (default)
name I J K L

LON ... ... ... 1:119641
LAT ... ... ... 1:119641
TM3CO2 ... ... ... 1:119641



yes? ! define destination axes from lat and lon in ecmwf_co2_jan2003


yes? define axis/x/units=longitudes/from_data xlon=lon[d=1]

yes? define axis/y/units=latitudes/from_data ylat=lat[d=1]

yes? define grid/x=xlon/y=ylat gcom

yes? define symbol radius = 0.25

yes? define symbol cutoff = 2.0

yes? let lon_1D = XSEQUENCE(lon[d=2])
yes? let lat_1D = XSEQUENCE(lat[d=2])
yes? let co2_1D = XSEQUENCE(tm3co2[d=2])

yes? let obs_count = scatgrid_nobs_xy(lon_1D,lat_1D,x[gx=gcom],y[gy=gcom])


yes? !griding CO2 using the mask if there is atleast 10 observations in one grid

yes? let co2_point = IF obs_count GE 10 THEN\
...? scat2gridgauss_xy(lon_1D,lat_1D,co2_1D,\
...? x[gx=gcom],y[gy=gcom],($radius),($radius),($cutoff),($cutoff))\
...? ELSE 1e35
!-> DEFINE VARIABLE co2_point = IF obs_count GE 10 THEN scat2gridgauss_xy(lon_1D,lat_1D,co2_1D,
x[gx=gcom],y[gy=gcom],0.25,0.25,2.0,2.0) ELSE 1e35


yes? shade co2_point
File name is ./default.spk
File name is /pool/ia64/ferret/v5.70/ppl/default.spk

*************************************************************

The ferret dosen't comes out from here after waiting of three-four hours.

Many thanks in advance for help,

Regards,
Yogesh







[Thread Prev][Thread Next][Index]

Dept of Commerce / NOAA / OAR / PMEL / TMAP

Contact Us | Privacy Policy | Disclaimer | Accessibility Statement