Hi Christian,
I am not sure if I understand you correctly, but the footnote talks
about one global AFC decay factor, but the documentation refers to AFC
-- 'Reset AFC to a' -- does this AFC refers to the decay factor, rather
than the AFC values accumulated with the constraints? If so, should the
documentation be changed to mention decay factor (it does in the
document for the afc_decay() method)
If afc_set() is used to reset the decay factor, then what is the
difference from afc_decay()? Is afc_decay() used to initialise the decay
factor, and afc_set() used to change the decay factor later on?
Cheers,
Kish
On 06/12/2013 11:35, Christian Schulte wrote:
Hi,
Gecode is cheating for AFC, read footnote 1 on page 120 in MPG.
I fixed the link.
Cheers
Christian
--
Christian Schulte, Professor of Computer Science, KTH,
www.ict.kth.se/~cschulte/
-----Original Message-----
From: users-boun...@gecode.org [mailto:users-boun...@gecode.org] On Behalf
Of Kish Shen
Sent: Thursday, December 05, 2013 10:05 PM
To: users@gecode.org
Subject: [gecode-users] changing a Space's AFC decay factor
Hi,
I am looking at the documentation for AFC in the class documentation for
Space (section low-level support for AFC), and I don't understand what
afc_set(double a) does:
The description say it 'Reset AFC to a', but I thought there is no global
AFC value, as each variable has its own AFC value?
[Also, I noticed a possibly incorrect link in the description for
afc_decay(double d):
the Set in 'Set AFC decay factor to d' is linked to Gecode:Set ]
Cheers,
Kish
_______________________________________________
Gecode users mailing list
users@gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users
_______________________________________________
Gecode users mailing list
users@gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users
