There are a few parts of the logic in simFoward that must be refreshed if a change is made. At present, we instantiate the entire community first and then call the relevant methods. In adding some exception handling, I have realised that this could become overlooked -- particularly if we were to make the simulation a module and that lead to changes in use.
This is a natural place to use an observer to refresh affected objects after any change. The refresh is not terribly costly in comparison to the ultimate long running tasks of generating many read pairs.
There are a few parts of the logic in simFoward that must be refreshed if a change is made. At present, we instantiate the entire community first and then call the relevant methods. In adding some exception handling, I have realised that this could become overlooked -- particularly if we were to make the simulation a module and that lead to changes in use.
This is a natural place to use an observer to refresh affected objects after any change. The refresh is not terribly costly in comparison to the ultimate long running tasks of generating many read pairs.