Hi Jakub, Jakub Wojt wrote: >> Hi Jakub, >> >> >> The code you sent seems to be missing computeQuality/3 -- I assume >your code actually spend most of its time there. > > sorry, > computeQuality is an external C function, code is in file attached to email. I compiled it under gcc 3.4.2.(Dev-Cpp package). > I don't belive that computeQuality is very time-consuming, in fact i can set it's execute time to ~0. > The timeout only works while executing ECLiPSe code, not external C code. However, if you say that your C function finished quickly, I assume it instantiates Result, the cost variable? You should get a first solution very quickly, and then backtracking starts. It seems that the labeling is able to produce solutions very quickly, and then the code should execute computeQuality again -- could these subsequent calls to it take a long time? Cheers, KishReceived on Fri Aug 03 2007 - 00:07:32 CEST
This archive was generated by hypermail 2.3.0 : Wed Sep 25 2024 - 15:13:20 CEST