Hello, even if the height is changed due to rotation (simply by fact that different parts of tip are shown if tip is rotated), it should not affect tip manipulation routines (dilation, erosion, etc.).
Regards, Petr On 05/19/2011 05:41 PM, Andrés Muñiz Piniella wrote: > Thanks Yeti, > > Found something new: for same image (256x256px), same tip radius, > (50nm), non-contact it does set to the 20x20px size but the height of > the tip changes with rotation. > After I model each tip I use the set minimum to zero data process and > measure the height of the tip > 0deg: 61.5 nm > 45deg: 66.9 nm > 90deg: 61.5 nm > 135deg: 63 nm > 180deg: 64.3 nm > 225deg: 59.1 nm > 270deg: 64.2 nm > 315deg: 63 nm > > I think about it I can't imagine a way in which the height would be > the same. I can't even imagine how you turn the tip in the first > place. I guess it's a small tip and rounding errors are more drastic? > > > On 5/19/11, David Nečas (Yeti)<[email protected]> wrote: > >> On Thu, May 19, 2011 at 03:18:11PM +0100, Andrés Muñiz Piniella wrote: >> >>> it has to do with the previous image that was selected. If I selected >>> the 256x256 image it will stick to 20x20px if I selected one of the >>> previously created tips it will do 21x21 px. >>> >> The physical dimensions are calculated from the parametres and tip type. >> Then the pixel dimensions are calculated to match the resolution >> (physical pixel size) of the selected image. Or at least that's how I >> recall it should work. So it is strange that you get different pixel >> dimensions if you select the image and the tip because the resolutions >> should match. Perhaps there's some rounding problem. >> >> Yeti >> >> >> ------------------------------------------------------------------------------ >> What Every C/C++ and Fortran developer Should Know! >> Read this article and learn how Intel has extended the reach of its >> next-generation tools to help Windows* and Linux* C/C++ and Fortran >> developers boost performance applications - including clusters. >> http://p.sf.net/sfu/intel-dev2devmay >> _______________________________________________ >> Gwyddion-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/gwyddion-users >> >> > > ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Gwyddion-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gwyddion-users
