@@ -74,7 +74,6 @@ class FileBasedImage:
74
74
75
75
properties:
76
76
77
- * shape
78
77
* header
79
78
80
79
methods:
@@ -118,25 +117,6 @@ class FileBasedImage:
118
117
119
118
img.to_file_map()
120
119
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
-
140
120
**Files interface**
141
121
142
122
The image has an attribute ``file_map``. This is a mapping, that has keys
@@ -158,7 +138,7 @@ class FileBasedImage:
158
138
contain enough information so that an existing image instance can save
159
139
itself back to the files pointed to in ``file_map``. When a file holder
160
140
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
162
142
carry the position at which a write (with ``to_file_map``) should place the
163
143
data. The ``file_map`` contents should therefore be such, that this will
164
144
work.
0 commit comments