File: tutorial.rst

package info (click to toggle)
pynfft 1.3.2-11
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,524 kB
  • sloc: python: 345; makefile: 134; sh: 8
file content (192 lines) | stat: -rw-r--r-- 7,054 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
Using the NFFT
==============

In this tutorial, we assume that you are already familiar with the `non-uniform
discrete Fourier transform
<http://en.wikipedia.org/wiki/Non-uniform_discrete_Fourier_transform>`_ and the
`NFFT library <http://www-user.tu-chemnitz.de/~potts/nfft/>`_ used for fast
computation of NDFTs. 

Like the `FFTW library <http://www.fftw.org/>`_, the NFFT library relies on a
specific data structure, called a plan, which stores all the data required for
efficient computation and re-use of the NDFT. Each plan is tailored for a
specific transform, depending on the geometry, level of precomputation and
design parameters. The `NFFT manual
<http://www-user.tu-chemnitz.de/~potts/nfft/guide3/html/index.html>`_ contains
comprehensive explanation on the NFFT implementation.

The pyNFFT package provides a set of Pythonic wrappers around the main data
structures of the NFFT library. Use of Python wrappers allows to simplify the
manipulation of the library, whilst benefiting from the significant speedup
provided by its C-implementation. Although the NFFT library supports many more
applications, only the NFFT and iterative solver components have been wrapped
so far. 

This tutorial is split into three main sections. In the first one, the general
workflow for using the core of the :class:`pynfft.NFFT` class will be
explained. Then, the :class:`pynfft.NFFT` class API will be detailed and
illustrated with examples for the univariate and multivariate cases. Finally,
the :class:`pynfft.Solver` iterative solver class will be briefly presented. 

.. _workflow:
 
Workflow
--------

For users already familiar with the NFFT C-library, the workflow is basically
the same. It consists in the following three steps:

    #. instantiation

    #. precomputation

    #. execution

In step 1, information such as the geometry of the transform or the desired
level of precomputation is provided to the constructor, which takes care of
allocating the internal arrays of the plan.

Precomputation (step 2) can be started once the location of the non-uniform
nodes have been set to the plan. Depending on the size of the transform and
level of precomputation, this step may take some time.

Finally (step 3), the forward or adjoint NFFT is computed by first setting the
input data in either `f_hat` (forward) or `f` (adjoint), calling the
corresponding function, and reading the output in `f` (forward) or `f_hat`
(adjoint).

.. _using_nfft:

Using the NFFT
--------------

The core of this library is encapsulated in the :class:`pyfftw.NFFT class`.

**instantiation**

The bare minimum to instantiate a new :class:`pynfft.NFFT` plan is to specify
the geometry to the transform, i.e. the shape of the matrix containing the
uniform data `N` and the number of non-uniform nodes `M`.

    >>> from pynfft.nfft import NFFT
    >>> plan = NFFT([16, 16], 92)
    >>> print plan.M
    96
    >>> print plan.N
    (16, 16)

More control over the precision, storage and speed of the NFFT can be gained by
overriding the default design parameters `m`, `n` and `flags`. For more
information, please consult the `NFFT manual
<http://www-user.tu-chemnitz.de/~potts/nfft/guide3/html/index.html>`_.

**precomputation**

Precomputation *must* be performed before calling any of the transforms. The
user can manually set the nodes of the NFFT object using the
:attr:`pynfft.nfft.NFFT.x` attribute before calling the
:meth:`pynfft.nfft.NFFT.precompute` method.

    >>> plan.x = x
    >>> plan.precompute()  

**execution**

The actual forward and adjoint NFFT are performed by calling the
:meth:`pynfft.nfft.NFFT.trafo` and :meth:`pynfft.nfft.NFFT.adjoint` methods.

    >>> # forward transform
    >>> plan.f_hat = f_hat
    >>> f = plan.trafo()
    >>> # adjoint transform
    >>> plan.f = f
    >>> f_hat = plan.adjoint()

.. _using_solver:

Using the iterative solver
--------------------------

**instantiation**

The instantiation of a :class:`pynfft.solver.Solver` object requires an
instance of :class:`pynfft.nfft.NFFT`. The following code shows you a simple
example:

    >>> from pynfft import NFFT, Solver
    >>> plan = NFFT(N, M)
    >>> infft = Solver(plan)

It is strongly recommended to use an already *precomputed*
:class:`pynfft.nfft.NFFT` object to instantiate a :class:`pynfft.solver.Solver`
object, or at the very least, make sure to call its precompute method before
using solver.

Since the solver will typically run several iterations before converging to a
stable solution, it is also strongly encourage to use the maximum level of
precomputation to speed-up each call to the NFFT.  Please check the paragraph
regarding the choice of precomputation flags for the :class:`pynfft.nfft.NFFT`. 

By default, the :class:`pynfft.solver.Solver` class uses the Conjugate Gradient
of the first kind method (CGNR flag). This may be overriden in the constructor:

    >>> infft = Solver(plan, flags='CGNE')

Convergence to a stable solution can be significantly speed-up using the right
pre-conditioning weights. These can accessed by the 
:attr:`pynfft.solver.Solver.w` and :attr:`pynfft.solver.Solver.w_hat`
attributes. By default, these weights are set to 1.

    >>> infft = Solver(plan)
    >>> infft.w = w

**using the solver**

Before iterating, the solver has to be intialized. As a reminder, make sure the
:class:`pynfft.nfft.NFFT` object used to instantiate the solver has been
*precomputed*. Otherwise, the solver will be in an undefined state and will not
behave properly.

Initialization of the solver is performed by first setting the non-uniform
samples :attr:`pynfft.solver.Solver.y`, an initial guess of the solution
:attr:`pynfft.solver.Solver.f_hat_iter` and then calling the
:meth:`pynfft.solver.Solver.before_loop` method.

    >>> infft.y = y
    >>> infft.f_hat_iter = f_hat_iter
    >>> infft.before_loop()

By default, the initial guess of the solution is set to 0.

After initialization of the solver, a single iteration can be performed by
calling the :meth:`pynfft.solver.Solver.loop_one_step` method. With each
iteration, the current solution is written in the
:attr:`pynfft.solver.Solver.f_hat_iter` attribute.

    >>> infft.loop_one_step()
    >>> print infft.f_hat_iter
    >>> infft.loop_one_step()
    >>> print infft.f_hat_iter

The :class:`pynfft.Solver` class only supports one iteration at a time.  It is
at the discretion to implement the desired stopping condition, based for
instance on a maximum iteration count or a threshold value on the residuals.
The residuals can be read in the :attr:`pynfft.solver.Solver.r_iter` attribute.
Below are two simple examples:

    - with a maximum number of iterations:

    >>> niter = 10  # set number of iterations to 10
    >>> for iiter in range(niter):
    >>>	    infft.loop_one_step()

    - with a threshold value:

    >>> threshold = 1e-3
    >>> try:
    >>>	    while True:
    >>>		infft.loop_one_step()
    >>>		if(np.all(infft.r_iter < threshold)):
    >>>		    raise StopCondition
    >>> except StopCondition:
    >>>	    # rest of the algorithm