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
|
:orphan:
Floating-point precision
========================
.. NOTE: part of this file is included in doc/manual/io.rst and
doc/overview/implementation.rst. Changes here are reflected there. If you
want to link to this content, link to :ref:`manual-precision` for the manual
or :ref:`precision` for the implementation page. The next line is a target
for :start-after: so we can omit the title above:
precision-begin-content
MNE-Python performs all computation in memory using the double-precision 64-bit
floating point format. This means that the data is typecast into float64 format
as soon as it is read into memory. The reason for this is that operations such
as filtering and preprocessing are more accurate when using the 64-bit format.
However, for backward compatibility, MNE-Python writes :file:`.fif` files in a
32-bit format by default. This reduces file size when saving data to disk, but
beware that *saving intermediate results to disk and re-loading them from disk
later may lead to loss in precision*. If you would like to ensure 64-bit
precision, there are two possibilities:
- Chain the operations in memory and avoid saving intermediate results.
- Save intermediate results but change the :class:`~numpy.dtype` used for
saving, by using the ``fmt`` parameter of :meth:`mne.io.Raw.save` (or
:meth:`mne.Epochs.save`, etc). However, note that this may render the
:file:`.fif` files unreadable in software packages other than MNE-Python.
|
