Passing multiple model objects to setNode (+ Issue #6) about hydenet HOT 4 CLOSED

I think I might be more comfortable with this as a separate function. setNode is very clearly structured for dealing with a single node, a decision I made because I assumed most users would work with one node at a time.

This proposal seems like the user is providing the information as several nodes at once. It's a great idea, and can be done, but I might suggest something more like

net <- setNodeModels(lm(wells ~ 1, data=d2),
    glm(pregnant ~ 1, family=binomial, data=d1))

This may require an additional element for each node, if we are going to accept the possibility of differing data objects for each model. But if net$nodeData$[node_name] = NULL, it could then look to net$data.

from hydenet.

Agreed to have separate functions.

from hydenet.

See Issue #20 .

We may consider doing the above but for single nodes, using an adaptation of modelToNode().

from hydenet.

setNodeModels is now included.

from hydenet.