On Mon, Sep 15, 2014 at 01:21:59PM +0200, Mathias Müller wrote:
> I already use the function as it is meant to be used and the sample data is
> fine, since the gwyddion fft-module displays everything correctly.
> But when getting data points via:
>
> gwy_selection_get_object(selection, ID, pos)
I don't understand what you are trying to accomplish. The selection is
just a set of real (as opposed to pixel) coordinates. If you have a
selection point saying it has coordinates (0,0) it has these
coordinates. You can use this selection in connection with some data
field to do something. Only in this combination the coordinates mean
something in some data field. If you shift the data field origin, (0,0)
will still mean ‘wherever (0,0) is in this field now’.
> This puzzles me. Somehow my (x,y) offsets are not corrected after
> having them postprocessed. I apply it right after gwy_data_field_2dfft
> as you do in prof_psdf.
Which offsets? For data field offsets, try printing
gwy_data_field_get_xoffset(dfield)
and
gwy_data_field_get_xoffset(dfield) + gwy_data_field_get_xreal(dfield)
They should be approximately the same with opposite signs (it depends on
the pixel size parity).
For selections, they will contain the coordinates you stored to them.
Regards,
Yeti
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Gwyddion-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gwyddion-users
