[gradsusr] smoothing large resolution data
Andrew Friedman
andfried at gmail.com
Mon Jan 23 10:33:00 EST 2017
Hi Wendy,
I would place the command at the end of your script.
'define try=(rr, albedo.2, aave)’
Do you get an error? Based on your script, I’m wondering if you might be closing your files too soon.
Assuming no error message, you can go to a specific lat/lon point where you know there is data in the original file and type
'd try’
You can also try ‘set gxout grid’ to look at the values in specific gridboxes.
Hope this helps.
Andrew
> On Jan 23, 2017, at 1:20 PM, wendi harjupa <wendiharjupa at gmail.com> wrote:
>
> Dear Mr. Andrew
>
> Thank you very much for your excellent supervision
>
> Below is my simple script
>
> 'open ./Rain.ctl'
> 'set lat 33.5 35.5'
> 'set lon 134.3 136.6'
> # 'd rr' ! variable
> 'xcbar 8.85 9.05 0.8 4 -fw 0.11 -fh 0.15 -edge triangle -fstep 1 -line on -lc 1'
> 'close 1'
>
> ##second data/resolution 0.1x0.1 (lat, lon)
>
> 'open ./Him.ctl'
> 'set lat 33.5 35.5'
> 'set lon 134.3 136.6'
> # 'd albedo' ! variable
> 'xcbar 6.3 9 0.23 0.37 -fw 0.11 -fh 0.15 -edge triangle -fs 2 -fo 1 -line on'
> 'close 1'
>
> 'd lterp(rr, albedo.2, aave)'
>
> my control file as below
> 1. Rain.ctl
>
> DSET ~/data1
> OPTIONS yrev
> UNDEF -1.E35
> XDEF 800 LINEAR 134.375 0.003125
> YDEF 960 LINEAR 33.5833 0.00208333
> ZDEF 1 LINEAR 1 1
> TDEF 120 LINEAR 08Aug2015 1hr
> VARS 1
> rr 0 98 rairate [mm/hr]
> ENDVARS
>
> 2. Him.ctl
> DSET ${file_in_vor2}
> UNDEF -1.0
> OPTIONS yrev
> XDEF 280 LINEAR 121.05 0.1
> YDEF 240 LINEAR 22.95 0.1
> ZDEF 1 LINEAR 1 1
> TDEF 1 LINEAR 13:05Z08AUG2015 5mn
> VARS 1
> ALBEDO 0 1 reflectivity
> ENDVARS
>
> My next question where should I locate my lterp command??
> and how it would be like?
> I have tried this command below, it doesnor work
>
> 'define try=(rr, albedo.2, aave)'
> 'd try'
>
> Thank you very much for your help. I am very sorry for ask many questions.
>
> Best regards,
> wendi
>
>
>
>
>
>
> On Mon, Jan 23, 2017 at 6:48 PM, Andrew Friedman <andfried at gmail.com> wrote:
> Hi Wendi,
>
> You can use the command as in examples 4 & 5 for the lterp documentation:
> 'define newvar = (rr, albedo.2, aave)’
> What does newvar look like over specific gridboxes where you know there is data?
>
> Again, I would try first running a simplified version of your script that doesn’t call other scripts in order to simplify the problem as much as possible.
>
> Best, Andrew
>
> > On Jan 23, 2017, at 3:08 AM, wendi harjupa <wendiharjupa at gmail.com> wrote:
> >
> > Dear Mr. Andrew
> >
> > Many thanks for your great support.
> >
> > I think my problem is, how to use the lterp function. where should I write the lterp funtion
> > and how to write is. I just found some sample in using lterp command, but It did work.
> >
> > Based on the sample script that I have sent in the previous email, where should I locate my lterp
> > command?
> >
> > Thank you very much.
> >
> > Best regards,
> > wendi
> >
> > On Sun, Jan 22, 2017 at 11:43 PM, Andrew Friedman <andfried at gmail.com> wrote:
> > Hi Wendi,
> >
> > I don’t see an error offhand with your dimensions.
> > What does the numerical output of lterp look like in the regions where you have data? Do you get any values?
> >
> > Andrew
> >
> > > On Jan 21, 2017, at 4:11 AM, wendi harjupa <wendiharjupa at gmail.com> wrote:
> > >
> > > Dear Mr. Andrew,
> > >
> > > Many thanks for your great support,
> > >
> > > Below is q dims and q file of my data,
> > >
> > > ## Data 1 (large scale : 0.1x0.1 deg)
> > >
> > > q dims 1
> > > X is varying Lon = 121.05 to 148.95 X = 1 to 280
> > > Y is varying Lat = 22.95 to 46.85 Y = 1 to 240
> > > Z is fixed Lev = 1 Z = 1
> > > T is fixed Time = 13:05Z08AUG2015 T = 1
> > > E is fixed Ens = 1 E = 1
> > >
> > > q file 1
> > >
> > > Descriptor: Him.ctl
> > > Binary: /TAKAYASU/wendi/RDCA/rdca_201508080520.dat
> > > Type = Gridded
> > > Xsize = 280 Ysize = 240 Zsize = 1 Tsize = 1 Esize = 1
> > > Number of Variables = 1
> > > albedo 0 1 reflectivity
> > >
> > >
> > > ## data 2 (small scale : 0.002x0.003 deg)
> > >
> > > q dims 2
> > >
> > > X is varying Lon = 134.375 to 136.872 X = 1 to 800
> > > Y is varying Lat = 33.5833 to 35.5812 Y = 1 to 960
> > > Z is fixed Lev = 1 Z = 1
> > > T is fixed Time = 00Z08AUG2015 T = 1
> > > E is fixed Ens = 1 E = 1
> > >
> > > q file 2
> > >
> > > Binary: /TAKAYASU/wendi/xband/G000.grads/KINKI/20150808_0900-1700/data/KINKI00001- 20150808-1420-G000-EL000000.bin
> > > Type = Gridded
> > > Xsize = 800 Ysize = 960 Zsize = 1 Tsize = 120 Esize = 1
> > > Number of Variables = 1
> > > rr 0 98 rairate [mm/hr]
> > >
> > > is there any mistakes on that information?
> > >
> > > Best regards,
> > > wendi
> > >
> > >
> > >
> > >
> > > On Fri, Jan 20, 2017 at 6:25 PM, Andrew Friedman <andfried at gmail.com> wrote:
> > > Hi Wendi,
> > > What is your dimension environment?
> > > Can you post the output of ‘q dims’, ‘q file 1’ and ‘q file 2'
> > > Andrew
> > >
> > > > On Jan 20, 2017, at 1:28 AM, wendi harjupa <wendiharjupa at gmail.com> wrote:
> > > >
> > > > Dear Mr. Andrew
> > > >
> > > > Thank you very much for your explanation,
> > > > I am still struggling to solve it.
> > > >
> > > > Best regards,
> > > > wendi
> > > >
> > > > On Wed, Jan 18, 2017 at 10:16 PM, Andrew Friedman <andfried at gmail.com> wrote:
> > > > Hi Wendi,
> > > >
> > > > You can check ‘q dims’ to see what your time dimensions are.
> > > >
> > > > I recommend going through the website examples for lterp.gs, particularly #3-5 - these show situations that often come up about mismatched dimensions.
> > > > As they show, you often need to specify time or dfile, or some combination. Another possibility could be wrapped longitude coordinates.
> > > >
> > > > If none of these steps work, can you post a simplified version of your problem, without the anciallary scripts in your code?
> > > >
> > > > Andrew
> > > >
> > > > > On Jan 18, 2017, at 2:56 AM, wendi harjupa <wendiharjupa at gmail.com> wrote:
> > > > >
> > > > > Dear Mr Andrew,
> > > > >
> > > > > Many thanks for your response
> > > > >
> > > > > There is no specific error, but the is no change of result when I use
> > > > > 'd lterp command'.
> > > > >
> > > > > I set my dimension environment as below :
> > > > >
> > > > > 'set lat 33.000 36.000'
> > > > > 'set lon 134.000 137.000'
> > > > >
> > > > > I am little confused how to use the 'd lterp' function in my script program.
> > > > >
> > > > > Would you mind to give me more clue?
> > > > >
> > > > > Best regards,
> > > > > wendi
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Jan 18, 2017 at 5:55 AM, Andrew Friedman <andfried at gmail.com> wrote:
> > > > > Hi Wendi,
> > > > > What specific error message are you getting?
> > > > > A typical problem is that the time axes of the two files have to be the same - you may want to check your dimension environment.
> > > > > Andrew
> > > > >
> > > > > > On Jan 17, 2017, at 1:53 PM, wendi harjupa <wendiharjupa at gmail.com> wrote:
> > > > > >
> > > > > > Dear Mr. Andrew and colleagues
> > > > > >
> > > > > > Please tell me what wrong with this script. It does not work to interpolate the coarse grid to fine grid
> > > > > >
> > > > > > ##first data/resolution 0.002x0.003 (lat, lon)
> > > > > >
> > > > > > 'open ./Rain.ctl'
> > > > > > 'setXrain.gs'
> > > > > > 'setCOMMON.gs' ! set parameter (lon, lat, parea, grid off, etc)
> > > > > > # 'd rr' ! variable
> > > > > > 'xcbar 8.85 9.05 0.8 4 -fw 0.11 -fh 0.15 -edge triangle -fstep 1 -line on -lc 1'
> > > > > > 'close 1'
> > > > > >
> > > > > > ##second data/resolution 0.1x0.1 (lat, lon)
> > > > > >
> > > > > > 'open ./Him.ctl'
> > > > > > 'setCOMMON.gs'
> > > > > > 'setHimawari.gs'
> > > > > > # 'd albedo' ! variable
> > > > > > 'xcbar 6.3 9 0.23 0.37 -fw 0.11 -fh 0.15 -edge triangle -fs 2 -fo 1 -line on'
> > > > > > 'close 1'
> > > > > >
> > > > > > 'd lterp(rr, albedo.2, aave)'
> > > > > >
> > > > > > Any help will be very appreciated.
> > > > > > Thank you very much.
> > > > > >
> > > > > > Best regards,
> > > > > > wendi
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, Jan 17, 2017 at 7:12 PM, wendi harjupa <wendiharjupa at gmail.com> wrote:
> > > > > > Dear Mr. Andrew..
> > > > > >
> > > > > > Many thanks for your valuable information.
> > > > > >
> > > > > > Best regards,
> > > > > > wendi
> > > > > >
> > > > > > On Tue, Jan 17, 2017 at 6:45 PM, Andrew Friedman <andfried at gmail.com> wrote:
> > > > > > Hi Wendi,
> > > > > > You can use the function lterp for spatial interpolation: http://cola.gmu.edu/grads/gadoc/gradfunclterp.html
> > > > > > -Andrew
> > > > > >
> > > > > > > On Jan 17, 2017, at 10:29 AM, wendi harjupa <wendiharjupa at gmail.com> wrote:
> > > > > > >
> > > > > > > Dear All
> > > > > > >
> > > > > > > I got problem in overlaying two type of data.
> > > > > > > As I have attached the plot of data in this email.
> > > > > > >
> > > > > > > First data is rain data with resolution is about 0.002x0.003 deg (lon ,lat).
> > > > > > > The rain data is indicated by rainbow color.
> > > > > > > and second data is cloud data with resolution is 0.1x0.1 deg (lon, lat)
> > > > > > > The cloud data is indicated by gray color
> > > > > > >
> > > > > > > The plot looks not good. Is there any tools in grads to smooth the cloud data?
> > > > > > > Then, we can interpolate cloud data to become 0.005 or 0.001, and plot data will be more nice.
> > > > > > >
> > > > > > > Thank you very much for your attention and help.
> > > > > > >
> > > > > > > Best regards,
> > > > > > > wendi
> > > > > > >
> > > > > > > <large skale.png>_______________________________________________
> > > > > > > gradsusr mailing list
> > > > > > > gradsusr at gradsusr.org
> > > > > > > http://gradsusr.org/mailman/listinfo/gradsusr
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > gradsusr mailing list
> > > > > > gradsusr at gradsusr.org
> > > > > > http://gradsusr.org/mailman/listinfo/gradsusr
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > gradsusr mailing list
> > > > > > gradsusr at gradsusr.org
> > > > > > http://gradsusr.org/mailman/listinfo/gradsusr
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > gradsusr mailing list
> > > > > gradsusr at gradsusr.org
> > > > > http://gradsusr.org/mailman/listinfo/gradsusr
> > > > >
> > > > > _______________________________________________
> > > > > gradsusr mailing list
> > > > > gradsusr at gradsusr.org
> > > > > http://gradsusr.org/mailman/listinfo/gradsusr
> > > >
> > > >
> > > > _______________________________________________
> > > > gradsusr mailing list
> > > > gradsusr at gradsusr.org
> > > > http://gradsusr.org/mailman/listinfo/gradsusr
> > > >
> > > > _______________________________________________
> > > > gradsusr mailing list
> > > > gradsusr at gradsusr.org
> > > > http://gradsusr.org/mailman/listinfo/gradsusr
> > >
> > >
> > > _______________________________________________
> > > gradsusr mailing list
> > > gradsusr at gradsusr.org
> > > http://gradsusr.org/mailman/listinfo/gradsusr
> > >
> > > _______________________________________________
> > > gradsusr mailing list
> > > gradsusr at gradsusr.org
> > > http://gradsusr.org/mailman/listinfo/gradsusr
> >
> >
> > _______________________________________________
> > gradsusr mailing list
> > gradsusr at gradsusr.org
> > http://gradsusr.org/mailman/listinfo/gradsusr
> >
> > _______________________________________________
> > gradsusr mailing list
> > gradsusr at gradsusr.org
> > http://gradsusr.org/mailman/listinfo/gradsusr
>
>
> _______________________________________________
> gradsusr mailing list
> gradsusr at gradsusr.org
> http://gradsusr.org/mailman/listinfo/gradsusr
>
> _______________________________________________
> gradsusr mailing list
> gradsusr at gradsusr.org
> http://gradsusr.org/mailman/listinfo/gradsusr
More information about the gradsusr
mailing list