8000 Does it have to be bayesian? · Issue #19 · giabaio/BCEA · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Does it have to be bayesian? #19

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

Open
seabbs opened this issue Nov 12, 2019 · 5 comments
Open

Does it have to be bayesian? #19

seabbs opened this issue Nov 12, 2019 · 5 comments

Comments

@seabbs
Copy link
seabbs commented Nov 12, 2019

My understanding of the analysis is that the output needs to be based on some kind of simulation that gives a distribution of outcomes.

Does this need to be a true Bayesian posterior or could it be a prior distribution or sample arrived at using other means?

Obviously, it would be better if everyone went bayesian but might it be a good idea to point out that this is optional (if it is)?

@giabaio
Copy link
Owner
giabaio commented Nov 12, 2019

Well --- BCEA is agnostic in that respect. It does have a strong prior that things should be done in a Bayesian way, but as long as you do have simulation-based output for the matrices of "effects" e and costs c (however defined --- and BCEA doesn't check that these are correct. Nor it could --- that's the modellers' job!), then you can run all its functionalities.

Essentially, BCEA is a software for post-processing of the outcome of the economic modelling and, as such, it can afford to be agnostic about the method (while silently judging non-Bayesian users)... ;-)

I do think this has been pointed out in several places (including the presentations, books and even in the help functions, I think).

@giabaio giabaio closed this as completed Nov 12, 2019
@seabbs
Copy link
Author
seabbs commented Nov 12, 2019

Awesome that is just as I thought.

Do you think there is any space for making that clearer in the README/package description? Some people that I have spoken to have dismissed the package after just looking at those.

Very much agree on the silent judgment aspect but perhaps easing people into the tool so that they are using it makes them more likely to switch (as they will see all the case studies + book using Bayesian methods).

Talking to some HE last week it seemed like using Excel was still quite common. My thought was that easing them into using something better (like BCEA) could be a good gateway to then improving the actual modeling.

Again happy to have a stab at this if you are okay with that?

@giabaio
Copy link
Owner
giabaio commented Nov 12, 2019

We're doing a big push to move people away from MS Excel and into proper stats software (see for example here) and I too was at a big health economics conference last week harassing people to that effect... ;-)

I'm happy for you to have a go at modifying the README file and if you feel there are other parts (eg help files etc) that need updating, please go ahead and send me a push request!
Thanks!

@seabbs
Copy link
Author
seabbs commented Nov 12, 2019

Awesome - will do 😄

Sounds like a great idea - I was pretty shocked to hear about all the excel use honestly.

Could you open this up so I can keep track of what I am having a crack at? I have some time blocked out tomorrow for this.

@giabaio giabaio reopened this Nov 12, 2019
@giabaio
Copy link
Owner
giabaio commented Nov 12, 2019

Just done.

giabaio pushed a commit that referenced this issue Jul 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0