Open matteodelucchi opened 8 months ago
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:
buildscorecache.c
limited by not handling multinomial variables?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