Ok, I got it work. I do not know why, but compiling against gwyddion stable [0] works fine but for the nightly snaptshot it doesn't. Moving to array position [1] works flawless with the desired image output. This is something I +do not understand yet. Maybe we should forget about this. I guess this is a strongly to my code related issue.
But this leads to problem #2. I am applying the gwy_data_field_fft_postprocess(data_field_fft_r,TRUE) ; to my fft data obtained via: gwy_data_field_2dfft(data_field,NULL,data_field_fft_r,data_field_fft_i,GWY_WINDOWING_NONE,GWY_TRANSFORM_DIRECTION_FORWARD,GWY_INTERPOLATION_ROUND,TRUE,1) ; results in the same data display, but with way larger x and y values. (0,0) is something like [2,57677e+09,2,56559e+09] (1/m I guess) and an example fft peak [1,7607e+09,2,57677e+09] which is in the gwyddion fft-module (-0.82/nm,0)...However,correcting the coorcdinates with the zero position it fits quit well. But the corrected fft-output is not centered at (0,0). Shouldn't this be done by the fft_postprocess() ? On 0, Mathias Müller <[email protected]> wrote: > Uff, ok t here is a bunch of documentation left to read. > > However, here is the line: > > g_object_set_data(G_OBJECT(args.detect.selection[0]), "vector-layer", > vector_layer[0]); > > > where: > > args.detect.selection is : GwySelection *selection[2]; > vector_layer[0] is : GwyVectorLayer *vector_layer[3]; > > This line works fine in gwyddion-stable. > > I let the plugin run with G_DEBUG=fatal-criticals environment, but the core > dump doesn't get more information. > > > On 0, "David Nečas (Yeti)" <[email protected]> wrote: > > On Mon, Sep 15, 2014 at 11:06:44AM +0200, Mathias Müller wrote: > > > ok, here we go: I recompiled the snapshot with > > > G_DEBUG=fatal-criticals....but still the symbols are missing somehow. > > > > This is a run-time environment variable to make it dump core on critical > > errors. It makes no difference on compilation. > > > > https://developer.gnome.org/glib/stable/glib-running.html#G-DEBUG:CAPS > > > > > #2 0x00007f247e22e186 in test_plugin (current_data=0x0, > > > run=GWY_RUN_NONE) at fft_plugin.c:222 > > > > Well, here's where it fails. So look at line 222 in your module. > > > > Compiling Gwyddion or the module with -Og -ggdb can help to make sense > > of the backtrace but does not seem necessary right now. > > > > 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
