Memory-mapped files with np.memmap in NumPy - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a memory-mapped file named 'data.dat' with shape (100,) and dtype float32.

NumPy

import numpy as np
mmap_array = np.memmap('data.dat', dtype=[1], mode='w+', shape=(100,))

Drag options to blanks, or click blank then click option'

A'int64'

B'float32'

C'bool'

D'complex128'

Attempts:

3 left

💡 Hint

Common Mistakes

Using an integer dtype instead of float32.

Forgetting to specify the dtype parameter.

The dtype float32 matches the requirement for the memory-mapped file.

2fill in blank

medium

Complete the code to open an existing memory-mapped file 'data.dat' in read-only mode.

NumPy

mmap_read = np.memmap('data.dat', dtype='float32', mode=[1], shape=(100,))

Drag options to blanks, or click blank then click option'

A'r'

B'w+'

C'c'

D'w'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'w+' which allows writing and truncates the file.

Using 'c' which allows copy-on-write but not pure read-only.

The mode 'r' opens the file in read-only mode without allowing changes.

3fill in blank

hard

Fix the error in the code to correctly create a memory-mapped file with shape (50, 2).

NumPy

mmap_array = np.memmap('data2.dat', dtype='float64', mode='w+', shape=[1])

Drag options to blanks, or click blank then click option'

A50, 2

B[50, 2]

C(50, 2)

D50

Attempts:

3 left

💡 Hint

Common Mistakes

Using a list instead of a tuple for shape.

Passing multiple arguments instead of a single tuple.

The shape must be a tuple, so (50, 2) is correct.

4fill in blank

hard

Fill both blanks to create a memory-mapped file 'data3.dat' with dtype int32 and shape (10, 10).

NumPy

mmap_file = np.memmap('data3.dat', dtype=[1], mode='w+', shape=[2])

Drag options to blanks, or click blank then click option'

A'int32'

B'float64'

C(10, 10)

D[10, 10]

Attempts:

3 left

💡 Hint

Common Mistakes

Using float64 instead of int32 for dtype.

Using a list instead of a tuple for shape.

The dtype should be int32 and the shape a tuple (10, 10).

5fill in blank

hard

Fill all three blanks to open an existing memory-mapped file 'data4.dat' with dtype float64, shape (5, 5), in copy-on-write mode.

NumPy

mmap_copy = np.memmap('data4.dat', dtype=[1], mode=[2], shape=[3])

Drag options to blanks, or click blank then click option'

A'float32'

B'c'

C(5, 5)

D'float64'

Attempts:

3 left

💡 Hint

Common Mistakes

Using float32 instead of float64 for dtype.

Using 'w+' or 'r' instead of 'c' for mode.

Using a list instead of a tuple for shape.

The dtype is float64, mode is 'c' for copy-on-write, and shape is (5, 5).

Practice

1. What is the main benefit of using np.memmap in data science?

easy

A. It allows working with large arrays stored on disk without loading all data into memory.

B. It automatically speeds up all calculations by using GPU acceleration.

C. It compresses data files to save disk space.

D. It converts arrays into Python lists for easier manipulation.

Solution

1. Step 1: Understand what np.memmap does

   np.memmap creates an array-like object that accesses data stored on disk instead of loading it fully into memory.

2. Step 2: Identify the main advantage

   This allows handling very large datasets without using large amounts of RAM, which is the main benefit.

3. Final Answer:

   It allows working with large arrays stored on disk without loading all data into memory. -> Option A

4. Quick Check:

   Memory-mapped files save RAM by accessing disk data [OK]

Hint: Remember: memmap works with disk data like memory arrays [OK]

Common Mistakes:

• Thinking memmap compresses data
• Assuming memmap loads all data into RAM
• Confusing memmap with GPU acceleration

2. Which of the following is the correct way to create a new memory-mapped file with np.memmap of shape (100, 100) and dtype float32?

easy

A. np.memmap('data.dat', dtype='float64', mode='w+', shape=(100, 100))

B. np.memmap('data.dat', dtype='float32', mode='r', shape=(100, 100))

C. np.memmap('data.dat', dtype='float32', mode='rw', shape=(100, 100))

D. np.memmap('data.dat', dtype='float32', mode='w+', shape=(100, 100))

