You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't quite understand why the creation of the parent combination matrix defn.res differs in buildScoreCache.mle() and buildScoreCache.bayes().
The Bayes case uses the C function buildscorecache.c. This looks reasonable, though not super efficient (it iterates twice over the same nested for loops). buildscorecache.c handles the different number of max.parents per node in the Bayes case.
Thoughts:
Is the Bayes variant with buildscorecache.c limited by not handling multinomial variables?
If yes, can we easily extend it? E.g. following the approach in buildscorecache.mle(), which splits them up in their levels after the parent combination matrix has been created in the first place. This would be a first step to the extension of the Bayes framework to multinomials -> make separate issue/milestone.
Issue description
Only with
method = "bayes"
we can set the number of maximal allowed parents individually per node.MRE
The text was updated successfully, but these errors were encountered: