Closed darcey closed 2 years ago
Hey, just noticed this bug was still open. From what I remember: each Node used to have a field called "value", which stored that Node's assignment (or None, if it was unassigned). David convinced me that it would be better to store assignments elsewhere, in a separate data structure, so we removed all the Node.value stuff from the code.
Was an assignment data structure ever implemented? Is there a reason why it's less necessary than it originally seemed? (Guess I should tag @davidweichiang.)
No, this has never been implemented and isn’t needed for the finite-domain sum-product code.
On Dec 5, 2021, at 13:19, Darcey Riley @.***> wrote:
Hey, just noticed this bug was still open. From what I remember: each Node used to have a field called "value", which stored that Node's assignment (or None, if it was unassigned). David convinced me that it would be better to store assignments elsewhere, in a separate data structure, so we removed all the Node.value stuff from the code.
Was an assignment data structure ever implemented? Is there a reason why it's less necessary than it originally seemed? (Guess I should tag @davidweichiang.)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
Hmm, do you think there are other places where we might need it?
I guess we would need something like it for a Viterbi-style algorithm and/or random sampling.
Aha, hmm. Seems like, in that case, we should probably just wait until we're implementing those things to add this?
Yeah, I think so.
The assignment data structure is just Dict[Node, Any]
.
The assignment data structure is just Dict[Node, Any]
.
Wow, why is everything appearing twice?
Wow, why is everything appearing twice?
A while ago, I remember we talked about needing this. I guess we should implement it at some point / think about how it should fit into the code structure.