I tested out the -Strace option today and noticed that the code gives an exception under a very specific situation. First, I simulated two trajectories using the -oTrace option starting selection in two scenarios:
If I then feed the trajectories generated in Scenario 1 to MSMS using the -Strace option, I get an exception. If I feed a trajectory generated in Scenario 2, I do not get an exception. If I truncate the trajectory generated in Scenario 1 to start at 2E-4 generations ago, then I am able to run MSMS. I tried this with different selection coefficients (s=0.001, s=0.01) and noticed the same behavior, so this seems to be an issue to the generations rather than selection coefficient.
This is the command I use to generate the trajectory for Scenario 1.
Hi Greg
I tested out the -Strace option today and noticed that the code gives an exception under a very specific situation. First, I simulated two trajectories using the -oTrace option starting selection in two scenarios:
Scenario 1: selection starts 0.00025 generations ago Scenario 2: selection starts 0.0002 generations
If I then feed the trajectories generated in Scenario 1 to MSMS using the -Strace option, I get an exception. If I feed a trajectory generated in Scenario 2, I do not get an exception. If I truncate the trajectory generated in Scenario 1 to start at 2E-4 generations ago, then I am able to run MSMS. I tried this with different selection coefficients (s=0.001, s=0.01) and noticed the same behavior, so this seems to be an issue to the generations rather than selection coefficient.
This is the command I use to generate the trajectory for Scenario 1.
./msms/bin/msms 145 1 -N 1000000 -t 400 -Sp 0.5 -r 2000 100000 -SAA 4000 -SaA 2000 -SI 0.00025 1 0.0000005 -SFC -oTrace