Thank you for the explanation Sean.
Going back to Ernesto's question: what are the implications of
extending MasonGeometry regarding Serialisation?
On 23 March 2016 at 16:55, Sean Luke <[log in to unmask]> wrote:
> If your model is entirely serializable, then you can checkpoint it. This means you can save out snapshots of the model as it's running to revisit later; you can also save out a model running (say) on a back-end server machine, move it forward to your laptop, and examine it under visualization, save it out AGAIN, and move it back on the server to keep running, etc.
> I would strongly suggest you try to make your model serializable. Generally this means you should avoid attaching to your agents any GUI or visualization stuff (or having them subclass from the same), and similarly for any objects in your SimState. And inner classes too! Nonserializable GUI stuff should instead go into your GUIState object.
> If you do NOT do this, your model will still run just fine under the GUI. But you won't be able to checkpoint/save it out or migrate it, just run it.