Envelope-to: eclipse-bugs@icparc.ic.ac.uk Delivery-date: Thu, 14 Mar 2002 23:23:11 +0000 Date: Fri, 15 Mar 2002 01:22:56 +0200 (EET) Sender: Deze Zhao <dzhao@niksula.hut.fi> From: Deze Zhao <dzhao@niksula.hut.fi> Content-Type: TEXT/PLAIN; charset=US-ASCII [SNIP] Yes (0.59s cpu) [eclipse 2]: cool(5,5). lists.eco loaded traceable 0 bytes in 0.04 seconds 0 0 0 0 480 0 0 0 0 480 0 0 0 0 480 0 0 0 0 480 0 0 0 0 480 [0.65, seconds] There are 1800 delayed goals. Do you want to see them? (y/n) More (0.66s cpu) ? ********************************************* my question is, if I got five 480, the constraint 1.0 *> sum(Temp) should not hold, in other words, sum(Temp) should be larger than 1. Hi Deze, >From what I can make out the IC library seems to be working fine. Looking at the column of five 480 values, and the loop which calculates the values for Temp (Around line 100), we have.... Squares[K,I] = 450 Target_sir[J] = 3.16 So U becomes 450*3.16 / (450*3.16 + 3840000.0) = 0.00395 and Temp = sum(U1,U2,U3,U4,U5) = 5*0.00395 = 0.00197 Which is significantly less that 1.0 so the constraint 1.0 *> sum(Temp) is not being violated by the data that you are using. and this constraint also shouldn't hold at the same time, 3.84*(R3/(R3+1))/((1-sum(Temp))*Gains[K]*25000000000.1) *>= 0.0, Likewise with this constraint, from what we can deduce this constraint will almost allways be satisfied. R3 is always positive, becuase Square[K,I] and Target_sir[K] are positive sum(Temp) is always less than 1.0 (because of the constraint above), so the sub expression 1-sum(Temp) will always be positive aswell Gains[K] is always positive so the whole of the left hand side of the *>= constraint will neccessarily be positive Was something wrong in my source code? or? I cant say that your source code is wrong, because I'm not sure what it is trying to achieve, but it appears to be running correctly. You may want to consider using the tkeclipse version of eclipse and tracing the programs executing until you see it doing something unexpected. Hope that helps -- Andrew Sadler PS. All the delayed goals are showing variables with very small domains, many of which are zero spanning. This is often the case, and is used to indicate any potential rounding errors.Received on Fri Mar 15 12:34:03 2002
This archive was generated by hypermail 2.1.8 : Wed 16 Nov 2005 06:08:14 PM GMT GMT