Re: Bug #1503114

[Daniel J S. <dan...@ie...>]

Hans-Bernhard Br=F6ker wrote:
> Daniel J Sebald wrote:
>=20
>> Hans-Bernhard Br=F6ker wrote:
>>
>>> Daniel J Sebald wrote:
>=20
>=20
>> My point here is that I think there is an inherent amount of visual=20
>> plotting information that a person can view.  I'm confortable with the=
=20
>> idea of limits on resolution.
>=20
>=20
> The idea of such limits is obviously correct.  The problems start when=20
> you try to fix those limits to an actual value, and use it.  The choice=
=20
> is so hard because there is no single such limit --- its choice is=20
> arbitrary.

I suppose.  There is a typical visual resolution, but nothing to cover al=
l resolutions.


>> The idea would be to reasonably catch the situation where the tic=20
>> interval is computed as 1/3 =3D 0.33333333333 and then the round outwa=
rd=20
>> test does something (after arithmetic) like deciding  0.999999999999 <=
=20
>> 1.0 because of rounding.
>=20
>=20
> That is a non-issue, because autoscaling never picks a tick interval of=
=20
> 1/3.  It picks power-of-ten multiples of 1, 2 or 5.
>=20
>> OK.  Did you want to change the demos and set the ranges in a few case=
s? =20
>=20
>=20
> I'm not even convinced that any change is necessary for this at all.
> A few tweaks to the demos would be about the maximum I would see as=20
> useful here.

That is what I'm suggesting.  Below is an example of something for the lo=
ngest time I couldn't understand, i.e., why the yrang here is as it is.  =
The y range could be forced to make it look better.

However, if what you say above is true, something seems odd.  This should=
 be a clear case where autoranging on y comes out as [1:2].  The tic inte=
rvals are 0.2.  (I would think, anyway, given that (2-1)/5 =3D 0.2.  No a=
rithmetic problems there.)  And the data in the file is exactly on (0,1) =
(1,1) and (2,1).

What is happening there?



PM3D.DEM CODE

reset

set title "Demo for clipping of 2 rectangles comes now. The xrange is [0:=
2]..."
set pm3d; set palette
set pm3d map

set xrange [0:2]
splot 'clip14in.dat'

CLIP14IN.DAT

# demo for set pm3d [clip1in | clip4in]

0 1 1
1 1 2
2 1 3

0 2 1
1 2 2
2 2 3