Indexing with ellipsis in NumPy - Time & Space Complexity
We want to understand how fast numpy runs when we use ellipsis for indexing.
Specifically, how does the time change when we select parts of big arrays with ellipsis?
Analyze the time complexity of the following code snippet.
import numpy as np
arr = np.random.rand(1000, 1000, 10)
result = arr[..., 5]
This code selects the 6th element from the last dimension of a 3D array using ellipsis.
Look for loops or repeated steps inside the operation.
- Primary operation: Constructing a strided view by adjusting strides, shape, and base pointer.
- How many times: Constant time, O(1), independent of array size.
When the array size grows, the execution time remains constant.
| Input Size (n x n x 10) | Approx. Operations |
|---|---|
| 10 x 10 x 10 | O(1) |
| 100 x 100 x 10 | O(1) |
| 1000 x 1000 x 10 | O(1) |
Pattern observation: The operations are constant regardless of array dimensions, as NumPy slicing creates a view without copying data.
Time Complexity: O(1)
This means the time is constant and independent of the number of elements in the array dimensions, because it creates a lightweight view.
[X] Wrong: "Using ellipsis takes O(n^2) time proportional to the output size."
[OK] Correct: Ellipsis expands to basic slicing (:, :, 5), which NumPy implements in constant time via views, without accessing or copying elements.
Understanding how indexing affects performance helps you write efficient data code and explain your choices clearly.
What if we changed the code to select a slice like arr[..., 2:7]? How would the time complexity change?
Practice
...) represent when indexing a NumPy array?Solution
Step 1: Understand ellipsis usage
The ellipsis (...) is used to replace multiple colons when slicing multi-dimensional arrays.Step 2: Interpret ellipsis effect
It selects all remaining dimensions not explicitly indexed, making code shorter and clearer.Final Answer:
It selects all remaining dimensions in the array. -> Option AQuick Check:
Ellipsis = all remaining dimensions [OK]
- Thinking ellipsis selects only one dimension
- Confusing ellipsis with new axis insertion
- Assuming ellipsis selects last element only
arr using ellipsis?Solution
Step 1: Understand the array shape and slicing
For a 3D array,arr[..., :-1]means select all elements in the first two dimensions and slice the last dimension up to but not including the last element.Step 2: Compare options
arr[..., :-1]uses ellipsis to cover first two dimensions and slices last dimension correctly.arr[:, :, -1]incorrectly selects only the last element in the last dimension.arr[..., -1]selects only the last slice, and D slices the second dimension incorrectly.Final Answer:
arr[..., :-1] -> Option BQuick Check:
Ellipsis + slice last dim = arr[..., :-1] [OK]
- Using ellipsis but slicing wrong dimension
- Confusing negative index with slice
- Not using ellipsis and writing long slices
import numpy as np arr = np.arange(24).reshape(2,3,4) result = arr[1, ..., 2]
What is the value of
result?Solution
Step 1: Understand array shape and indexing
The arrayarrhas shape (2, 3, 4). Indexingarr[1, ..., 2]means select the second block (index 1) in the first dimension, all elements in the second dimension, and the element at index 2 in the last dimension.Step 2: Extract values
Forarr[1], the 3x4 block is:
[ [12,13,14,15],
[16,17,18,19],
[20,21,22,23] ]
Selecting all rows and column 2 gives [14, 18, 22]. But since the last dimension index is 2, it picks the third element in each row.
So the result is [14, 18, 22].Final Answer:
[14 18 22] -> Option DQuick Check:
arr[1, :, 2] = [14 18 22] [OK]
- Confusing dimension order
- Mixing up index 1 and 2
- Assuming ellipsis selects only one dimension
import numpy as np arr = np.arange(27).reshape(3,3,3) print(arr[..., 1:])
It raises an error. What is the most likely cause?
Solution
Step 1: Analyze ellipsis with slice
Ellipsis (...) can be combined with slices to select parts of the array. Here,arr[..., 1:]means select all elements in the first two dimensions and slice from index 1 to end in the last dimension.Step 2: Check array shape compatibility
The array shape is (3,3,3), so slicing last dimension from 1 to end is valid (indexes 1 and 2). No error should occur.Final Answer:
The code is correct and will not raise an error. -> Option AQuick Check:
Ellipsis + slice = valid syntax [OK]
- Assuming ellipsis can't be combined with slices
- Thinking slice 1: is out of bounds
- Believing ellipsis changes array shape
data with shape (5, 4, 3, 2). You want to select the last element in the second dimension, all elements in the third dimension, and the first element in the last dimension, for all elements in the first dimension. Which indexing expression using ellipsis is correct?Solution
Step 1: Understand the array shape and desired selection
The array shape is (5, 4, 3, 2). We want:
- all elements in first dimension (5)
- last element in second dimension (index -1)
- all elements in third dimension (3)
- first element in last dimension (index 0)Step 2: Use ellipsis to simplify indexing
Usingdata[:, -1, ..., 0]means:
- select all in first dim
- select last in second dim
- ellipsis covers remaining dims (third and last)
- then select 0 in last dim
But ellipsis here covers dims 3 and 4, so0applies to last dim.data[:, -1, ..., 0]matches this logic correctly.Step 3: Check other options
data[:, -1, :, 0]is correct but does not use ellipsis.data[:, ..., :, 0]uses ellipsis but selects all elements in the second dimension (instead of the last one).data[:, -1, :, 0, ...]has too many indices (5) for 4D array.Final Answer:
data[:, -1, ..., 0] -> Option CQuick Check:
Ellipsis fills middle dims; index last dim after ellipsis [OK]
- Using too many indices for array dimensions
- Misplacing ellipsis causing wrong dimension selection
- Not understanding which dims ellipsis covers
Ready to prove it?
Pass the test and this pattern moves unknown
