This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
1) Not related to your error, but I would always display the field mapping for anchor O. This can prevent mistakes in case you don't have the casing right (Variable instead of variable) or spelling right (variabel instead of variable).
2) I would verify that in your A input, the first field is named variable.
3) I would verify that all of your constraint columns in the A input are numeric datatypes (click on the line going into the A input).
4) for the B anchor, I would use a select tool to get it down to just 2 columns (dir and rhs, in that order). Make sure rhs is a numeric datatype. from the help doc:
dir: a string, direction of the constraint inequality. It has to be >=, <= or ==.
rhs: a number, the right hand side of the inequality, corresponding tob.
5) I would make sure that if you have x columns of constraints in your input A, you have x rows in input B.
If that still doesn't solve it, try and provide sample data or a dummy dataset that is giving you the same problem.
Just to add to Patrick’s great response, a quick simple thing to check is that your constraints input should have as many rows as your matrix input has columns (-1, as you will have a column with your decision variables in).
If this is not met then that’s likely the root cause.