-
Notifications
You must be signed in to change notification settings - Fork 36
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
Maybe split gold standards to a separate project? #63
Comments
Im not sure about this. The stan team (with paul as lead) is looking into a posteriors R package that is similar. We should build on that instead is my guess. But @paul-buerkner paul knows more about this. |
Yes if we can build on it that would be ideal. Looking forward to hearing more about it. |
@paul-buerkner can you give a short summary on what the |
From the current README: The posterior R package will provide various tools for working with posterior distributions that are represented by draws. Goals:
|
Thanks! Ah so I guess it's a public repo, can you link to it? I couldn't find it under either |
Will be public in a few days.
Am Do., 31. Okt. 2019 um 16:19 Uhr schrieb Eero Linna <
notifications@github.com>:
… Thanks! Ah so I guess it's a public repo, can you link to it? I couldn't
find it under either stan_dev or your user
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#63>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADCW2AE6F6GDMMB5442P74LQRLZP7ANCNFSM4JEDM5NA>
.
|
Now, this is public. https://github.com/jgabry/posterior So I close this issue. |
I've started to think that maybe the gold standards should be in a separate project. This idea is not yet fully formed but I thought it would be good to put it out now. I'll use the name
goldstandards
for this hypothetical project.posteriordb
provides posterior names that are used as unique identifiers ingoldstandards
goldstandards
can get greater flexibility in how it is implemented: perhaps a central database and a web server along with client packages would work best for that project instead of the git repo with PRs model that we currently use inposteriordb
gs <- gold_standard(po)
could still work (however there are some caveats)posteriordb
and only later add the gold standards. Of course this doesn't necessarily require two separate projectsGoing more general
We dont have to restrict the other project to just gold standards, it could include posterior samples for any method. I'll call this more general project
posteriorsamples
Selecting a gold standard
Having the ability to upload multiple posterior samples for a posterior might make it easier to come up with a good gold standard
Developing inference methods
niceinference
and runs it on 50 posteriors fromposteriordb
. They publish a paper about their method that includes comparisons to gold standards. They also upload the posterior samples toposteriorsamples
.niceinference
. You run your method on the same 50 posteriors. You also download the posterior samples ofniceinference
. Now in your paper you can include both comparisons to the gold standard and between the two methods.Next steps
So as a reminder, this idea is not yet fully developed. Maybe keeping gold standards under
posteriordb
is the best idea. Maybe it's not. I might write a follow-up post later if the idea develops further, right now I just wanted to put this out here.I'll tag you here so you notice this, but commenting right now is not necessary (but if you got some ideas from this of course feel free to comment) @MansMeg @paul-buerkner
The text was updated successfully, but these errors were encountered: