Closed rdinnager closed 1 year ago
A temporary solution now is to run slim_run()
with progress = FALSE
(which is now the default), which forces processing of output at the end of the simulation. this seems to solve the problem suggesting that the problem is with how data is processed on the fly during the simulation. It appears some part of the output slips through the cracks, which you can see by examining the slimr_result
objects output
slot, which contains the sections that were missed. It still only happens occasionally. I should recommend for production work, users only use progress = FALSE
to make sure this does not happen. I've decided to resolve the issue with an overhaul of the output processing system which I have been planning for awhile. SHould get to that soon.
Workaround will do until enhancement in #66 is implemented.
slim_extract_genome()
occasionally 'loses' some data being passed from SLiM. Usually a small amount of data but can break some examples. This is probably caused by either a change in how SLiM outputs data or possibly a change inreadr
. This is a high priority to fix because some manuscript examples use this.