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
JOSS review: Documentation #25
Comments
linking openjournals/joss-reviews#3045 |
Thank you for catching this. The paper and doc are now updated to state:
The main point is that automatic analyses can be performed, which is difficult with the available MCMC implementations (because they need to be combined with custom initialisation and termination criteria). While a numerical study that compares the performance of MCMC flavors+init+convergence checks and BXA on a example problem is beyond the scope of this paper/documentation, the paper text was updated to go into more detail on the differences to existing MCMC implementations. I focus on highlighting the difference in nature of the approaches (complete solution with initialisation and termination, no algorithm parameters need to be tuned to the problem). It is certainly possible to do low-count analyses also with the existing MCMC capabilities, at least with mono-modal gaussian-like posteriors. |
In the documentation several important features are listed but without explanation. It would be helpful if these were explained quantitatively with examples / comparisons:
How does this differ from what is available in XSPEC/Sherpa?
This is explained well for those initiated with Bayes factor model comparison, but a link to that part of the docs would be useful to make the point
This claim is made here and here as well as the normal use of proper Poisson likelihoods. What specific features makes BXA shine in comparison? Can links be provided as well as comparative examples?
What is meant by this statement? As stated above, can examples be linked/ shown that validate this?
I'm assuming it is because there is a stopping criteria in nested sampling, but is this meant to inform the user that they do not need to access the correctness of their posterior?
I suppose this could be answered with the previous question.
In general, it could be important to fully separate what is a feature or strength of BXA vs what is inherited from the package it relies on / compliments.
The text was updated successfully, but these errors were encountered: