Achievement unlocked: Solving a linear program on a phone.
No software to install. Take a picture of an LP, get a solution in return. The demo in this video uses the CPLEX solver on @NeosOpt servers.
Today's a big day! We are very proud to introduce AIMMS Community Edition, a free entry point for anyone interested in building mathematical optimization models and applications using our feature-rich IDE
https://t.co/XdktOFojaV #AIMMS#ORMS#datascience
Should also mention that this new feature was made possible with the generous support of our friends at @AIMMS.
Join the discussion at https://t.co/GYnf6FhPk2. Your feedback helps us improve tex2solver.
Our session at the #informs2020 Annual Meeting is happening now!
Lots of interesting and varied talks on optimization. We look forward to chatting with you at 10am EST.
https://t.co/gF8OvWJknG
Our session at the #informs2020 Annual Meeting is happening now!
Lots of interesting and varied talks on optimization. We look forward to chatting with you at 10am EST.
https://t.co/gF8OvWJknG
@GeoffreyDeSmet@GeoOptimization Very nice API, Geoffrey, which seems well-suited to address the different challenge/audience you've described.
tex2solver aims to save time for those who already have an IP/LP model, by automating the translation to solver code. For example: https://t.co/2p3glPmhyc
New video:
Solving a linear program...from a screenshot...without writing any code.
tex2solver converts MILP models to solver code. Test it out at https://t.co/rX5D1VzPQF
#optimization#orms
@ORatWork Thank you, John!
We wanted to help people validate their models as easily as possible. Hopefully this will also encourage students to further explore the art of modeling.
Would love to get your feedback if you get time to test it out.
Using tex2solver on your smartphone, you can take a picture of your linear or integer programming model and automatically generate the solver code.
Here's an example with a handwritten LP model.
https://t.co/rX5D1VzPQF
#orms community,
We're trying to compile some generally-accepted best practices for formatting IP/LP models...we need your input!
What are your DOs and DON'Ts when it comes to writing an MILP? Any formatting issues that you frequently point out during peer reviews?
2) Constraints should begin in the second line of the model, which should start with any of these LaTeX text tags (the text itself is case insensitive):
@thyunes@mluebbecke Hi, Tallys. You're correct. For LaTeX -> code, we need the mapping to indicate which elements of subscripts and/or superscripts are actually indices (vs. parts of the variable name itself).
Some more details are documented here:
https://t.co/bzOcxxpu3Y
@derduff Thank you! Yes, summations, set operators, conditionals, and others are currently supported. Our work-in-process documentation provides some details: https://t.co/bzOcxxpu3Y
Please do let us know if we've missed something.