Skip to content

Commit b34f7de

Browse files
committed
Clarify the support for new optimizer
1 parent a44c3e0 commit b34f7de

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

docs/source/faq.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,3 +35,22 @@ model = gurobi.Model(env)
3535
In YALMIP, you can use the matrix form $Ax \leq b$ to add linear constraints, which is quite convenient.
3636

3737
In PyOptInterface, you can use [`model.add_m_linear_constraints`](<project:#model.add_m_linear_constraints>) to add linear constraints in matrix form.
38+
39+
## Will PyOptInterface support new optimizers in the future?
40+
41+
In short, no, there are no plans to support new optimizers. Supporting a new optimizer is not a trivial task, as it requires a lot of work to implement, test and maintain the interface.
42+
43+
Basically, a new optimizer should satisfy the following criteria to be considered for support:
44+
45+
- Actively maintained
46+
- Good performance (open source or commercial)
47+
- Not difficult to acquire an academic license
48+
- Have well-defined C/C++ API
49+
50+
Support for a new optimizer will only happen if one or more of the following conditions are met:
51+
52+
- I am personally interested in the optimizer and plan to use it in my research, so I am willing to invest time in implementing it.
53+
- Someone steps up to implement and maintain the interface for the optimizer in PyOptInterface.
54+
- External funding or sponsorship become available to support the development and maintenance of the optimizer interface.
55+
56+
Finally, we are always open to external contributions. If you have a specific optimizer in mind and plan to implement it, feel free to open an issue on our GitHub repository to discuss it.

0 commit comments

Comments
 (0)