Re: pdfx() bin boundaries

From: Dennis Shea <shea_at_nyahnyahspammersnyahnyah>
Date: Sun Jul 04 2010 - 22:29:52 MDT

The function code is in contributed.ncl

A quick look does not see how that could happen.

D

[snip]
   XMIN = min(x)*1d0 ; min/max for ENTIRE array
   XMAX = max(x)*1d0 ; force "double" [*1d0]

   xMin = 0.0d ; prototype as double
   xMax = 0.0d

   if (opt .and. isatt(opt,"bin_min")) then
       xMin = opt@bin_min ; user set
   else
       xMin = XMIN ; calculate
   end if

   if (opt .and. isatt(opt,"bin_max")) then
       xMax = opt@bin_max ; user set
   else
       xMax = XMAX ; calculate
   end if
[snip]

On 7/4/10 10:16 PM, Rob Nicholas wrote:
> For the function pdfx(), it appears (via trial and error) that the
> option opt@bin_max sets the *lower* boundary of the final bin. Is
> this the intended behavior? The documentation is a little vague on
> this point, but I interpreted it to mean that this should set the
> upper boundary of the final bin, expecting (bin_max - bin_min)/nbins =
> bin_width.
>
> ~Rob
> _______________________________________________
> ncl-talk mailing list
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
_______________________________________________
ncl-talk mailing list
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/ncl-talk
Received on Sun Jul 4 22:29:57 2010

This archive was generated by hypermail 2.1.8 : Fri Jul 09 2010 - 16:06:22 MDT