Re: ComputeRange

From: Rene Brun <Rene.Brun_at_cern.ch>
Date: Sat, 13 Oct 2007 16:23:27 +0200


This behavior is now fixed in the SVN version.

Rene Brun

Marat Vznuzdaev wrote:
> Hi,
>
> I use a function: TGraphErrors::ComputeRange(Double_t &xmin, Double_t
> &ymin, Double_t &xmax, Double_t &ymax) to calculate limits of my
> graph. I see the strange behaviour of this function - the result
> depends on the initial value of &xmin, &ymin etc.
> For example, if I have the real range of a plotted function from 200
> to 300 it calculates maximum ymax=300 (it's ok) and ymin=0 (wrong). If
> I set ymin=1000 before, it computes ymin=200 (ok).
> The same error is for all parameters.
> Thus, this function use the initial value of parameter and, if the
> parameter out of range of the graph, for instance, if the initial
> value ymin is less than actual y-minimum of the graph, then
> ComputeRange keeps it as the minimum.
> It's really mistake or might be I do something wrong with the function?
>
> ROOT: 5.17.02 for Windows, recommended version.
>
> Regards
>
> Marat.
>
>
Received on Sat Oct 13 2007 - 16:23:42 CEST

This archive was generated by hypermail 2.2.0 : Mon Oct 15 2007 - 11:50:01 CEST