Hi NCL supporter,
Does NCL have KML support ?
Thanks
Ming Ge
On Thu, 05 Sep 2013 21:13:14 -0600
ncl-talk-request@ucar.edu wrote:
> Send ncl-talk mailing list submissions to
> ncl-talk@ucar.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
> or, via email, send a message with subject or body 'help' to
> ncl-talk-request@ucar.edu
>
> You can reach the person managing the list at
> ncl-talk-owner@ucar.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ncl-talk digest..."
>
>
> Today's Topics:
>
> 1. Re: High/Low labels not showing for gsn_csm_contour_map_ce()
> (A.J. Eiserloh)
> 2. Re: High/Low labels not showing for gsn_csm_contour_map_ce()
> (A.J. Eiserloh)
> 3. Re: High/Low labels not showing for gsn_csm_contour_map_ce()
> (Adam Phillips)
> 4. check_for_y_lat_coord ( ??? )
> 5. Re: check_for_y_lat_coord (Adam Phillips)
> 6. Re: cnFillPalette: last contour fill reverts to black
> (Kyle Griffin)
> 7. Re: check_for_y_lat_coord ( ??? )
> 8. Re: check_for_y_lat_coord (Adam Phillips)
> 9. Re: check_for_y_lat_coord ( ??? )
> 10. Re: check_for_y_lat_coord (Adam Phillips)
> 11. 2-6 days band pass filter (Soumik Basu)
> 12. Re: 2-6 days band pass filter (Dennis Shea)
> 13. meteogram from grib2 file (Luis Fernando Montana Roa)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 5 Sep 2013 11:02:10 -0700
>From: "A.J. Eiserloh" <arthur.eiserloh@gmail.com>
> Subject: Re: High/Low labels not showing for
> gsn_csm_contour_map_ce()
> To: Adam Phillips <asphilli@ucar.edu>
> Cc: "ncl-talk@ucar.edu USERS" <ncl-talk@ucar.edu>
> Message-ID:
> <CAGoaJHwut6_5DxFDn2KACjuK+Q7+op32LZ7TserCzOZecKqJRg@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Adam,
>
> When I took off the resources cnHighLabelString/cnLowLabelString,
>The lows
> and highs with the numbers appeared finally. However, it does not
>put H/L s
> for every high and low. I tried increasing the value for
> res@cnConpackParams= (/ "HLX:4, HLY:4" /) to a higher number for HLX
> and HLY, however, it did
> not change anything. So, for certain times my "low of interest" has
>an "L"
> associeated with it, but then for certain later times there is no L
>within
> the "low" but yet there are definitely contours around the "low".
>How can I
> get it to put a H/L stamp for every high/low ?
>
> I tried adding the res@cnHighLabelString = "H~B~$ZDV$~E~" and
> res@cnLowLabelString = "L~B~$ZDV$~E~" resources, but I noticed that
>it did
> not change anything, so I left those out. Also, I am not very
>familiar with
> that syntax.
>
> Thanks,
>
> A.J.
>
>
> On Thu, Sep 5, 2013 at 8:20 AM, Adam Phillips <asphilli@ucar.edu>
>wrote:
>
>> Hi A.J.,
>> You are telling NCL to not label the min/max values by setting the
>> cnHighLabelString/cnLowLabelString resources = "H"/"L"..
>>
>> According to the documentation here:
>>
>> http://www.ncl.ucar.edu/Document/Graphics/Resources/cn.shtml#cnHighLabelString
>>
>> http://www.ncl.ucar.edu/Document/Graphics/Resources/cn.shtml#cnLowLabelString
>> the defaults are:
>> res@cnHighLabelString = "H~B~$ZDV$~E~"
>> res@cnLowLabelString = "L~B~$ZDV$~E~"
>> (note that I replaced the : with ~ as that is what most people have
>>their
>> function code set to..)
>>
>> Try setting the resources as I have it above and see if that works..
>>If
>> not, please let ncl-talk know..
>> Adam
>>
>>
>> On 09/04/2013 06:04 PM, A.J. Eiserloh wrote:
>>
>> Thanks Adam,
>>
>> That worked, however, is there a way to put the minimum/maximum
>>values
>> under the L/H symbols? Right now, only the "L" for low shows up.
>>
>> -A.J.
>>
>>
>> On Wed, Sep 4, 2013 at 12:36 PM, Adam Phillips <asphilli@ucar.edu>
>>wrote:
>>
>>> Hi A.J.,
>>> I don't see anything amiss with your script. Take a look at this
>>>ncl-talk
>>> email from the archive:
>>> http://www.ncl.ucar.edu/Support/talk_archives/all/0877.html
>>> Specifically try setting cnConpackParams, and see if you can get the
>>> labels on there.
>>> If that resource doesn't help let ncl-talk know.
>>> Adam
>>>
>>>
>>> On 9/4/13 12:27 PM, A.J. Eiserloh wrote:
>>>
>>> Hi,
>>>
>>> I am trying to put high/low label marks on my contour map of 500 mb
>>> geopotential height surface but for some reason it does not seem to
>>>be
>>> working. Here is my script below:
>>>
>>> ;==============================================================
>>> load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_code.ncl"
>>> load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_csm.ncl"
>>> load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/contributed.ncl"
>>> load "$NCARG_ROOT/lib/ncarg/nclscripts/contrib/calendar_decode2.ncl"
>>> ;==============================================================
>>>
>>> begin
>>>
>>> f = addfile("./hgt.2012.nc","r")
>>>
>>> ;geopotential height
>>> hgt = short2flt(f->hgt) ; hgt(time,lev,lat,lon)
>>> ; short2flt() function uses scale_factor
>>>and
>>> add_offset attribute to convert
>>> hgt = hgt/(10.0)
>>> hgt@units = "dam"
>>> hgt@description = "Geopotential Height"
>>> time = f->time
>>> ntimes=dimsizes(time)
>>>
>>> lat = f->lat
>>> lon = f->lon
>>> lev = f->level
>>>
>>> nlat = dimsizes(lat)
>>> nlon = dimsizes(lon)
>>>
>>> ;convert times to dates
>>> times =fspan(time@actual_range(0),time@actual_range(1),ntimes)
>>> times@units= "hours since 1800-1-1 00:00:00"
>>> dates = calendar_decode2(times,-3)
>>>
>>> print(dates)
>>> ;create lat2d and lon2d arrays
>>> ;lat2d = conform_dims((/nlat,nlon/),lat,0)
>>> ;lon2d = conform_dims((/nlat,nlon/),lon,1)
>>>
>>> ;hgt@lat2d = lat2d
>>> ;hgt@lon2d = lon2d
>>>
>>>
>>> ;---------------------------------------------------------------
>>> ;Plot
>>> ;---------------------------------------------------------------
>>>
>>> ;What level do you want to plot?
>>> plev = 500.
>>> dateStart = ind(dates.eq."2012112800")
>>> dateEnd = ind(dates.eq."2012120318")
>>>
>>> ;do i=0,0 ; begin plotting loop
>>>
>>> fname = "500mb-"+dates(1335)
>>> wks = gsn_open_wks("png",fname)
>>>
>>> ;plot resources
>>> res = True
>>>
>>> res@tiMainString = " NCEP Reanalysis-2"
>>> res@tiMainFontAspectF = 1.4
>>> res@tiMainFontThicknessF = 0.80
>>> res@tiMainFontHeightF = 0.03
>>>
>>> res@gsnAddCyclic = False ; regional data
>>> res@tfDoNDCOverlay = False
>>>
>>> colr="black"
>>> res@mpFillOn = False
>>> res@mpGeophysicalLineColor = colr ; color of
>>> continental outlines
>>> res@mpPerimOn = True ; draw box
>>>around
>>> map
>>> res@mpGridLineDashPattern = 2 ; lat/lon
>>>lines
>>> as dashed
>>> res@mpDataBaseVersion = "MediumRes"
>>> res@mpOutlineBoundarySets = "GeophysicalAndUSStates" ; add state
>>> boundaries
>>> res@mpUSStateLineColor = colr
>>> res@mpGeophysicalLineColor = colr
>>> res@mpNationalLineColor = colr
>>> res@mpUSStateLineColor = colr
>>> res@mpGridLineColor = colr
>>> res@mpLimbLineColor = colr
>>> res@mpPerimLineColor = colr
>>> res@mpGeophysicalLineThicknessF = 1.0
>>> res@mpGridLineThicknessF = 1.0
>>> res@mpLimbLineThicknessF = 1.0
>>> res@mpNationalLineThicknessF = 1.0
>>> res@mpUSStateLineThicknessF = 1.0
>>>
>>> res@cnLevelSpacingF = 4
>>> res@cnLineLabelFontHeightF = 0.011
>>>
>>> res@cnHighLabelsOn = True; label highs
>>> res@cnHighLabelString = "H"; highs' label
>>> res@cnHighLabelFontHeightF = 0.013; larger H labels
>>> ; res@cnHighLabelBackgroundColor = "Transparent"; no box
>>> res@cnLowLabelsOn = True; label lows
>>> res@cnLowLabelString = "L"; lows' label
>>> res@cnLowLabelFontHeightF = 0.013; larger L labels
>>> ; res@cnLowLabelBackgroundColor = "Transparent"; no box
>>>
>>> res@mpLimitMode="LatLon"
>>> res@mpMinLatF = 20
>>> res@mpMaxLatF = 60
>>> res@mpMinLonF = -170
>>> res@mpMaxLonF = -110
>>>
>>> res@gsnLeftStringFontHeightF=0.015
>>> res@gsnRightStringFontHeightF=0.015
>>> res@gsnLeftString = hgt@description+" "+flt2string(plev)+"mb " +
>>> dates(1335)
>>> res@gsnRightString= hgt@units
>>>
>>> plot =
>>>gsn_csm_contour_map_ce(wks,hgt(1335,ind(lev.eq.plev),:,:),res)
>>>
>>> ;end do
>>>
>>> end
>>>
>>> I've attatched an image to show what it looks like so far.
>>>
>>> Any help would be much appreciated.
>>> Thanks,
>>>
>>> --
>>> Arthur J. Eiserloh, Jr.
>>> San Jose State University
>>> Graduate Student
>>> Dept. of Meteorology and Climate Science
>>>
>>>
>>> _______________________________________________
>>> ncl-talk mailing list
>>> List instructions, subscriber options,
>>>unsubscribe:http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>>>
>>>
>>
>>
>> --
>> Arthur J. Eiserloh, Jr.
>> San Jose State University
>> Graduate Student
>> Dept. of Meteorology and Climate Science
>>
>>
>> --
>> ______________________________________________________________
>> Adam Phillips asphilli@ucar.edu
>> NCAR/Climate and Global Dynamics Division (303) 497-1726
>> P.O. Box 3000
>> Boulder, CO 80307-3000 http://www.cgd.ucar.edu/cas/asphilli
>>
>>
>
>
> --
> Arthur J. Eiserloh, Jr.
> San Jose State University
> Graduate Student
> Dept. of Meteorology and Climate Science
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20130905/7acd5917/attachment.html
>
> ------------------------------
>
> Message: 2
> Date: Thu, 5 Sep 2013 11:08:05 -0700
>From: "A.J. Eiserloh" <arthur.eiserloh@gmail.com>
> Subject: Re: High/Low labels not showing for
> gsn_csm_contour_map_ce()
> To: Adam Phillips <asphilli@ucar.edu>
> Cc: "ncl-talk@ucar.edu USERS" <ncl-talk@ucar.edu>
> Message-ID:
> <CAGoaJHwHp+_dAWXc7XqfOeR6U70jk_QemTmwC+0qn=_U_cEdFQ@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I forgot to show that part of my code:
>
> res@cnLevelSpacingF = 4
> res@cnLineLabelFontHeightF = 0.011
>
> ;set High/Low Labels
> res@cnHighLabelsOn = True; label highs
> res@cnHighLabelPerimOn = False
> res@cnHighLabelFontHeightF = 0.015; larger H labels
> res@cnHighLabelBackgroundColor = "Transparent"
> res@cnLowLabelsOn = True; label lows
> res@cnLowLabelPerimOn = False
> res@cnLowLabelFontHeightF = 0.015; larger L labels
> res@cnLowLabelBackgroundColor = "Transparent"
> res@cnConpackParams = (/ "HLX:4, HLY:4" /)
> ; res@cnHighLabelString = "H~B~$ZDV$~E~"
> ; res@cnLowLabelString = "L~B~$ZDV$~E~"
>
> res@cnSmoothingOn = True
> res@cnSmoothingTensionF = 1.8
>
>
>
> On Thu, Sep 5, 2013 at 11:02 AM, A.J. Eiserloh
><arthur.eiserloh@gmail.com>wrote:
>
>> Hi Adam,
>>
>> When I took off the resources cnHighLabelString/cnLowLabelString,
>>The
>> lows and highs with the numbers appeared finally. However, it does
>>not put
>> H/L s for every high and low. I tried increasing the value for
>> res@cnConpackParams = (/ "HLX:4, HLY:4" /) to a higher number for
>>HLX and
>> HLY, however, it did not change anything. So, for certain times my
>>"low of
>> interest" has an "L" associeated with it, but then for certain later
>>times
>> there is no L within the "low" but yet there are definitely contours
>>around
>> the "low". How can I get it to put a H/L stamp for every high/low ?
>>
>> I tried adding the res@cnHighLabelString = "H~B~$ZDV$~E~" and
>> res@cnLowLabelString = "L~B~$ZDV$~E~" resources, but I noticed that
>>it
>> did not change anything, so I left those out. Also, I am not very
>>familiar
>> with that syntax.
>>
>> Thanks,
>>
>> A.J.
>>
>>
>> On Thu, Sep 5, 2013 at 8:20 AM, Adam Phillips <asphilli@ucar.edu>
>>wrote:
>>
>>> Hi A.J.,
>>> You are telling NCL to not label the min/max values by setting the
>>> cnHighLabelString/cnLowLabelString resources = "H"/"L"..
>>>
>>> According to the documentation here:
>>>
>>> http://www.ncl.ucar.edu/Document/Graphics/Resources/cn.shtml#cnHighLabelString
>>>
>>> http://www.ncl.ucar.edu/Document/Graphics/Resources/cn.shtml#cnLowLabelString
>>> the defaults are:
>>> res@cnHighLabelString = "H~B~$ZDV$~E~"
>>> res@cnLowLabelString = "L~B~$ZDV$~E~"
>>> (note that I replaced the : with ~ as that is what most people have
>>>their
>>> function code set to..)
>>>
>>> Try setting the resources as I have it above and see if that works..
>>>If
>>> not, please let ncl-talk know..
>>> Adam
>>>
>>>
>>> On 09/04/2013 06:04 PM, A.J. Eiserloh wrote:
>>>
>>> Thanks Adam,
>>>
>>> That worked, however, is there a way to put the minimum/maximum
>>>values
>>> under the L/H symbols? Right now, only the "L" for low shows up.
>>>
>>> -A.J.
>>>
>>>
>>> On Wed, Sep 4, 2013 at 12:36 PM, Adam Phillips <asphilli@ucar.edu>
>>>wrote:
>>>
>>>> Hi A.J.,
>>>> I don't see anything amiss with your script. Take a look at this
>>>> ncl-talk email from the archive:
>>>> http://www.ncl.ucar.edu/Support/talk_archives/all/0877.html
>>>> Specifically try setting cnConpackParams, and see if you can get the
>>>> labels on there.
>>>> If that resource doesn't help let ncl-talk know.
>>>> Adam
>>>>
>>>>
>>>> On 9/4/13 12:27 PM, A.J. Eiserloh wrote:
>>>>
>>>> Hi,
>>>>
>>>> I am trying to put high/low label marks on my contour map of 500 mb
>>>> geopotential height surface but for some reason it does not seem to
>>>>be
>>>> working. Here is my script below:
>>>>
>>>> ;==============================================================
>>>> load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_code.ncl"
>>>> load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_csm.ncl"
>>>> load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/contributed.ncl"
>>>> load "$NCARG_ROOT/lib/ncarg/nclscripts/contrib/calendar_decode2.ncl"
>>>> ;==============================================================
>>>>
>>>> begin
>>>>
>>>> f = addfile("./hgt.2012.nc","r")
>>>>
>>>> ;geopotential height
>>>> hgt = short2flt(f->hgt) ; hgt(time,lev,lat,lon)
>>>> ; short2flt() function uses scale_factor
>>>>and
>>>> add_offset attribute to convert
>>>> hgt = hgt/(10.0)
>>>> hgt@units = "dam"
>>>> hgt@description = "Geopotential Height"
>>>> time = f->time
>>>> ntimes=dimsizes(time)
>>>>
>>>> lat = f->lat
>>>> lon = f->lon
>>>> lev = f->level
>>>>
>>>> nlat = dimsizes(lat)
>>>> nlon = dimsizes(lon)
>>>>
>>>> ;convert times to dates
>>>> times =fspan(time@actual_range(0),time@actual_range(1),ntimes)
>>>> times@units= "hours since 1800-1-1 00:00:00"
>>>> dates = calendar_decode2(times,-3)
>>>>
>>>> print(dates)
>>>> ;create lat2d and lon2d arrays
>>>> ;lat2d = conform_dims((/nlat,nlon/),lat,0)
>>>> ;lon2d = conform_dims((/nlat,nlon/),lon,1)
>>>>
>>>> ;hgt@lat2d = lat2d
>>>> ;hgt@lon2d = lon2d
>>>>
>>>>
>>>> ;---------------------------------------------------------------
>>>> ;Plot
>>>> ;---------------------------------------------------------------
>>>>
>>>> ;What level do you want to plot?
>>>> plev = 500.
>>>> dateStart = ind(dates.eq."2012112800")
>>>> dateEnd = ind(dates.eq."2012120318")
>>>>
>>>> ;do i=0,0 ; begin plotting loop
>>>>
>>>> fname = "500mb-"+dates(1335)
>>>> wks = gsn_open_wks("png",fname)
>>>>
>>>> ;plot resources
>>>> res = True
>>>>
>>>> res@tiMainString = " NCEP Reanalysis-2"
>>>> res@tiMainFontAspectF = 1.4
>>>> res@tiMainFontThicknessF = 0.80
>>>> res@tiMainFontHeightF = 0.03
>>>>
>>>> res@gsnAddCyclic = False ; regional data
>>>> res@tfDoNDCOverlay = False
>>>>
>>>> colr="black"
>>>> res@mpFillOn = False
>>>> res@mpGeophysicalLineColor = colr ; color of
>>>> continental outlines
>>>> res@mpPerimOn = True ; draw box
>>>> around map
>>>> res@mpGridLineDashPattern = 2 ; lat/lon
>>>>lines
>>>> as dashed
>>>> res@mpDataBaseVersion = "MediumRes"
>>>> res@mpOutlineBoundarySets = "GeophysicalAndUSStates" ; add state
>>>> boundaries
>>>> res@mpUSStateLineColor = colr
>>>> res@mpGeophysicalLineColor = colr
>>>> res@mpNationalLineColor = colr
>>>> res@mpUSStateLineColor = colr
>>>> res@mpGridLineColor = colr
>>>> res@mpLimbLineColor = colr
>>>> res@mpPerimLineColor = colr
>>>> res@mpGeophysicalLineThicknessF = 1.0
>>>> res@mpGridLineThicknessF = 1.0
>>>> res@mpLimbLineThicknessF = 1.0
>>>> res@mpNationalLineThicknessF = 1.0
>>>> res@mpUSStateLineThicknessF = 1.0
>>>>
>>>> res@cnLevelSpacingF = 4
>>>> res@cnLineLabelFontHeightF = 0.011
>>>>
>>>> res@cnHighLabelsOn = True; label highs
>>>> res@cnHighLabelString = "H"; highs' label
>>>> res@cnHighLabelFontHeightF = 0.013; larger H labels
>>>> ; res@cnHighLabelBackgroundColor = "Transparent"; no box
>>>> res@cnLowLabelsOn = True; label lows
>>>> res@cnLowLabelString = "L"; lows' label
>>>> res@cnLowLabelFontHeightF = 0.013; larger L labels
>>>> ; res@cnLowLabelBackgroundColor = "Transparent"; no box
>>>>
>>>> res@mpLimitMode="LatLon"
>>>> res@mpMinLatF = 20
>>>> res@mpMaxLatF = 60
>>>> res@mpMinLonF = -170
>>>> res@mpMaxLonF = -110
>>>>
>>>> res@gsnLeftStringFontHeightF=0.015
>>>> res@gsnRightStringFontHeightF=0.015
>>>> res@gsnLeftString = hgt@description+" "+flt2string(plev)+"mb " +
>>>> dates(1335)
>>>> res@gsnRightString= hgt@units
>>>>
>>>> plot =
>>>>gsn_csm_contour_map_ce(wks,hgt(1335,ind(lev.eq.plev),:,:),res)
>>>>
>>>> ;end do
>>>>
>>>> end
>>>>
>>>> I've attatched an image to show what it looks like so far.
>>>>
>>>> Any help would be much appreciated.
>>>> Thanks,
>>>>
>>>> --
>>>> Arthur J. Eiserloh, Jr.
>>>> San Jose State University
>>>> Graduate Student
>>>> Dept. of Meteorology and Climate Science
>>>>
>>>>
>>>> _______________________________________________
>>>> ncl-talk mailing list
>>>> List instructions, subscriber options,
>>>>unsubscribe:http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>>>>
>>>>
>>>
>>>
>>> --
>>> Arthur J. Eiserloh, Jr.
>>> San Jose State University
>>> Graduate Student
>>> Dept. of Meteorology and Climate Science
>>>
>>>
>>> --
>>> ______________________________________________________________
>>> Adam Phillips asphilli@ucar.edu
>>> NCAR/Climate and Global Dynamics Division (303) 497-1726
>>> P.O. Box 3000
>>> Boulder, CO 80307-3000 http://www.cgd.ucar.edu/cas/asphilli
>>>
>>>
>>
>>
>> --
>> Arthur J. Eiserloh, Jr.
>> San Jose State University
>> Graduate Student
>> Dept. of Meteorology and Climate Science
>>
>
>
>
> --
> Arthur J. Eiserloh, Jr.
> San Jose State University
> Graduate Student
> Dept. of Meteorology and Climate Science
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20130905/5c45cd7f/attachment.html
>
> ------------------------------
>
> Message: 3
> Date: Thu, 05 Sep 2013 12:28:43 -0600
>From: Adam Phillips <asphilli@ucar.edu>
> Subject: Re: High/Low labels not showing for
> gsn_csm_contour_map_ce()
> To: "A.J. Eiserloh" <arthur.eiserloh@gmail.com>
> Cc: "ncl-talk@ucar.edu USERS" <ncl-talk@ucar.edu>
> Message-ID: <5228CD5B.9050700@ucar.edu>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi A.J.,
> Try setting:
> res@cnConpackParams = (/ "HLX:1, HLY:1" /)
> In testing it seems like lower numbers increase the number of
>high/low
> labels.
>
> As far as cnHighLabelString / cnLowLabelString settings go: The
>default
> (for highs) is "H~B~$ZDV$~E~", thus not setting the resource is the
>same
> as setting it to "H~B~$ZDV$~E~". If you are happy enough with the
>format
> of the high/low labels there's no need to decipher what that coding
> means. But if you're interested see here:
> http://www.ncl.ucar.edu/Document/Graphics/function_code.shtml
> ~B~ = subscript, ~E~ = stop the subscripting, and $ZDV$ is equal to
>the
> identified high/low value and that value will be formatted according
>to
> the cnHighLabelFormat resource:
> http://www.ncl.ucar.edu/Document/Graphics/Resources/cn.shtml#cnHighLabelFormat
> Adam
>
> On 09/05/2013 12:08 PM, A.J. Eiserloh wrote:
>> I forgot to show that part of my code:
>>
>> res@cnLevelSpacingF = 4
>> res@cnLineLabelFontHeightF = 0.011
>>
>> ;set High/Low Labels
>> res@cnHighLabelsOn = True; label highs
>> res@cnHighLabelPerimOn = False
>> res@cnHighLabelFontHeightF = 0.015; larger H labels
>> res@cnHighLabelBackgroundColor = "Transparent"
>> res@cnLowLabelsOn = True; label lows
>> res@cnLowLabelPerimOn = False
>> res@cnLowLabelFontHeightF = 0.015; larger L labels
>> res@cnLowLabelBackgroundColor = "Transparent"
>> res@cnConpackParams = (/ "HLX:4, HLY:4" /)
>> ; res@cnHighLabelString = "H~B~$ZDV$~E~"
>> ; res@cnLowLabelString = "L~B~$ZDV$~E~"
>>
>> res@cnSmoothingOn = True
>> res@cnSmoothingTensionF = 1.8
>>
>>
>>
>> On Thu, Sep 5, 2013 at 11:02 AM, A.J. Eiserloh
>> <arthur.eiserloh@gmail.com <mailto:arthur.eiserloh@gmail.com>>
>>wrote:
>>
>> Hi Adam,
>>
>> When I took off the resources
>>cnHighLabelString/cnLowLabelString,
>> The lows and highs with the numbers appeared finally. However,
>>it
>> does not put H/L s for every high and low. I tried increasing
>>the
>> value for res@cnConpackParams = (/ "HLX:4, HLY:4" /) to a higher
>> number for HLX and HLY, however, it did not change anything. So,
>> for certain times my "low of interest" has an "L" associeated
>>with
>> it, but then for certain later times there is no L within the
>> "low" but yet there are definitely contours around the "low".
>>How
>> can I get it to put a H/L stamp for every high/low ?
>>
>> I tried adding the res@cnHighLabelString = "H~B~$ZDV$~E~"and
>> res@cnLowLabelString = "L~B~$ZDV$~E~" resources, but I noticed
>> that it did not change anything, so I left those out. Also, I am
>> not very familiar with that syntax.
>>
>> Thanks,
>>
>> A.J.
>>
>>
>> On Thu, Sep 5, 2013 at 8:20 AM, Adam Phillips <asphilli@ucar.edu
>> <mailto:asphilli@ucar.edu>> wrote:
>>
>> Hi A.J.,
>> You are telling NCL to not label the min/max values by
>>setting
>> the cnHighLabelString/cnLowLabelString resources = "H"/"L"..
>>
>> According to the documentation here:
>> http://www.ncl.ucar.edu/Document/Graphics/Resources/cn.shtml#cnHighLabelString
>> http://www.ncl.ucar.edu/Document/Graphics/Resources/cn.shtml#cnLowLabelString
>> the defaults are:
>> res@cnHighLabelString = "H~B~$ZDV$~E~"
>> res@cnLowLabelString = "L~B~$ZDV$~E~"
>> (note that I replaced the : with ~ as that is what most
>>people
>> have their function code set to..)
>>
>> Try setting the resources as I have it above and see if that
>> works.. If not, please let ncl-talk know..
>> Adam
>>
>>
>> On 09/04/2013 06:04 PM, A.J. Eiserloh wrote:
>>> Thanks Adam,
>>>
>>> That worked, however, is there a way to put the
>>> minimum/maximum values under the L/H symbols? Right now,
>>>only
>>> the "L" for low shows up.
>>>
>>> -A.J.
>>>
>>>
>>> On Wed, Sep 4, 2013 at 12:36 PM, Adam Phillips
>>> <asphilli@ucar.edu <mailto:asphilli@ucar.edu>> wrote:
>>>
>>> Hi A.J.,
>>> I don't see anything amiss with your script. Take a look
>>> at this ncl-talk email from the archive:
>>> http://www.ncl.ucar.edu/Support/talk_archives/all/0877.html
>>> Specifically try setting cnConpackParams, and see if you
>>> can get the labels on there.
>>> If that resource doesn't help let ncl-talk know.
>>> Adam
>>>
>>>
>>> On 9/4/13 12:27 PM, A.J. Eiserloh wrote:
>>>> Hi,
>>>>
>>>> I am trying to put high/low label marks on my contour
>>>> map of 500 mb geopotential height surface but for some
>>>> reason it does not seem to be working. Here is my script
>>>> below:
>>>>
>>>> ;==============================================================
>>>> load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_code.ncl"
>>>> load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_csm.ncl"
>>>> load
>>>>"$NCARG_ROOT/lib/ncarg/nclscripts/csm/contributed.ncl"
>>>> load
>>>> "$NCARG_ROOT/lib/ncarg/nclscripts/contrib/calendar_decode2.ncl"
>>>> ;==============================================================
>>>>
>>>> begin
>>>>
>>>> f = addfile("./hgt.2012.nc <http://hgt.2012.nc>","r")
>>>>
>>>> ;geopotential height
>>>> hgt = short2flt(f->hgt) ; hgt(time,lev,lat,lon)
>>>> ; short2flt() function uses scale_factor and
>>>> add_offset attribute to convert
>>>> hgt = hgt/(10.0)
>>>> hgt@units = "dam"
>>>> hgt@description = "Geopotential Height"
>>>> time = f->time
>>>> ntimes=dimsizes(time)
>>>>
>>>> lat = f->lat
>>>> lon = f->lon
>>>> lev = f->level
>>>>
>>>> nlat = dimsizes(lat)
>>>> nlon = dimsizes(lon)
>>>>
>>>> ;convert times to dates
>>>> times
>>>> =fspan(time@actual_range(0),time@actual_range(1),ntimes)
>>>> times@units= "hours since 1800-1-1 00:00:00"
>>>> dates = calendar_decode2(times,-3)
>>>>
>>>> print(dates)
>>>> ;create lat2d and lon2d arrays
>>>> ;lat2d = conform_dims((/nlat,nlon/),lat,0)
>>>> ;lon2d = conform_dims((/nlat,nlon/),lon,1)
>>>>
>>>> ;hgt@lat2d = lat2d
>>>> ;hgt@lon2d = lon2d
>>>>
>>>>
>>>> ;---------------------------------------------------------------
>>>> ;Plot
>>>> ;---------------------------------------------------------------
>>>>
>>>> ;What level do you want to plot?
>>>> plev = 500.
>>>> dateStart = ind(dates.eq."2012112800 <tel:2012112800>")
>>>> dateEnd = ind(dates.eq."2012120318 <tel:2012120318>")
>>>>
>>>> ;do i=0,0 ; begin plotting loop
>>>>
>>>> fname = "500mb-"+dates(1335)
>>>> wks = gsn_open_wks("png",fname)
>>>>
>>>> ;plot resources
>>>> res = True
>>>>
>>>> res@tiMainString = " NCEP Reanalysis-2"
>>>> res@tiMainFontAspectF = 1.4
>>>> res@tiMainFontThicknessF = 0.80
>>>> res@tiMainFontHeightF = 0.03
>>>>
>>>> res@gsnAddCyclic = False ; regional data
>>>> res@tfDoNDCOverlay = False
>>>>
>>>> colr="black"
>>>> res@mpFillOn = False
>>>> res@mpGeophysicalLineColor = colr ; color of
>>>> continental outlines
>>>> res@mpPerimOn = True ; draw box
>>>> around map
>>>> res@mpGridLineDashPattern = 2 ; lat/lon lines as
>>>> dashed
>>>> res@mpDataBaseVersion = "MediumRes"
>>>> res@mpOutlineBoundarySets = "GeophysicalAndUSStates" ;
>>>> add state boundaries
>>>> res@mpUSStateLineColor = colr
>>>> res@mpGeophysicalLineColor = colr
>>>> res@mpNationalLineColor = colr
>>>> res@mpUSStateLineColor = colr
>>>> res@mpGridLineColor = colr
>>>> res@mpLimbLineColor = colr
>>>> res@mpPerimLineColor = colr
>>>> res@mpGeophysicalLineThicknessF = 1.0
>>>> res@mpGridLineThicknessF = 1.0
>>>> res@mpLimbLineThicknessF = 1.0
>>>> res@mpNationalLineThicknessF = 1.0
>>>> res@mpUSStateLineThicknessF = 1.0
>>>>
>>>> res@cnLevelSpacingF = 4
>>>> res@cnLineLabelFontHeightF = 0.011
>>>>
>>>> res@cnHighLabelsOn = True; label highs
>>>> res@cnHighLabelString = "H"; highs' label
>>>> res@cnHighLabelFontHeightF = 0.013; larger H labels
>>>> ; res@cnHighLabelBackgroundColor = "Transparent"; no
>>>>box
>>>> res@cnLowLabelsOn = True; label lows
>>>> res@cnLowLabelString = "L"; lows' label
>>>> res@cnLowLabelFontHeightF = 0.013; larger L labels
>>>> ; res@cnLowLabelBackgroundColor = "Transparent"; no
>>>>box
>>>>
>>>> res@mpLimitMode="LatLon"
>>>> res@mpMinLatF = 20
>>>> res@mpMaxLatF = 60
>>>> res@mpMinLonF = -170
>>>> res@mpMaxLonF = -110
>>>>
>>>> res@gsnLeftStringFontHeightF=0.015
>>>> <mailto:res@gsnLeftStringFontHeightF=0.015>
>>>> res@gsnRightStringFontHeightF=0.015
>>>> <mailto:res@gsnRightStringFontHeightF=0.015>
>>>> res@gsnLeftString = hgt@description+"
>>>> "+flt2string(plev)+"mb " + dates(1335)
>>>> res@gsnRightString= hgt@units
>>>>
>>>> plot =
>>>> gsn_csm_contour_map_ce(wks,hgt(1335,ind(lev.eq.plev),:,:),res)
>>>>
>>>> ;end do
>>>>
>>>> end
>>>>
>>>> I've attatched an image to show what it looks like so
>>>>far.
>>>>
>>>> Any help would be much appreciated.
>>>> Thanks,
>>>>
>>>> --
>>>> Arthur J. Eiserloh, Jr.
>>>> San Jose State University
>>>> Graduate Student
>>>> Dept. of Meteorology and Climate Science
>>>>
>>>>
>>>> _______________________________________________
>>>> ncl-talk mailing list
>>>> List instructions, subscriber options, unsubscribe:
>>>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>>>
>>>
>>>
>>>
>>> --
>>> Arthur J. Eiserloh, Jr.
>>> San Jose State University
>>> Graduate Student
>>> Dept. of Meteorology and Climate Science
>>
>> --
>> ______________________________________________________________
>> Adam Phillipsasphilli@ucar.edu <mailto:asphilli@ucar.edu>
>> NCAR/Climate and Global Dynamics Division(303) 497-1726
>> <tel:%28303%29%20497-1726>
>> P.O. Box 3000
>> Boulder, CO 80307-3000http://www.cgd.ucar.edu/cas/asphilli
>>
>>
>>
>>
>> --
>> Arthur J. Eiserloh, Jr.
>> San Jose State University
>> Graduate Student
>> Dept. of Meteorology and Climate Science
>>
>>
>>
>>
>> --
>> Arthur J. Eiserloh, Jr.
>> San Jose State University
>> Graduate Student
>> Dept. of Meteorology and Climate Science
>>
>>
>> _______________________________________________
>> ncl-talk mailing list
>> List instructions, subscriber options, unsubscribe:
>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
> --
> ______________________________________________________________
> Adam Phillips asphilli@ucar.edu
> NCAR/Climate and Global Dynamics Division (303) 497-1726
> P.O. Box 3000
> Boulder, CO 80307-3000 http://www.cgd.ucar.edu/cas/asphilli
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20130905/51facca1/attachment.html
>
> ------------------------------
>
> Message: 4
> Date: Fri, 6 Sep 2013 02:39:17 +0800
>From: " ??? "<557xiaozhu@163.com>
> Subject: check_for_y_lat_coord
> To: "ncl-talk@ucar.edu USERS"<ncl-talk@ucar.edu>
> Message-ID: <325dcdf1.2f.140ef6bfde9.Coremail.557xiaozhu@163.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi All,
> I am trying to plot the geostrophic current fields from aviso. And
>get some screen output and error messages as follow,
>
> (0) 19930101
>
> Variable: u
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
> Coordinates:
> NbLongitudes: [98.33333333332349..290.9999999999709]
> NbLatitudes: [-17.79766126545592..60.88112837177402]
> Number Of Attributes: 5
> date : 1993-01-01 00:00:00.000000 UTC
> Date_CNES_JD : 15706
> units : cm/s
> long_name : U
> _FillValue : 1.844674e+19
>
> Variable: v
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
> Coordinates:
> NbLongitudes: [98.33333333332349..290.9999999999709]
> NbLatitudes: [-17.79766126545592..60.88112837177402]
> Number Of Attributes: 5
> _FillValue : 1.844674e+19
> long_name : V
> units : cm/s
> Date_CNES_JD : 15706
> date : 1993-01-01 00:00:00.000000 UTC
>
> Variable: speed
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [579] x [287]
> Coordinates:
> Number Of Attributes: 1
> _FillValue : 1.844674e+19
> (0) check_for_y_lat_coord: Warning: Data either does not contain
>a valid latitude coordinate array or doesn't contain one at all.
> (0) A valid latitude coordinate array should have a 'units'
>attribute equal to one of the following values:
> (0) 'degrees_north' 'degrees-north' 'degree_north' 'degrees
>north' 'degrees_N' 'Degrees_north' 'degree_N' 'degreeN' 'degreesN'
>'deg north'
> (0) check_for_lon_coord: Warning: Data either does not contain a
>valid longitude coordinate array or doesn't contain one at all.
> (0) A valid longitude coordinate array should have a 'units'
>attribute equal to one of the following values:
> (0) 'degrees_east' 'degrees-east' 'degree_east' 'degrees
>east' 'degrees_E' 'Degrees_east' 'degree_E' 'degreeE' 'degreesE' 'deg
>east'
> (0) gsn_csm_map_ce: Warning: you set mpMaxLonF to a value > 180,
>but
> (0) didn't set mpCenterLonF. Setting
>mpCenterLonF to 194.5
>
> My code is as follow,
>
> do nt=nb,ne
> in = addfile(infile(nt-1),"r")
> utc_date = str_get_cols(infile(nt-1),44,51)
> print(""+utc_date)
>
> ;************************************************
> ; read in zonal [u] and meridional [v] winds
> ;************************************************
> tmp = in->Grid_0001
> u = tmp({lon_min:lon_max},{lat_min:lat_max}) ;/100.0
> tmp = in->Grid_0002
> v = tmp({lon_min:lon_max},{lat_min:lat_max}) ;/100.0
> speed = sqrt(u^2 + v^2)
>
> vcres@tiMainString = "Geostrophic Current Field"
> vcres@gsnLeftString = utc_date
> vcres@gsnRightString = "m/s"
>
> wks = gsn_open_wks(wks_type ,"uv_"+utc_date) ;
>open a ps file
> gsn_define_colormap(wks,"rainbow") ;"BlAqGrYeOrRe") ;
>choose colormap
> printVarSummary(u)
> printVarSummary(v)
> printVarSummary(speed)
> plot=gsn_csm_vector_scalar_map_ce(wks,u,v,speed,vcres) ; create
>plot
> end do
>
> Anyone can help me for figuring out the error? Thanks.
>
> 2013-09-06
>
>
>
> ???
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20130906/5b105f5f/attachment.html
>
> ------------------------------
>
> Message: 5
> Date: Thu, 05 Sep 2013 12:56:04 -0600
>From: Adam Phillips <asphilli@ucar.edu>
> Subject: Re: check_for_y_lat_coord
> To: ??? <557xiaozhu@163.com>
> Cc: "ncl-talk@ucar.edu USERS" <ncl-talk@ucar.edu>
> Message-ID: <5228D3C4.2080801@ucar.edu>
> Content-Type: text/plain; charset="utf-8"
>
> Thanks for sending printVarSummary's of your three arrays, as that
> likely identifies the issue. Unlike your u and v arrays, your speed
> array does not have any metadata/coordinate variables associated
>with it.
>
> Try adding this after you create your speed array:
> copy_VarCoords(u,speed)
>
> Alternatively, you can do this:
> speed = u
> speed = (/ sqrt(u^2 + v^2) /) ; overwrite speed values, but leave
>the
> metadata
>
> This is all assuming that your NbLongitudes / NbLatitudes have units
> attributes set. See this FAQ here:
> http://www.ncl.ucar.edu/FAQ/#err_msgs_027
>
>Finally, note that your u/v/speed arrays are dimensioned longitude by
> latitude. The gsn_csm_vector_scalar_map_ce plotting function expects
>the
> order to be latitude by longitude. Thus, you will have to reorder
>your
> dimensions like this:
> plot=gsn_csm_vector_scalar_map_ce(wks,u(NbLatitudes|:,NbLongitudes|:),v(NbLatitudes|:,NbLongitudes|:),speed(NbLatitudes|:,NbLongitudes|:),vcres)
>
>
> Hope that helps. If you have any further questions please respond
>only
> to the ncl-talk email list.
> Adam
>
> On 09/05/2013 12:39 PM, ??? wrote:
>> Hi All,
>> I am trying to plot the geostrophic current fields from aviso.
>>And
>> get some screen output and error messages as follow,
>> (0) 19930101
>> Variable: u
>> Type: float
>> Total Size: 664692 bytes
>> 166173 values
>> Number of Dimensions: 2
>> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
>> Coordinates:
>> NbLongitudes: [98.33333333332349..290.9999999999709]
>> NbLatitudes: [-17.79766126545592..60.88112837177402]
>> Number Of Attributes: 5
>> date : 1993-01-01 00:00:00.000000 UTC
>> Date_CNES_JD : 15706
>> units : cm/s
>> long_name : U
>> _FillValue : 1.844674e+19
>> Variable: v
>> Type: float
>> Total Size: 664692 bytes
>> 166173 values
>> Number of Dimensions: 2
>> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
>> Coordinates:
>> NbLongitudes: [98.33333333332349..290.9999999999709]
>> NbLatitudes: [-17.79766126545592..60.88112837177402]
>> Number Of Attributes: 5
>> _FillValue : 1.844674e+19
>> long_name : V
>> units : cm/s
>> Date_CNES_JD : 15706
>> date : 1993-01-01 00:00:00.000000 UTC
>> Variable: speed
>> Type: float
>> Total Size: 664692 bytes
>> 166173 values
>> Number of Dimensions: 2
>> Dimensions and sizes: [579] x [287]
>> Coordinates:
>> Number Of Attributes: 1
>> _FillValue : 1.844674e+19
>> (0) check_for_y_lat_coord: Warning: Data either does not contain
>>a
>> valid latitude coordinate array or doesn't contain one at all.
>> (0) A valid latitude coordinate array should have a 'units'
>> attribute equal to one of the following values:
>> (0) 'degrees_north' 'degrees-north' 'degree_north' 'degrees
>> north' 'degrees_N' 'Degrees_north' 'degree_N' 'degreeN' 'degreesN'
>> 'deg north'
>> (0) check_for_lon_coord: Warning: Data either does not contain a
>> valid longitude coordinate array or doesn't contain one at all.
>> (0) A valid longitude coordinate array should have a 'units'
>> attribute equal to one of the following values:
>> (0) 'degrees_east' 'degrees-east' 'degree_east' 'degrees
>>east'
>> 'degrees_E' 'Degrees_east' 'degree_E' 'degreeE' 'degreesE' 'deg
>>east'
>> (0) gsn_csm_map_ce: Warning: you set mpMaxLonF to a value > 180,
>>but
>> (0) didn't set mpCenterLonF. Setting
>>mpCenterLonF
>> to 194.5
>> My code is as follow,
>> do nt=nb,ne
>> in = addfile(infile(nt-1),"r")
>> utc_date = str_get_cols(infile(nt-1),44,51)
>> print(""+utc_date)
>>
>> ;************************************************
>> ; read in zonal [u] and meridional [v] winds
>> ;************************************************
>> tmp = in->Grid_0001
>> u = tmp({lon_min:lon_max},{lat_min:lat_max}) ;/100.0
>> tmp = in->Grid_0002
>> v = tmp({lon_min:lon_max},{lat_min:lat_max}) ;/100.0
>> speed = sqrt(u^2 + v^2)
>>
>> vcres@tiMainString <mailto:vcres@tiMainString> =
>>"Geostrophic
>> Current Field"
>> vcres@gsnLeftString <mailto:vcres@gsnLeftString> = utc_date
>> vcres@gsnRightString <mailto:vcres@gsnRightString> = "m/s"
>> wks = gsn_open_wks(wks_type ,"uv_"+utc_date) ;
>> open a ps file
>> gsn_define_colormap(wks,"rainbow") ;"BlAqGrYeOrRe") ;
>> choose colormap
>> printVarSummary(u)
>> printVarSummary(v)
>> printVarSummary(speed)
>> plot=gsn_csm_vector_scalar_map_ce(wks,u,v,speed,vcres) ; create
>>plot
>> end do
>> Anyone can help me for figuring out the error? Thanks.
>> 2013-09-06
>> ------------------------------------------------------------------------
>> ???
>>
>>
>> _______________________________________________
>> ncl-talk mailing list
>> List instructions, subscriber options, unsubscribe:
>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
> --
> ______________________________________________________________
> Adam Phillips asphilli@ucar.edu
> NCAR/Climate and Global Dynamics Division (303) 497-1726
> P.O. Box 3000
> Boulder, CO 80307-3000 http://www.cgd.ucar.edu/cas/asphilli
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20130905/ad72f565/attachment.html
>
> ------------------------------
>
> Message: 6
> Date: Thu, 5 Sep 2013 14:00:30 -0500
>From: Kyle Griffin <ksgriffin2@wisc.edu>
> Subject: Re: cnFillPalette: last contour fill reverts to
> black
> To: jonathan meyer <tallj03@hotmail.com>
> Cc: "ncl-talk@ucar.edu" <ncl-talk@ucar.edu>
> Message-ID:
> <CAKt9o=h4ej8etLf5gBAr6-vHFNsK8VOZj_=LU8pmnMimUYgxKQ@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Jon,
>
> You should note that NCL is a zero-index language. This means that
>your
> colors are indexed 0-253 for that table, as BlueYellowRed contains
>256
> colors as a color map and 254 as a color palette.
>
> http://www.ncl.ucar.edu/Document/Graphics/ColorTables/BlueYellowRed.shtml
>
> Without looking at your code, it looks like you're trying to
>explicitly
> reference a 255th color, which simply doesn't exist. There are a few
>ways
> to manage this if you need a full 255 colors. The most common is
>probably
> cnSpanFillPalette, which I'm pretty sure will duplicate colors at
>points
> within the spectrum to create the extra colors if the count of your
>levels
> exceeds the count of your colors. It's generally used for making a
>plot
> with fewer plot levels than there are colors, however. If you are
>looking
> to do something else with the colors, I can give you some more
>complicated
>FillColor management suggestions as well that I tend to use in most
>of my
> plots.
>
> http://www.ncl.ucar.edu/Document/Graphics/Resources/cn.shtml#cnSpanFillPalette
>
> Let us know if you need any additional help...
>
>
> Kyle
>
> ----------------------------------------
> Kyle S. Griffin
> Department of Atmospheric and Oceanic Sciences
> University of Wisconsin - Madison
> Room 1421
> 1225 W Dayton St, Madison, WI 53706
> Email: ksgriffin2@wisc.edu
>
>
> On Thu, Sep 5, 2013 at 12:46 PM, jonathan meyer
><tallj03@hotmail.com> wrote:
>
>> Hi Devs,
>>
>> I've been enjoying the functionality of the cnFillPalette resource
>>for my
>> panel plots where different color tables are desired.
>>
>> I am wondering how to reset the last contour fill which is
>>reassigned to a
>> black color (foreground color).
>>
>> From the documentation:
>>
>> "If you set
>>*cnFillPalette*<http://www.ncl.ucar.edu/Document/Graphics/Resources/cn.shtml#cnFillPalette>
>>using
>> a predefined color map, it will have two fewer elements than if you
>>set *
>> wkColorMap*<http://www.ncl.ucar.edu/Document/Graphics/Resources/wk.shtml#wkColorMap>
>>using
>> the same color map. This is because the
>>*wkColorMap*<http://www.ncl.ucar.edu/Document/Graphics/Resources/wk.shtml#wkColorMap>
>>resource
>> contains special elements (0 and 1) for the Background and
>>Foreground colors,
>> whereas the palette-type resources do not."
>>
>>
>>
>>
>> My question is how to reset that color? Is it as simple as giving a
>>named
>> color to a different resource?
>>
>> For future search reference, here is the warning generated when
>>using the
>> resource and a 256 color table (resdiff@cnFillPalette =
>> "BlueYellowRed")
>>
>> warning:ContourPlotSetValues: color index (255) exceeds size of
>>palette,
>> defaulting to foreground color for entry (21)
>>
>>
>>
>> Thanks for the time!
>>
>> Jon
>>
>>
>> _______________________________________________
>> ncl-talk mailing list
>> List instructions, subscriber options, unsubscribe:
>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>>
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20130905/3b0cfd2b/attachment.html
>
> ------------------------------
>
> Message: 7
> Date: Fri, 6 Sep 2013 03:21:00 +0800
>From: " ??? "<557xiaozhu@163.com>
> Subject: Re: check_for_y_lat_coord
> To: "ncl-talk@ucar.edu USERS"<ncl-talk@ucar.edu>
> Message-ID: <44343ad1.4f.140ef9231f8.Coremail.557xiaozhu@163.com>
> Content-Type: text/plain; charset="utf-8"
>
> Adam,
> Thanks for your responding. I have added what you mentioned, but
>the error is still there.
> (0) 19930101
>
> Variable: u
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
> Coordinates:
> NbLongitudes: [98.33333333332349..290.9999999999709]
> NbLatitudes: [-17.79766126545592..60.88112837177402]
> Number Of Attributes: 5
> date : 1993-01-01 00:00:00.000000 UTC
> Date_CNES_JD : 15706
> units : cm/s
> long_name : U
> _FillValue : 1.844674e+19
>
> Variable: v
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
> Coordinates:
> NbLongitudes: [98.33333333332349..290.9999999999709]
> NbLatitudes: [-17.79766126545592..60.88112837177402]
> Number Of Attributes: 5
> _FillValue : 1.844674e+19
> long_name : V
> units : cm/s
> Date_CNES_JD : 15706
> date : 1993-01-01 00:00:00.000000 UTC
>
> Variable: speed
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [579] x [287]
> Coordinates:
> Number Of Attributes: 1
> _FillValue : 1.844674e+19
> (0) check_for_y_lat_coord: Warning: Data either does not contain
>a valid latitude coordinate array or doesn't contain one at all.
> (0) A valid latitude coordinate array should have a 'units'
>attribute equal to one of the following values:
> (0) 'degrees_north' 'degrees-north' 'degree_north' 'degrees
>north' 'degrees_N' 'Degrees_north' 'degree_N' 'degreeN' 'degreesN'
>'deg north'
> (0) check_for_lon_coord: Warning: Data either does not contain a
>valid longitude coordinate array or doesn't contain one at all.
> (0) A valid longitude coordinate array should have a 'units'
>attribute equal to one of the following values:
> (0) 'degrees_east' 'degrees-east' 'degree_east' 'degrees
>east' 'degrees_E' 'Degrees_east' 'degree_E' 'degreeE' 'degreesE' 'deg
>east'
> (0) gsn_csm_map_ce: Warning: you set mpMaxLonF to a value > 180,
>but
> (0) didn't set mpCenterLonF. Setting
>mpCenterLonF to 194.5
>
> The newer code is
>
> do nt=nb,ne
> time=in[:] ->time(nt-1)
> utc_date = cd_calendar(time, -3)
> print(""+utc_date)
>
> ;************************************************
> ; read in zonal [u] and meridional [v] winds
> ;************************************************
> tmp = in[:]->UGRD_10maboveground(nt-1,:,:)
> u = tmp({lat_min:lat_max},{lon_min:lon_max})/100.0
> tmp = in[:]->VGRD_10maboveground(nt-1,:,:)
> v = tmp({lat_min:lat_max},{lon_min:lon_max})/100.0
> speed = sqrt(u^2 + v^2)
> copy_VarCoords(u,speed)
>
> vcres@tiMainString = "Wind 10m above ground"
> vcres@gsnLeftString = utc_date
> vcres@gsnRightString = "m/s"
>
> wks = gsn_open_wks(wks_type ,"wind_"+utc_date) ;
>open a ps file
> gsn_define_colormap(wks,"rainbow") ;"BlAqGrYeOrRe") ;
>choose colormap
> printVarSummary(u)
> printVarSummary(v)
> printVarSummary(speed)
> plot=gsn_csm_vector_scalar_map_ce(wks,u(NbLatitudes|:,NbLongitudes|:),v(NbLatitudes|:,NbLongitudes|:),speed(NbLatitudes|:,NbLongitudes|:),vcres)
> ; create plot
> end do
>
> 2013-09-06
>
>
>
> ???
>
>
>
> ????Adam Phillips <asphilli@ucar.edu>
> ?????2013-09-06 02:56
> ???Re: [ncl-talk] check_for_y_lat_coord
> ????"???"<557xiaozhu@163.com>
> ???"ncl-talk@ucar.edu USERS"<ncl-talk@ucar.edu>
>
> Thanks for sending printVarSummary's of your three arrays, as that
>likely identifies the issue. Unlike your u and v arrays, your speed
>array does not have any metadata/coordinate variables associated with
>it.
>
> Try adding this after you create your speed array:
> copy_VarCoords(u,speed)
>
> Alternatively, you can do this:
> speed = u
> speed = (/ sqrt(u^2 + v^2) /) ; overwrite speed values, but leave
>the metadata
>
> This is all assuming that your NbLongitudes / NbLatitudes have units
>attributes set. See this FAQ here:
> http://www.ncl.ucar.edu/FAQ/#err_msgs_027
>
>Finally, note that your u/v/speed arrays are dimensioned longitude by
>latitude. The gsn_csm_vector_scalar_map_ce plotting function expects
>the order to be latitude by longitude. Thus, you will have to reorder
>your dimensions like this:
> plot=gsn_csm_vector_scalar_map_ce(wks,u(NbLatitudes|:,NbLongitudes|:),v(NbLatitudes|:,NbLongitudes|:),speed(NbLatitudes|:,NbLongitudes|:),vcres)
>
> Hope that helps. If you have any further questions please respond
>only to the ncl-talk email list.
> Adam
>
>
> On 09/05/2013 12:39 PM, ??? wrote:
>
> Hi All,
> I am trying to plot the geostrophic current fields from aviso. And
>get some screen output and error messages as follow,
>
> (0) 19930101
>
> Variable: u
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
> Coordinates:
> NbLongitudes: [98.33333333332349..290.9999999999709]
> NbLatitudes: [-17.79766126545592..60.88112837177402]
> Number Of Attributes: 5
> date : 1993-01-01 00:00:00.000000 UTC
> Date_CNES_JD : 15706
> units : cm/s
> long_name : U
> _FillValue : 1.844674e+19
>
> Variable: v
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
> Coordinates:
> NbLongitudes: [98.33333333332349..290.9999999999709]
> NbLatitudes: [-17.79766126545592..60.88112837177402]
> Number Of Attributes: 5
> _FillValue : 1.844674e+19
> long_name : V
> units : cm/s
> Date_CNES_JD : 15706
> date : 1993-01-01 00:00:00.000000 UTC
>
> Variable: speed
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [579] x [287]
> Coordinates:
> Number Of Attributes: 1
> _FillValue : 1.844674e+19
> (0) check_for_y_lat_coord: Warning: Data either does not contain
>a valid latitude coordinate array or doesn't contain one at all.
> (0) A valid latitude coordinate array should have a 'units'
>attribute equal to one of the following values:
> (0) 'degrees_north' 'degrees-north' 'degree_north' 'degrees
>north' 'degrees_N' 'Degrees_north' 'degree_N' 'degreeN' 'degreesN'
>'deg north'
> (0) check_for_lon_coord: Warning: Data either does not contain a
>valid longitude coordinate array or doesn't contain one at all.
> (0) A valid longitude coordinate array should have a 'units'
>attribute equal to one of the following values:
> (0) 'degrees_east' 'degrees-east' 'degree_east' 'degrees
>east' 'degrees_E' 'Degrees_east' 'degree_E' 'degreeE' 'degreesE' 'deg
>east'
> (0) gsn_csm_map_ce: Warning: you set mpMaxLonF to a value > 180,
>but
> (0) didn't set mpCenterLonF. Setting
>mpCenterLonF to 194.5
>
> My code is as follow,
>
> do nt=nb,ne
> in = addfile(infile(nt-1),"r")
> utc_date = str_get_cols(infile(nt-1),44,51)
> print(""+utc_date)
>
> ;************************************************
> ; read in zonal [u] and meridional [v] winds
> ;************************************************
> tmp = in->Grid_0001
> u = tmp({lon_min:lon_max},{lat_min:lat_max}) ;/100.0
> tmp = in->Grid_0002
> v = tmp({lon_min:lon_max},{lat_min:lat_max}) ;/100.0
> speed = sqrt(u^2 + v^2)
>
> vcres@tiMainString = "Geostrophic Current Field"
> vcres@gsnLeftString = utc_date
> vcres@gsnRightString = "m/s"
>
> wks = gsn_open_wks(wks_type ,"uv_"+utc_date) ;
>open a ps file
> gsn_define_colormap(wks,"rainbow") ;"BlAqGrYeOrRe") ;
>choose colormap
> printVarSummary(u)
> printVarSummary(v)
> printVarSummary(speed)
> plot=gsn_csm_vector_scalar_map_ce(wks,u,v,speed,vcres) ; create
>plot
> end do
>
> Anyone can help me for figuring out the error? Thanks.
>
> 2013-09-06
>
>
>
> ???
>
>
>
> _______________________________________________
> ncl-talk mailing list
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
>
>
> --
> ______________________________________________________________
> Adam Phillips asphilli@ucar.edu
> NCAR/Climate and Global Dynamics Division (303) 497-1726
> P.O. Box 3000
> Boulder, CO 80307-3000 http://www.cgd.ucar.edu/cas/asphilli
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20130906/51313344/attachment.html
>
> ------------------------------
>
> Message: 8
> Date: Thu, 05 Sep 2013 13:31:56 -0600
>From: Adam Phillips <asphilli@ucar.edu>
> Subject: Re: check_for_y_lat_coord
> To: ??? <557xiaozhu@163.com>
> Cc: "ncl-talk@ucar.edu USERS" <ncl-talk@ucar.edu>
> Message-ID: <5228DC2C.3010204@ucar.edu>
> Content-Type: text/plain; charset="utf-8"
>
> If you are still getting that error message then your
>latitude/longitude
> coordinate variables do not have valid units attributes, as is
>stated in
> the error message. Please refer to the FAQ I previously sent. You
>may
> have to do something like this:
>
> u&NbLongitudes@units = "degrees_east"
> u&NbLatitudes@units = "degrees_north"
> v&NbLongitudes@units = "degrees_east"
> v&NbLatitudes@units = "degrees_north"
> speed&NbLongitudes@units = "degrees_east"
> speed&NbLatitudes@units = "degrees_north"
>
> If that doesn't fix the issue let ncl-tal know.
> Adam
>
> On 09/05/2013 01:21 PM, ??? wrote:
>> Adam,
>> Thanks for your responding. I have added what you mentioned, but
>> the error is still there.
>> (0) 19930101
>> Variable: u
>> Type: float
>> Total Size: 664692 bytes
>> 166173 values
>> Number of Dimensions: 2
>> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
>> Coordinates:
>> NbLongitudes: [98.33333333332349..290.9999999999709]
>> NbLatitudes: [-17.79766126545592..60.88112837177402]
>> Number Of Attributes: 5
>> date : 1993-01-01 00:00:00.000000 UTC
>> Date_CNES_JD : 15706
>> units : cm/s
>> long_name : U
>> _FillValue : 1.844674e+19
>> Variable: v
>> Type: float
>> Total Size: 664692 bytes
>> 166173 values
>> Number of Dimensions: 2
>> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
>> Coordinates:
>> NbLongitudes: [98.33333333332349..290.9999999999709]
>> NbLatitudes: [-17.79766126545592..60.88112837177402]
>> Number Of Attributes: 5
>> _FillValue : 1.844674e+19
>> long_name : V
>> units : cm/s
>> Date_CNES_JD : 15706
>> date : 1993-01-01 00:00:00.000000 UTC
>> Variable: speed
>> Type: float
>> Total Size: 664692 bytes
>> 166173 values
>> Number of Dimensions: 2
>> Dimensions and sizes: [579] x [287]
>> Coordinates:
>> Number Of Attributes: 1
>> _FillValue : 1.844674e+19
>> (0) check_for_y_lat_coord: Warning: Data either does not contain
>>a
>> valid latitude coordinate array or doesn't contain one at all.
>> (0) A valid latitude coordinate array should have a 'units'
>> attribute equal to one of the following values:
>> (0) 'degrees_north' 'degrees-north' 'degree_north' 'degrees
>> north' 'degrees_N' 'Degrees_north' 'degree_N' 'degreeN' 'degreesN'
>> 'deg north'
>> (0) check_for_lon_coord: Warning: Data either does not contain a
>> valid longitude coordinate array or doesn't contain one at all.
>> (0) A valid longitude coordinate array should have a 'units'
>> attribute equal to one of the following values:
>> (0) 'degrees_east' 'degrees-east' 'degree_east' 'degrees
>>east'
>> 'degrees_E' 'Degrees_east' 'degree_E' 'degreeE' 'degreesE' 'deg
>>east'
>> (0) gsn_csm_map_ce: Warning: you set mpMaxLonF to a value > 180,
>>but
>> (0) didn't set mpCenterLonF. Setting
>>mpCenterLonF
>> to 194.5
>> The newer code is
>> do nt=nb,ne
>> time=in[:] ->time(nt-1)
>> utc_date = cd_calendar(time, -3)
>> print(""+utc_date)
>>
>> ;************************************************
>> ; read in zonal [u] and meridional [v] winds
>> ;************************************************
>> tmp = in[:]->UGRD_10maboveground(nt-1,:,:)
>> u = tmp({lat_min:lat_max},{lon_min:lon_max})/100.0
>> tmp = in[:]->VGRD_10maboveground(nt-1,:,:)
>> v = tmp({lat_min:lat_max},{lon_min:lon_max})/100.0
>> speed = sqrt(u^2 + v^2)
>> copy_VarCoords(u,speed)
>>
>> vcres@tiMainString <mailto:vcres@tiMainString> = "Wind 10m
>> above ground"
>> vcres@gsnLeftString <mailto:vcres@gsnLeftString> = utc_date
>> vcres@gsnRightString <mailto:vcres@gsnRightString> = "m/s"
>> wks = gsn_open_wks(wks_type ,"wind_"+utc_date) ;
>> open a ps file
>> gsn_define_colormap(wks,"rainbow") ;"BlAqGrYeOrRe") ;
>> choose colormap
>> printVarSummary(u)
>> printVarSummary(v)
>> printVarSummary(speed)
>> plot=gsn_csm_vector_scalar_map_ce(wks,u(NbLatitudes|:,NbLongitudes|:),v(NbLatitudes|:,NbLongitudes|:),speed(NbLatitudes|:,NbLongitudes|:),vcres)
>> ; create plot
>> end do
>> 2013-09-06
>> ------------------------------------------------------------------------
>> ???
>> ------------------------------------------------------------------------
>> *????*Adam Phillips <asphilli@ucar.edu>
>> *?????*2013-09-06 02:56
>> *???*Re: [ncl-talk] check_for_y_lat_coord
>> *????*"?? ?"<557xiaozhu@163.com>
>> *???*"ncl-talk@ucar.edu USERS"<ncl-talk@ucar.edu>
>> Thanks for sending printVarSummary's of your three arrays, as that
>> likely identifies the issue. Unlike your u and v arrays, your speed
>> array does not have any metadata/coordinate variables associated
>>with it.
>>
>> Try adding this after you create your speed array:
>> copy_VarCoords(u,speed)
>>
>> Alternatively, you can do this:
>> speed = u
>> speed = (/ sqrt(u^2 + v^2) /) ; overwrite speed values, but leave
>> the metadata
>>
>> This is all assuming that your NbLongitudes / NbLatitudes have units
>> attributes set. See this FAQ here:
>> http://www.ncl.ucar.edu/FAQ/#err_msgs_027
>>
>> Finally, note that your u/v/speed arrays are dimensioned longitude
>>by
>> latitude. The gsn_csm_vector_scalar_map_ce plotting function expects
>> the order to be latitude by longitude. Thus, you will have to
>>reorder
>> your dimensions like this:
>> plot=gsn_csm_vector_scalar_map_ce(wks,u(NbLatitudes|:,NbLongitudes|:),v(NbLatitudes|:,NbLongitudes|:),speed(NbLatitudes|:,NbLongitudes|:),vcres)
>>
>>
>> Hope that helps. If you have any further questions please respond
>>only
>> to the ncl-talk email list.
>> Adam
>>
>> On 09/05/2013 12:39 PM, ??? wrote:
>>> Hi All,
>>> I am trying to plot the geostrophic current fields from aviso.
>>>And
>>> get some screen output and error messages as follow,
>>> (0) 19930101
>>> Variable: u
>>> Type: float
>>> Total Size: 664692 bytes
>>> 166173 values
>>> Number of Dimensions: 2
>>> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
>>> Coordinates:
>>> NbLongitudes: [98.33333333332349..290.9999999999709]
>>> NbLatitudes: [-17.79766126545592..60.88112837177402]
>>> Number Of Attributes: 5
>>> date : 1993-01-01 00:00:00.000000 UTC
>>> Date_CNES_JD : 15706
>>> units : cm/s
>>> long_name : U
>>> _FillValue : 1.844674e+19
>>> Variable: v
>>> Type: float
>>> Total Size: 664692 bytes
>>> 166173 values
>>> Number of Dimensions: 2
>>> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
>>> Coordinates:
>>> NbLongitudes: [98.33333333332349..290.9999999999709]
>>> NbLatitudes: [-17.79766126545592..60.88112837177402]
>>> Number Of Attributes: 5
>>> _FillValue : 1.844674e+19
>>> long_name : V
>>> units : cm/s
>>> Date_CNES_JD : 15706
>>> date : 1993-01-01 00:00:00.000000 UTC
>>> Variable: speed
>>> Type: float
>>> Total Size: 664692 bytes
>>> 166173 values
>>> Number of Dimensions: 2
>>> Dimensions and sizes: [579] x [287]
>>> Coordinates:
>>> Number Of Attributes: 1
>>> _FillValue : 1.844674e+19
>>> (0) check_for_y_lat_coord: Warning: Data either does not contain
>>> a valid latitude coordinate array or doesn't contain one at all.
>>> (0) A valid latitude coordinate array should have a 'units'
>>> attribute equal to one of the following values:
>>> (0) 'degrees_north' 'degrees-north' 'degree_north' 'degrees
>>> north' 'degrees_N' 'Degrees_north' 'degree_N' 'degreeN' 'degreesN'
>>> 'deg north'
>>> (0) check_for_lon_coord: Warning: Data either does not contain a
>>> valid longitude coordinate array or doesn't contain one at all.
>>> (0) A valid longitude coordinate array should have a 'units'
>>> attribute equal to one of the following values:
>>> (0) 'degrees_east' 'degrees-east' 'degree_east' 'degrees
>>> east' 'degrees_E' 'Degrees_east' 'degree_E' 'degreeE' 'degreesE'
>>>'deg
>>> east'
>>> (0) gsn_csm_map_ce: Warning: you set mpMaxLonF to a value > 180,
>>>but
>>> (0) didn't set mpCenterLonF. Setting
>>>mpCenterLonF
>>> to 194.5
>>> My code is as follow,
>>> do nt=nb,ne
>>> in = addfile(infile(nt-1),"r")
>>> utc_date = str_get_cols(infile(nt-1),44,51)
>>> print(""+utc_date)
>>>
>>> ;************************************************
>>> ; read in zonal [u] and meridional [v] winds
>>> ;************************************************
>>> tmp = in->Grid_0001
>>> u = tmp({lon_min:lon_max},{lat_min:lat_max}) ;/100.0
>>> tmp = in->Grid_0002
>>> v = tmp({lon_min:lon_max},{lat_min:lat_max}) ;/100.0
>>> speed = sqrt(u^2 + v^2)
>>>
>>> vcres@tiMainString <mailto:vcres@tiMainString> =
>>> "Geostrophic Current Field"
>>> vcres@gsnLeftString <mailto:vcres@gsnLeftString> = utc_date
>>> vcres@gsnRightString <mailto:vcres@gsnRightString> = "m/s"
>>> wks = gsn_open_wks(wks_type ,"uv_"+utc_date) ;
>>> open a ps file
>>> gsn_define_colormap(wks,"rainbow") ;"BlAqGrYeOrRe") ;
>>> choose colormap
>>> printVarSummary(u)
>>> printVarSummary(v)
>>> printVarSummary(speed)
>>> plot=gsn_csm_vector_scalar_map_ce(wks,u,v,speed,vcres) ; create plot
>>> end do
>>> Anyone can help me for figuring out the error? Thanks.
>>> 2013-09-06
>>> ------------------------------------------------------------------------
>>> ???
>>>
>>>
>>> _______________________________________________
>>> ncl-talk mailing list
>>> List instructions, subscriber options, unsubscribe:
>>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>>
>> --
>> ______________________________________________________________
>> Adam Phillipsasphilli@ucar.edu
>> NCAR/Climate and Global Dynamics Division (303) 497-1726
>> P.O. Box 3000
>> Boulder, CO 80307-3000http://www.cgd.ucar.edu/cas/asphilli
>>
>>
>> _______________________________________________
>> ncl-talk mailing list
>> List instructions, subscriber options, unsubscribe:
>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
> --
> ______________________________________________________________
> Adam Phillips asphilli@ucar.edu
> NCAR/Climate and Global Dynamics Division (303) 497-1726
> P.O. Box 3000
> Boulder, CO 80307-3000 http://www.cgd.ucar.edu/cas/asphilli
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20130905/d9ef8309/attachment.html
>
> ------------------------------
>
> Message: 9
> Date: Fri, 6 Sep 2013 03:47:22 +0800
>From: " ??? "<557xiaozhu@163.com>
> Subject: Re: check_for_y_lat_coord
> To: "ncl-talk@ucar.edu USERS"<ncl-talk@ucar.edu>
> Message-ID: <5891b770.7d.140efaa790c.Coremail.557xiaozhu@163.com>
> Content-Type: text/plain; charset="utf-8"
>
> Thanks. I have figured out the problem. Now I still have two other
>questions :
> (1) I have setted
> vcres@mpMinLonF = 98
> vcres@mpMaxLonF = 291
>
> Then I have a warning message as
> (0) gsn_csm_map_ce: Warning: you set mpMaxLonF to a value > 180,
>but
> (0) didn't set mpCenterLonF. Setting
>mpCenterLonF to 194.5
>
> How and when should I set mpCenterLonF? What can decide the value of
>mpCenterLonF ? Is it equal to the average of mpMinLonF and mpMaxLonF?
>
> (2) From the codes
> u = in->Grid_0001({lon_min:lon_max},{lat_min:lat_max})/100.0
> printVarSummary(u)
> I got the output like this,
> Variable: u
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [579] x [287]
> Coordinates:
> Number Of Attributes: 1
> _FillValue : 1.844674e+19
> But if I comment out the "/100.0", make the code like this
> u = in->Grid_0001({lon_min:lon_max},{lat_min:lat_max}) ; /100.0
> printVarSummary(u)
> I can get the output like this
> Variable: u
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
> Coordinates:
> NbLongitudes: [98.33333333332349..290.9999999999709]
> NbLatitudes: [-17.79766126545592..60.88112837177402]
> Number Of Attributes: 5
> date : 1993-01-02 00:00:00.000000 UTC
> Date_CNES_JD : 15707
> units : cm/s
> long_name : U
> _FillValue : 1.844674e+19
> So if I want to keep /100.0 to transfer the units from centimeter to
>meter, how should I do to keep the u's attributes?
>
> Thanks.
>
> 2013-09-06
>
>
>
> ???
>
>
>
> ????Adam Phillips <asphilli@ucar.edu>
> ?????2013-09-06 03:31
> ???Re: [ncl-talk] check_for_y_lat_coord
> ????"???"<557xiaozhu@163.com>
> ???"ncl-talk@ucar.edu USERS"<ncl-talk@ucar.edu>
>
> If you are still getting that error message then your
>latitude/longitude coordinate variables do not have valid units
>attributes, as is stated in the error message. Please refer to the
>FAQ I previously sent. You may have to do something like this:
>
> u&NbLongitudes@units = "degrees_east"
> u&NbLatitudes@units = "degrees_north"
> v&NbLongitudes@units = "degrees_east"
> v&NbLatitudes@units = "degrees_north"
> speed&NbLongitudes@units = "degrees_east"
> speed&NbLatitudes@units = "degrees_north"
>
> If that doesn't fix the issue let ncl-tal know.
> Adam
>
>
> On 09/05/2013 01:21 PM, ??? wrote:
>
> Adam,
> Thanks for your responding. I have added what you mentioned, but
>the error is still there.
> (0) 19930101
>
> Variable: u
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
> Coordinates:
> NbLongitudes: [98.33333333332349..290.9999999999709]
> NbLatitudes: [-17.79766126545592..60.88112837177402]
> Number Of Attributes: 5
> date : 1993-01-01 00:00:00.000000 UTC
> Date_CNES_JD : 15706
> units : cm/s
> long_name : U
> _FillValue : 1.844674e+19
>
> Variable: v
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
> Coordinates:
> NbLongitudes: [98.33333333332349..290.9999999999709]
> NbLatitudes: [-17.79766126545592..60.88112837177402]
> Number Of Attributes: 5
> _FillValue : 1.844674e+19
> long_name : V
> units : cm/s
> Date_CNES_JD : 15706
> date : 1993-01-01 00:00:00.000000 UTC
>
> Variable: speed
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [579] x [287]
> Coordinates:
> Number Of Attributes: 1
> _FillValue : 1.844674e+19
> (0) check_for_y_lat_coord: Warning: Data either does not contain
>a valid latitude coordinate array or doesn't contain one at all.
> (0) A valid latitude coordinate array should have a 'units'
>attribute equal to one of the following values:
> (0) 'degrees_north' 'degrees-north' 'degree_north' 'degrees
>north' 'degrees_N' 'Degrees_north' 'degree_N' 'degreeN' 'degreesN'
>'deg north'
> (0) check_for_lon_coord: Warning: Data either does not contain a
>valid longitude coordinate array or doesn't contain one at all.
> (0) A valid longitude coordinate array should have a 'units'
>attribute equal to one of the following values:
> (0) 'degrees_east' 'degrees-east' 'degree_east' 'degrees
>east' 'degrees_E' 'Degrees_east' 'degree_E' 'degreeE' 'degreesE' 'deg
>east'
> (0) gsn_csm_map_ce: Warning: you set mpMaxLonF to a value > 180,
>but
> (0) didn't set mpCenterLonF. Setting
>mpCenterLonF to 194.5
>
> The newer code is
>
> do nt=nb,ne
> time=in[:] ->time(nt-1)
> utc_date = cd_calendar(time, -3)
> print(""+utc_date)
>
> ;************************************************
> ; read in zonal [u] and meridional [v] winds
> ;************************************************
> tmp = in[:]->UGRD_10maboveground(nt-1,:,:)
> u = tmp({lat_min:lat_max},{lon_min:lon_max})/100.0
> tmp = in[:]->VGRD_10maboveground(nt-1,:,:)
> v = tmp({lat_min:lat_max},{lon_min:lon_max})/100.0
> speed = sqrt(u^2 + v^2)
> copy_VarCoords(u,speed)
>
> vcres@tiMainString = "Wind 10m above ground"
> vcres@gsnLeftString = utc_date
> vcres@gsnRightString = "m/s"
>
> wks = gsn_open_wks(wks_type ,"wind_"+utc_date) ;
>open a ps file
> gsn_define_colormap(wks,"rainbow") ;"BlAqGrYeOrRe") ;
>choose colormap
> printVarSummary(u)
> printVarSummary(v)
> printVarSummary(speed)
> plot=gsn_csm_vector_scalar_map_ce(wks,u(NbLatitudes|:,NbLongitudes|:),v(NbLatitudes|:,NbLongitudes|:),speed(NbLatitudes|:,NbLongitudes|:),vcres)
> ; create plot
> end do
>
> 2013-09-06
>
>
>
> ???
>
>
>
> ????Adam Phillips <asphilli@ucar.edu>
> ?????2013-09-06 02:56
> ???Re: [ncl-talk] check_for_y_lat_coord
> ????"?? ?"<557xiaozhu@163.com>
> ???"ncl-talk@ucar.edu USERS"<ncl-talk@ucar.edu>
>
> Thanks for sending printVarSummary's of your three arrays, as that
>likely identifies the issue. Unlike your u and v arrays, your speed
>array does not have any metadata/coordinate variables associated with
>it.
>
> Try adding this after you create your speed array:
> copy_VarCoords(u,speed)
>
> Alternatively, you can do this:
> speed = u
> speed = (/ sqrt(u^2 + v^2) /) ; overwrite speed values, but leave
>the metadata
>
> This is all assuming that your NbLongitudes / NbLatitudes have units
>attributes set. See this FAQ here:
> http://www.ncl.ucar.edu/FAQ/#err_msgs_027
>
>Finally, note that your u/v/speed arrays are dimensioned longitude by
>latitude. The gsn_csm_vector_scalar_map_ce plotting function expects
>the order to be latitude by longitude. Thus, you will have to reorder
>your dimensions like this:
> plot=gsn_csm_vector_scalar_map_ce(wks,u(NbLatitudes|:,NbLongitudes|:),v(NbLatitudes|:,NbLongitudes|:),speed(NbLatitudes|:,NbLongitudes|:),vcres)
>
> Hope that helps. If you have any further questions please respond
>only to the ncl-talk email list.
> Adam
>
>
> On 09/05/2013 12:39 PM, ??? wrote:
>
> Hi All,
> I am trying to plot the geostrophic current fields from aviso. And
>get some screen output and error messages as follow,
>
> (0) 19930101
>
> Variable: u
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
> Coordinates:
> NbLongitudes: [98.33333333332349..290.9999999999709]
> NbLatitudes: [-17.79766126545592..60.88112837177402]
> Number Of Attributes: 5
> date : 1993-01-01 00:00:00.000000 UTC
> Date_CNES_JD : 15706
> units : cm/s
> long_name : U
> _FillValue : 1.844674e+19
>
> Variable: v
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
> Coordinates:
> NbLongitudes: [98.33333333332349..290.9999999999709]
> NbLatitudes: [-17.79766126545592..60.88112837177402]
> Number Of Attributes: 5
> _FillValue : 1.844674e+19
> long_name : V
> units : cm/s
> Date_CNES_JD : 15706
> date : 1993-01-01 00:00:00.000000 UTC
>
> Variable: speed
> Type: float
> Total Size: 664692 bytes
> 166173 values
> Number of Dimensions: 2
> Dimensions and sizes: [579] x [287]
> Coordinates:
> Number Of Attributes: 1
> _FillValue : 1.844674e+19
> (0) check_for_y_lat_coord: Warning: Data either does not contain
>a valid latitude coordinate array or doesn't contain one at all.
> (0) A valid latitude coordinate array should have a 'units'
>attribute equal to one of the following values:
> (0) 'degrees_north' 'degrees-north' 'degree_north' 'degrees
>north' 'degrees_N' 'Degrees_north' 'degree_N' 'degreeN' 'degreesN'
>'deg north'
> (0) check_for_lon_coord: Warning: Data either does not contain a
>valid longitude coordinate array or doesn't contain one at all.
> (0) A valid longitude coordinate array should have a 'units'
>attribute equal to one of the following values:
> (0) 'degrees_east' 'degrees-east' 'degree_east' 'degrees
>east' 'degrees_E' 'Degrees_east' 'degree_E' 'degreeE' 'degreesE' 'deg
>east'
> (0) gsn_csm_map_ce: Warning: you set mpMaxLonF to a value > 180,
>but
> (0) didn't set mpCenterLonF. Setting
>mpCenterLonF to 194.5
>
> My code is as follow,
>
> do nt=nb,ne
> in = addfile(infile(nt-1),"r")
> utc_date = str_get_cols(infile(nt-1),44,51)
> print(""+utc_date)
>
> ;************************************************
> ; read in zonal [u] and meridional [v] winds
> ;************************************************
> tmp = in->Grid_0001
> u = tmp({lon_min:lon_max},{lat_min:lat_max}) ;/100.0
> tmp = in->Grid_0002
> v = tmp({lon_min:lon_max},{lat_min:lat_max}) ;/100.0
> speed = sqrt(u^2 + v^2)
>
> vcres@tiMainString = "Geostrophic Current Field"
> vcres@gsnLeftString = utc_date
> vcres@gsnRightString = "m/s"
>
> wks = gsn_open_wks(wks_type ,"uv_"+utc_date) ;
>open a ps file
> gsn_define_colormap(wks,"rainbow") ;"BlAqGrYeOrRe") ;
>choose colormap
> printVarSummary(u)
> printVarSummary(v)
> printVarSummary(speed)
> plot=gsn_csm_vector_scalar_map_ce(wks,u,v,speed,vcres) ; create
>plot
> end do
>
> Anyone can help me for figuring out the error? Thanks.
>
> 2013-09-06
>
>
>
> ???
>
>
>
> _______________________________________________
> ncl-talk mailing list
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
>
>
> --
> ______________________________________________________________
> Adam Phillips asphilli@ucar.edu
> NCAR/Climate and Global Dynamics Division (303) 497-1726
> P.O. Box 3000
> Boulder, CO 80307-3000 http://www.cgd.ucar.edu/cas/asphilli
>
>
>
>
> _______________________________________________
> ncl-talk mailing list
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
>
>
> --
> ______________________________________________________________
> Adam Phillips asphilli@ucar.edu
> NCAR/Climate and Global Dynamics Division (303) 497-1726
> P.O. Box 3000
> Boulder, CO 80307-3000 http://www.cgd.ucar.edu/cas/asphilli
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20130906/2f36b6fd/attachment.html
>
> ------------------------------
>
> Message: 10
> Date: Thu, 05 Sep 2013 14:15:38 -0600
>From: Adam Phillips <asphilli@ucar.edu>
> Subject: Re: check_for_y_lat_coord
> To: ??? <557xiaozhu@163.com>
> Cc: "ncl-talk@ucar.edu USERS" <ncl-talk@ucar.edu>
> Message-ID: <5228E66A.5080809@ucar.edu>
> Content-Type: text/plain; charset="utf-8"
>
> 1) Yes, typically mpCenterLonF is the average of the mpMinLonF and
> mpMaxLonF. I typically set this in my code:
> res@mpCenterLonF = (res@mpMinLonF+res@mpMaxLonF)/2.
>
> In my experience mpCenterLonF typically needs to be set when
>plotting a
> region (=not going from 0:360E), and it almost always needs to be
>set
> when doing a regional plot that crosses the date line at 180E.
>
> 2) This line:
> u = in->Grid_0001({lon_min:lon_max},{lat_min:lat_max}) ; /100.0
> results in u having no metadata transferred from Grid_0001 because
>you
> are performing a mathematical operation on the data, and u was not
> previously defined. NCL isn't sure what metadata should be
>transferred
> from Grid_0001->u, so it does the safe thing and doesn't transfer
>anything.
>
> Try this:
> u = in->Grid_0001({lon_min:lon_max},{lat_min:lat_max})
> u = u/100.0
> or this should do the same thing:
> u = in->Grid_0001({lon_min:lon_max},{lat_min:lat_max})
> u = (/ u/100.0 /) ; (/ /) mean transfer data only, do not
>attempt
> to transfer coordinate variables from right side of = sign to left
>side.
>
> Adam
>
> On 09/05/2013 01:47 PM, ??? wrote:
>> Thanks. I have figured out the problem. Now I still have two other
>> questions :
>> (1) I have setted
>> vcres@mpMinLonF <mailto:vcres@mpMinLonF> = 98
>> vcres@mpMaxLonF <mailto:vcres@mpMaxLonF> = 291
>> Then I have a warning message as
>> (0) gsn_csm_map_ce: Warning: you set mpMaxLonF to a value > 180,
>>but
>> (0) didn't set mpCenterLonF. Setting
>>mpCenterLonF
>> to 194.5
>> How and when should I set mpCenterLonF? What can decide the value of
>> mpCenterLonF ? Is it equal to the average of mpMinLonF and
>>mpMaxLonF?
>> (2) From the codes
>> u = in->Grid_0001({lon_min:lon_max},{lat_min:lat_max})/100.0
>> printVarSummary(u)
>> I got the output like this,
>> Variable: u
>> Type: float
>> Total Size: 664692 bytes
>> 166173 values
>> Number of Dimensions: 2
>> Dimensions and sizes: [579] x [287]
>> Coordinates:
>> Number Of Attributes: 1
>> _FillValue : 1.844674e+19
>> But if I comment out the "/100.0", make the code like this
>> u = in->Grid_0001({lon_min:lon_max},{lat_min:lat_max}) ; /100.0
>> printVarSummary(u)
>> I can get the output like this
>> Variable: u
>> Type: float
>> Total Size: 664692 bytes
>> 166173 values
>> Number of Dimensions: 2
>> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
>> Coordinates:
>> NbLongitudes: [98.33333333332349..290.9999999999709]
>> NbLatitudes: [-17.79766126545592..60.88112837177402]
>> Number Of Attributes: 5
>> date : 1993-01-02 00:00:00.000000 UTC
>> Date_CNES_JD : 15707
>> units : cm/s
>> long_name : U
>> _FillValue : 1.844674e+19
>> So if I want to keep /100.0 to transfer the units from centimeter to
>> meter, how should I do to keep the u's attributes?
>> Thanks.
>> 2013-09-06
>> ------------------------------------------------------------------------
>> ???
>> ------------------------------------------------------------------------
>> *????*Adam Phillips <asphilli@ucar.edu>
>> *?????*2013-09-06 03:31
>> *???*Re: [ncl-talk] check_for_y_lat_coord
>> *????*"?? ?"<557xiaozhu@163.com>
>> *???*"ncl-talk@ucar.edu USERS"<ncl-talk@ucar.edu>
>> If you are still getting that error message then your
>> latitude/longitude coordinate variables do not have valid units
>> attributes, as is stated in the error message. Please refer to the
>> FAQ I previously sent. You may have to do something like this:
>>
>> u&NbLongitudes@units = "degrees_east"
>> u&NbLatitudes@units = "degrees_north"
>> v&NbLongitudes@units = "degrees_east"
>> v&NbLatitudes@units = "degrees_north"
>> speed&NbLongitudes@units = "degrees_east"
>> speed&NbLatitudes@units = "degrees_north"
>>
>> If that doesn't fix the issue let ncl-tal know.
>> Adam
>>
>> On 09/05/2013 01:21 PM, ??? wrote:
>>> Adam,
>>> Thanks for your responding. I have added what you mentioned, but
>>> the error is still there.
>>> (0) 19930101
>>> Variable: u
>>> Type: float
>>> Total Size: 664692 bytes
>>> 166173 values
>>> Number of Dimensions: 2
>>> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
>>> Coordinates:
>>> NbLongitudes: [98.33333333332349..290.9999999999709]
>>> NbLatitudes: [-17.79766126545592..60.88112837177402]
>>> Number Of Attributes: 5
>>> date : 1993-01-01 00:00:00.000000 UTC
>>> Date_CNES_JD : 15706
>>> units : cm/s
>>> long_name : U
>>> _FillValue : 1.844674e+19
>>> Variable: v
>>> Type: float
>>> Total Size: 664692 bytes
>>> 166173 values
>>> Number of Dimensions: 2
>>> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
>>> Coordinates:
>>> NbLongitudes: [98.33333333332349..290.9999999999709]
>>> NbLatitudes: [-17.79766126545592..60.88112837177402]
>>> Number Of Attributes: 5
>>> _FillValue : 1.844674e+19
>>> long_name : V
>>> units : cm/s
>>> Date_CNES_JD : 15706
>>> date : 1993-01-01 00:00:00.000000 UTC
>>> Variable: speed
>>> Type: float
>>> Total Size: 664692 bytes
>>> 166173 values
>>> Number of Dimensions: 2
>>> Dimensions and sizes: [579] x [287]
>>> Coordinates:
>>> Number Of Attributes: 1
>>> _FillValue : 1.844674e+19
>>> (0) check_for_y_lat_coord: Warning: Data either does not contain
>>> a valid latitude coordinate array or doesn't contain one at all.
>>> (0) A valid latitude coordinate array should have a 'units'
>>> attribute equal to one of the following values:
>>> (0) 'degrees_north' 'degrees-north' 'degree_north' 'degrees
>>> north' 'degrees_N' 'Degrees_north' 'degree_N' 'degreeN' 'degreesN'
>>> 'deg north'
>>> (0) check_for_lon_coord: Warning: Data either does not contain a
>>> valid longitude coordinate array or doesn't contain one at all.
>>> (0) A valid longitude coordinate array should have a 'units'
>>> attribute equal to one of the following values:
>>> (0) 'degrees_east' 'degrees-east' 'degree_east' 'degrees
>>> east' 'degrees_E' 'Degrees_east' 'degree_E' 'degreeE' 'degreesE'
>>>'deg
>>> east'
>>> (0) gsn_csm_map_ce: Warning: you set mpMaxLonF to a value > 180,
>>>but
>>> (0) didn't set mpCenterLonF. Setting
>>>mpCenterLonF
>>> to 194.5
>>> The newer code is
>>> do nt=nb,ne
>>> time=in[:] ->time(nt-1)
>>> utc_date = cd_calendar(time, -3)
>>> print(""+utc_date)
>>>
>>> ;************************************************
>>> ; read in zonal [u] and meridional [v] winds
>>> ;************************************************
>>> tmp = in[:]->UGRD_10maboveground(nt-1,:,:)
>>> u = tmp({lat_min:lat_max},{lon_min:lon_max})/100.0
>>> tmp = in[:]->VGRD_10maboveground(nt-1,:,:)
>>> v = tmp({lat_min:lat_max},{lon_min:lon_max})/100.0
>>> speed = sqrt(u^2 + v^2)
>>> copy_VarCoords(u,speed)
>>>
>>> vcres@tiMainString <mailto:vcres@tiMainString> = "Wind 10m
>>> above ground"
>>> vcres@gsnLeftString <mailto:vcres@gsnLeftString> = utc_date
>>> vcres@gsnRightString <mailto:vcres@gsnRightString> = "m/s"
>>> wks = gsn_open_wks(wks_type ,"wind_"+utc_date) ;
>>> open a ps file
>>> gsn_define_colormap(wks,"rainbow") ;"BlAqGrYeOrRe") ;
>>> choose colormap
>>> printVarSummary(u)
>>> printVarSummary(v)
>>> printVarSummary(speed)
>>> plot=gsn_csm_vector_scalar_map_ce(wks,u(NbLatitudes|:,NbLongitudes|:),v(NbLatitudes|:,NbLongitudes|:),speed(NbLatitudes|:,NbLongitudes|:),vcres)
>>> ; create plot
>>> end do
>>> 2013-09-06
>>> ------------------------------------------------------------------------
>>> ???
>>> ------------------------------------------------------------------------
>>> *????*Adam Phillips <asphilli@ucar.edu>
>>> *?????*2013-09-06 02:56
>>> *???*Re: [ncl-talk] check_for_y_lat_coord
>>> *????*"?? ?"<557xiaozhu@163.com>
>>> *???*"ncl-talk@ucar.edu USERS"<ncl-talk@ucar.edu>
>>> Thanks for sending printVarSummary's of your three arrays, as that
>>> likely identifies the issue. Unlike your u and v arrays, your speed
>>> array does not have any metadata/coordinate variables associated
>>>with
>>> it.
>>>
>>> Try adding this after you create your speed array:
>>> copy_VarCoords(u,speed)
>>>
>>> Alternatively, you can do this:
>>> speed = u
>>> speed = (/ sqrt(u^2 + v^2) /) ; overwrite speed values, but leave
>>> the metadata
>>>
>>> This is all assuming that your NbLongitudes / NbLatitudes have units
>>> attributes set. See this FAQ here:
>>> http://www.ncl.ucar.edu/FAQ/#err_msgs_027
>>>
>>> Finally, note that your u/v/speed arrays are dimensioned longitude
>>>by
>>> latitude. The gsn_csm_vector_scalar_map_ce plotting function expects
>>> the order to be latitude by longitude. Thus, you will have to
>>>reorder
>>> your dimensions like this:
>>> plot=gsn_csm_vector_scalar_map_ce(wks,u(NbLatitudes|:,NbLongitudes|:),v(NbLatitudes|:,NbLongitudes|:),speed(NbLatitudes|:,NbLongitudes|:),vcres)
>>>
>>>
>>> Hope that helps. If you have any further questions please respond
>>> only to the ncl-talk email list.
>>> Adam
>>>
>>> On 09/05/2013 12:39 PM, ??? wrote:
>>>> Hi All,
>>>> I am trying to plot the geostrophic current fields from aviso.
>>>> And get some screen output and error messages as follow,
>>>> (0) 19930101
>>>> Variable: u
>>>> Type: float
>>>> Total Size: 664692 bytes
>>>> 166173 values
>>>> Number of Dimensions: 2
>>>> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
>>>> Coordinates:
>>>> NbLongitudes: [98.33333333332349..290.9999999999709]
>>>> NbLatitudes: [-17.79766126545592..60.88112837177402]
>>>> Number Of Attributes: 5
>>>> date : 1993-01-01 00:00:00.000000 UTC
>>>> Date_CNES_JD : 15706
>>>> units : cm/s
>>>> long_name : U
>>>> _FillValue : 1.844674e+19
>>>> Variable: v
>>>> Type: float
>>>> Total Size: 664692 bytes
>>>> 166173 values
>>>> Number of Dimensions: 2
>>>> Dimensions and sizes: [NbLongitudes | 579] x [NbLatitudes | 287]
>>>> Coordinates:
>>>> NbLongitudes: [98.33333333332349..290.9999999999709]
>>>> NbLatitudes: [-17.79766126545592..60.88112837177402]
>>>> Number Of Attributes: 5
>>>> _FillValue : 1.844674e+19
>>>> long_name : V
>>>> units : cm/s
>>>> Date_CNES_JD : 15706
>>>> date : 1993-01-01 00:00:00.000000 UTC
>>>> Variable: speed
>>>> Type: float
>>>> Total Size: 664692 bytes
>>>> 166173 values
>>>> Number of Dimensions: 2
>>>> Dimensions and sizes: [579] x [287]
>>>> Coordinates:
>>>> Number Of Attributes: 1
>>>> _FillValue : 1.844674e+19
>>>> (0) check_for_y_lat_coord: Warning: Data either does not contain
>>>> a valid latitude coordinate array or doesn't contain one at all.
>>>> (0) A valid latitude coordinate array should have a 'units'
>>>> attribute equal to one of the following values:
>>>> (0) 'degrees_north' 'degrees-north' 'degree_north' 'degrees
>>>> north' 'degrees_N' 'Degrees_north' 'degree_N' 'degreeN' 'degreesN'
>>>> 'deg north'
>>>> (0) check_for_lon_coord: Warning: Data either does not contain a
>>>> valid longitude coordinate array or doesn't contain one at all.
>>>> (0) A valid longitude coordinate array should have a 'units'
>>>> attribute equal to one of the following values:
>>>> (0) 'degrees_east' 'degrees-east' 'degree_east' 'degrees
>>>> east' 'degrees_E' 'Degrees_east' 'degree_E' 'degreeE' 'degreesE'
>>>> 'deg east'
>>>> (0) gsn_csm_map_ce: Warning: you set mpMaxLonF to a value > 180,
>>>>but
>>>> (0) didn't set mpCenterLonF. Setting
>>>> mpCenterLonF to 194.5
>>>> My code is as follow,
>>>> do nt=nb,ne
>>>> in = addfile(infile(nt-1),"r")
>>>> utc_date = str_get_cols(infile(nt-1),44,51)
>>>> print(""+utc_date)
>>>>
>>>> ;************************************************
>>>> ; read in zonal [u] and meridional [v] winds
>>>> ;************************************************
>>>> tmp = in->Grid_0001
>>>> u = tmp({lon_min:lon_max},{lat_min:lat_max}) ;/100.0
>>>> tmp = in->Grid_0002
>>>> v = tmp({lon_min:lon_max},{lat_min:lat_max}) ;/100.0
>>>> speed = sqrt(u^2 + v^2)
>>>>
>>>> vcres@tiMainString <mailto:vcres@tiMainString>= "Geostrophic Current
>>>> Field"
>>>> vcres@gsnLeftString <mailto:vcres@gsnLeftString>= utc_date
>>>> vcres@gsnRightString <mailto:vcres@gsnRightString> = "m/s"
>>>> wks = gsn_open_wks(wks_type ,"uv_"+utc_date) ;
>>>> open a ps file
>>>> gsn_define_colormap(wks,"rainbow") ;"BlAqGrYeOrRe") ;
>>>> choose colormap
>>>> printVarSummary(u)
>>>> printVarSummary(v)
>>>> printVarSummary(speed)
>>>> plot=gsn_csm_vector_scalar_map_ce(wks,u,v,speed,vcres) ; create plot
>>>> end do
>>>> Anyone can help me for figuring out the error? Thanks.
>>>> 2013-09-06
>>>> ------------------------------------------------------------------------
>>>> ???
>>>>
>>>>
>>>> _______________________________________________
>>>> ncl-talk mailing list
>>>> List instructions, subscriber options, unsubscribe:
>>>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>>>
>>> --
>>> ______________________________________________________________
>>> Adam Phillipsasphilli@ucar.edu
>>> NCAR/Climate and Global Dynamics Division (303) 497-1726
>>> P.O. Box 3000
>>> Boulder, CO 80307-3000http://www.cgd.ucar.edu/cas/asphilli
>>>
>>>
>>> _______________________________________________
>>> ncl-talk mailing list
>>> List instructions, subscriber options, unsubscribe:
>>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>>
>> --
>> ______________________________________________________________
>> Adam Phillipsasphilli@ucar.edu
>> NCAR/Climate and Global Dynamics Division (303) 497-1726
>> P.O. Box 3000
>> Boulder, CO 80307-3000http://www.cgd.ucar.edu/cas/asphilli
>>
>>
>> _______________________________________________
>> ncl-talk mailing list
>> List instructions, subscriber options, unsubscribe:
>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
> --
> ______________________________________________________________
> Adam Phillips asphilli@ucar.edu
> NCAR/Climate and Global Dynamics Division (303) 497-1726
> P.O. Box 3000
> Boulder, CO 80307-3000 http://www.cgd.ucar.edu/cas/asphilli
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20130905/41ed3654/attachment.html
>
> ------------------------------
>
> Message: 11
> Date: Thu, 05 Sep 2013 14:37:08 -0800
>From: Soumik Basu <sbasu@iarc.uaf.edu>
> Subject: 2-6 days band pass filter
> To: Ncl Talk <ncl-talk@ucar.edu>
> Message-ID: <1a5d6d57888e4c6de08f25185de3a328@arthur.iarc.uaf.edu>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Hi,
>
> I am trying to a band pass filter 0f 2-6 days. My data has 6 hourly
>time
> steps. My questions are:
>
> 1) For using 2-6 days band pass filter on transient eddy kinetic
>energy
> how many weights should I use? I am using 101 weights.
>
> 2)How can negative values come when it does not have any negative
>values
> before doing the running average.
>
> Here is the printVarSummary before running average
>
> Variable: eke775
> Type: float
> Total Size: 47185920 bytes
> 11796480 values
> Number of Dimensions: 3
> Dimensions and sizes: [time | 360] x [lat | 128] x [lon | 256]
> Coordinates:
> time: [30.5..120.25]
> lat: [-88.92773535229591..88.92773535229591]
> lon: [ 0..358.59375]
> Number Of Attributes: 2
> lev_p : 775
> _FillValue : 9.96921e+36
> (0)
> (0) min=6.84898e-06 max=2269.73
>
> Here is the printVarSummary and min max after running average
>
>
> Variable: eke_f
> Type: float
> Total Size: 47185920 bytes
> 11796480 values
> Number of Dimensions: 3
> Dimensions and sizes: [time | 360] x [lat | 128] x [lon | 256]
> Coordinates:
> time: [30.5..120.25]
> lat: [-88.92773535229591..88.92773535229591]
> lon: [ 0..358.59375]
> Number Of Attributes: 3
> lev_p : 775
> _FillValue : 9.96921e+36
> wgt_runave_op_ncl : wgt_runave_n
> (0)
> (0) min=-689.534 max=1134.18
>
>
> This is the part of the script I am using for filtering and running
> average:
>
> ;*******************************************************
> ; Calculate band pass filter weights
> ;*******************************************************
> ;lanczos weights for 2-6 day bandpass using 6-hourly data
>
>
> ;number of timesteps in low pass cutoff -- in this case 6 days (6*4
>= 24
> time steps)
>
>
> low = 24
>
>
> ;number of timesteps in high pass cutoff -- in this case 2 days (8
>time
> steps)
>
>
> high= 8.
>
>
> nwt = 101 ;A scalar indicating the total number of weights
>
> ;(must be an odd number; nwt >= 3).
>
> ;The more weights, the better the filter, but there is a
>
> ;greater loss of data.
>
> fca = 1./low ;A scalar indicating the cut-off frequency of the
>ideal
>
> ;high or low-pass filter: (0.0 < fca < 0.5)
>
> fcb = 1./high ;A scalar used only when a band-pass filter is
>desired.
>
> ;It is the second cut-off frequency (fca < fcb < 0.5).
>
> ihp = 2 ;A scalar indicating the low-pass filter:
>
> ;ihp = 0; high-pass ihp = 1; band-pass ihp = 2.
>
> nsigma = 1. ;A scalar indicating the power of the sigma factor
>(nsigma
> >= 0).
>
> ;Note: nsigma=1. is common.
>
>
> ; compute weights
>
>
> wts = filwgts_lancos (nwt, ihp, fca, fcb, nsigma)
>
>
> print(wts)
>
>
> print(wts@resp+" "+wts@freq)
>
>
> ;********************************************************
> ; apply lanczos wts to 6 hourly data -> band pass filtering
> ;********************************************************
>
>
> eke_f = wgt_runave_n_Wrap(eke775,wts,0,0)
>
>
> printVarSummary(eke_f)
> printMinMax(eke_f,True)
>
> Thanks,
> Soumik
>
>
>
>
> --
> "Numbing the pain for a while will make it worse when you finally
>feel
> it.
> ~J.K. Rowling"
> *****************************************
> Soumik Basu
> Graduate Student, Research Assistant
> International Arctic Research Center
> University of Alaska Fairbanks
>Fairbanks,Alaska,USA
> *****************************************
>
>
> ------------------------------
>
> Message: 12
> Date: Thu, 05 Sep 2013 18:59:04 -0600
>From: Dennis Shea <shea@ucar.edu>
> Subject: Re: 2-6 days band pass filter
> To: Soumik Basu <sbasu@iarc.uaf.edu>
> Cc: Ncl Talk <ncl-talk@ucar.edu>
> Message-ID: <522928D8.5030408@ucar.edu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>For 2 to 6 daya [ 1.0/(2*365) to 1.0/(6*365) cycles per year]
>
> You need a *lot* of weights: say 751
>
> On 9/5/13 4:37 PM, Soumik Basu wrote:
>> Hi,
>>
>> I am trying to a band pass filter 0f 2-6 days. My data has 6 hourly
>>time
>> steps. My questions are:
>>
>> 1) For using 2-6 days band pass filter on transient eddy kinetic
>>energy
>> how many weights should I use? I am using 101 weights.
>>
>> 2)How can negative values come when it does not have any negative
>>values
>> before doing the running average.
>>
>> Here is the printVarSummary before running average
>>
>> Variable: eke775
>> Type: float
>> Total Size: 47185920 bytes
>> 11796480 values
>> Number of Dimensions: 3
>> Dimensions and sizes: [time | 360] x [lat | 128] x [lon | 256]
>> Coordinates:
>> time: [30.5..120.25]
>> lat: [-88.92773535229591..88.92773535229591]
>> lon: [ 0..358.59375]
>> Number Of Attributes: 2
>> lev_p : 775
>> _FillValue : 9.96921e+36
>> (0)
>> (0) min=6.84898e-06 max=2269.73
>>
>> Here is the printVarSummary and min max after running average
>>
>>
>> Variable: eke_f
>> Type: float
>> Total Size: 47185920 bytes
>> 11796480 values
>> Number of Dimensions: 3
>> Dimensions and sizes: [time | 360] x [lat | 128] x [lon | 256]
>> Coordinates:
>> time: [30.5..120.25]
>> lat: [-88.92773535229591..88.92773535229591]
>> lon: [ 0..358.59375]
>> Number Of Attributes: 3
>> lev_p : 775
>> _FillValue : 9.96921e+36
>> wgt_runave_op_ncl : wgt_runave_n
>> (0)
>> (0) min=-689.534 max=1134.18
>>
>>
>> This is the part of the script I am using for filtering and running
>> average:
>>
>> ;*******************************************************
>> ; Calculate band pass filter weights
>> ;*******************************************************
>> ;lanczos weights for 2-6 day bandpass using 6-hourly data
>>
>>
>> ;number of timesteps in low pass cutoff -- in this case 6 days (6*4
>>= 24
>> time steps)
>>
>>
>> low = 24
>>
>>
>> ;number of timesteps in high pass cutoff -- in this case 2 days (8
>>time
>> steps)
>>
>>
>> high= 8.
>>
>>
>> nwt = 101 ;A scalar indicating the total number of weights
>>
>> ;(must be an odd number; nwt >= 3).
>>
>> ;The more weights, the better the filter, but there is a
>>
>> ;greater loss of data.
>>
>> fca = 1./low ;A scalar indicating the cut-off frequency of the
>>ideal
>>
>> ;high or low-pass filter: (0.0 < fca < 0.5)
>>
>> fcb = 1./high ;A scalar used only when a band-pass filter is
>>desired.
>>
>> ;It is the second cut-off frequency (fca < fcb < 0.5).
>>
>> ihp = 2 ;A scalar indicating the low-pass filter:
>>
>> ;ihp = 0; high-pass ihp = 1; band-pass ihp = 2.
>>
>> nsigma = 1. ;A scalar indicating the power of the sigma factor
>>(nsigma
>> >= 0).
>>
>> ;Note: nsigma=1. is common.
>>
>>
>> ; compute weights
>>
>>
>> wts = filwgts_lancos (nwt, ihp, fca, fcb, nsigma)
>>
>>
>> print(wts)
>>
>>
>> print(wts@resp+" "+wts@freq)
>>
>>
>> ;********************************************************
>> ; apply lanczos wts to 6 hourly data -> band pass filtering
>> ;********************************************************
>>
>>
>> eke_f = wgt_runave_n_Wrap(eke775,wts,0,0)
>>
>>
>> printVarSummary(eke_f)
>> printMinMax(eke_f,True)
>>
>> Thanks,
>> Soumik
>>
>>
>>
>>
>
>
> ------------------------------
>
> Message: 13
> Date: Thu, 5 Sep 2013 22:13:07 -0500
>From: Luis Fernando Montana Roa <lfmontanar@unal.edu.co>
> Subject: meteogram from grib2 file
> To: ncl-talk@ucar.edu
> Message-ID:
> <CAMXiZs6A5XBSpXD4XLEm9mYkhpgQ0HqR+1wgysZKENY3hySt0Q@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi, I'm trying to plot a meteogram from GRIB2 files (such as
>attached).
> When I run the script, shows the following errors:
> ...
> warning:Attempt to reference attribute (MAP_PROJ) which is undefined
> warning:Attempt to reference attribute (TRUELAT1) which is undefined
> warning:Attempt to reference attribute (TRUELAT2) which is undefined
> warning:Attempt to reference attribute (STAND_LON) which is
>undefined
> warning:Attempt to reference attribute (DX) which is undefined
> warning:Attempt to reference attribute (DY) which is undefined
> fatal:The result of the conditional expression yields a missing
>value. NCL
> can not determine branch, see ismissing function
> fatal:["Execute.c":8128]:Execute: Error occurred at or near line
>2262 in
> file $NCARG_ROOT/lib/ncarg/nclscripts/wrf/WRFUserARW.ncl
>
> fatal:["Execute.c":8128]:Execute: Error occurred at or near line 21
>in file
> meteogram02.ncl
>
> Any suggestions?
>
> Thanks,
>
> -- Fernando
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20130905/6927242f/attachment.html
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: meteogram02.ncl
> Type: application/octet-stream
> Size: 5788 bytes
> Desc: not available
> Url :
>http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20130905/6927242f/attachment.obj
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: grid_WRF_20130904-060000_ECOLOMBIA_F00080000_Pideam_R4km.grb2
> Type: application/octet-stream
> Size: 762585 bytes
> Desc: not available
> Url :
>http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20130905/6927242f/attachment-0001.obj
>
> ------------------------------
>
> _______________________________________________
> ncl-talk mailing list
> ncl-talk@ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
>
> End of ncl-talk Digest, Vol 118, Issue 10
> *****************************************
_______________________________________________
ncl-talk mailing list
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/ncl-talk
Received on Fri Sep 6 11:36:53 2013
This archive was generated by hypermail 2.1.8 : Mon Sep 16 2013 - 13:43:52 MDT