You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have already created a page for the general workflow for Hakaru programming (7a849c3) and the burglary alarm example from the system description paper (6e257c8).
Regarding the burglary example, I would recommend (1) documenting the optional use of simplification (rather than sampling) after disintegration to figure an exact (rather than approximate) answer to the problem; (2) add each transformation in the documented workflow as tests.
Regarding which example next, I would recommend the second of the two examples of the system description paper, which we call "easier roadmap".
I have been reading the paper that was suggested to me for documenting GMM Gibbs, and I have a few questions:
How did you want this example to look in the documentation? It is not like the burglary or thermometer examples (which were published like tutorials). This one looks more like a "Sure, you can do this in Hakaru". My only thought right now is that perhaps this could be added to the "Examples" page with a description of the program and a reference to the paper. If you would prefer a page on its own, what should be included? Regarding testing, this pipeline has already been added to haskell/Tests/RoundTrip.hs.
The first example in the paper is a series of transformations on a Kalman filter. Isn't this the same as the thermometer example (hakaru/tests/RoundTrip/thermometer_workflow.hk)? If it isn't, I want to add it to haskell/Tests/RoundTrip.hs as a pipeline.
I am not actually 100% sure that this is done -- Geneva was waiting for Yuriy to finish a couple of things to close this off, and he didn't finish them until some time in September.
Activity
zaxtax commentedon Jun 26, 2017
GenevaS commentedon Jun 26, 2017
I have already created a page for the general workflow for Hakaru programming (7a849c3) and the burglary alarm example from the system description paper (6e257c8).
Which examples should I work on next?
ccshan commentedon Jun 26, 2017
Thanks!
Regarding the burglary example, I would recommend (1) documenting the optional use of simplification (rather than sampling) after disintegration to figure an exact (rather than approximate) answer to the problem; (2) add each transformation in the documented workflow as tests.
Regarding which example next, I would recommend the second of the two examples of the system description paper, which we call "easier roadmap".
GenevaS commentedon Jun 30, 2017
I've added simplification to the discrete model workflow (fc2af24) and I will start work on the continuous model.
GenevaS commentedon Aug 28, 2017
As of 45456a1, the continuous model/easy road workflow has been documented and added to the test suite.
GenevaS commentedon Aug 30, 2017
I have been reading the paper that was suggested to me for documenting GMM Gibbs, and I have a few questions:
How did you want this example to look in the documentation? It is not like the burglary or thermometer examples (which were published like tutorials). This one looks more like a "Sure, you can do this in Hakaru". My only thought right now is that perhaps this could be added to the "Examples" page with a description of the program and a reference to the paper. If you would prefer a page on its own, what should be included? Regarding testing, this pipeline has already been added to
haskell/Tests/RoundTrip.hs.The first example in the paper is a series of transformations on a Kalman filter. Isn't this the same as the thermometer example (hakaru/tests/RoundTrip/thermometer_workflow.hk)? If it isn't, I want to add it to
haskell/Tests/RoundTrip.hsas a pipeline.ccshan commentedon Nov 27, 2017
Is this done?
JacquesCarette commentedon Nov 27, 2017
I am not actually 100% sure that this is done -- Geneva was waiting for Yuriy to finish a couple of things to close this off, and he didn't finish them until some time in September.
GenevaS commentedon Nov 29, 2017
No, this issue has not yet been resolved. I am reopening it, but I will not be able to work on it for a few weeks yet.