np.piecewise(x, [cond1, cond2], [func1, func2]) applies different functions per interval
All three operate element-wise and return same-shape arrays as the input
Performance: np.where ~3-5× faster than list comprehension for 1M elements
Gotcha: np.where with single argument returns tuple of index arrays, not a mask
Array operations often need conditional logic—clip outliers, assign grades, replace missing values. Most tutorials stop after showing np.where with a single condition. But production code frequently has multiple conditions, overlapping ranges, or per-interval functions. That's where np.select and np.piecewise earn their place. This article covers all three, the failure modes each solves, and the one rule that prevents most debugging pain: match the function to the shape of your decision logic.
np.where — Single Condition, Two Outcomes
np.where(condition, x, y) is the vectorised ternary operator for arrays. It evaluates condition element-wise, returns x[i] where condition[i] is True, y[i] otherwise. The single-argument form np.where(condition) returns a tuple of index arrays where condition is True, equivalent to np.nonzero(condition).
Common use cases: clipping values, replacing NaNs, assigning binary labels. The output dtype is inferred from x and y—if one is integer and the other float, the result is float.
One subtlety: when x and y are scalars, they're broadcast to match the condition shape. But if they are arrays, they must be broadcastable—mismatched shapes silently produce garbage or error.
where_examples.pyPYTHON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
import numpy as np
# Binary classification based on threshold
scores = np.array([55, 72, 88, 45, 91, 60])
grade = np.where(scores >= 70, 'pass', 'fail')
print(grade) # ['fail' 'pass' 'pass' 'fail' 'pass' 'fail']# Clip negative values to 0.0
data = np.array([-2.0, 3.0, -1.0, 5.0])
positive_only = np.where(data > 0, data, 0.0)
print(positive_only) # [0. 3. 0. 5.]# Single-argument form: find indices where condition is True
indices = np.where(scores < 60)
print(indices) # (array([0, 3]),)# Use indices to modify original array (in-place filtering)
scores[indices] = 0print(scores) # [0 72 88 0 91 60]
Output
['fail' 'pass' 'pass' 'fail' 'pass' 'fail']
[0. 3. 0. 5.]
(array([0, 3]),)
[0 72 88 0 91 60]
Quick check: single vs multi-arg
If you pass only one argument, np.where returns indices. If you pass three arguments, it returns values. Mixing them up is the #1 mistake.
Production Insight
Using np.where to replace large array values creates intermediate boolean and value arrays.
For arrays > 1GB, memory usage triples briefly—watch for OOM in memory-constrained environments.
Prefer in-place indexing (arr[cond] = new_value) when modifying a minority of elements to avoid extra allocation.
Key Takeaway
np.where is a direct replacement for if-else on arrays.
For more than two branches, reach for np.select.
Memory footprint doubles; watch for OOM on large data.
When to use np.where
IfExactly two outcomes (x vs y)
→
UseUse np.where(condition, x, y)
IfNeed only indices of True elements
→
UseUse np.where(condition) or np.nonzero(condition)
IfMore than two mutually exclusive outcomes
→
UseUse np.select—nested np.where becomes unreadable and slower
np.select — Multiple Exclusive Conditions
np.select evaluates a list of conditions in order and returns the corresponding choice for the first True condition encountered per element. If no condition is True, the default value is returned.
Key properties
Conditions are evaluated in order—the first True wins (like if-elif chain)
All condition arrays must be boolean, all choice arrays must have the same shape (or be scalars)
default can be any scalar or array—subject to broadcasting rules
The function is fully vectorised: conditions are evaluated together, but the first-match logic is applied per element
Real-world uses: categorising continuous values (temperature → description), mapping error codes to severity levels, applying business rules to transaction amounts.
select_examples.pyPYTHON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
import numpy as np
# Categorise temperature into four ranges
temp = np.array([-5.0, 8.0, 18.0, 26.0, 35.0])
conditions = [
temp < 0,
(temp >= 0) & (temp < 15),
(temp >= 15) & (temp < 28),
temp >= 28
]
choices = ['freezing', 'cold', 'comfortable', 'hot']
result = np.select(conditions, choices, default='unknown')
print(result)
# Output: ['freezing' 'cold' 'comfortable' 'comfortable' 'hot']# With overlapping conditions, first True wins
overlap_conditions = [temp < 10, temp < 20] # second condition is broader but comes later
overlap_choices = ['low', 'medium']
result2 = np.select(overlap_conditions, overlap_choices, default='high')
print(result2) # ['low' 'low' 'medium' 'high' 'high']
All conditions evaluate fully (vectorised), but only the first True per element is used
Performance is constant with respect to number of conditions (all evaluated once)
Production Insight
np.select does not short-circuit per element—it evaluates all conditions for all elements before picking winners.
This means memory and compute scale linearly with number of conditions.
For 10+ conditions, consider a dictionary-based lookup or np.piecewise for function-based ranges.
Watch for dtype mismatches between choices and default—they must be broadcastable to common dtype.
Key Takeaway
np.select replaces nested if-elif with a single vectorised call.
Order conditions from most to least specific.
All conditions are computed—memory scales with condition count.
np.select vs alternatives
If3–10 mutually exclusive conditions, values are scalars or arrays
→
UseUse np.select
IfConditions are continuous intervals with function per interval
→
UseUse np.piecewise
IfConditions are non-exclusive (multiple can be True, need all results)
→
UseUse np.where in a loop or boolean indexing per condition
np.piecewise — Function per Interval
np.piecewise applies different functions to different regions of an array. Unlike np.select which returns values directly, piecewise evaluates a callable for the elements that fall into each interval. This is useful when the outcome depends on a mathematical transformation specific to each range.
Signature: np.piecewise(x, condlist, funclist, args, *kw) - condlist: list of boolean arrays or scalars (conditions) - funclist: list of callables or values. If a value is not a callable, it's treated as a constant function returning that value. - If None is the last element of funclist, elements not matching any condition are set to the default (0 for numeric, False for bool, etc.).
The function is applied only to the subset of elements where the condition is True—this can reduce unnecessary computation.
Common use: piecewise linear transformations, clamping functions, adaptive masking.
piecewise_examples.pyPYTHON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
import numpy as np
# Soft clamp function: -1 below -1, identity between -1 and 1, 1 above 1
x = np.linspace(-3, 3, 7)
result = np.piecewise(
x,
[x < -1, (x >= -1) & (x <= 1), x > 1],
[lambda x: -1, lambda x: x, lambda x: 1]
)
print(x)
print(result) # [-3. -2. -1. 0. 1. 2. 3.] -> [-1. -1. -1. 0. 1. 1. 1.]# Using constant values (non-callable) in funclist# Assign 0 for negative, original for others
result2 = np.piecewise(x, [x < 0, x >= 0], [0, lambda x: x])
print(result2) # [0. 0. 0. 0. 1. 2. 3.]
Output
[-3. -2. -1. 0. 1. 2. 3.]
[-1. -1. -1. 0. 1. 1. 1.]
[0. 0. 0. 0. 1. 2. 3.]
piecewise function signature gotcha
Each callable in funclist receives only the elements that satisfy the corresponding condition, not the whole array. Write lambda x: x 2, not lambda: x 2. Failing to include x as parameter causes TypeError.
Production Insight
np.piecewise applies functions only to the elements that match the condition—no wasted computation.
But the overhead of calling lambdas per element for large arrays (~10M+) can outweigh the savings.
For pure arithmetic transformations (clamp, scale), prefer np.clip, np.where, or vectorised expressions.
Piecewise shines when the transformation is complex (e.g., log or sqrt on positive, linear on negative).
Key Takeaway
np.piecewise applies functions per interval, not just values.
Use it for piecewise-linear or piecewise-log transformations.
For simple clamping, prefer np.clip—it's faster and clearer.
np.piecewise vs np.where vs np.select
IfEach region needs a different mathematical function
→
UseUse np.piecewise
IfEach region maps to a constant or array value
→
UseUse np.select
IfOnly two outcomes (e.g., clip at zero)
→
UseUse np.where or np.clip
Performance Comparison: Vectorised vs Loop
The primary value of conditional array functions is that they are vectorised—they operate on the entire array at once using compiled C code. A Python loop over elements with if-else runs at Python speed, often 10–100× slower.
But not all vectorised functions are equal. np.where creates intermediate boolean arrays. np.select evaluates all conditions. np.piecewise calls Python callables per condition group, which adds overhead.
Benchmark on 10 million elements
np.where: ~50 ms
np.select (5 conditions): ~120 ms
np.piecewise (3 intervals): ~200 ms
List comprehension with if-elif-else: ~2.5 s
The gap widens with more conditions: np.select adds ~20 ms per condition; nested np.where adds ~40 ms per nesting level due to repeated allocations.
Memory-wise, np.select allocates one boolean array per condition plus the output array. For 10M float64 elements, that's 80 MB per boolean array (10M × 1 byte) — 5 conditions = 400 MB temporary memory. np.where with 3 args allocates two temporary arrays (condition mask and one value array).
benchmark.pyPYTHON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
import numpy as np
import time
n = 10_000_000
arr = np.random.uniform(-10, 10, n)
# np.where (single condition, two outcomes)
start = time.time()
result = np.where(arr > 0, arr, 0.0)
print(f"np.where: {time.time()-start:.3f}s")
# np.select
conditions = [arr < -5, (arr >= -5) & (arr < 0), (arr >= 0) & (arr < 5), arr >= 5]
choices = [-5, 0, arr, 5]
start = time.time()
result = np.select(conditions, choices, default=0.0)
print(f"np.select: {time.time()-start:.3f}s")
# List comprehension
start = time.time()
result = [ -5if v < -5else (0if v < 0else (v if v < 5else5)) for v in arr ]
print(f"Loop: {time.time()-start:.3f}s")
Output
np.where: 0.051s
np.select: 0.118s
Loop: 2.431s
Key takeaway
Vectorised functions are always faster than Python loops, but among vectorised options, pick the one that matches your logic structure—not just the one you're most familiar with.
Production Insight
Memory vs speed trade-off: np.select uses more memory but is predictable.
If memory is constrained (e.g., AWS Lambda 128 MB), consider splitting the array into chunks and applying logic per chunk.
Or use np.piecewise with constant values to avoid boolean array allocation.
Key Takeaway
Vectorised conditional functions are 10–100× faster than loops.
But memory scales with number of conditions—watch for exhaustion.
Benchmark with real-sized data before choosing.
Choosing the fastest vectorised method
IfTwo outcomes, simple condition
→
Usenp.where—fastest, lowest memory
IfMultiple outcomes, small number of conditions (≤10)
→
Usenp.select—balanced speed and readability
IfMultiple outcomes, many conditions (>10), or complex per-region functions
→
Usenp.piecewise—avoid boolean explosion at cost of callable overhead
IfCritical performance, need to minimise memory
→
UseApply logic per chunk with a simple loop (surprisingly fast due to NumPy's internal iteration)
Common Pitfalls and How to Avoid Them
Even experienced NumPy users trip on these:
Singular argument form: Calling np.where(cond) when you intended np.where(cond, x, y). The single-arg form returns a tuple of index arrays, not an array of values. Use it only when you explicitly need indices.
Dtype mismatches: np.where and np.select infer output dtype from x, y, or choices/default. Mixing strings and numbers may force object dtype, losing performance. Keep types consistent.
Overlapping conditions in np.select: The first True wins. If two conditions overlap unintentionally, you'll get unexpected results. Always check that conditions are mutually exclusive if that's the intent.
np.piecewise function signature: The lambda must accept the array slice, not the whole array. Write lambda x: x + 1, not lambda: x + 1.
Broadcasting errors: When x and y in np.where are arrays, they must broadcast to the shape of condition. Scalars are fine, but arrays may cause ValueError if shapes don't match.
Default handling in np.select: If default is not provided, it defaults to 0, which may not be meaningful. Always specify an explicit default.
pitfalls.pyPYTHON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
import numpy as np
# Pitfall 1: Single-arg instead of three-arg
arr = np.array([1, -2, 3])
# Wrong: indices = np.where(arr > 0) # returns (array([0, 2]),)# Correct:
positives = np.where(arr > 0, arr, 0)
print(positives) # [1 0 3]# Pitfall 2: Dtype mismatch forces object
scores = np.array([55, 72])
# Wrong: result = np.where(scores > 60, 'pass', 0) # object dtype, slow# Correct: use same type
result = np.where(scores > 60, 'pass', 'fail')
print(result) # ['fail' 'pass']# Pitfall 3: Overlapping conditions in np.select
temp = np.array([20])
# Overlap: condition[0] temp >= 10, condition[1] temp >= 18 — both True# Wrong order (narrower first is correct)
conds = [temp >= 10, temp >= 18] # first wins: both match, first is 10+
choices = ['mild', 'warm']
print(np.select(conds, choices)) # ['mild'] — never reaches 'warm'# Fix: put narrower condition first
conds_fixed = [temp >= 18, temp >= 10]
print(np.select(conds_fixed, choices)) # ['warm']
Output
[1 0 3]
['fail' 'pass']
['mild']
['warm']
The most common silent bug
Using np.select with overlapping conditions in the wrong order. The first True wins—if a broad condition comes before a narrow one, the narrow condition is effectively dead code. Always order from most specific to least specific.
Production Insight
Silent bugs from overlapping conditions are hard to catch because no error is raised.
Add a test that checks no element matches more than one condition when excluding default.
Use np.unique over condition indices to detect overlaps.
Key Takeaway
Order conditions from specific to general in np.select.
Always specify an explicit default in np.select.
Test edge cases (boundary values) explicitly.
Debugging logic when results look wrong
Ifnp.select returns only default values
→
UseCheck condition arrays: are they all False? Use np.any(conditions, axis=0)
Ifnp.where returns a tuple instead of array
→
UseYou used single argument; use three-argument form
Ifnp.piecewise returns all default
→
UseCheck that conditions cover the entire domain; add fallback funclist
● Production incidentPOST-MORTEMseverity: high
The 10× Slower Pipeline: Using np.where Where np.select Belongs
Symptom
Batch job processing temperature readings for factory equipment regularly timed out beyond the 30-minute SLA. Monitoring showed CPU 100% on a single core despite using NumPy.
Assumption
The team assumed np.where was always the fastest option for conditional logic. They used five nested np.where calls to classify temperatures into six categories.
Root cause
Chaining np.where calls forces Python to evaluate each condition sequentially for all elements, recomputing intermediate boolean arrays. np.select evaluates all conditions in a single vectorised pass, reducing overhead and memory allocation.
Fix
Replaced the nested np.where chain with a single np.select call using six condition arrays and six choice arrays. Runtime dropped from 40 minutes to 3.8 minutes.
Key lesson
For more than two outcomes, prefer np.select over nested np.where—it's both faster and more readable.
Profile early: a single vectorised function may still be slower than a better-chosen one.
Measure runtime on representative data before deploying—not just correctness on toy samples.
Production debug guideSymptom → Action mapping for np.where, np.select, and np.piecewise issues in production5 entries
Symptom · 01
Unexpected 'The truth value of an array is ambiguous' error
→
Fix
Check if you used Python's built-in if/elif on an array. Use np.where or np.select instead—they handle array conditions natively.
Symptom · 02
np.select returns default for all rows
→
Fix
Verify condition arrays are boolean dtype and that at least one condition is True per element. Use np.any(conditions, axis=0) to find elements where no condition matches.
Symptom · 03
np.piecewise returns all outputs from the default function
→
Fix
Check interval boundaries: piecewise uses inclusive/exclusive boundaries as defined in conditions. If a value falls exactly on a boundary, verify which condition it satisfies (typically exclusive left, inclusive right).
Symptom · 04
MemoryError on large arrays with np.where
→
Fix
np.where creates intermediate boolean arrays. For gigabyte-scale data, consider using np.nonzero + fancy indexing or out-of-core processing with dask.
Symptom · 05
np.where returns tuple instead of array
→
Fix
You used the single-argument form: np.where(cond) returns indices. To get a filtered array, use np.where(cond, x, y) or array[cond].
Feature comparison
Feature
np.where
np.select
np.piecewise
Number of outcomes
2
Unlimited
Unlimited
Outcome type
Value or array
Value or array
Function (callable) or value
Conditions evaluated
Single
All (first True wins)
All (first True wins)
Default fallback
Implicit (y)
Explicit default param
None or last function
Memory usage
Low (2 temp arrays)
High (1 boolean per condition)
Moderate (calls per match)
Speed (10M elements)
~50 ms
~120 ms (5 conds)
~200 ms (3 intervals)
Readability growth with conditions
Degrades (nested)
Good (list forms)
Good (list forms)
Key takeaways
1
np.where(condition, x, y) is a vectorised ternary operator
no loop needed.
2
np.select evaluates conditions in order
the first True condition wins.
3
np.piecewise is useful when different mathematical functions apply to different intervals.
4
np.where with a single argument returns a tuple of index arrays
equivalent to np.nonzero.
5
All three functions operate element-wise and return arrays of the same shape as the input.
6
For more than two outcomes, prefer np.select over nested np.where for both performance and readability.
7
np.piecewise is 10–50× faster than a Python loop but 2–4× slower than np.clip for simple operations.
Common mistakes to avoid
4 patterns
×
Using np.where with a single argument to get values
Symptom
You write filtered = np.where(condition) expecting an array of values, but get a tuple of index arrays. Downstream code that expects an array fails with TypeError or IndexError.
Fix
Use np.where(condition, x, y) for value selection, or array[condition] for boolean indexing. Only use the single-argument form when you explicitly need index positions.
×
Placing broad conditions before narrow ones in np.select
Symptom
The narrow condition never triggers because a broader condition earlier in the list matches first. Output appears correct at first glance but misses specific cases.
Fix
Order conditions from most specific (narrowest) to least specific (broadest). Test with known edge cases. Use overlapping conditions only if that's the intended behaviour.
×
Passing lambdas without the array parameter to np.piecewise
Symptom
Python raises TypeError: <lambda>() takes 0 positional arguments but 1 was given. The error occurs because piecewise passes the matching array slice to each function.
Fix
Always define lambda x: ... (or a named function with one parameter) even if you don't use the value. For constant values, pass the constant directly (not lambda).
×
Using np.piecewise when arithmetic is sufficient
Symptom
Code works but runs slower than necessary. For example, clipping values with np.piecewise is 4× slower than np.clip.
Fix
Prefer vectorised arithmetic (np.clip, np.where, np.maximum) for simple transformations. Reserve np.piecewise for cases where each interval needs a different mathematical function (log on positive, linear on negative).
INTERVIEW PREP · PRACTICE MODE
Interview Questions on This Topic
Q01JUNIOR
How would you replace all negative values in a NumPy array with zero wit...
Q02SENIOR
When would you use np.select instead of nested np.where calls?
Q03SENIOR
Explain the difference between np.where and np.piecewise when both can h...
Q01 of 03JUNIOR
How would you replace all negative values in a NumPy array with zero without a loop?
ANSWER
Use np.where(data > 0, data, 0). This returns a new array where positive values are kept and negatives become zero. If you need to keep the original shape, use np.clip(data, 0, np.inf) which is faster. For in-place modification, use data[data < 0] = 0.
Q02 of 03SENIOR
When would you use np.select instead of nested np.where calls?
ANSWER
When you have three or more mutually exclusive conditions. Nested np.where is hard to read and slower because it evaluates conditions multiple times. np.select takes a list of conditions and choices, evaluates all conditions once, and returns the choice for the first True condition per element. Example: classifying temperatures into 'freezing', 'cold', 'comfortable', 'hot'—a single np.select with four conditions is cleaner and faster than three nested np.where calls.
Q03 of 03SENIOR
Explain the difference between np.where and np.piecewise when both can handle multiple conditions.
ANSWER
np.where returns a fixed value per condition (or array) based on a single condition. For multiple conditions you nest them, which is messy. np.piecewise applies a function per condition—each condition gets its own callable that receives only the matching elements. Use np.where when each branch returns a constant or derived array; use np.piecewise when each branch involves a different mathematical transformation (e.g., log on one interval, square on another). Also, np.piecewise can avoid evaluating the function on all elements—it only applies the function to those that match, which can save compute for expensive operations.
01
How would you replace all negative values in a NumPy array with zero without a loop?
JUNIOR
02
When would you use np.select instead of nested np.where calls?
SENIOR
03
Explain the difference between np.where and np.piecewise when both can handle multiple conditions.
SENIOR
FAQ · 5 QUESTIONS
Frequently Asked Questions
01
What is the difference between np.where and np.select?
np.where handles a single condition with two outcomes (x if True, y if False). np.select handles multiple mutually exclusive conditions with a corresponding value for each, plus a default for when none match. For complex logic, np.select is cleaner than nesting multiple np.where calls.
Was this helpful?
02
Can np.where return strings?
Yes. The output dtype is inferred from x and y. If both are strings, the result is a string array. np.where(arr > 0, 'positive', 'non-positive') works as expected.
Was this helpful?
03
Does np.piecewise evaluate all functions for all elements?
No. Each function in funclist is called only with the array elements that satisfy the corresponding condition. This means expensive functions are only applied where needed. However, the conditions themselves are evaluated for all elements.
Was this helpful?
04
What happens if no condition matches in np.select?
The default value is returned for that element. If no default is provided, it defaults to 0 (or False for bool arrays). Always specify an explicit default to avoid silent bugs.
Was this helpful?
05
Can I use np.where to modify the original array in-place?
Not directly with the three-argument form—it returns a new array. For in-place modification, use boolean indexing: arr[condition] = new_value. This avoids allocating a new array.