Skip to content

fix: Include semi-continuous in Variable.type property#635

Merged
FabianHofmann merged 1 commit into
masterfrom
fix/variable-type-semi-continuous
Mar 26, 2026
Merged

fix: Include semi-continuous in Variable.type property#635
FabianHofmann merged 1 commit into
masterfrom
fix/variable-type-semi-continuous

Conversation

@FBumann
Copy link
Copy Markdown
Collaborator

@FBumann FBumann commented Mar 25, 2026

follow up on #593

Summary

  • Variable.type only checked integer and binary attributes, so semi-continuous variables incorrectly returned "Continuous Variable"
  • Added the missing semi_continuous check
  • Added test_variable_type covering all four variable types

No Changelog entry needed if included in the release that adds semi continuous variables

Test plan

  • New test test_variable_type verifies all four types: continuous, binary, integer, semi-continuous

🤖 Generated with Claude Code

Variable.type only checked integer and binary attributes, falling
through to "Continuous Variable" for semi-continuous variables.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@FBumann FBumann requested a review from FabianHofmann March 25, 2026 21:12
@FabianHofmann FabianHofmann merged commit 1bc3efc into master Mar 26, 2026
22 checks passed
@FabianHofmann FabianHofmann deleted the fix/variable-type-semi-continuous branch March 26, 2026 08:19
FBumann added a commit that referenced this pull request May 7, 2026
* docs: restructure upcoming release notes and fold in missing PRs

Group the upcoming version block into Features / Performance / Bug Fixes
/ Breaking Changes / Documentation sections so the headline (piecewise)
leads, and add the entries for #589, #595, #601, #614, #619, #635, #656,
#671, #672, #674. Tighten the piecewise block to its final state.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs: tighten upcoming changelog and drop internal-only entries

Trim verbose phrasing in the piecewise / variables / model / solvers
sections, fold subset-superset sub-bullets into one paragraph, and drop
two entries that aren't user-facing for a release notes audience:
sphinx-copybutton (doc tooling) and Model.__weakref__ (only relevant to
extension authors).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs: move align convention from breakpoints() to Slopes in changelog

#673 removed the slopes-mode (and slopes_align kwarg) from breakpoints();
the align kwarg now lives on the Slopes class.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs: move SOS reformulation bullet from Variables to Model

SOS reformulation is a model-rewrite/solve-pipeline concern, not a
variable attribute.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs: split coord alignment into Expressions, move CPLEX to Bug Fixes

- New *Expressions* subsection holds the subset/superset coord
  harmonization, which was misfiled under *Model*.
- CPLEX quality-attribute handling is a fix for crashes on missing
  attributes, not a new feature — moved to **Bug Fixes**.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs: fold as_dataarray MultiIndex fix into add_variables bullet

#659 fixes a regression introduced by #614 in the same release cycle —
no end user ever saw the broken state, so a standalone bullet
overstates the change. Net behavior is captured by extending the
add_variables bullet to mention MultiIndex coords.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs: tighter pass on upcoming changelog

Drop implementation details that belong in API docs (numpy-vs-pandas
note, JSON encoding for netCDF, "with no auxiliary variables" piecewise
detail), merge the two OETC bullets, and trim "Add X. Supports Y."
wrappers across most lines.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs: rephrase active gating bullet to avoid output-zeroing implication

Previous wording ("zeros all auxiliaries when off") was true at the
auxiliary level but glossed over the bounded-tuple case where the
output is not automatically pinned to 0. Drop the implication and
defer the detail to the docstring.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs: drop option-name detail from upcoming changelog

Trim references to specific kwargs/attributes the reader doesn't need
in the high-level summary: method="auto" parens, align="pieces|leading",
deep / include_solution, reformulate_sos="auto", solver_name /
**solver_options, max_dual_infeasibility example, and the
operator-by-operator coord-alignment breakdown.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants