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

Cross-model proposals are problematic #5

Open
pgrinaway opened this issue Apr 27, 2015 · 4 comments
Open

Cross-model proposals are problematic #5

pgrinaway opened this issue Apr 27, 2015 · 4 comments

Comments

@pgrinaway
Copy link
Member

I've noticed that certain cross-model proposals (specifically OBC1 and OBC2 to HCT) are very bad, and almost always result in rejection. I figured I'd post this to have some discussion of possible remedies.

@pgrinaway pgrinaway mentioned this issue Apr 27, 2015
@jchodera
Copy link
Member

jchodera commented Apr 27, 2015 via email

@jchodera
Copy link
Member

HCT is also a very old model, and might simply be a poor quality model. Do we have a way to distinguish between poor mixing and highly disfavored models?

@pgrinaway
Copy link
Member Author

Can you compute an empirical transition matrix? If you write the model
every iteration, you can compute P(model at t+1 is j | model at t was i) =
T_{ij}.

Sounds good!

(1) either use a parameterization
of variables that makes the GB functions more similar to each other for the
same value of parameters

I agree that this could be the simplest way. Given that the functional forms are not that complex, I don't think that a deterministic transformation would have a particularly hairy Jacobian, right?

(2) use proposal distributions to sample new
parameters for the new model that attempt to make the functions more
similar for the new proposal.

I'll look into this as well.

HCT is also a very old model, and might simply be a poor quality model. Do we have a way to distinguish between poor mixing and highly disfavored models?

Good point! I was saying that the moves are difficult because it seemed that a proposed transition to HCT resulted in NaNs, but I agree that it is important to distinguish between the two. I ran a few chains last night, and I'll take a look at them today to see how it went.

@jchodera
Copy link
Member

jchodera commented Apr 27, 2015 via email

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