You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just flagging something that could be unexpected behavior: I've recently run an importance sampler, using an input chain that was run with nautilus. One way the nautilus chains differ from things run with other samplers I've worked with, is that it has a log_weight column instead of just weight.
Usually when running the importance sampler on a nested sampler chain results in an output file which has one column called old_weight (the weight from the original chain), and one called weight, for the importance sampling weight from the ratio of the two posteriors in question.
For the run on this nautilus chain, the last handful of column labels are log_weight prio r old_post log_weight post. That is to say, there is no old_weight, there is just two copies of log_weight. It looks like the data in the columns are probably what they're supposed to be, so I think this is just an issue with the labels.
The text was updated successfully, but these errors were encountered:
Just flagging something that could be unexpected behavior: I've recently run an importance sampler, using an input chain that was run with nautilus. One way the nautilus chains differ from things run with other samplers I've worked with, is that it has a
log_weight
column instead of justweight
.Usually when running the importance sampler on a nested sampler chain results in an output file which has one column called
old_weight
(the weight from the original chain), and one calledweight
, for the importance sampling weight from the ratio of the two posteriors in question.For the run on this nautilus chain, the last handful of column labels are
log_weight prio r old_post log_weight post
. That is to say, there is noold_weight
, there is just two copies oflog_weight
. It looks like the data in the columns are probably what they're supposed to be, so I think this is just an issue with the labels.The text was updated successfully, but these errors were encountered: