<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>Hi Andreas,<BR>
<BR>
I have detected what caused my segmentation fault. With the new version of AMPL (AMPL Version 20071121) my AMPL script didn't work either with Ipopt 3.2.3 or with the new version 3.3.3. The instruction causing the problem was:<BR>
<BR>
let UNYCNT:= UNYCNT union {j in UNY[c]: prp[c,j,i] == max{l in UNY[c] diff UNYCNT} prp[c,l,i]}; <BR>
<BR>
I guess it makes a mess with the set UNYCNT. Now everything goes well.<BR>
<BR>
Sorry for any inconvenience and thanks for the new version,<BR>
Adela<BR>
<BR><BR><BR><BR> <BR>
<HR id=stopSpelling>
<BR>
> Date: Fri, 16 Nov 2007 10:14:02 -0500<BR>> From: andreasw@watson.ibm.com<BR>> To: pages25300@hotmail.com<BR>> CC: coin-ipopt@list.coin-or.org<BR>> Subject: Re: [Coin-ipopt] ipopt 3.3.3 - segmentation fault<BR>> <BR>> Hi Adela,<BR>> <BR>> In order to fix this, we would need more information in order to reproduce <BR>> the prblem.<BR>> <BR>> Please create a ticket at the Ipopt Trac pages (you will need to create an <BR>> account for COIN if you don't have one yet and log in):<BR>> <BR>> https://projects.coin-or.org/Ipopt<BR>> <BR>> Please include all information necessary to reproduce what you see, such <BR>> as Operating systems, compilers, and the exact sequence of commands that <BR>> lead to this problem. You can attach an AMPL model to the ticket (ideally <BR>> a simple one) that ends up with the segmentation fault.<BR>> <BR>> Thanks<BR>> <BR>> Andreas<BR>> <BR>> On Fri, 16 Nov 2007, [iso-8859-1] Adela Pagès Bernaus wrote:<BR>> <BR>> > Dear all,<BR>> ><BR>> > I've just installed the new version of Ipopt (3.3.3). I use Ipopt from AMPL and I have an script that I was using with Ipopt 3.2.3.<BR>> > The installation was smooth and successful (the tests were passed!) but my surprise comes when I run again my code: Ipopt solves the first problem ending with<BR>> ><BR>> > EXIT: Optimal Solution Found.<BR>> > Ipopt 3.3.3: Optimal Solution Found<BR>> > suffix ipopt_zU_out OUT;suffix ipopt_zL_out OUT;Segmentation fault1.408u 0.076s 0:01.71 85.9% 0+0k 0+0io 0pf+0w<BR>> ><BR>> > Any hint of what may happen?<BR>> ><BR>> > Thanks a lot!<BR>> > Adela<BR>> ><BR>> ><BR>> ><BR>> > PS: I'm using the following options:<BR>> > option ipopt_options $ipopt_options ' mu_init 1000000 '; # initial mu option ipopt_options $ipopt_options ' bound_mult_init_val 1000000 '; option ipopt_options $ipopt_options ' max_soc 8 '; # Max 2nd order correc. option ipopt_options $ipopt_options ' min_refinement_steps 8 ';<BR>> > _________________________________________________________________<BR>> > Explore the seven wonders of the world<BR>> > http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE<BR><BR><br /><hr />Express yourself instantly with MSN Messenger! <a href='http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/' target='_new'>MSN Messenger</a></body>
</html>