File: //proc/self/root/opt/alt/python27/lib64/python2.7/site-packages/numpy/core/memmap.pyo
�
� 9Zc @` s� d d l m Z m Z m Z d d l Z d d l m Z m Z m Z d d l
m Z m Z d g Z
e Z d d d d
g Z d d
g Z i d d 6d d 6d d
6d
d 6Z d e f d � � YZ d S( i ( t divisiont absolute_importt print_functionNi ( t uint8t ndarrayt dtype( t longt
basestringt memmapt rt cs r+s w+t readonlyt copyonwritet readwritet writec B` s> e Z d Z d Z e d d d d d � Z d � Z d � Z RS( s� Create a memory-map to an array stored in a *binary* file on disk.
Memory-mapped files are used for accessing small segments of large files
on disk, without reading the entire file into memory. Numpy's
memmap's are array-like objects. This differs from Python's ``mmap``
module, which uses file-like objects.
This subclass of ndarray has some unpleasant interactions with
some operations, because it doesn't quite fit properly as a subclass.
An alternative to using this subclass is to create the ``mmap``
object yourself, then create an ndarray with ndarray.__new__ directly,
passing the object created in its 'buffer=' parameter.
This class may at some point be turned into a factory function
which returns a view into an mmap buffer.
Delete the memmap instance to close.
Parameters
----------
filename : str or file-like object
The file name or file object to be used as the array data buffer.
dtype : data-type, optional
The data-type used to interpret the file contents.
Default is `uint8`.
mode : {'r+', 'r', 'w+', 'c'}, optional
The file is opened in this mode:
+------+-------------------------------------------------------------+
| 'r' | Open existing file for reading only. |
+------+-------------------------------------------------------------+
| 'r+' | Open existing file for reading and writing. |
+------+-------------------------------------------------------------+
| 'w+' | Create or overwrite existing file for reading and writing. |
+------+-------------------------------------------------------------+
| 'c' | Copy-on-write: assignments affect data in memory, but |
| | changes are not saved to disk. The file on disk is |
| | read-only. |
+------+-------------------------------------------------------------+
Default is 'r+'.
offset : int, optional
In the file, array data starts at this offset. Since `offset` is
measured in bytes, it should normally be a multiple of the byte-size
of `dtype`. When ``mode != 'r'``, even positive offsets beyond end of
file are valid; The file will be extended to accommodate the
additional data. By default, ``memmap`` will start at the beginning of
the file, even if ``filename`` is a file pointer ``fp`` and
``fp.tell() != 0``.
shape : tuple, optional
The desired shape of the array. If ``mode == 'r'`` and the number
of remaining bytes after `offset` is not a multiple of the byte-size
of `dtype`, you must specify `shape`. By default, the returned array
will be 1-D with the number of elements determined by file size
and data-type.
order : {'C', 'F'}, optional
Specify the order of the ndarray memory layout:
:term:`row-major`, C-style or :term:`column-major`,
Fortran-style. This only has an effect if the shape is
greater than 1-D. The default order is 'C'.
Attributes
----------
filename : str
Path to the mapped file.
offset : int
Offset position in the file.
mode : str
File mode.
Methods
-------
flush
Flush any changes in memory to file on disk.
When you delete a memmap object, flush is called first to write
changes to disk before removing the object.
Notes
-----
The memmap object can be used anywhere an ndarray is accepted.
Given a memmap ``fp``, ``isinstance(fp, numpy.ndarray)`` returns
``True``.
Memory-mapped arrays use the Python memory-map object which
(prior to Python 2.5) does not allow files to be larger than a
certain size depending on the platform. This size is always < 2GB
even on 64-bit systems.
When a memmap causes a file to be created or extended beyond its
current size in the filesystem, the contents of the new part are
unspecified. On systems with POSIX filesystem semantics, the extended
part will be filled with zero bytes.
Examples
--------
>>> data = np.arange(12, dtype='float32')
>>> data.resize((3,4))
This example uses a temporary file so that doctest doesn't write
files to your directory. You would use a 'normal' filename.
>>> from tempfile import mkdtemp
>>> import os.path as path
>>> filename = path.join(mkdtemp(), 'newfile.dat')
Create a memmap with dtype and shape that matches our data:
>>> fp = np.memmap(filename, dtype='float32', mode='w+', shape=(3,4))
>>> fp
memmap([[ 0., 0., 0., 0.],
[ 0., 0., 0., 0.],
[ 0., 0., 0., 0.]], dtype=float32)
Write data to memmap array:
>>> fp[:] = data[:]
>>> fp
memmap([[ 0., 1., 2., 3.],
[ 4., 5., 6., 7.],
[ 8., 9., 10., 11.]], dtype=float32)
>>> fp.filename == path.abspath(filename)
True
Deletion flushes memory changes to disk before removing the object:
>>> del fp
Load the memmap and verify data was stored:
>>> newfp = np.memmap(filename, dtype='float32', mode='r', shape=(3,4))
>>> newfp
memmap([[ 0., 1., 2., 3.],
[ 4., 5., 6., 7.],
[ 8., 9., 10., 11.]], dtype=float32)
Read-only memmap:
>>> fpr = np.memmap(filename, dtype='float32', mode='r', shape=(3,4))
>>> fpr.flags.writeable
False
Copy-on-write memmap:
>>> fpc = np.memmap(filename, dtype='float32', mode='c', shape=(3,4))
>>> fpc.flags.writeable
True
It's possible to assign to copy-on-write array, but values are only
written into the memory copy of the array, and not written to disk:
>>> fpc
memmap([[ 0., 1., 2., 3.],
[ 4., 5., 6., 7.],
[ 8., 9., 10., 11.]], dtype=float32)
>>> fpc[0,:] = 0
>>> fpc
memmap([[ 0., 0., 0., 0.],
[ 4., 5., 6., 7.],
[ 8., 9., 10., 11.]], dtype=float32)
File on disk is unchanged:
>>> fpr
memmap([[ 0., 1., 2., 3.],
[ 4., 5., 6., 7.],
[ 8., 9., 10., 11.]], dtype=float32)
Offset into a memmap:
>>> fpo = np.memmap(filename, dtype='float32', mode='r', offset=16)
>>> fpo
memmap([ 4., 5., 6., 7., 8., 9., 10., 11.], dtype=float32)
g Y�s r+i t Cc C` sQ d d l } d d l } y t | } Wn@ t k
rh | t k ri t d t t t j � � � � qi n Xt | d � r� | } t }
n+ t
| | d k r� d p� | d � } t }
| d k r� | d k r� t d � � n | j
d d � | j � } t | � } | j }
| d k rY| | } | |
rC| j � t d
� � n | |
} | f } n< t | t � st| f } n d } x | D] } | | 9} q�Wt | | |
� } | d k s�| d k r| | k r| j
| d d � | j t j j d
� � | j � n | d k r | j } n! | d k r7| j } n | j } | | | j } | | 8} | | 8} | j | j � | d | d | �} t j | | d | d | d | d | �} | | _! | | _" | | _# t | t$ � r�| j% j& | � | _' nE t | d � r1t | j( t$ � r1| j% j& | j( � | _' n d | _' |
rM| j � n | S( Ni s mode must be one of %st readR
R t bs w+s shape must be giveni s? Size of available data is not a multiple of the data-type size.i s r+s t accesst offsetR t buffert ordert name() t mmapt os.patht mode_equivalentst KeyErrort valid_filemodest
ValueErrort listt keyst hasattrt Falset opent Truet Nonet seekt tellt
dtypedescrt itemsizet closet
isinstancet tupleR R t npt compatt asbytest flusht ACCESS_COPYt ACCESS_READt ACCESS_WRITEt ALLOCATIONGRANULARITYt filenoR t __new__t _mmapR t modeR t patht abspatht filenameR ( t subtypeR9 R R6 R t shapeR R t ost fidt own_filet flent descrt _dbytest bytest sizet kt acct startt mmt self( ( sD /opt/alt/python27/lib64/python2.7/site-packages/numpy/core/memmap.pyR4 � sv
! %
$
$
c C` s| t | d � rT t j | | � rT | j | _ | j | _ | j | _ | j | _ n$ d | _ d | _ d | _ d | _ d S( NR5 ( R R+ t may_share_memoryR5 R9 R R6 R# ( RH t obj( ( sD /opt/alt/python27/lib64/python2.7/site-packages/numpy/core/memmap.pyt __array_finalize__ s ! c C` s5 | j d k r1 t | j d � r1 | j j � n d S( s�
Write any changes in the array to the file on disk.
For further information, see `memmap`.
Parameters
----------
None
See Also
--------
memmap
R. N( t baseR# R R. ( RH ( ( sD /opt/alt/python27/lib64/python2.7/site-packages/numpy/core/memmap.pyR. ' s !N( t __name__t
__module__t __doc__t __array_priority__R R# R4 RK R. ( ( ( sD /opt/alt/python27/lib64/python2.7/site-packages/numpy/core/memmap.pyR s � Q ( t
__future__R R R t numpyR+ t numericR R R t numpy.compatR R t __all__R& R t writeable_filemodesR R ( ( ( sD /opt/alt/python27/lib64/python2.7/site-packages/numpy/core/memmap.pyt <module> s