Solution

1. Step 1: Check the mode for creating a new file

   Mode 'w+' creates a new file or overwrites existing one for reading and writing.

2. Step 2: Verify dtype and shape parameters

   The dtype should be 'float32' and shape (100, 100) as given.

3. Final Answer:

   np.memmap('data.dat', dtype='float32', mode='w+', shape=(100, 100)) -> Option D

4. Quick Check:

   Use mode='w+' to create new memmap files [OK]

Hint: Use mode='w+' to create or overwrite memmap files [OK]

Common Mistakes:

• Using mode='r' when creating a new file
• Using incorrect dtype like float64 instead of float32
• Using invalid mode 'rw' which does not exist

3. What will be the output of this code snippet?

import numpy as np
filename = 'test.dat'
# Create memmap file
fp = np.memmap(filename, dtype='int32', mode='w+', shape=(3,3))
fp[:] = np.arange(9).reshape(3,3)
fp.flush()
# Open memmap file in read mode
fp2 = np.memmap(filename, dtype='int32', mode='r', shape=(3,3))
print(fp2[1,2])

medium

A. 6

B. 5

C. 7

D. 8

Solution

1. Step 1: Understand the array content

   np.arange(9).reshape(3,3) creates a 3x3 array: [[0,1,2],[3,4,5],[6,7,8]]

2. Step 2: Identify the value at position [1,2]

   Row 1, column 2 is the third element in second row, which is 5.

3. Final Answer:

   5 -> Option B

4. Quick Check:

   Index [1,2] in arange(9).reshape(3,3) = 5 [OK]

Hint: Remember zero-based indexing for rows and columns [OK]

Common Mistakes:

• Confusing row and column indices
• Forgetting zero-based indexing
• Assuming flush() changes data values

4. Identify the error in this code snippet that tries to open a memmap file:

import numpy as np
filename = 'data.dat'
# Attempt to open memmap file
fp = np.memmap(filename, dtype='float64', mode='r+', shape=(10,10))
print(fp[0,0])

medium

A. File 'data.dat' does not exist, so mode 'r+' causes an error.

B. dtype 'float64' is not supported by np.memmap.

C. Shape parameter must be omitted when opening existing memmap files.

D. Mode 'r+' is read-only and cannot write to file.

Solution

1. Step 1: Understand mode 'r+'

   Mode 'r+' opens an existing file for reading and writing. If file does not exist, it raises an error.

2. Step 2: Check file existence

   If 'data.dat' does not exist, this code will raise a FileNotFoundError.

3. Final Answer:

   File 'data.dat' does not exist, so mode 'r+' causes an error. -> Option A

4. Quick Check:

   Mode 'r+' requires existing file [OK]

Hint: Use mode='w+' to create files, 'r+' needs existing file [OK]

Common Mistakes:

• Assuming 'r+' creates new files
• Thinking dtype 'float64' is invalid
• Believing shape must be omitted always

5. You have a very large dataset stored in a binary file 'large_data.dat' with shape (10000, 10000) and dtype float64. You want to compute the mean of the first column without loading the entire file into memory. Which approach using np.memmap is best?

hard

A. Open the file with mode='w+' and overwrite data before computing mean.

B. Load the entire file into a numpy array and then compute the mean of the first column.

C. Open the file with mode='r' and read only the first column slice to compute the mean.

D. Use np.memmap with mode='c' and compute mean on the whole array.

Solution

1. Step 1: Understand memory constraints

   The dataset is very large (10000x10000), so loading all data into memory is inefficient.

2. Step 2: Use memmap to read only needed data

   Opening with mode='r' allows read-only access. Slicing the first column reads only that part from disk, saving memory.

3. Step 3: Avoid unnecessary writes or full reads

   Mode 'w+' overwrites data, which is not desired. Mode 'c' is copy-on-write and still loads data. Loading full array wastes memory.

4. Final Answer:

   Open the file with mode='r' and read only the first column slice to compute the mean. -> Option C

5. Quick Check:

   Read-only memmap + slice = efficient mean calculation [OK]

Hint: Read only needed slices with mode='r' to save memory [OK]

Common Mistakes:

• Loading entire large file into memory
• Using mode='w+' which overwrites data
• Not slicing and reading whole array unnecessarily