|
From: Petr M. <mi...@ph...> - 2006-04-09 12:52:34
|
>>> Enable verify every pixel coordinate in image (EXPERIMENTAL) >> I don't even know what that 'verify' one does. > > Because we are forced to stay with the "points" method of storing data (see > above), every pixel in an image has an (x,y,z) location. Now, that data > could have come from binary or ascii, with or without implied physical > position. So, it could be the case that the user did or did not supply the > coordinates. If the user did supply coordinates, there is the possibility > that the the coordinates don't form a valid grid. We then ask, should or > should we not verify the location of every individual pixel? Or is it good > enough just to know the four corners of the image and assume an evenly spaced > grid even though the user may have entered data that doesn't fit to that. > > I'm happy with not verifying the points. (Matlab/Octave sometimes does that > sort of thing... just looks at the end points and assumes even spacing. > Also, speeds things up a bit.) I don't know how others feel. I propose to remove the verification. I've already met a trouble where plotting of an experimental map (in gnuplot binary format) was refused because "equidistant" stepper motor positions were above the built-in tolerance. If a user wants to draw a non-equistant map, then he should use with pm3d, not with image. --- PM |