JijZept Updates
We’re pleased to announce the release of JijZept with important updates and fixes that further refine your experience.
Updated SDKs
- JijModeling latest version - jijmodeling v1.1.1
- JijZept Client latest version - jijzept v1.17.0
New Features
MIPLIB Instances with
jijmodeling
: A tutorial is now available for efficiently loading MIPLIB instances usingjijmodeling
, aimed at simplifying benchmarking and testing workflows.jijzept
v1.17.0: This release removes JijDA3Sampler and adds a new row-oriented SampleSet, accessible as follows:import jijzept as jz
sampler = jz.JijSASampler(config="config.toml")
sampleset = sampler.sample_model(problem, instance_data).get_sampleset()Enhanced Sampler Metadata: SampleSets from JijDA4Sampler and JijLeapHybridCQMSampler now include details on trivial constraints in their metadata:
sampleset.metadata["presolve"]["trivial_constraint"]
Expanded Support in JijLeapHybridCQMSampler: Continuous variables via
jijmodeling.ContinuousVar
are now supported, enhancing the sampler's flexibility.
Bug Fixes
Server Response Stability: We have fixed a critical issue where certain
jm.Problem
submissions caused server unresponsiveness.Scoped Element Naming:
Element
names are now context-specific within constraints and functions, enabling the reuse of generic identifiers likei
andj
without introducing errors or conflicts with other variables and placeholders:import jijmodeling as jm
n = jm.Placeholder("n")
x = jm.BinaryVar("x", shape=(n,))
problem = jm.Problem("problem")
i = jm.Element("i", belong_to=n)
problem += jm.Constraint("const1", x[i] == 1, forall=i)
i = jm.Element("i", belong_to=3)
# No more ModelingError for reusing "i" with a different definition in the same problem scope.
problem += jm.Constraint("const2", i * x[i] == 1, forall=i)
Important Notices
End of Support for JijDA3Sampler: Please be advised that as of today, November 6th, support for JijDA3Sampler has ended. We continue to support JijDA4Sampler and encourage users to consider using this sampler for future projects.
Transition to New SampleSet Schema: We are planning a transition to a new schema for SampleSets. This upgrade will enhance the data structure and user access patterns. Details and instructions for this transition will be provided well in advance to ensure a smooth update process.
Thank you for your continued support. Should you need any assistance or have inquiries, please do not hesitate to contact us.