Skip to content
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

Post-processing with a different volume ratio #19

Open
MichelleLochner opened this issue Mar 28, 2017 · 3 comments
Open

Post-processing with a different volume ratio #19

MichelleLochner opened this issue Mar 28, 2017 · 3 comments

Comments

@MichelleLochner
Copy link

In Appendix A of the code paper, you mention you can change the level compression ratio with the "-c" option. My question is does, something corresponding need to change when post processing? Is there an explanation somewhere that I missed of the parameters in the post-processing function, as they have a big difference on the number of samples produced...

Thank you!

@eggplantbren
Copy link
Owner

You shouldn't need to do anything different with postprocess if you've used -c. Are you able to post the output plots? That might show what's happening.

@MichelleLochner
Copy link
Author

Ok cool. The output plots look absolutely fine (posterior weights peaking nicely, levels being explored well etc.). I just wanted to check the output posterior samples are representative of reality. The only problem I face sometimes (in high dimensions) is that too few samples are produced, and running the chain longer doesn't actually seem to help (the effective sample size remains the same). There's a few options in post_process like the helpful "moreSamples" which seems to do the trick... But I just wanted to check if there was an implicit volume ratio assumption in post_process that I needed to change.

@eggplantbren
Copy link
Owner

The only problem I face sometimes (in high dimensions) is that too few samples are produced, and running the chain longer doesn't actually seem to help (the effective sample size remains the same).

This shouldn't be the case, but everything else you've said sounds good. I am puzzled.

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