[SCIP] Check on SCIP license issue

Tue Nov 15 01:06:55 CET 2022

Dear Mathieu

Thank you for your reply.
That has solved all my doubts.

Best regards,
Yuzhu

From: Besancon, Mathieu <besancon at zib.de>
Sent: Monday, November 14, 2022 5:45 PM
To: 汪 玉柱 <yuzhu.wang.b85 at jp.nssol.nipponsteel.com>
Cc: scip at zib.de
Subject: Re: Check on SCIP license issue

Dear Yuzhu,

Thank you for pointing it out. The doxygen documentation is released with each version of SCIP, the text will change with the new version which is already under the new license.

And yes that's correct a commercial license will not be necessary. You can already see the new license on the github mirror: https://github.com/scipopt/scip/blob/master/LICENSE
[イメージは差出人によって削除されました。]<https://github.com/scipopt/scip/blob/master/LICENSE>

scip/LICENSE at master * scipopt/scip * GitHub<https://github.com/scipopt/scip/blob/master/LICENSE>
github.com
SCIP - Solving Constraint Integer Programs. Contribute to scipopt/scip development by creating an account on GitHub.

Cheers,

Mathieu

________________________________
From: yuzhu.wang.b85 at jp.nssol.nipponsteel.com <yuzhu.wang.b85 at jp.nssol.nipponsteel.com>
Sent: Monday, November 14, 2022 9:40:42 AM
To: Besancon, Mathieu
Cc: scip at zib.de
Subject: RE: Check on SCIP license issue

Dear Mathieu

Thank you for answering my questions.
|“SCIP is now open-source under Apache 2.0 since about two weeks ago.”
Dose this mean that a commercial license is no longer required, even for commercial uses?
I’m a bit confused because the FAQ on the SCIP Doxygen Documentation 8.0.2 still says “If you want to use SCIP commercially, please write an e-mail to koch at zib.de<mailto:koch at zib.de>.”.

Many thanks,
Yuzhu

From: Besancon, Mathieu <besancon at zib.de>
Sent: Monday, November 14, 2022 4:44 PM
To: 汪 玉柱 <yuzhu.wang.b85 at jp.nssol.nipponsteel.com>; scip at zib.de
Subject: Re: Check on SCIP license issue

Dear Yuzhu,

SCIP is now open-source under Apache 2.0 since about two weeks ago, so the license should not be a blocker for anything on cloud services. I cannot answer for commercial solvers.

Building SCIP on Docker should be straightforward with the same installation instructions.

For question two, you can start as many instances as you want since the license is not a blocker (note, this is not about concurrent solving within one SCIP instance).

Best,

Mathieu

________________________________
From: Scip <scip-bounces at zib.de<mailto:scip-bounces at zib.de>> on behalf of yuzhu.wang.b85 at jp.nssol.nipponsteel.com<mailto:yuzhu.wang.b85 at jp.nssol.nipponsteel.com> <yuzhu.wang.b85 at jp.nssol.nipponsteel.com<mailto:yuzhu.wang.b85 at jp.nssol.nipponsteel.com>>
Sent: Monday, November 14, 2022 2:32:42 AM
To: scip at zib.de<mailto:scip at zib.de>
Subject: [SCIP] Check on SCIP license issue

Dear SCIP team,

I am currently investigating commercial MIP solvers that can run in Docker containers.
If possible, I would appreciate your answers to the following questions regarding licensing and working images.
Following the SCIP document Q&A, I wrote an email to Prof. Koch last Wednesday with questions about the license, but am still waiting for a reply. So, I would like to ask a question here.

  1.  Is there a commercial license system that allows optimization processing from applications in Docker containers on GCP (Google Cloud Platform)? If so, I would be grateful if you can give me a concrete image of how SCIP works in this environment.
  2.  I would also like to know the number of optimization processes that can be run concurrently with one commercial license.

Many thanks,
Yuzhu

*****************************************************************
This e-mail and any attachments are intended only for
the named addressee(s) and may contain confidential information.
If you have received this e-mail in error, please delete
the e-mail and any attachments and notify the sender immediately.
If you are not the intended recipient, any disclosure, copying,
printing, transmission or distribution of, or any action taken
in reliance upon, the information contained in this e-mail and
any attachments is strictly prohibited.

このメール及び添付資料には機密情報を含む場合があります。
本メールにお心当たりのない場合は、速やかに破棄頂くとともに、
送信元へその旨ご連絡ください。また、本メール及び添付資料に
ついては、一切の開示、複写、配布、その他の利用、または、
記載内容に基づくいかなる行動もされないようにお願いします。
*****************************************************************
*****************************************************************
This e-mail and any attachments are intended only for
the named addressee(s) and may contain confidential information.
If you have received this e-mail in error, please delete
the e-mail and any attachments and notify the sender immediately.
If you are not the intended recipient, any disclosure, copying,
printing, transmission or distribution of, or any action taken
in reliance upon, the information contained in this e-mail and
any attachments is strictly prohibited.

このメール及び添付資料には機密情報を含む場合があります。
本メールにお心当たりのない場合は、速やかに破棄頂くとともに、
送信元へその旨ご連絡ください。また、本メール及び添付資料に
ついては、一切の開示、複写、配布、その他の利用、または、
記載内容に基づくいかなる行動もされないようにお願いします。
*****************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.zib.de/pipermail/scip/attachments/20221115/1bb086a2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ~WRD0000.jpg
Type: image/jpeg
Size: 823 bytes
Desc: ~WRD0000.jpg
URL: <http://listserv.zib.de/pipermail/scip/attachments/20221115/1bb086a2/attachment.jpg>