I think I discovered a bug trying to bootstrap a program I wrote involving the bayesmh command. Instead of 1000 runs with different subsamples, I got 1000 copies of the same result. To confirm, I wrote a toy program that doesn't use bayesmh, which works as expected, then added an irrelevant bayesmh call to it, which then produced the 1000 copies problem.
I suspect there is a macro keeping track of simulation runs shared by both procedures that gets overwritten.
I suspect there is a macro keeping track of simulation runs shared by both procedures that gets overwritten.

Comment