Fix ifelse support and update ModelingToolkit compat #54
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes issue #36 by addressing two related problems:
Added
ifelsehelper function for MATLABifelsefunction, butSymbolics.jlgenerates code usingifelse(cond, a, b)for theMATLABTarget()ifelse = @(cond, a, b) cond .* a + ~cond .* b;in MATLAB before evaluating the generated codeifelseexpressions (likeifelse(a > 0, -a, a)) to work correctlyUpdated ModelingToolkit compat to support versions 8, 9, 10, 11
TypeError: non-boolean (Num) used in boolean contextwas fixed in newer ModelingToolkit/Symbolics versionsstates->unknownsAPI rename (v9+)Background
The original issue used this MWE:
Which failed with
TypeError: non-boolean (Num) used in boolean context.Test plan
cc @ChrisRackauckas
🤖 Generated with Claude Code