@@ -74,7 +74,6 @@ class FileBasedImage:
7474
7575 properties:
7676
77- * shape
7877 * header
7978
8079 methods:
@@ -118,25 +117,6 @@ class FileBasedImage:
118117
119118 img.to_file_map()
120119
121- You can get the data out again with::
122-
123- img.get_fdata()
124-
125- Less commonly, for some image types that support it, you might want to
126- fetch out the unscaled array via the object containing the data::
127-
128- unscaled_data = img.dataoobj.get_unscaled()
129-
130- Analyze-type images (including nifti) support this, but others may not
131- (MINC, for example).
132-
133- Sometimes you might to avoid any loss of precision by making the
134- data type the same as the input::
135-
136- hdr = img.header
137- hdr.set_data_dtype(data.dtype)
138- img.to_filename(fname)
139-
140120 **Files interface**
141121
142122 The image has an attribute ``file_map``. This is a mapping, that has keys
@@ -158,7 +138,7 @@ class FileBasedImage:
158138 contain enough information so that an existing image instance can save
159139 itself back to the files pointed to in ``file_map``. When a file holder
160140 holds active file-like objects, then these may be affected by the
161- initial file read; in this case, the contains file-like objects need to
141+ initial file read; in this case, the file-like objects need to
162142 carry the position at which a write (with ``to_file_map``) should place the
163143 data. The ``file_map`` contents should therefore be such, that this will
164144 work.
0 commit comments