This is still some code, as opposed to no code. It does seem to model everything in the research paper.
Aside from the original research paper needing to be included in the repo, it definitely does not need anything more than what's already there. It all builds and compiles without errors, only 2 warnings for the library proper and 6 warnings for the test project. Oh and it comes with a unit testing project: 59 tests written that covers about 73% of the library code. Only 2 tests failed.
Even having a unit testing library means it beats out like 50% of all repos you see on GitHub.
https://github.com/klipto/uncertainty
10 years since commit and no attached documents besides a tiny readme. Pass.
This is still some code, as opposed to no code. It does seem to model everything in the research paper.
Aside from the original research paper needing to be included in the repo, it definitely does not need anything more than what's already there. It all builds and compiles without errors, only 2 warnings for the library proper and 6 warnings for the test project. Oh and it comes with a unit testing project: 59 tests written that covers about 73% of the library code. Only 2 tests failed.
Even having a unit testing library means it beats out like 50% of all repos you see on GitHub.
Blame Microsoft Research, as the link came directly from them: https://www.microsoft.com/en-us/research/project/uncertainty.... I don't think they ever really took the project past the initial paper/presentation.
Sometimes things can just be "done", and the paper is pretty good documentation if the implementation is faithful to what is described there.