-
Notifications
You must be signed in to change notification settings - Fork 11
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
Limits to missingness handled by learn_circuit_miss
?
#118
Comments
Thanks for the report. At the moment in the next version v0.4 both Our v0.4 is in master branch and is fairly stable now, some example scripts here. We are planning on releasing soon after some more testing and documentation. There is major API changes so some code change would be needed. (For example, not using DataFrames anymore and just using Comment for v0.3.3In case, you want to stay with v0.3.3 for now. I think bug is not from learning the initial structure, and seems to be more of from paramter learning or bad paramter initilization. I will try to reproduce the bug. If you can provide minimal code that reproduces this would be nice. Alternative Structure (HCLT)Both this options give you determnistic and structured decomposable circuite, if you don't need determinism, we suggest using HCLT structures instead (they are decomposable but not determinsitic) as they usually perform better.
The code is much more simplified in v0.4 (current in master), so might be worth the swith there is major API changes though. |
Also forgot to ask, where you using CPU or GPU version? |
I have a situation where I need to train models with lots of missing information, i.e. the training matrix is very sparse (on the order of more than 90% of values are missing (in a sub-matrix of the full training matrix)). There are many training instances overall but for each one only a small subset of the covariates are active/non-missing.
Is there some known limit to the missingness that can be handled?
When I try training with this data I get an AssertionError:
I can provide a fuller stack trace if it would be useful. It is 65 levels deep though. ;)
The text was updated successfully, but these errors were encountered: