All labels are correct, but now the X axis don’t fit the data cube anymore. Any tips on how to make it start at 0 and end at 4.0 (and not -2 to 6, as shown)

when I use Transform filter (ParaView 5.9.1) to scale the model view with the data, sometimes I have the same issue. To correct it, I just check/uncheck the Show box checkbox (which is close to Scale fields on the same Properties panel). If this is not a solution in your case, please describe how you re-scale X-axis.

Maybe if I describe all the steps we can figure it out. First let me describe an example without scaling the X-axis. First I load a raw binary dataset, where the vertical dimension X is the fastest, and positive down; the horizontal dimesion Y is second fastest and positive to the right; and the crossline dimension Z is the slowest and positive inwards (this needs left-handed axes). So the first step would be getting left-handed axes with Transform and Edit the Axes Grid window. My sampling rates are dx,dy,dz=(0.004,10,10); if we focus on only the lef-handed axes plotting and leave dx,dz,dy=(1,10,10) we get, on the Load data Properties (eye deactivated):

With Transform Properties (eye icon activated):

and the Axes Window Edit as:

we get a final result with all the Axes labels close to the data cube, as below:

The thing is, the X-axis shows 0 to 1023, but I wanted it to be 0 to 4. Hence, the re-scaling part, as below (I mentioned the left-handed axes conversion because maybe it influenced something…)

Now doing both the left-handed axes adaptation and X-axis rescaling (dx=0.004), the steps would be, on the load data Properties window:

And on the Transform Properties window:

With Axes Grid “Edit” as:

But this gives the box away from the data cube, as in the first message. Any hints?

Just a guess… but maybe the “Data bounds inflate factor” (last option in your screenshots) plays a trick on you with the large scaling values? I noticed that the default value is 1.0008 in the current ParaView version - probably due to updates. Maybe it could help to work with PV 5.10 instead of 5.4?
Good luck…
Venke

Hello Pavel and Venke, thanks for the help! I am using Paraview 5.4.1 because it is the version available on the Linux Mint package manager. The time spent on installing the newest version manually will probably pay off (as in problems like this…) so will definitely try installing it today.

Data bounds inflate factor solved the problem; 1.0008 exacerbated the problem, while 0.0000125 produced the desired result