The Future of SCIP
sourcegraph.com
The Future of SCIP
1–10 of 27 posts
Re: The Future of SCIP
#2Oh, not SICP.
Re: The Future of SCIP
#3Oh, not SICP.
... and not the solver for mixed integer (linear) programming (MI(L)P) and mixed integer nonlinear programming (MINLP):
Re: The Future of SCIP
#4Oh, not SICP.
I misread it too.
Re: The Future of SCIP
#5The git repo is here: https://github.com/scip-code/scip
Looks like it's defined using protocol buffers, with "rich Go and Rust bindings" and links to implementations for many other languages.
Re: The Future of SCIP
#6The git repo is here: https://github.com/scip-code/scip Looks like it's defined using protocol buffers, with "rich Go and Rust bindings" and links to implementations for many other languages.
I can’t speak for the Go bindings, but using the Rust crate has been pretty clean. Haven’t really felt the need to dip into deserializing raw .scip file in the time that I’ve been working with SCIP.
Re: The Future of SCIP
#7Oh, not SICP.
Also not SCPI (Standard Commands for Programmable Instrumentation), widely used to control lab instruments and pronounced similarly ("skippy").
Re: The Future of SCIP
#8Oh, not SICP.
Nor the other SCIP.
https://en.wikipedia.org/wiki/Secure_Communications_Interope...
Re: The Future of SCIP
#9Oh, not SICP.
There IS no… wait, wrong acronym.
Re: The Future of SCIP
#10Oh, not SICP.
The similar acronym appears to be intentional:
> Note on the name: SCIP is pronounced the same way as “skip” and it’s a recursive acronym that stands for “SCIP Code Intelligence Protocol.”
> SCIP is also a purposeful nod to SICP (Structure and Interpretation of Programs), a book about analyzing programs.
https://sourcegraph.com/blog/announcing-scip#:~:text=SCIP%20...