Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Add access to SCIP solver options configuration #85

Closed
gn64 opened this issue Jan 24, 2025 · 1 comment
Closed

Feature Request: Add access to SCIP solver options configuration #85

gn64 opened this issue Jan 24, 2025 · 1 comment

Comments

@gn64
Copy link

gn64 commented Jan 24, 2025

Hi!

First, I want to express my sincere gratitude for good_lp - it's an excellent library that has been incredibly helpful for linear programming in Rust. The clean API design and solver integrations have made it a valuable tool for many projects.

Currently, good_lp provides access to HiGHS solver options configuration, but similar functionality is not available for the SCIP solver. Would it be possible to add support for configuring SCIP solver options?

The recent implementation for HiGHS (#54, #56) added the ability to set solver options directly. I would like to request similar functionality for SCIP, allowing users to configure SCIP-specific parameters through good_lp's interface.

This would be particularly useful for:

  • Tuning solver performance for specific problem types
  • Adjusting algorithmic behavior
  • Setting numerical tolerances
  • Controlling output verbosity

If this feature request is acceptable, I'd be happy to contribute by creating a PR for this functionality.

Thank you for considering this request and for maintaining such a valuable library for the Rust ecosystem!

Related issues:

@gn64
Copy link
Author

gn64 commented Jan 24, 2025

Apologies - I just noticed that PR #84 already implements SCIP solver options configuration. Closing this issue as duplicate.

For reference:
PR #84: Add set option for SCIP backend

@gn64 gn64 closed this as completed Jan 24, 2025
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

No branches or pull requests

1 participant