-
Notifications
You must be signed in to change notification settings - Fork 2
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
Missing code examples in documentation #3
Comments
Generally speaking, if some functionality does not have a unittest associated to it, I don't mention it. So far I could not find test cases for I also thought about the real dataset/model suggestion before as well. However I also think toy examples I provide seem a little too ad hoc. What would you prefer to see as a description for toy examples ? Would you mind giving an example ? |
@D-K-E Thanks for the clarification. For the description, I just meant describing the problem statement that the code example is trying to solve in simple words. An example could be the Monte Hall problem example in pgmpy here: https://github.com/pgmpy/pgmpy/blob/dev/examples/Monty%20Hall%20Problem.ipynb. The notebook gives a context of the Monte Hall problem (which is a toy example) and how you would solve something like that using pgmpy. |
@ankurankan I added some new tests and added a usage examples under Most my examples are toy examples taken from text books. I'll try to add more real world examples when I have a bit more time. |
@D-K-E The examples look good, but I am getting errors in running all of them (except the first one). Could you please check? |
@ankurankan All right, they all should have been fixed now, both in the documentation and the newly added jupyet notebooks |
In the documentation at https://d-k-e.github.io/graphical-models/html/index.html, I can see an example of PGModel but for other model types, there are no code examples. Also, it would be nice if you could use a real dataset/model for the examples, but if you are using a toy example, it would be helpful if you could describe it a bit before the code.
Ref: openjournals/joss-reviews#3115
The text was updated successfully, but these errors were encountered: