[ncl-talk] unable to plot correctly
Mary Haley
haley at ucar.edu
Mon Aug 20 13:55:25 MDT 2018
Geeta,
In the future please respond to the original message and not to the
"digest" form of the message, as it makes it hard for the reader to pick
out your messages. I changed the subject back to the original one that you
posted under.
The issue with your script is that you are trying to turn Y and X into
lat/lon arrays, but Y and X are projection coordinates, *not* latitude /
longitude values in the required "degrees" units. Just because you attached
them to your variable as "lat" and "lon" doesn't mean they automatically
turn into degrees. NCL has *no* way of knowing how to translate Y and X
into lat/lon because this depends on a lot of factors, including what map
projection the data were originally measured on.
I see that there's a "Projection_Information" variable, and it provides
what looks like the corners of the lat/lon rectangle of your data in
degrees. Using this information, I attempted to create a plot of your data
using the "native" map projection that's defined on the file. The problem
is I don't know if I have the map projection correct, so it will be up to
you to fix any errors.
I've included the modified script and the resultant graphics. I also
changed the contour levels to better reflect the layout of your data. I
used a "print_binned_info" procedure to help me select the levels. I've
included that here too.
It is critical that you look at your data file and understand it before you
try plotting it, especially since the latitude and longitude arrays are not
provided on the file. You may need to go back to wherever you downloaded
the data and read documentation to understand how to correctly plot it. I
took a guess at it, but I don't have the time to do this kind of research.
-Mary
On Sat, Aug 18, 2018 at 7:17 AM, Geeta Geeta <geetag54 at yahoo.com> wrote:
> Thanks Mary.
> I am first trying to plot the count values (IMG_MIR variable). and then
> going for the MIRF (Radiance)
> Earlier, I was attaching the X and Y axis Labels explicitly as given
> below, So the plot was not correct. Dont know why
> [; res at tmXBMode = "Explicit"
> ; res at tmXBValues = (/"60","65","70","75","80","85","90","95","100"/)
> ]
>
> The lat/lon are large numbers, varyning between (5401854.420193..-1058893.687497]
> But the meta data says the lat/lon bounds are 44.5-105.5/-10S to 45.5.
> So lat/lon in the file are to be converted to the meaningful ones (as
> given in the meta data)
>
> Now I am not attaching the X and Y axis Labels explicitly to the plot
> (attached) so it plots the contours. But I get a warning like this
> (0) get_lon_values: Warning: The range your of longitude values is
> greater than 360.
> warning:ManualComputeMajorTickMarks: Maximum tickmarks (256) has been
> reached, tickmarks may appear in complete
> warning:ExplicitComputeMinorTickMarks: Maximum minor tickmarks (1024) has
> been reached, tickmarks may appear incomplete
> warning:ManualComputeMajorTickMarks: Maximum tickmarks (256) has been
> reached, tickmarks may appear in complete
> warning:ExplicitComputeMinorTickMarks: Maximum minor tickmarks (1024) has
> been reached, tickmarks may appear incomplete
> (0) get_lat_values: Warning: Your latitude values do not fall between -90
> and 90 inclusive.
> (0) You will not get 'nice' latitude labels.
>
>
> Output from the code
> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> Variable: MIR
> Type: ushort
> Total Size: 5229376 bytes
> 2614688 values
> Number of Dimensions: 3
> Dimensions and sizes: [time | 1] x [lat | 1616] x [lon | 1618]
> Coordinates:
> lat: [5401854.420193..-1058893.687497]
> lon: [-3234623.003937..3234623.003937]
> Number Of Attributes: 18
> DIMENSION_LIST : <ARRAY of 0 elements>
> _FillValue : 1023
> bandwidth : 0.2
> bits_per_pixel : 10
> central_wavelength : 3.9313
> grid_mapping : Projection_Information
> invert : trueection_Information
> lab_radiance_add_offset : -0.00413433
> lab_radiance_add_offset_gsics : -0.0110259
> lab_radiance_quad : -1.31797e-07
> lab_radiance_quad_gsics : -1.88751e-07
> lab_radiance_scale_factor : 0.000281346
> lab_radiance_scale_factor_gsics : 0.000402925
> long_name : Middle Infrared Countn
> radiance_units : mW.cm-2.sr-1.micron-1n
> resolution : 4
> resolution_unit : km.cm-2.sr-1.micron-1n
> wavelength_unit : micron2.sr-1.micron-1n
> (0) MIRi
> (0)
> (0) Middle Infrared Countn: min=0 max=1001
>
> Variable: MIRF
> Type: float
> Total Size: 10458752 bytes
> 2614688 values
> Number of Dimensions: 3
> Dimensions and sizes: [time | 1] x [lat | 1616] x [lon | 1618]
> Coordinates:
> lat: [5401854.420193..-1058893.687497]
> lon: [-3234623.003937..3234623.003937]
> Number Of Attributes: 19
> _FillValue : 1023
> _FillValue_original : 1023
> wavelength_unit : micron2.sr-1.micron-1n
> resolution_unit : km.cm-2.sr-1.micron-1n
> resolution : 4
> radiance_units : mW.cm-2.sr-1.micron-1n
> long_name : Middle Infrared Countn
> lab_radiance_scale_factor_gsics : 0.000402925
> lab_radiance_scale_factor : 0.000281346
> lab_radiance_quad_gsics : -1.88751e-07
> lab_radiance_quad : -1.31797e-07
> lab_radiance_add_offset_gsics : -0.0110259
> lab_radiance_add_offset : -0.00413433
> invert : trueection_Information
> grid_mapping : Projection_Information
> central_wavelength : 3.9313
> bits_per_pixel : 10
> bandwidth : 0.2
> DIMENSION_LIST : <ARRAY of 0 elements>
> (0)
> (0) Middle Infrared Countn: min=-0.00413433 max=0.277493
> ;;;;;;;;;;;;; O/P ended
>
>
> ;;;;;;;;;;;;;;;;;;;
> f = addfile("/home/aditya/geeta/ncl/h5/3DIMG_23JUN2018_0300_
> L1C_ASIA_MER.h5","r")
> ; printVarSummary(f)
> print(f)
> var = getfilevarnames(f)
> ; print(var)
> longt = f->X
> ; printVarSummary(longt)
> print(longt(0))
> print(longt(1))
> lati = f->Y
> ; printVarSummary(lati)
> TIME = f->time
>
> MIR = (f->IMG_MIR)
> MIR!0 = "time"
> MIR!1 = "lat"
> MIR!2 = "lon"
> MIR&lat = lati
> MIR&lon = longt
> MIR&lat at units = "degrees_north"
> MIR&lon at units = "degrees_east"
> MIR at _FillValue = integertoshort(1023)
> printVarSummary(MIR)
> print("MIRi ")
> printMinMax(MIR,True)
>
>
> I have sent the data file.
>
> Geeta.
>
>
> On Friday, 17 August 2018 8:14 AM, "ncl-talk-request at ucar.edu" <
> ncl-talk-request at ucar.edu> wrote:
>
>
> Send ncl-talk mailing list submissions to
> ncl-talk at 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 at ucar.edu
>
> You can reach the person managing the list at
> ncl-talk-owner at 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: confused about tickmarks (Mary Haley)
> 2. Re: unable to plot correctly (Mary Haley)
> 3. ??? Significance with contour: positive in solid line
> andnegative in dash line (=?gb18030?B?wfXV8Q==?=)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 16 Aug 2018 20:20:29 -0600
> From: Mary Haley <haley at ucar.edu>
> To: Laura Fowler <laura at ucar.edu>
> Cc: Ncl-talk <ncl-talk at ucar.edu>
> Subject: Re: [ncl-talk] confused about tickmarks
> Message-ID:
> <CACNN_CJd=PsHK5bvLa470WYzLEjqHcdid7fyYBYsCjW4W0aZvQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Laura,
>
> I'm going through some older emails that look like they don't have
> responses, and this is one of them.
>
> The gsn_csm_pres_hgt function is actually two plots overlaid on top of each
> other. The base plot is a "LogLin" plot which allows us to have a log
> axis. The overlaid plot is the contour plot and it's the one that's setting
> all the tickmark stuff.
>
> When you did a getvalues on plot, this is the LogLin plot and hence doesn't
> have the tickmark labels. If you call "print(plot)" you will see it has an
> attribute "contour" that looks something like this:
>
> contour : h_lat_contour contourPlotClass 11
>
> This is the thing you want to retrieve the labels from:
>
> getvalues plot at contour
> "tmXBValues" : tmXBValues
> end getvalues
>
> Did you get your labeling problem figured out?
>
> --Mary
>
>
> On Thu, Aug 2, 2018 at 9:41 AM, Laura Fowler <laura at ucar.edu> wrote:
>
> > Hello:
> >
> > Following the -email I sent yesterday regarding tickmarks, I simplified
> my
> > ncl script to understand about the bottom tickmarks are labelled by
> default
> > so that I can understand how to change them using tmXBValues and
> > tmXBLabels. The simplified script is in
> >
> > /glade2/scratch2/laura/MPASprojects.2018/forPUBLICATION/TENDENCIES/
> > rect.cu_kain_fritsch_sca.20151129-20160102 and the script is plot.ncl.
> > Also see attached plot dtcup.kf.pdf.
> >
> >
> > I tried to retrieve the default values of tmXBValues with the lines:
> >
> >
> > res2 at tmXBMode = "Automatic"
> >
> > plot = gsn_csm_pres_hgt(wks,dtcup_interp_kf,res2)
> >
> >
> > getvalues plot
> >
> > "tmXBValues" : tmXBValues
> >
> > end getvalues
> >
> > print(" ")
> >
> > print(tmXBValues)
> >
> > Then I get:
> >
> > Variable: tmXBValues
> >
> > Type: float
> >
> > Total Size: 16 bytes
> >
> > 4 values
> >
> > Number of Dimensions: 1
> >
> > Dimensions and sizes: [4]
> >
> > Coordinates:
> >
> > (0) 0
> >
> > (1) 100
> >
> > (2) 200
> >
> > (3) 300
> >
> > (0)
> >
> > which is super confusing to me since the plot shows at least 6 values for
> > the major tickmarks and not just 4. Is it possible to actually set
> > different XB labels with gsn_csm_pres_hgt?
> >
> >
> > I would really appreciate some hints on how to do this.
> >
> >
> >
> > Many thanks,
> >
> > Laura
> >
> >
> >
> > --
> > !-----------------------------------------------------------
> > --------------------------------------------------
> > Laura D. Fowler
> >
> > Mesoscale and Microscale Meteorology Division (MMM)
> > National Center for Atmospheric Research
> > P.O. Box 3000, Boulder CO 80307-3000
> >
> > e-mail: laura at ucar.edu
> > phone: 303-497-1628
> >
> > !-----------------------------------------------------------
> > --------------------------------------------------
> >
> > _______________________________________________
> > ncl-talk mailing list
> > ncl-talk at ucar.edu
> > 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/20180816/bfdeb56b/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 16 Aug 2018 20:21:56 -0600
> From: Mary Haley <haley at ucar.edu>
> To: Geeta Geeta <geetag54 at yahoo.com>
> Cc: "ncl-talk \[ncl-talk\]" <ncl-talk at ucar.edu>
> Subject: Re: [ncl-talk] unable to plot correctly
> Message-ID:
> <CACNN_C+8vMWS_Q4dyXA1HMx65Hed3xp8cW_ac2Y61EDDDCphog at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Geeta,
>
> I don't know if you ever resolved this, but part of the problem is if you
> are drawing contour lines of a very high-res plot, it is not a surprise
> that you would get a lot of black lines.
>
> To make the plotting go faster, I suggest:
>
> res at cnFillOn = True
> res at cnFillMode = "RasterFill"
>
> Dennis suggested that you use this:
>
> MIRF = MIR*MIR at lab_radiance_scale_factor + MIR at lab_radiance_add_offset
>
> but then in the script that you sent, MIRF is not used for plotting.
> However, I think there would be an issue with plotting anyway, because when
> you do a calculation like the above, all the metadata that was attached to
> MIR is going to be stripped off, and MIRF will not have anything but a
> _FillValue attribute. To fix something like that, we suggest:
>
> MIRF = MIR*MIR at lab_radiance_scale_factor + MIR at lab_radiance_add_offset
>
> copy_VarMeta(MIR,MIRF)
>
> before you try to plot MIRF.
>
> If you are still having problems, it would help if you include a
> printVarSummary output of various variables in your script, especially the
> MIR variables and the lat/lon variables. Even better, if you could provide
> the file on ftp.
>
> Thanks,
>
> --Mary
>
>
>
>
> On Wed, Aug 1, 2018 at 12:18 PM, Geeta Geeta <geetag54 at yahoo.com> wrote:
>
> > thanks Dennis.
> > I have to plot the count value only which is between 0-1001. (MinMax
> MIR).
> > the plotting is over but the plot shows small white dots and is fully
> black
> > on careful examination.
> > I could not understand why should that be (i mean black with white dots)
> > because below the plot, it is shown "Contour from 0-1001".
> >
> > If I ON the contour resources, the code runs forever.
> >
> >
> > thanks
> > Geeta.
> >
> >
> > On Wednesday, 1 August 2018 5:05 AM, Dennis Shea <shea at ucar.edu> wrote:
> >
> >
> > I think this has been mentioned to you before:
> >
> > *The most important rule in data processing is look at your data.'*---
> > T*he 2nd-most important rule is* *read the documentation of the project.*
> >
> > Note: It is not ncl-talk's job to read the documentation. It is your job.
> > ---
> >
> > Variable: MIR
> > Type: *ushort*
> > Dimensions and sizes: [DIM_000 | 1] x [DIM_001 | 1616] x [DIM_002 | 1618]
> >
> > * lab_radiance_add_offset *: -0.00413433
> > lab_radiance_add_offset_gsics : -0.0110259
> > lab_radiance_quad : -1.31797e-07
> > lab_radiance_quad_gsics : -1.88751e-07
> > *lab_radiance_scale_factor *: 0.000281346
> > lab_radiance_scale_factor_ gsics : 0.000402925
> >
> > I *speculate* that to get correct values you would have to use something
> > like:
> >
> > MIRF = MIR***MIR@*lab_radiance_scale_factor + MIR@*
> >
> > *lab_radiance_add_offset*
> > or
> >
> >
> > MIRF = *(*MIR* + **MIR at lab_radiance_add_offset**)**MIR@
> > *lab_radiance_scale_factor*
> >
> > or
> >
> >
> > * ????*
> > Again, this is your responsibility.
> >
> > Good Luck
> >
> > On Tue, Jul 31, 2018 at 11:27 AM, Geeta Geeta <geetag54 at yahoo.com>
> wrote:
> >
> > Hi all.
> > I am trying to plot MIR_int (variable defined in the ncl code), but it is
> > not being plotted properly. the output is without any error
> >
> >
> > aditya at agniilap:~/geeta/ncl/ h5$ ../bin/ncl readh5.v2.ncl
> > Copyright (C) 1995-2014 - All Rights Reserved
> > University Corporation for Atmospheric Research
> > NCAR Command Language Version 6.2.1
> > The use of this software is governed by a License Agreement.
> > See http://www.ncl.ucar.edu/ for more details.
> >
> > Variable: f
> > Type: file
> > File path: /home/aditya/geeta/ncl/h5/ 3DIMG_23JUN2018_0300_L1C_ASIA_
> > MER.h5
> > Number of global attributes: 38
> > Number of dimensions: 4
> > Number of variables: 27
> >
> >
> > Variable: var
> > Type: string
> > Total Size: 108 bytes
> > 27 values
> > Number of Dimensions: 1
> > Dimensions and sizes: [27]
> > Coordinates:
> > (0) /GreyCount
> > (1) /IMG_MIR
> > (2) /IMG_MIR_RADIANCE
> > (3) /IMG_MIR_TEMP
> > (4) /IMG_SWIR
> > (5) /IMG_SWIR_RADIANCE
> > (6) /IMG_TIR1
> > (7) /IMG_TIR1_RADIANCE
> > (8) /IMG_TIR1_TEMP
> > (9) /IMG_TIR2
> > (10) /IMG_TIR2_RADIANCE
> > (11) /IMG_TIR2_TEMP
> > (12) /IMG_VIS
> > (13) /IMG_VIS_ALBEDO
> > (14) /IMG_VIS_RADIANCE
> > (15) /IMG_WV
> > (16) /IMG_WV_RADIANCE
> > (17) /IMG_WV_TEMP
> > (18) /Projection_Information
> > (19) /Sat_Azimuth
> > (20) /Sat_Elevation
> > (21) /Sun_Azimuth
> > (22) /Sun_Elevation
> > (23) /X
> > (24) /Y
> > (25) /proj_dim
> > (26) /time
> >
> > Variable: MIR
> > Type: ushort
> > Total Size: 5229376 bytes
> > 2614688 values
> > Number of Dimensions: 3
> > Dimensions and sizes: [DIM_000 | 1] x [DIM_001 | 1616] x [DIM_002 | 1618]
> > Coordinates:
> > Number Of Attributes: 18
> > DIMENSION_LIST : <ARRAY of 0 elements>
> > _FillValue : 1023
> > bandwidth : 0.2
> > bits_per_pixel : 10
> > central_wavelength : 3.9313
> > grid_mapping : Projection_Information
> > invert : trueection_Information
> > lab_radiance_add_offset : -0.00413433
> > lab_radiance_add_offset_gsics : -0.0110259
> > lab_radiance_quad : -1.31797e-07
> > lab_radiance_quad_gsics : -1.88751e-07
> > lab_radiance_scale_factor : 0.000281346
> > lab_radiance_scale_factor_ gsics : 0.000402925
> > long_name : Middle Infrared Countn
> > radiance_units : mW.cm-2.sr-1.micron-1n
> > resolution : 4
> > resolution_unit : km.cm-2.sr-1.micron-1n
> > wavelength_unit : micron2.sr-1.micron-1n
> >
> > Variable: MIR_int
> > Type: integer
> > Total Size: 10458752 bytes
> > 2614688 values
> > Number of Dimensions: 2
> > Dimensions and sizes: [1616] x [1618]
> > Coordinates:
> > Number Of Attributes: 1
> > _FillValue : 1023
> > (0)
> > (0) Middle Infrared Countn: min=0 max=1001
> >
> > Variable: longi
> > Type: double
> > Total Size: 12944 bytes
> > 1618 values
> > Number of Dimensions: 1
> > Dimensions and sizes: [DIM_002 | 1618]
> > Coordinates:
> > Number Of Attributes: 5
> > CLASS : DIMENSION_SCALE
> > REFERENCE_LIST : <ARRAY of 0 elements>
> > long_name : x coordinate of projectionperaturerature
> > standard_name : projection_x_ coordinateionperaturerature
> > units : mrojection_x_ coordinateionperaturerature
> > (0)
> > (0) x coordinate of projectionperaturerature: min=-3234623.003937
> > max=3234623.003937
> >
> > Variable: lati
> > Type: double
> > Total Size: 12928 bytes
> > 1616 values
> > Number of Dimensions: 1
> > Dimensions and sizes: [DIM_001 | 1616]
> > Coordinates:
> > Number Of Attributes: 5
> > CLASS : DIMENSION_SCALE
> > REFERENCE_LIST : <ARRAY of 0 elements>
> > long_name : y coordinate of projectionperaturerature
> > standard_name : projection_y_ coordinateionperaturerature
> > units : mrojection_y_ coordinateionperaturerature
> > (0)
> > (0) y coordinate of projectionperaturerature: min=-1058893.687497
> > max=5401854.420193
> >
> > Variable: TIME
> > Type: double
> > Total Size: 8 bytes
> > 1 values
> > Number of Dimensions: 1
> > Dimensions and sizes: [DIM_000 | 1]
> > Coordinates:
> > Number Of Attributes: 3
> > CLASS : DIMENSION_SCALE
> > REFERENCE_LIST : <ARRAY of 0 elements>
> > units : minutes since 2000-01-01 00:00:00erature
> >
> > Variable: proj
> > Type: integer
> > Total Size: 4 bytes
> > 1 values
> > Number of Dimensions: 1
> > Dimensions and sizes: [DIM_000 | 1]
> > Coordinates:
> > Number Of Attributes: 13
> > DIMENSION_LIST : <ARRAY of 0 elements>
> > false_easting : 0
> > false_northing : 0
> > grid_mapping_name : mercatorpor Brightness Temperaturerature
> > longitude_of_projection_origin : 75
> > lower_left_lat_lon(degrees) : ( -10, 44.5 )
> > lower_right_lat_lon(degrees) : ( -10, 105.5 )
> > semi_major_axis : 6378137
> > semi_minor_axis : 6356752.3142
> > standard_parallel : 17.75
> > upper_left_lat_lon(degrees) : ( 45.5, 44.5 )
> > upper_left_xy(meters) : ( -3234623.003937, 5401854.420193 )
> > upper_right_lat_lon(degrees) : ( 45.5, 105.5 )
> > (0)
> > (0) min=1461309144 max=1461309144
> > (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'
> > aditya at agniilap:~/geeta/ncl/ h5$
> >
> >
> > thanks
> >
> > Geeta.
> >
> > ______________________________ _________________
> > ncl-talk mailing list
> > ncl-talk at ucar.edu
> > List instructions, subscriber options, unsubscribe:
> > http://mailman.ucar.edu/ mailman/listinfo/ncl-talk
> > <http://mailman.ucar.edu/mailman/listinfo/ncl-talk>
> >
> >
> >
> >
> >
> > _______________________________________________
> > ncl-talk mailing list
> > ncl-talk at ucar.edu
> > 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/20180816/4fc5039b/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 17 Aug 2018 10:43:41 +0800
> From: "=?gb18030?B?wfXV8Q==?=" <286909655 at qq.com>
> To: "=?gb18030?B?TWFyeSBIYWxleQ==?=" <haley at ucar.edu>
> Cc: NCL <ncl-talk at ucar.edu>
> Subject: [ncl-talk] ??? Significance with contour: positive in solid
> line andnegative in dash line
> Message-ID: <tencent_BE9334A174DB2BD1BAB01EBE8933E95DED0A at qq.com>
> Content-Type: text/plain; charset="gb18030"
>
> Dear Mary,
>
>
> Thanks a lot for you reply and very good suggestions.
> Your methods perfectly solve my second problem.
> But, for the first one, it is, somehow, a little tricky. The contour
> line I want to plot represents p value (according to student's t test),
> which is always positive. In order to plot the positive (value in shading)
> with solid line while negative with dash line, I use
> ?prob=where(var.lt.0,-prob,prob)? in my script to change the p value
> (i.e., prob) first. Then I plot the p value using contour with negative p
> value in dash. But the region at 95% significant area totally changed.
> Please check the differences between the two outputs attached. The var.pdf
> should be the right one. Could you please help me to solve this issue.
> Thanks.
>
>
> Best regards,
> zhen
>
>
> ------------------
> ??
> ????
> ?????????
> ?????
> Phone: +86-15013246049
> Liu Zhen
> Department of Atmospheric Science
> School of Environmental Science and Engineering
> Sun Yat-sen University
> Email address: liuzhen9 at mail2.sysu.edu.cn
>
>
>
>
>
>
>
> ------------------ ???? ------------------
> ???: "Mary Haley"<haley at ucar.edu>;
> ????: 2018?8?17?(???) ??7:49
> ???: "??"<286909655 at qq.com>;
> ??: "ncl-talk"<ncl-talk at ucar.edu>;
> ??: Re: [ncl-talk] Significance with contour: positive in solid line
> andnegative in dash line
>
>
>
> Dear Zhen,
>
>
> One way to find out if there's an example for something specific you are
> trying to do, you can use the "tips" link on the examples page:
>
>
> List of tips, resources, functions/procedures and the example scripts they
> appear in.
>
>
> Which takes you to this page:
>
>
> http://www.ncl.ucar.edu/Applications/concepts_list.shtml
>
>
>
> You can then use your browser search to search for "negative" or
> "positive". You will find this under the search for "negative":
>
>
> Drawing negative contour lines as dashed lines
> conOncon_1.ncl (contours on contours)
> conOncon_2.ncl (contours on contours)
> conOncon_4.ncl (contours on contours)
> coneff_3.ncl (contour effects)
> coneff_5.ncl (contour effects)
> coneff_6.ncl (contour effects)
> coneff_9.ncl (contour effects)
>
>
>
>
>
> I recommend clicking on the link inside the "(...)" and not the actual NCL
> script, because this way you can see the description of the example, the
> image, and the link to the script. A good example to start with is
> "coneff_3.ncl":
>
>
> http://www.ncl.ucar.edu/Applications/coneff.shtml#ex3
>
>
>
> which mentions two resources, gsnContourNegLineDashPattern and
> gsnContourPosLineDashPattern
>
>
> http://www.ncl.ucar.edu/Document/Graphics/Resources/gsn.shtml#
> gsnContourNegLineDashPattern
>
> http://www.ncl.ucar.edu/Document/Graphics/Resources/gsn.shtml#
> gsnContourPosLineDashPattern
>
>
>
> which should hopefully answer your first question.
>
>
> To answer your second question, you can also use the "tips" page, but this
> time search for "dot" or "stipple". In this case, "dot" gives you the best
> results, and "coneff_11.ncl" may be the best example to look into. The
> resources cnFillScaleF and cnFillDotSizeF may help you with the density and
> size of your dots.
>
>
>
> http://www.ncl.ucar.edu/Applications/coneff.shtml#ex11
>
>
>
> If this doesn't help, please post back to ncl-talk.
>
>
> Thanks,
>
>
> --Mary
>
>
>
>
> On Thu, Aug 16, 2018 at 8:02 AM, ?? <286909655 at qq.com> wrote:
> Dear Sir/Madam,
>
>
> I use the script attached to plot the significance area (student's t
> test) with contour lines. I am wondering if there is a way to make the
> positive area (shading) in solid line while negative area in dash line. The
> output is also attached. Thanks.
> For another output named T2-CTLF-CTL-sum.pdf, most of the area are at
> 95% significant. By contrast, only region not significant show with
> contours. Could you also tell me how to deal with such kind of situation. I
> try to use dot instead of contour to show significant area. But all the
> plot become black because of the data at a high resolution. Here comes the
> question that how to decrease the density of the dots? Thanks.
>
>
> Best regards,
> zhen
>
>
> ------------------
> ??
> ????
> ?????????
> ?????
> Phone: +86-15013246049
> Liu Zhen
> Department of Atmospheric Science
> School of Environmental Science and Engineering
> Sun Yat-sen University
> Email address: liuzhen9 at mail2.sysu.edu.cn
>
>
>
>
> _______________________________________________
> ncl-talk mailing list
> ncl-talk at ucar.edu
> 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/20180817/5f32680a/attachment.html>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: T2.pdf
> Type: application/octet-stream
> Size: 712381 bytes
> Desc: not available
> URL: <http://mailman.ucar.edu/pipermail/ncl-talk/
> attachments/20180817/5f32680a/attachment.obj>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: var.pdf
> Type: application/octet-stream
> Size: 624750 bytes
> Desc: not available
> URL: <http://mailman.ucar.edu/pipermail/ncl-talk/
> attachments/20180817/5f32680a/attachment-0001.obj>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> ncl-talk mailing list
> ncl-talk at ucar.edu
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
>
> ------------------------------
>
> End of ncl-talk Digest, Vol 177, Issue 29
> *****************************************
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20180820/aed037b0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: readh5.v2.mod.ncl
Type: application/octet-stream
Size: 3577 bytes
Desc: not available
URL: <http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20180820/aed037b0/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test1.000002.png
Type: image/png
Size: 551268 bytes
Desc: not available
URL: <http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20180820/aed037b0/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test1.000001.png
Type: image/png
Size: 594157 bytes
Desc: not available
URL: <http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20180820/aed037b0/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: print_binned_info.ncl
Type: application/octet-stream
Size: 1639 bytes
Desc: not available
URL: <http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20180820/aed037b0/attachment-0003.obj>
More information about the ncl-talk
mailing list