#266 logz and alters GPVAL_TERM_XMIN on pm3d with view map

[thomas]

Hi I am using the variables GPVAL_TERM_XMIN and so on.
When I turn on set log z scaling on pm3d together with set view map,
I get very large wrong values, here is some minimal example:
I am using Version 5.4 patchlevel 1, tested either on windows or linux.

set term pngcairo enhanced size 100,200
set output "123.png"
set view map
set pm3d 
set log z
set log cb
splot sin(sqrt(x**2+y**2))/sqrt(x**2+y**2)
print GPVAL_TERM_XMIN
print GPVAL_TERM_XMAX
print GPVAL_TERM_YMIN
print GPVAL_TERM_YMAX
print GPVAL_X_MIN
print GPVAL_X_MAX
print GPVAL_Y_MIN
print GPVAL_Y_MAX
print GPVAL_TERM_SCALE

this prints:

-107374132
-107374132
-107374073
-107374073
-10.0
10.0
-10.0
10.0
20

if you run it without the set view map you get:

25
73
47
170
-10.0
10.0
-10.0
10.0
20

and if you run it with set view map and without set log z

29
69
159
58
-10.0
10.0
-10.0
10.0
20

The latter two are fine, but values like -107374132, seem wrong to me.
I do not really understand this.
Hope someone can help me.

[thomas]

Ok if I only use set log cb, it is working as expected. Still no idea why the z-axis log affects the spacing.

[Ethan Merritt]

It's a bug. It will be fixed for 5.4.2

logz + set view map triggers the bug because the calculation of corner points for the plot assumed that for 'set view map' the actual z coordinates don't matter. And they don't matter. The bug was it then used zero as a default value and that obviously doesn't work for a log-scaled axis.

[thomas]

Ah ok great. Thanks for you response.