carolynzy

Any luck you there? I have the same problem here. It seems that the data structure is the problem. Because with the same environment and parameters, with another slightly different...

@maxbiostat Thanks for the hint! I have just tried to work around with the priors. So it seems the priors I used were not optimized. I changed the "alpha" and...

@maxbiostat the problem solved after changing the priors.

@maxbiostat I have a question, is this problem a computational one? Or it might a statistical one. Because I think this problem is caused by the constante rejection of the...

@maxbiostat Your suggestion improved the stuck problem. Now it could run through millions of interations withou stuck. But the coverge takes really a long time. It's still running at the...

Hi, @maxbiostat , while I'm still running on your suggestions, I found something strange. I uploaded the log file here, [mdr_filterinv_testMaxbiostat_skygrid_cutoff70_2.72e-5.log](https://github.com/beast-dev/beast-mcmc/files/3255185/mdr_filterinv_testMaxbiostat_skygrid_cutoff70_2.72e-5.log) When opening it in Trace, you could notice the...

Thanks! Your post saved me a lot time!

I think this parameter is disabled, as said in the instruction. So it doesn't matter what value you use just keep a position for it will be fine.

I noticed the same behavior in my data. The start position from other SV callers is one digit larger than the referred one in SURVIVOR. So if the start position...

I had the same issue using whamg. I'm processing paired-end samples. whamg used to be working on this sample, the only change I made was using bbduk.sh to trim low...