Suggested edit to message passing notation in junction tree notes#198
Suggested edit to message passing notation in junction tree notes#198apappu97 wants to merge 1 commit intoermongroup:masterfrom
Conversation
Responds to Pull Request ermongroup#198 by reverting a change made in commit feca805. Additionally fixes some typos.
|
"The factor |
|
Oh okay, thanks for clarifying. And thanks for all of the effort on these notes, they are wonderful! To followup: isn't the subscript redundant then? As a reader, and having cross referenced with other message passing notes, the double index subscript feels much clearer, as it makes explicit the destination and source nodes in the message passing algorithm. Additionally, the single index subscript notation seems inconsistent with the explicit "The factor Also on line 21: "At each step, we will eliminate If you agree, I'm happy to make changes. Thanks for looking! |
Responds to Pull Request ermongroup#198 by reverting a change made in commit feca805. Additionally fixes some typos.
|
Thanks for taking the time to read these notes so carefully! Your point about potentially having multiple children is something I overlooked, so I'm going to re-open this pull request. Will come back and think through this more thoroughly. I think there is significant room to improve this section of the notes. Just a small example: the notes on VE never mention "forming cliques" of a certain size and instead talks about the size of factor scopes. I'll take a deeper pass through this when I have time. Feel free to continue making changes as you see fit and I'll see what makes sense to incorporate! |
I believe in line with the notation earlier in the notes and discussion of message passing, the sentence "The factor$$\tau_j(x_j)$$ can be thought of as a message that ..." should instead be "The factor $$\tau_{jk}(x_k)$$ ..." as we've summed over the values of variable $$x_j$$ , leaving a new factor that is a function of $x_k$ , i.e. the message from $$x_j$$ to $$x_k$$ .