|
Boost : |
Subject: Re: [boost] Is there interest in a Simulation library?
From: Klaim - Joël Lamotte (mjklaim_at_[hidden])
Date: 2013-09-26 18:27:24
On Fri, Sep 27, 2013 at 12:09 AM, David Bellot <david.bellot_at_[hidden]>wrote:
> Can you tell us more about what you mean by Simulation library ? It's a
> broad concept.
>
My expectation is that:
1. you have some data representing the state of the simulation;
2. you have a set of rules that have to be applied on each cycle of the
simulation; (each cycle might correspond to a time frame but it's important
that it's "fixed");
3. you have some set of events that needs to be triggered (maybe by the
rules?);
4. the library take all that in, then provide a function to iterate to the
next cycle;
5. each cycle is double buffered (or something similar) that is:
a. the library first keep a read-only copy of the state of the last
cycle and the state of the next cycle;
b. the rules are applied using the read-only last cycle state to modify
the state of the next cycle;
c. meanwhile, events are collected;
d. once the cycle is complete, the events are dispatched or provided as
a set to the user code;
e. the events will also be used by the rules on the next cycle, which
makes it a simulation;
If it's not what the library is about, then I'll need some clarifications.
:)
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk