-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
checking bayes nets: arrows go from relational attributes to rnodes, not the other way #81
Comments
Examples 👍
|
the old xml file of toyexample |
Thanks runnan. This is because we are currently failing to add these edges by hand (from Rnodes to 2Nodes). Need to check why that part of the SQL script is not being called. Otherwise the edges are the same which is reassuring. |
@woodsouths @rmar3a So the problem seems to be that in model-manager.sql to build the SchemaEdges table, we need to refer to lattice_membership.member, not rnid. I hope this will fix Runnan's issue. As for the general logic, here's the behaviour I think we need.
|
So I did a bit of investigating to see how/why we dropped the values in the rnid column and it happened/is explained in this commit:
Also this issue is related to this pull request I made before:
I will attempt to fix both of this issues in a future pull request. |
Sounds good. I think we can resolve this in 15 min. At least for the schema edges. |
- Removed the "rnid" column from the lattice_membership table and made all references to that column use the "member" column instead. This is safe to do now because the values in the "member" column are using the full RNID instead of the short RNID. - This should fix the issue where some arrows are missing in the Bayes Net that gets generated by FactorBase. GitHub Issue: #81
So if link analysis is off, schema edges should be added after structure learning and before parameter learning. |
Eliminate where clause from the creating the schemaEdges table When link analysis is on:
When link analysis is off:
|
No description provided.
The text was updated successfully, but these errors were encountered: