<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Attached lp comes up infeasible in cbc, but finds optimal objective in cplex. In cbc I ran it with and without preprocessing which has given me problems before.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I ran latest trunk build and an older one. I saw one checkin in latest saying SOS shouldn’t have tolerance, and wonder if this is another similar manifestation.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It looks like it is correctly computing l1 (63999/64000), but then rounding l2 (1/64000 = 1.5625e-5) down to zero. It would seem that a consistent rounding strategy would yield a feasible solution. If it doesn’t admit l2 = 1.5625e-5 to the solution, it shouldn’t let l4 = 1.5930576e-09 in . If it rounds l2 = 1.5625e-5 to zero, it should round l1 = .99998089 to 1.0. I would prefer no tolerance.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>X0009905: S2:: HS_ST(0)_l1:1 HS_ST(0)_l2:2 HS_ST(0)_l3:3 HS_ST(0)_l4:4<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Integer infeasible - objective value 0.00000000<o:p></o:p></p><p class=MsoNormal> 10 HS_ST(0)_l1 0.99998089 0<o:p></o:p></p><p class=MsoNormal> 11 HS_ST(0)_l2 0 0<o:p></o:p></p><p class=MsoNormal> 12 HS_ST(0)_l3 1.9106687e-05 0<o:p></o:p></p><p class=MsoNormal> 13 HS_ST(0)_l4 1.5930576e-09 0<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In the meantime, can anyone suggest a workaround?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>jkh<o:p></o:p></p></div></body></html>