On 04/22/2015 09:46 PM, Chris Angelico wrote:
On Thu, Apr 23, 2015 at 11:37 AM, Dave Angel <da...@davea.name> wrote:
On 04/22/2015 09:30 PM, Cem Karan wrote:
On Apr 22, 2015, at 8:53 AM, Peter Otten <__pete...@web.de> wrote:
Another slightly more involved idea:
Make the events pickleable, and save the simulator only for every 100th
(for
example) event. To restore the 7531th state load pickle 7500 and apply
events 7501 to 7531.
I was hoping to avoid doing this as I lose information. BUT, its likely
that this will be the best approach regardless of what other methods I use;
there is just too much data.
Why would that lose any information???
It loses information if event processing isn't perfectly deterministic.
Quite right. But I hadn't seen anything in this thread to imply that.
I used an approach like that on the Game of Life, in 1976. I saved
every 10th or so state, and was able to run the simulation backwards by
going forward from the previous saved state. In this case, the analogue
of the "event" is determined from the previous state. But it's quite
similar, and quite deterministic.
--
DaveA
--
https://mail.python.org/mailman/listinfo/python-list
